25.0214 (Gdrive)

• MERN. Frontend, backend, and DB. The core functional parts. Note: My focus is on API-docs and AI (LLMs). But the basics of MERN (and other "stacks") are important to understand when creating API-docs (and I need examples stacks anyway for my demos).
• API (adding to the backend). Same note as for MERN: I need API demos, so they are an integral part of the AI API sandbox.
• API doc sites. API doc sites can get complex with endpoint testing boxes, etc.
• Text doc sites. Setting up the "scaffolding" for the docs (the various web sites, etc).

Use Copilot as much as possible.

The following diagram (of the MAIN) deployment) shows the ecosystem (AI agents, etc to be added).

My initial thinking is there will be 9 possible stages of building the infrastructure, API, and API docs:

• 1 Backend
• 2 DB
• 3 REST API
• 4 Frontend (integrates the REST API)
• 5 Swagger
• 6 GraphQL backend
• 7 GraphQL UI
• 8 API docs (for complete REST API descriptions (what swagger does not cover) or for GraphQL)
• 9 AIEO (AI engine optimization)

---

25.0126 add this somewhere

• start with Dave etc demo, or from vercel
• git backups
• docs all stuff, docxs and wiki
• mix and match
• top down
• avoid coding, use AI wherever possible

The goal is to create a set of portfolio deployments using AI wherever possible. Frontends that connect to multiple backends that connect to multiple DBs. With APIs and API-docs.

The goal is to create a set of portfolio deployments using AI wherever possible. Frontends that connect to multiple backends that connect to multiple DBs. With APIs and API-docs.