Add Community Resources page to docs landing

[miharp]

Background

Discussion in Slack raised the idea of surfacing community-authored content (tutorials, how-to guides, blog posts) alongside the official docs. The Vox Pupuli blog at https://voxpupuli.org/blog/ already serves as a natural home for this kind of content.

Rather than pulling community content into this repo (which would require style alignment and maintenance overhead), a lightweight Community Resources page could link out to relevant external resources.

Requirements to define

• What should the page link to? (Vox Pupuli blog, specific posts, other community sites?)
• Where does it live in the site navigation? (top-level, or under a specific product?)
• Who maintains the link list as content comes and goes?
• Should entries be curated (reviewed before adding) or open contribution?
• What metadata per entry is useful? (title, author, date, product/version relevance)

Related Slack discussion

Martin Alfke, binford2k, and Yury Bushmelev discussed a getting-started/guides section. The community resources page is a lower-friction alternative that avoids mixing authoritative docs with community-authored content.

[jay7x]

I'd like to have contents available in the repo if possible. Blogs and blog platforms are dying frequently enough from my experience... so another copy made with author's permission (or by the original author) sounds better for me personally. /imho

[jay7x]

But anyway, links are better than nothing :)

[tuxmea]

A "getting started" or "Quick start" section helps people getting success with OpenVox fast.
I thought about something similar to https://theforeman.org/manuals/3.18/quickstart_guide.html

[miharp]

We already have getting started sections in the landing page for both agent and server

https://docs.openvoxproject.org/openvox/latest/#getting-started

https://docs.openvoxproject.org/openvox-server/latest/#getting-started

[miharp]

We could use the blog feature in Jekyll, it's well documented and would not require changing nav links. Downside is we already have https://voxpupuli.org/blog/ and https://voxpupuli.org/docs/ to think about.

[binford2k]

It won't hurt to have content in multiple places as long as we do it intentionally. We can easily syndicate content from blogs using a canonical link like this example.

<link rel="canonical" href="https://dev.to/betadots/how-to-keep-your-puppet-modules-up-to-date-with-renovate-19jn">

[binford2k]

We already have getting started sections in the landing page for both agent and server

Those are technical guides for steps to take with the new thing that you totally already are an expert at using. What's missing is the "what's this OpenVox thing I keep hearing about and how does this ecosystem work?" QuickStart guide. Don't worry, I'm not just schlupping new sections in without carefully organizing it all to fit.

[binford2k]

we already have [...] https://voxpupuli.org/docs/ to think about.

It's possible that this will be replaced with the new docs site once things are in full swing. At minimum, it will be reworked such that it feels like a coherent part of the whole docs setup. We have no reason to maintain distinctly separate things.