- Update sidebar navigation links in astro.config.mjs
- Remove core-philosophy.md, deployment-guides.md, and getting-started.md files
- Add new navigation items for introduction, local setup, and deployment guides
- Comment out core philosophy item in sidebar navigation

- Create new API reference index page with general information
- Add sections for base URL, authentication, and standard responses
- Include cards for authentication and data access endpoint guides
- Use consistent formatting and AstroJS components for layout

- Added a new card on the API server homepage
- Card links to the API reference section
- Provides a complete reference for all API endpoints and data models

- Detail endpoints for sign-in, sign-up, and session management
- Include request/response formats and error handling
- Cover anonymous sign-in, current user retrieval, sign-out, and account deletion

- Describe the generic data access endpoint for CRUD operations
- List supported models and endpoint usage
- Detail query parameters for filtering, sorting, and pagination
- Provide examples for different request methods (GET, POST, PUT, DELETE)
- Explain success and error responses for each operation

- Create new documentation page for core data models used across the API
- Describe common fields shared by all primary data models
- Provide detailed information for User, Headline, Topic, Source, and Country models

- Introduce standardized error response format
- Define common error codes and their descriptions
- Specify HTTP status codes associated with each error code

- Add Error Handling to Features section
- Add Core Data Models to Advanced section
- Add API Reference section with Overview, Authentication, and Data Access

- Remove core data models entry from advanced section in sidebar
- Add core data models entry to api reference section in sidebar
- Rename file path from advanced to api-reference for core-models.mdx

- Create new markdown file for configuring the .env file
- Explain purpose and setup of environment variables for API server
- Detail required variables: DATABASE_URL, JWT_SECRET_KEY, SENDGRID_API_KEY, DEFAULT_SENDER_EMAIL, OTP_TEMPLATE_ID
- Include instructions for generating and obtaining API keys
- Cover

- Create new markdown file for MongoDB configuration instructions
- Include step-by-step guide for setting up MongoDB using Docker
- Explain how to update .env file for API server connection
- Provide helpful tips and command explanations

- Explain how to set up Cross-Origin Resource Sharing for the API server
- Describe default CORS configuration for development
- Provide instructions for configuring CORS in production
- Emphasize the importance of using a specific origin instead of a wildcard
- Include troubleshooting steps for CORS errors

- Create new markdown file explaining how to replace default SendGrid email client
- Detail process for creating custom email client implementation
- Provide example of logging-only email client for development/testing
- Explain how to integrate custom email client into dependency injection setup

- Create new documentation page for understanding database seeding
- Describe how the API server automatically seeds the database on startup
- Explain the role of AppDependencies.init() and DatabaseSeedingService
- Detail the process of ensuring indexes and upserting data
- Define key concepts like 'upsert' and idempotency
- Mention the use of fixture data from the core package

- Add a new step in the local setup guide for automatic database seeding
- Explain that the seeding process is idempotent
- Include a link to the "Understand Database Seeding" guide for more details

... reduced prescriptiveness
- Outline two main Docker deployment strategies: pre-built image and deploying from source
- Refocus on essential steps and link to official documentation for hosting providers
- Improve flow and clarity of the guide
- Move CORS configuration to a separate step with a link to a how-to guide

- Add a new card to the CardGrid component
- The card links to the API Server environment variables configuration guide
- This change highlights the availability of practical guides for specific setup tasks

- Explain how the API server converts anonymous guest users into permanent accounts
- Describe the guest user flow and data accumulation process
- Detail the conversion process for creating permanent accounts
- Highlight the seamless transition of user data during account conversion

- Introduce the API server's transactional email capabilities
- Explain core components: EmailClient, EmailSendGrid, EmailRepository, and AuthService
- Describe the decoupled architecture and its benefits
- Include an aside tip about implementing alternative email clients

- Create new page to showcase key features of the API server
- Include CardGrid component to display features visually
- Add descriptions and links for each feature: Authentication, User Data Sync, Email Service, Role-Based Access Control, and Remote Configuration

- Add step for setting up local database using Docker
- Clarify environment variables configuration process
- Update step numbers accordingly
- Improve overall clarity and guidance for new developers

...on and middleware
- Create new markdown file for advanced topics
- Add cards for dependency injection and middleware
- Include descriptions and links for further reading

- Create new index page for API server how-to guides
- Add CardGrid component to display various how-to topics
- Include guides on environment variables, MongoDB setup, CORS configuration, custom email client implementation, and database seeding

- Add new menu items under 'Features', 'How-To Guides', and 'Advanced' sections
- Introduce new sections with collapsed menus for better organization
- Include overview pages for each main section
- Add new how-to guides for various configuration and implementation topics

- Renamed file from 'advanced' to 'architecture' folder
- This change reflects the better categorization of the content

We're changing the folder name to better reflect the content and avoid confusion with the advanced docs, which will be a separate section.
Closes NEXT-1122

- Renamed middleware.mdx from advanced to architecture folder

- Remove 'understand-database-seeding.mdx' file
- Add 'data-seeding-and-fixtures.mdx' file with expanded content
- Refactor content structure to better fit architectural documentation

...registry
- Introduce the concept of a generic data endpoint to reduce boilerplate code
- Explain the implementation using a model registry
- Describe the advantages of this architectural pattern
- Include examples of usage and reference to source code

- Rename 'Advanced' section to 'Architecture'
- Add new items under Architecture: Data Seeding & Fixtures, Generic Data Endpoint
- Rename 'API Reference' to 'Reference'
- Update existing links and labels for consistency

- Move authentication page from api-reference to reference folder
- Move core-models page from api-reference to reference folder
- Move data-access page from api-reference to reference folder
- Move index page from api-reference to reference folder

@gemini-code-assist gemini-code-assist bot left a comment

@gemini-code-assist gemini-code-assist bot left a comment