Add "Community & Resources" section to website - #92
Open
krisjdev wants to merge 2 commits into
Open
Conversation
This commit adds a new section on the website to consolidate community links and useful resources. It is also placed into the nav bar for easy access. Unlike the other pages present, this one exists within it's own folder and uses `index.md` to avoid the ugly `.html` slug in the URL. This page should resolve to `https://wafer.space/community-resources`. Ref #51
This commit removes the "Coming soon" info, and adds a button which takes the user straight to the community & resources page.
WalkthroughThis PR launches a new "Community & Resources" section on the site. A navigation menu entry routes to a new dedicated page featuring community platform links (Discord, Matrix) and curated external resources. Existing design documentation is updated to replace placeholder text with active descriptions. ChangesCommunity & Resources Page Launch
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
🚀 Preview Deployment Ready!
This preview will be automatically updated when you push new commits to this PR. Browse all previews: https://preview.wafer.space ⚡ Deployed to custom domain • Preview will be removed when PR is closed |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
_data/navigation.yml (1)
31-31: ⚡ Quick winQuote the text value to prevent potential YAML parsing issues.
The ampersand (
&) inCommunity & Resourcesis a special character in YAML (used for anchors). While it may parse correctly when not at the start of the value, best practice is to quote strings containing special characters to ensure consistent parsing across all YAML implementations.📝 Proposed fix
- - text: Community & Resources + - text: "Community & Resources" url: "/community-resources" menu_type: "simple"🤖 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 `@_data/navigation.yml` at line 31, The navigation item value containing an ampersand must be quoted to avoid YAML parsing issues; update the entry with the key "text" whose current value is Community & Resources to use either single or double quotes (e.g., "Community & Resources" or 'Community & Resources') so the ampersand is treated as a literal string in _data/navigation.yml.
🤖 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.
Inline comments:
In `@community-resources/index.md`:
- Line 7: Uncomment the navigation include by removing the HTML comment markers
around the include tag ("{% include layouts/nav/nav.html drop_search=false
alignment_class=\"ms-auto\" %}") so the nav partial is rendered on the page;
specifically locate the commented line containing that include and make it
active (match other pages such as the one using help.html:9) so the site menu
appears.
---
Nitpick comments:
In `@_data/navigation.yml`:
- Line 31: The navigation item value containing an ampersand must be quoted to
avoid YAML parsing issues; update the entry with the key "text" whose current
value is Community & Resources to use either single or double quotes (e.g.,
"Community & Resources" or 'Community & Resources') so the ampersand is treated
as a literal string in _data/navigation.yml.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 4c87cd1c-2e15-4dbc-8731-02f874c6bd6b
📒 Files selected for processing (3)
_data/navigation.ymlcommunity-resources/index.mddesign-help.html
| sub_title: Join our community, or check out some resources to help you with your next tapeout | ||
| header_image: "/assets/images/header/mpw-one-partial-dice-top-1.jpg" | ||
| --- | ||
| <!-- {% include layouts/nav/nav.html drop_search=false alignment_class="ms-auto" %} --> |
There was a problem hiding this comment.
Uncomment the navigation include to display the site menu.
The navigation include is commented out, which will prevent the site's main navigation menu from appearing on this page. Cross-referencing with other pages (e.g., help.html:9), the nav include should be active.
🔧 Proposed fix
-<!-- {% include layouts/nav/nav.html drop_search=false alignment_class="ms-auto" %} -->
+{% include layouts/nav/nav.html drop_search=false alignment_class="ms-auto" %}
{% include layouts/header/page-title.html %}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| <!-- {% include layouts/nav/nav.html drop_search=false alignment_class="ms-auto" %} --> | |
| {% include layouts/nav/nav.html drop_search=false alignment_class="ms-auto" %} | |
| {% include layouts/header/page-title.html %} |
🤖 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 `@community-resources/index.md` at line 7, Uncomment the navigation include by
removing the HTML comment markers around the include tag ("{% include
layouts/nav/nav.html drop_search=false alignment_class=\"ms-auto\" %}") so the
nav partial is rendered on the page; specifically locate the commented line
containing that include and make it active (match other pages such as the one
using help.html:9) so the site menu appears.
❌ Preview Site Verification FAILEDPreview Site Verification ReportPR: #92 1. Basic Connectivity ✅
2. Content Verification
3. Multi-Page Asset VerificationDiscovering all pages in the site...
4. Link and Asset Verification (muffet)Running comprehensive muffet validation...
Summary: 0 5. Performance Check
6. Mobile Responsiveness
Summary❌ Some verification checks failed 🔍 Automated verification • Run ID: 26887501216 • 2026-06-03T13:24:52.771Z |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a "Community & Resources" section to the website in order to consolidate community links and useful resources for people looking to get started with wafer.space. This page is accessible via the navbar.
Unlike the other pages, this exists within its own folder and uses
index.md- this ensures that when built, it won't have the ugly.htmlsuffix in the URL. This page should resolve tohttps://wafer.space/community-resourcesand nothttps://wafer.space/community-resources.html.The design help page was also updated and now links directly to the community & resources page.
Linked resources:
Closes #51
Summary by CodeRabbit