Skip to content

feat(community): add a Community page and link it from the main menu - #637

Draft
Timur Tukaev (tym83) wants to merge 1 commit into
mainfrom
feat/community-page
Draft

feat(community): add a Community page and link it from the main menu#637
Timur Tukaev (tym83) wants to merge 1 commit into
mainfrom
feat/community-page

Conversation

@tym83

Copy link
Copy Markdown
Contributor

Summary

cozystack.io/community returned 404, and nothing on the site pointed at the
community meeting, its recordings, or the contributor path. From the website
alone a visitor could not learn that public community calls happen at all —
they have been running every two weeks since April 2024.

What

  • content/en/community.md — chat channels, the community meeting (schedule,
    Zoom link, calendar, link to the archive), contributor entry points, the
    governance documents, and the four YouTube playlists.
  • hugo.yaml — a Community entry in the main menu at weight 30, so it lands
    between Blog and OSS Health.
  • content/en/.gitignore — dropped the community.md line.

Why the .gitignore change

That file has been ignoring community.md, contributing.md, governance.md
and security.md under an # Imported comment, but nothing in the tree imports
them: no hack/ script, Makefile target or workflow references any of those
names. The rule only prevented the page from being committed. Only the
community.md line is removed — the other three are left alone in case they
belong to a plan I am not aware of.

Preview

Verified locally: the page renders, the menu entry appears in the expected
position, and the ref to the Developer Guide resolves.

Note for whoever builds locally — hugo newer than the pinned 0.160.1 fails on
this repo before reaching any of these changes, with
access denied: "text/html" is not whitelisted in policy "security.allowContent"
on content/<lang>/_index.html. That reproduces on a clean main too, so it is
unrelated to this PR, but it does mean the pinned version is now effectively
mandatory rather than advisory.

Localisation

Only the English page is added; the translation pipeline owns the other locales.

@netlify

netlify Bot commented Aug 3, 2026

Copy link
Copy Markdown

Deploy Preview for cozystack ready!

Name Link
🔨 Latest commit 9085dd0
🔍 Latest deploy log https://app.netlify.com/projects/cozystack/deploys/6a70e6756ede6a0008eac52d
😎 Deploy Preview https://deploy-preview-637--cozystack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 08438662-3dd4-4125-a437-518fd9183f70

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

cozystack.io had no community page: /community/ returned 404, and nothing on
the site pointed at the community meeting, its two years of recordings, or the
contributor path. A visitor could not find out that public calls happen at all.

The page collects the chat channels, the meeting (schedule, joining link,
calendar, archive), the contributor entry points, the governance documents and
the video playlists. It links to cozystack/community, which now holds the
meeting archive and the onboarding guide.

content/en/.gitignore has been ignoring community.md under an "# Imported"
comment, but no import mechanism exists anywhere in the tree — no hack script,
Makefile target or workflow references it. The rule only prevented the page
from being added, so drop that one line and keep the rest untouched.

Signed-off-by: Timur Tukaev <timur.tukaev@aenix.io>

Signed-off-by: tym83 <6355522@gmail.com>
@IvanHunters

Copy link
Copy Markdown
Contributor

The core justification checks out: content/en/.gitignore ignores those four files under # Imported, and nothing in the tree actually imports them (every hack/ script, the Makefile and the workflows only write into content/en/docs/ and static/; the only hits for those names elsewhere are external links to the cozystack repo). Dropping the community.md line is safe. The {{% ref "/docs/v1.6/development" %}} target exists and type: "page" has a layout.

Two small things:

  1. weight: 30 on the Community menu entry collides with Blog, which is also weight: 30 (content/en/blog/_index.md:6). "Between Blog and OSS Health" only holds via Hugo's alphabetical tie-break, so give it a distinct weight (e.g. 32). Note also that Blog's menu entry is front-matter-defined and English-only, while this hugo.yaml entry appears on every locale, where Community's neighbour will be GitHub rather than Blog.
  2. The "hugo newer than 0.160.1 fails ... the pinned version is now effectively mandatory" note in the description is stale after the rebase: main pins 0.164.0 (netlify.toml:6, .github/workflows/hugo.yaml:35) and the landing pages are markdown. Worth dropping so it does not mislead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants