Repository navigation
PM-45227 - Add a Seeder page to the server getting-started section - #896
Conversation
A new local database has no accounts, and the contributing site pointed to the Seeder only from a note inside "Set up Aspire". Manual Setup did not mention it. Add Getting started > Server > Seeder: what the Seeder is, a flowchart for choosing between the Seeder CLI and the Seeder API, the steps to seed a database, and links to the reference docs in the server repo. Link to the page from the Setup Guide and Manual Setup after the Api alive check, and repoint the Aspire note to it. Reference content such as flags and presets stays in the server repo per rule 2 of the documentation standard. Refs: PM-45227
Deploying contributing-docs with
|
| Latest commit: |
f467a12
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7b2fed18.contributing-docs.pages.dev |
| Branch Preview URL: | https://docs-seeder-02.contributing-docs.pages.dev |
theMickster
added
ai-review
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE This PR adds |
withinfocus
left a comment
withinfocus
left a comment
There was a problem hiding this comment.
Few ideas for future enhancements but this is a great addition to the setup workflow.
|
Still good for merge as I see it. |
- Bullet the three Seeder CLI commands, and mark organization and individual for use only when no preset fits - Replace the list, choose, and run steps with one step: ask Claude, which uses the seeding-bitwarden-data skill, or find a command in the scenarios index
|
With the merging of server/pull/8678, I think we are ready for a final review here @withinfocus 😁 |
withinfocus
left a comment
withinfocus
left a comment
There was a problem hiding this comment.
Super hot, but some ⛏️s.
Copilot also reads skills from .claude/skills, so the seeding step no longer names Claude. Drop the "Bitwarden developers" sentence from the same step.
🎟️ Tracking
PM-45227
📔 Objective
Crafted a new Seeder page to aid in finding the Seeder without searching the server repo. Reference content such as CLI flags and the preset list stays in the server repo per rule 2 of the documentation standard.
🧪 Testing
Expand for lint, spellcheck, build, render, and link checks
Step 1: Lint, spellcheck, build
npm run lintnpm run spellchecknpm run buildStep 2: Render the page
Served the site locally and opened
/getting-started/server/seederwith Playwright. The page sitsin the Server sidebar after Manual Setup, the Mermaid flowchart renders with no syntax error, the
perspective caption sits under it, and the inbound links from the Setup Guide and Manual Setup
resolve.
Step 3: Check the outbound links
util/SeederUtility/README.mdutil/SeederApi/README.mdutil/Seeder/Seeds/docs/presets.mdutil/Seeder/Seeds/docs/scenarios/README.md