Add consistent contact footer to all markdown files

[Copilot]

Standardizes contact information across the knowledge base by adding a uniform footer to all markdown files, enabling users to report corrections and access support.

Changes

• Created canonical contact page (content/includes/contact.md)

  • Centralized contact info: email, website, team name
  • Instructions for submitting corrections

• Created layout guidelines (content/site-layout-guidelines.md)

  • Template for consistent page structure
  • Footer format specification

• Added footer to 424 markdown files across all directories

  ---
  Contact: Cosmos Knowledge Base — SolveForce  
  Email: contact@solveforce.com  
  For corrections or suggestions, please open an issue in the repository.
  ---

• Updated site-map.md to reference new files

Structure

content/
├── includes/
│   └── contact.md          # New: canonical contact page
├── site-layout-guidelines.md  # New: layout template
└── site-map.md             # Updated: added new file references

All existing content preserved. Footer appended only.

Original prompt

Ensure all pages in the content directory have consistent contact information and layout to match the site's templates. Create a canonical contact page at content/includes/contact.md with the following content:

Contact

Cosmos Knowledge Base — SolveForce

• Email: contact@solveforce.com
• Website: https://cosmos.solveforce.com
• Team: SolveForce Knowledge Team

If you have corrections, additions, or issues with any page, please open an issue in the repository or email the contact above with the page path.

Create site layout guidelines at content/site-layout-guidelines.md with the following content:

Site Layout Guidelines (Canonical Template)

Use this minimal per-page footer/contact block at the end of every Markdown file to achieve consistent layout across the site. Copy the "Site footer" block as-is to the bottom of each content page.

Site header (per-page top-of-file):

• Keep page title as the first top-level header (# Title)
• Optional: one short description paragraph below the title

Site content:

• Keep sections small and focused (one concept per file)
• Use relative links to other pages using the existing lowercase, hyphen-separated names

Site footer (place at the bottom of every page):

---
Contact: Cosmos Knowledge Base — SolveForce  
Email: contact@solveforce.com  
For corrections or suggestions, please open an issue in the repository.
---

Notes:

• Replace contact@solveforce.com with your official contact address if different.
• If you prefer a single central contact page, link to content/includes/contact.md from each page with a short footer line, e.g., "See Contact" — adjust relative path based on folder depth.
• For glossary entries (in content/glossary/), place the footer after the main definition content.

Append the following footer block to the end of every Markdown (.md) file in the content/ directory and its subdirectories (recursively), ensuring the layout matches other templates:

---

Contact: Cosmos Knowledge Base — SolveForce
Email: contact@solveforce.com
For corrections or suggestions, please open an issue in the repository.

Do not modify existing content, only add the footer if not already present. Ensure all files from the main GitHub repository are included and displayed correctly by verifying the site-map.md reflects the current structure.

This pull request was created as a result of the following prompt from Copilot chat.

Ensure all pages in the content directory have consistent contact information and layout to match the site's templates. Create a canonical contact page at content/includes/contact.md with the following content:

Contact

Cosmos Knowledge Base — SolveForce

• Email: contact@solveforce.com
• Website: https://cosmos.solveforce.com
• Team: SolveForce Knowledge Team

If you have corrections, additions, or issues with any page, please open an issue in the repository or email the contact above with the page path.

Create site layout guidelines at content/site-layout-guidelines.md with the following content:

Site Layout Guidelines (Canonical Template)

Use this minimal per-page footer/contact block at the end of every Markdown file to achieve consistent layout across the site. Copy the "Site footer" block as-is to the bottom of each content page.

Site header (per-page top-of-file):

• Keep page title as the first top-level header (# Title)
• Optional: one short description paragraph below the title

Site content:

• Keep sections small and focused (one concept per file)
• Use relative links to other pages using the existing lowercase, hyphen-separated names

Site footer (place at the bottom of every page):

---
Contact: Cosmos Knowledge Base — SolveForce  
Email: contact@solveforce.com  
For corrections or suggestions, please open an issue in the repository.
---

Notes:

• Replace contact@solveforce.com with your official contact address if different.
• If you prefer a single central contact page, link to content/includes/contact.md from each page with a short footer line, e.g., "See Contact" — adjust relative path based on folder depth.
• For glossary entries (in content/glossary/), place the footer after the main definition content.

Append the following footer block to the end of every Markdown (.md) file in the content/ directory and its subdirectories (recursively), ensuring the layout matches other templates:

---

Contact: Cosmos Knowledge Base — SolveForce
Email: contact@solveforce.com
For corrections or suggestions, please open an issue in the repository.

Do not modify existing content, only add the footer if not already present. Ensure all files from the main GitHub repository are included and displayed correctly by verifying the site-map.md reflects the current structure.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.