Organize documentation files and sections

.dockerignore

@@ -10,6 +10,6 @@ node_modules
 coverage
 
 # Ignore documentation related files
-additionaldocs
+docs
 images
 *.md

.kiro/steering/documentation.md

@@ -25,7 +25,7 @@
 ### Documentation Hierarchy
 
 - **README.md**: Project overview and quick start
-- **additionaldocs/**: Detailed guides organized by user journey
+- **docs/**: Detailed guides organized by user journey
   - `getting-started/`: Installation, first connection, basic usage
   - `user-guide/`: Feature documentation for end users
   - `deployment/`: Production deployment guides
@@ -62,7 +62,7 @@
 
 ```
 README.md                           # Project overview and quick start
-additionaldocs/
+docs/
 ├── getting-started/
 │   ├── installation.md            # Local and Docker setup
 │   ├── first-connection.md        # Connecting to your first database
@@ -92,6 +92,44 @@ additionaldocs/
 - Use descriptive names that match user tasks: `first-connection.md`
 - Group related content in folders by user journey
 
+### Folder README Files
+
+Each documentation folder should include a `README.md` file that serves as a
+table of contents for that folder:
+
+- **Purpose**: Explain what the folder contains and who it's for
+- **Summary**: Briefly describe the folder's purpose and content
+- **File Listing**: List all files in the folder with brief descriptions
+- **Reading Order**: Suggest the recommended order for reading files
+- **Prerequisites**: Note any required knowledge or setup before starting
+- **Navigation**: Link to parent folder and related sections
+
+Example folder README structure:
+
+```markdown
+# Getting Started
+
+This section helps new users install and configure Graph Explorer for the first
+time.
+
+## Files in this section
+
+1. [Installation](installation.md) - Local and Docker setup options
+2. [First Connection](first-connection.md) - Connect to your first database
+3. [Basic Usage](basic-usage.md) - Essential features walkthrough
+
+## Prerequisites
+
+- Basic familiarity with graph databases
+- Access to a graph database endpoint
+- Docker or Node.js >=24.4.0 installed
+
+## Next Steps
+
+After completing this section, see the [User Guide](../user-guide/) for detailed
+feature documentation.
+```
+
 ## Formatting Standards
 
 ### Code Examples

.kiro/steering/structure.md

@@ -14,7 +14,7 @@ graph-explorer/
 │   ├── graph-explorer/           # React frontend application
 │   ├── graph-explorer-proxy-server/  # Express.js backend server
 │   └── shared/                   # Shared types and utilities
-├── additionaldocs/               # Documentation
+├── docs/                        # Documentation
 ├── samples/                      # Example configurations
 └── [root config files]           # Workspace-level configuration
 ```

Changelog.md

@@ -137,7 +137,7 @@ editor with Neptune Analytics for the first time.
 
 As before, if you are a Neptune user concerned about data integrity, check out
 the
-[instructions on configuring IAM permissions to restrict mutations](./README.md#permissions),
+[instructions on configuring IAM permissions to restrict mutations](./docs/user-guide/security.md#permissions),
 ensuring that users can enforce read-only operations.
 
 ### New features & major changes
@@ -163,15 +163,15 @@ ensuring that users can enforce read-only operations.
 
 Graph Explorer v2.0 marks a significant milestone with the introduction of the
 new
-[query editor for Gremlin connections](./additionaldocs/features/README.md#query-search).
+[query editor for Gremlin connections](./docs/user-guide/graph-explorer.md#query-search).
 This powerful feature allows users to enter any valid Gremlin query and
 visualize the returned nodes, edges, and scalar values directly from the
 database. You can review the results in the sidebar and choose to add all nodes
 & edges to the graph or add results individually.
 
 For Neptune users concerned about data integrity, [the README](./README.md) now
 includes
-[instructions on configuring IAM permissions to restrict mutations](./README.md#permissions),
+[instructions on configuring IAM permissions to restrict mutations](./docs/user-guide/security.md#permissions),
 ensuring users can enforce read-only operations.
 
 The release also changes the default strategy for representing node & edge
@@ -662,11 +662,11 @@ a more pleasant experience, especially for users with larger databases.
 - **Improved** diagnostic logging in Neptune Notebooks by adding CloudWatch logs
   ([#517](https://github.com/aws/graph-explorer/pull/517))
   - Check out the example
-    [lifecycle script](additionaldocs/sagemaker/install-graph-explorer-lc.sh)
+    [lifecycle script](docs/deployment/aws-sagemaker/install-graph-explorer-lc.sh)
     and IAM policies for
-    [Neptune](additionaldocs/sagemaker/graph-explorer-neptune-db-policy.json)
+    [Neptune](docs/deployment/aws-sagemaker/graph-explorer-neptune-db-policy.json)
     and
-    [Neptune Analytics](additionaldocs/sagemaker/graph-explorer-neptune-analytics-policy.json)
+    [Neptune Analytics](docs/deployment/aws-sagemaker/graph-explorer-neptune-analytics-policy.json)
 
 **Bug Fixes and Minor Changes**