VZ update contributors to organization

[vickimzhang]

Summary by CodeRabbit

• Documentation
  • Updated the documentation homepage footer to enhance the Developers section presentation and clarity. The previous list of multiple named contributors has been streamlined and consolidated into a single dedicated maintainer entry, now accompanied by an associated organizational link to provide clear attribution of project leadership.

[coderabbitai]

Walkthrough

The documentation homepage footer updates the Developers section to replace a list of named contributors (Katie Birchard, Leonardo Frid, Colin Daniel) with a single linked ApexRMS author/maintainer entry.

Changes

Documentation Footer Update

Layer / File(s)	Summary
Developers Section Footer docs/index.md	The Developers section footer content is changed from a list of individual author names to a single linked ApexRMS maintainer entry.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'VZ update contributors to organization' directly describes the main change: updating the documentation footer to replace individual contributors with an organization (ApexRMS) reference.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch vz-update-contributors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

docs/index.md (1)

58-59: Consider maintaining individual contributor attribution.

While consolidating to organisational attribution is appropriate for maintainership, you may want to ensure individual contributors are still credited elsewhere in the repository (e.g., a CONTRIBUTORS.md or AUTHORS.md file). This aligns with open source best practices for recognising contributions.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/index.md` around lines 58 - 59, The docs currently show organizational
attribution "ApexRMS (Author, maintainer)"; add or reference an individual
contributor list to preserve credit by creating a CONTRIBUTORS.md or AUTHORS.md
file and updating docs/index.md (or the project README) to link to it and
optionally add a short "Contributors" section near the attribution line; ensure
the new file lists individual names and roles (or points to contribution
guidelines) and include a link from the existing "ApexRMS (Author, maintainer)"
attribution to that contributors file so maintainership stays organizational
while individuals remain credited.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@docs/index.md`:
- Around line 58-59: The docs currently show organizational attribution "ApexRMS
(Author, maintainer)"; add or reference an individual contributor list to
preserve credit by creating a CONTRIBUTORS.md or AUTHORS.md file and updating
docs/index.md (or the project README) to link to it and optionally add a short
"Contributors" section near the attribution line; ensure the new file lists
individual names and roles (or points to contribution guidelines) and include a
link from the existing "ApexRMS (Author, maintainer)" attribution to that
contributors file so maintainership stays organizational while individuals
remain credited.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7f6f3f70-3c35-4fd5-ada2-f3da30dcdbbd

📥 Commits

Reviewing files that changed from the base of the PR and between 46abfde and 9458cee.

📒 Files selected for processing (1)

• docs/index.md