docs: remove templates and more

[jdegand]

Summary by CodeRabbit

• Documentation
  • Reorganized and reordered several resource lists for improved clarity.
  • Removed outdated or redundant entries in site templates and testing guides.
  • Corrected spelling and updated descriptions for clarity and version neutrality.

[coderabbitai]

Walkthrough

This update reorganizes and reorders various lists in the README.md file, adjusting the sequence of entries within several Angular ecosystem categories. Multiple site template and guide links were removed, and some descriptions were edited for clarity or neutrality. No code or exported entities were altered—only documentation content was affected.

Changes

File(s)	Change Summary
README.md	Reordered list entries in multiple sections; removed several site template and testing guide links; corrected spelling and made minor wording edits for clarity and version neutrality; no functional or logical code changes.

Possibly related PRs

• docs: removals from rxjs and much more #1512: Reorganizes and updates README.md by modifying order and descriptions of Angular ecosystem resources, similar in scope and intent.
• docs: removals from 28 sections #1515: Removes and reorganizes Angular ecosystem entries in README.md, related by purpose but differing in scope and specific changes.
• docs: deletion of stale repos #1511: Deletes stale repository entries and reorders resource lists in README.md, related by scope but not overlapping exact entries.

Poem

In README rows, a shuffle and trim,
Old links removed, fresh order within.
Templates and guides, some bid adieu,
Clarity shines through wording anew.
🐇 With every hop, the docs grow neat—
A garden of lists, now tidy and sweet!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b7790a4 and 8ecf982.

📒 Files selected for processing (1)

• README.md (5 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

880-887: Fix typo in “Snyk” entry

The security vendor is spelled Snyk, not Synk. Recommend correcting for credibility and searchability.

-* [Synk](https://snyk.io/) - Snyk is a developer security platform that integrates directly into development tools, workflows, and automation pipelines.
+* [Snyk](https://snyk.io/) - Snyk is a developer security platform that integrates directly into development tools, workflows, and automation pipelines.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 885c49f and b7790a4.

📒 Files selected for processing (1)

• README.md (5 hunks)

🔇 Additional comments (8)

README.md (8)

690-696: Ordering change looks good

No functional issues found; the re-ordering improves logical grouping without affecting link validity.

---

699-702: Single-line move OK

JHipster entry relocation is harmless; link and description remain intact.

---

704-707: GraphQL section reorder confirmed

apollo-orbit bumped up in the list – all good.

---

862-865: Monorepos – “Moon” promoted

No issues; link renders correctly.

---

870-877: Payments list shuffle

Links for Google Pay, ngx-stripe and Solidgate verified – no concerns.

---

912-916: CoreUI entry remains accurate

No issues detected; wording and URL are valid.

---

921-925: Angular + Nest template reorder

Entry still points to the correct repository; looks fine.

---

1017-1020: Guide list trim makes sense

Keeping only the Tim Deschryver blog link is acceptable; link resolves.