Official documentation for Nouns Builder, a protocol for creating and managing Nouns-style DAOs.
- π Live Site
- ποΈ Nouns Builder App
- π GitHub
- π¬ Discord
- π£ Farcaster
.
βββ public/ # Static assets and guide screenshots
β βββ guides/ # Screenshots organized by feature
β βββ onboarding/ # Onboarding guide images
βββ src/
β βββ assets/images/ # Documentation images
β βββ content/
β β βββ docs/
β β β βββ onboarding/ # Getting started guides
β β β βββ guides/ # User guides
β β β βββ contributors/ # Contributor documentation
β β βββ config.ts # Content schema configuration
β βββ env.d.ts
βββ astro.config.mjs # Astro and Starlight configuration
βββ package.json
βββ tsconfig.json
Documentation is written in .mdx files in the src/content/docs/ directory. The site navigation is automatically generated from the directory structure as configured in astro.config.mjs.
All commands are run from the root of the project, from a terminal:
| Command | Action |
|---|---|
npm install |
Installs dependencies |
npm run dev |
Starts local dev server at localhost:4321 |
npm run build |
Build your production site to ./dist/ |
npm run preview |
Preview your build locally, before deploying |
npm run astro ... |
Run CLI commands like astro add, astro check |
npm run astro -- --help |
Get help using the Astro CLI |
The documentation is organized into three main sections:
- Getting Started (
src/content/docs/onboarding/) - Onboarding guides for new users - User Guide (
src/content/docs/guides/) - Feature guides for creating DAOs, auctions, governance, etc. - Contributor Guide (
src/content/docs/contributors/) - Documentation for contributors and developers
This site is built with Astro and Starlight. To contribute:
- Fork the repository
- Install dependencies:
npm install - Start development server:
npm run dev - Make your changes to the content in
src/content/docs/ - Test your changes locally
- Submit a pull request
- Use
.mdxfiles for all documentation - Place images in
src/assets/images/and reference with relative paths - Guide screenshots should be placed in
public/guides/[feature-name]/ - Follow the existing content structure and style