[WIP] Update project structure to improve documentation organization

[Copilot]

• Create docs/README.md with current README content
• Create docs/ADMIN_SETUP.md with current ADMIN_SETUP.md content
• Update root README.md with brief overview and navigation links to both docs files
• Fix internal link in docs/ADMIN_SETUP.md to point to docs/README.md

Original prompt

Organize the project documentation by:

1. Creating a /docs folder containing:

   • docs/README.md - move the current README content here
   • docs/ADMIN_SETUP.md - move the current ADMIN_SETUP.md content here

2. Update the main README.md in the root to:

   • Keep a brief overview of the project
   • Add a prominent documentation navigation section with links to both guides
   • Link to docs/README.md for the main setup guide
   • Link to docs/ADMIN_SETUP.md for admin configuration
   • Make the documentation easily discoverable

This will make the README and Admin Setup guide visible together in the docs folder while maintaining clear navigation from the root README.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: how can i make so the readme can be seen next tothe admin setupmd file

Assistant: I'll help you make the README visible next to the admin-setup.md file. First, let me explore the repository structure to understand the current layout.

Assistant: I can see your repository has both README.md and ADMIN_SETUP.md files in the root. To display the README next to the ADMIN_SETUP.md file on GitHub, you have a few options:

Option 1: Create a /docs folder (Recommended)

Move both files into a docs subdirectory so they're organized together:

• docs/README.md
• docs/ADMIN_SETUP.md

GitHub will render docs/README.md as the folder overview when viewing the docs directory.

Option 2: Link them in the main README

Edit your main README.md to include a prominent link/section pointing to ADMIN_SETUP.md:

# Portfolio Template

[Quick Start Guide](./README.md) | [Admin Setup](./ADMIN_SETUP.md)

... rest of content ...

Option 3: Use GitHub Wiki or GitHub Pages

Create a wiki page or use GitHub Pages to display both documents side-by-side in a more integrated way.

Option 4: Create a Table of Contents

Add a navigation section at the top of your main README that clearly links to related documentation:

## Documentation
- [Setup Instructions](#setup)
- [Admin Guide](./ADMIN_SETUP.md)

Which approach would work best for your use case? The most common solution is Option 1 (organizing in a /docs folder) or Option 2 (adding clear links in the README).

User: Would like 1 and 2

Assistant: I'll help you set up both options. Let me create a pull request that:

1. Creates a /docs folder with both README.md and ADMIN_SETUP.md
2. Updates the main README.md with links to the documentation

Assistant: Perfect! I've initiated the process to implement both options for you:

What will happen:

1. ✅ Create a /docs folder in your repository
2. ✅ Move README.md → docs/README.md (full setup guide)
3. ✅ Move ADMIN_SETUP.md → docs/ADMIN_SETUP.md (admin configuration)
4. ✅ Create a new root README.md with:
   • A brief project overview
   • A Documentation section with clear links to both guides
   • Easy navigation so viewers can quickly access either guide

This way, both files will be visible together in the docs folder, and the main README will have prominent links directing people to each document. The user acceptance dialog is active—please confirm or deny the proposed changes to proceed.

This pull request was created from Copilot chat.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.