chore(docs): add onboarding and how we work guide#2444
Conversation
✅ Deploy Preview for ocm-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (2)
📝 WalkthroughWalkthroughRestructures the website community area: updates community menu and changelog templates, expands the wordlist, adds a Community index, updates community pages (Zulip, contributing link), revises the contributing guide, and adds "How We Work" and onboarding pages. ChangesCommunity Section Restructuring & Documentation Expansion
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested reviewers
🚥 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)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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 |
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
52428df to
a0230ef
Compare
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
matthiasbruns
left a comment
There was a problem hiding this comment.
Content is great - I like the infos that are made. I think ocm still needs some kind of mentoring in the beginning due to the deep-tech nature (not part of this issue, but in general worth thinking about for people who are really interested and show that they would invest more)
…omponent-model into add-onboarding-guide
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
There was a problem hiding this comment.
♻️ Duplicate comments (1)
website/content/community/how-we-work.md (1)
11-12:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winResolve contradictory meeting-access statement.
Line 11-12 says all listed meetings are public, but Line 66 defines the retrospective as invite-only. Please narrow this statement so it matches the table and avoids confusing newcomers.
Suggested wording change
-This page describes how the OCM team organizes its day-to-day development work. All meetings listed here are open to -the public - anyone is welcome to join, listen, or participate. +This page describes how the OCM team organizes its day-to-day development work. Most meetings listed here are open to +the public - anyone is welcome to join, listen, or participate unless explicitly marked otherwise.🤖 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 `@website/content/community/how-we-work.md` around lines 11 - 12, The opening paragraph claims "All meetings listed here are open to the public" which contradicts the table entry for the "Retrospective" that is invite-only; update the opening sentence to be accurate and non-contradictory—for example change it to "Most meetings listed here are open to the public; exceptions (such as the Retrospective, which is invite-only) are noted below." Ensure you reference the "Retrospective" by name in the sentence so newcomers see the exception and that the table's invite-only status remains authoritative.
🤖 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.
Duplicate comments:
In `@website/content/community/how-we-work.md`:
- Around line 11-12: The opening paragraph claims "All meetings listed here are
open to the public" which contradicts the table entry for the "Retrospective"
that is invite-only; update the opening sentence to be accurate and
non-contradictory—for example change it to "Most meetings listed here are open
to the public; exceptions (such as the Retrospective, which is invite-only) are
noted below." Ensure you reference the "Retrospective" by name in the sentence
so newcomers see the exception and that the table's invite-only status remains
authoritative.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: b6a21a94-6402-4114-9597-5090b8b7805e
📒 Files selected for processing (2)
website/content/community/how-we-work.mdwebsite/content/community/onboarding.md
✅ Files skipped from review due to trivial changes (1)
- website/content/community/onboarding.md
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
piotrjanik
left a comment
There was a problem hiding this comment.
LGTM, Really good job @frewilhelm
…omponent-model into add-onboarding-guide
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
4a06b94
…omponent-model into add-onboarding-guide
Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com>
|
https://deploy-preview-2444--ocm-website.netlify.app/ looks and reads cool. Great work! |
<!-- markdownlint-disable MD041 --> #### What this PR does / why we need it Adds community documentation to the website as outlined in the onboarding epic. This PR introduces: - **Developer Onboarding** (`/community/onboarding`) - a guided entry point for new developers covering what OCM is, the mono-repo structure, technical layers, and learning paths. - **How We Work** (`/community/how-we-work`) - documents the team's work item hierarchy (initiatives, epics, tasks, spikes), project board, sprint intake process, meeting cadence, and decision-making. - **Community section restructuring** - replaces `community.md` (slug: `/community/engagement`) with a proper Hugo section `_index.md`, updates the nav menu to point to `/community/`, and adjusts page weights for logical ordering. The old `/community/engagement/` URL is preserved via an alias redirect. - **Existing page updates**: - `community.md` replaced by `_index.md`: adds Zulip channel, uses `relref` for the contributing link, improves description meta. - `contributing.md`: removes "SAP" from AI policy, replaces duplicated channel info with a link to the community page, adds direct links to the mono-repo and website `CONTRIBUTING.md` files. - **Cross-repo link updates** - updates `/community/engagement` references in `CONTRIBUTING.md`, both `cliff.toml` changelog templates, `SIG-Runtime-CHARTER.md`, `docs/community/README.md`, the OCM v2 blog post, and the container image how-to guide. #### Which issue(s) this PR fixes Fixes open-component-model/ocm-project#991 #### Testing ##### How to test the changes This is a documentation-only change. To verify locally: ```bash cd website npm run build ``` The Hugo build should complete without errors. To preview: ```bash npm run dev ``` Then navigate to: - http://localhost:1313/community/ - http://localhost:1313/community/onboarding/ - http://localhost:1313/community/how-we-work/ - http://localhost:1313/community/contributing/ Verify that: - All internal links resolve (no 404s) - Mermaid diagrams render correctly on the onboarding and how-we-work pages - The community section landing page lists all child pages - Navigation menu "Community" link lands on the section page - `/community/engagement/` redirects to `/community/` --------- Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com> Co-authored-by: Matthias Bruns <github@matthiasbruns.com> b32f4a0
…el#2444) <!-- markdownlint-disable MD041 --> #### What this PR does / why we need it Adds community documentation to the website as outlined in the onboarding epic. This PR introduces: - **Developer Onboarding** (`/community/onboarding`) - a guided entry point for new developers covering what OCM is, the mono-repo structure, technical layers, and learning paths. - **How We Work** (`/community/how-we-work`) - documents the team's work item hierarchy (initiatives, epics, tasks, spikes), project board, sprint intake process, meeting cadence, and decision-making. - **Community section restructuring** - replaces `community.md` (slug: `/community/engagement`) with a proper Hugo section `_index.md`, updates the nav menu to point to `/community/`, and adjusts page weights for logical ordering. The old `/community/engagement/` URL is preserved via an alias redirect. - **Existing page updates**: - `community.md` replaced by `_index.md`: adds Zulip channel, uses `relref` for the contributing link, improves description meta. - `contributing.md`: removes "SAP" from AI policy, replaces duplicated channel info with a link to the community page, adds direct links to the mono-repo and website `CONTRIBUTING.md` files. - **Cross-repo link updates** - updates `/community/engagement` references in `CONTRIBUTING.md`, both `cliff.toml` changelog templates, `SIG-Runtime-CHARTER.md`, `docs/community/README.md`, the OCM v2 blog post, and the container image how-to guide. #### Which issue(s) this PR fixes Fixes open-component-model/ocm-project#991 #### Testing ##### How to test the changes This is a documentation-only change. To verify locally: ```bash cd website npm run build ``` The Hugo build should complete without errors. To preview: ```bash npm run dev ``` Then navigate to: - http://localhost:1313/community/ - http://localhost:1313/community/onboarding/ - http://localhost:1313/community/how-we-work/ - http://localhost:1313/community/contributing/ Verify that: - All internal links resolve (no 404s) - Mermaid diagrams render correctly on the onboarding and how-we-work pages - The community section landing page lists all child pages - Navigation menu "Community" link lands on the section page - `/community/engagement/` redirects to `/community/` --------- Signed-off-by: Frederic Wilhelm <frederic.wilhelm@sap.com> Co-authored-by: Matthias Bruns <github@matthiasbruns.com>
What this PR does / why we need it
Adds community documentation to the website as outlined in the onboarding epic. This PR introduces:
/community/onboarding) - a guided entry point for new developers covering what OCM is, the mono-repo structure, technical layers, and learning paths./community/how-we-work) - documents the team's work item hierarchy (initiatives, epics, tasks, spikes), project board, sprint intake process, meeting cadence, and decision-making.community.md(slug:/community/engagement) with a proper Hugo section_index.md, updates the nav menu to point to/community/, and adjusts page weights for logical ordering. The old/community/engagement/URL is preserved via an alias redirect.community.mdreplaced by_index.md: adds Zulip channel, usesrelreffor the contributing link, improves description meta.contributing.md: removes "SAP" from AI policy, replaces duplicated channel info with a link to the community page, adds direct links to the mono-repo and websiteCONTRIBUTING.mdfiles./community/engagementreferences inCONTRIBUTING.md, bothcliff.tomlchangelog templates,SIG-Runtime-CHARTER.md,docs/community/README.md, the OCM v2 blog post, and the container image how-to guide.Which issue(s) this PR fixes
Fixes open-component-model/ocm-project#991
Testing
How to test the changes
This is a documentation-only change. To verify locally:
cd website npm run buildThe Hugo build should complete without errors. To preview:
Then navigate to:
Verify that:
/community/engagement/redirects to/community/