See Astro docs on Content Collections, via.

When deploying the site I did this which was recommended somewhere in docs, but it doesn't work or is not sufficient:

it renders the homepage

Description:

The current version of the Operately website lacks a dedicated community section, which is essential for fostering engagement, providing support, and showcasing user success stories.

Expected Behavior:
The community section should provide a platform for users to connect, share experiences, ask questions, and learn from each other. It should include features such as:

• Discussion forums or boards for different topics related to Operately usage, best practices, and troubleshooting.

• User-generated content area where customers can share case studies, tutorials, and tips.

• Support resources such as FAQs, knowledge base articles, and troubleshooting guides.

• Events calendar for webinars, workshops, and community meetups.

• Integration with social media platforms to encourage sharing and networking.

Actual Behavior:
Currently, there is no dedicated space for community engagement on the Operately website, limiting user interaction and support opportunities.

Description:

Add a toggle button to switch between dark and light modes on the website for improved user experience and accessibility.

Details:

Objective: Enhance user experience by providing a toggle button for dark and light modes.

Behavior: Toggle button switches color scheme and layout for readability in different environments.

Interaction: Users click the toggle button to switch between modes, with visual feedback.

Design: Ensure readability and accessibility in both dark and light modes.

It looks like when I added anchor which I intended for Handbook only #13 the code spilled over into pages that are generated with Article layout too (Blueprint, Masterplan).

Anchor links are always on, like this:

I think that it's useful to have anchor links on all article-like pages, but JS should behave.