Merge remote-tracking branch 'origin/v4' into v4

content/Glossary/Technical/ACL.md

@@ -6,8 +6,6 @@ There are several types of ACLs, with the most common being **Discretionary ACLs
 
 ACLs are widely used in file systems to secure files and directories, as well as in network devices such as routers and firewalls to control the flow of data and protect against unauthorized access. By using ACLs, administrators can set fine-grained permissions, ensuring that only authorized users can access specific resources, and maintaining the confidentiality and integrity of the system.
 
-However, managing ACLs can become complex in large environments with numerous users and resources. If not properly configured, ACLs can also lead to security risks, such as overly permissive access or conflicts in permissions. To mitigate these challenges, it’s important to regularly audit ACL configurations and ensure that permissions are set in line with the principle of least privilege.
-
-Overall, ACLs are a powerful tool for securing resources and enforcing access control policies, but they must be carefully managed to maintain system security and efficiency.
+Managing ACLs can become complex in large environments with numerous users and resources. If not properly configured, ACLs can also lead to security risks, such as overly permissive access or conflicts in permissions. To mitigate these challenges, it’s important to regularly audit ACL configurations and ensure that permissions are set in line with the principle of least privilege.
 
 Learn more about ACLs [[https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html|here]].

content/Glossary/Technical/Batteries Inclusion.md

@@ -1,4 +1,4 @@
-The term **"batteries-included"** is commonly used in the software and technology world to describe a philosophy or approach where a tool, framework, or platform comes with a comprehensive set of built-in features and components. This means that users do not need to install or configure additional modules, plugins, or dependencies to get started. The core functionality required to use the software is already included, making it easier for users to quickly begin using the tool without having to worry about additional setup or external dependencies.
+**"Batteries-included"** is commonly used in the software and technology world to describe a philosophy or approach where a tool, framework, or platform comes with a comprehensive set of built-in features and components. This means that users do not need to install or configure additional modules, plugins, or dependencies to get started. The core functionality required to use the software is already included, making it easier for users to quickly begin using the tool without having to worry about additional setup or external dependencies.
 
 The **batteries-included** approach aims to provide a seamless, user-friendly experience by bundling together all essential features that are likely to be needed in common use cases. This contrasts with other approaches, where the software may be more minimalistic, and users are required to install and configure additional packages or libraries to achieve the desired functionality.
 

content/Glossary/Technical/Form Fields.md

@@ -0,0 +1 @@
+#WIP 

content/Glossary/Technical/Queues.md

@@ -0,0 +1 @@
+#WIP 

content/Glossary/Technical/SSE.md

@@ -0,0 +1 @@
+#WIP 

content/Glossary/Technical/Soft Deletion.md

@@ -0,0 +1,7 @@
+Soft deletion is a technique used in databases where data is marked as deleted but not actually removed from the system. Instead of permanently deleting a record, a "deleted" flag or timestamp is added to it, indicating that the record is no longer active or in use. This allows the data to be retained for historical purposes or potential recovery, while preventing it from appearing in active queries or being accessed by users. Soft deletion provides a way to recover deleted data if necessary, offering an additional layer of protection and flexibility in managing records.
+
+Soft deletion plays a crucial role in optimizing database performance and management. By marking records as deleted rather than physically removing them, it helps reduce the need for frequent tree rebalances in databases, particularly in systems that use index-based data structures like B-trees. When records are deleted, the tree structure may need to be reorganized to maintain balance, which can be resource-intensive. With soft deletion, this rebalancing is avoided, as the records remain in place, only hidden from active queries.
+
+Soft deletion can ease the workload on database engines. Since the data isn't actually removed, the database doesn't need to perform expensive operations to physically delete and reclaim storage space. This allows the system to handle more transactions efficiently, without the overhead of constantly adjusting storage or re-indexing after deletions.
+
+From an audit perspective, soft deletion is particularly valuable. It provides a clear, traceable record of what data was marked as deleted and when, without actually losing the information. This is essential for maintaining data integrity and compliance, especially in systems that require audit trails for legal or regulatory purposes. By keeping deleted records accessible, soft deletion enables administrators to review and recover data if necessary, supporting transparency and accountability in data management.

content/Glossary/Technical/Websockets.md

@@ -0,0 +1 @@
+#WIP 

content/index.md

@@ -2,6 +2,9 @@
 title: Welcome to Project Documentation !
 ---
 Welcome to the **API Documentation Repository** for all projects under the Programming Society (PSoc) at IIIT Bhubaneswar. This page serves as a centralized hub for maintaining and accessing Requirement Docs, API Documentation,Decision explanations for various projects developed by the society members.
+
+![[psoc.png]]
+
 ## Purpose
 The primary objective of this repository is to:
 - Provide a well-organized and user-friendly repository for all API-related documentation across PSoc projects.