The website that provides documentation along with a blog for the Bluelink project. This contains general documentation for the high-level concepts and components of Bluelink along with versioned documentation for the libraries and applications that make up Bluelink.
This is a Next.js application generated with Create Fumadocs.
Run development server:
npm run dev
# or
pnpm dev
# or
yarn devOpen http://localhost:3000 with your browser to see the result.
In the project, you can see:
lib/source.ts: Code for content source adapter,loader()provides the interface to access your content.lib/layout.shared.tsx: Shared options for layouts, optional but preferred to keep.
| Route | Description |
|---|---|
app/(home) |
The route group for your landing page and other pages. |
app/docs |
The documentation layout and pages. |
app/api/search/route.ts |
The Route Handler for search. |
A source.config.ts config file has been included, you can customise different options like frontmatter schema.
Read the Introduction for further details.
The Celerity docs site is made up of sections for different components of the framework.
The following components are independently versioned:
- CLI
- Deploy Engine
- Blueprint Framework
- Plugin Framework
Versioning is implemented using folders as per the fumadocs versioning documentation.
Each version folder should have a meta.json file that lists the pages for the version, with the first page being the getting started/introduction page.
The component root folder should have a meta.json file that lists the version folders in the pages directory, the ordering should be most recent version first.
For example, for a component that has 2 versions, the meta.json file would look like this:
{
// Other metadata ...
"pages": ["v2", "v1"]
}To validate links in the documentation, you can run the following command:
yarn check-linksThis will look for broken or invalid links, however, it will not detect missing pages under a [[...slug]] route such as docs/framework/auth/missing-page that comes under the docs/[[...slug]] route.
The Deploy Engine provides a HTTP API that is used by the CLI and other clients to interact with the Deploy Engine to validate and deploy blueprints.
To generate the API docs, you can run the following command:
yarn generate-api-docsWhenever changes are made to the OpenAPI specification, you must run this command to generate the mdx pages for the API docs and commit to source control.
The source OpenAPI specification can be found in the api-docs directory.
The installation page displays download links and version information for Bluelink components. This data is fetched from GitHub releases at build time and stored in src/data/releases.json.
This file is not committed to version control and is generated automatically during the deploy workflow. To generate it locally for development:
yarn fetch-releasesThis will fetch the latest releases from GitHub and write them to src/data/releases.json. You may need to set the GITHUB_TOKEN environment variable if you hit rate limits:
GITHUB_TOKEN=your_token yarn fetch-releasesThe yarn build command automatically runs fetch-releases as part of the build process.
To learn more about Next.js and Fumadocs, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
- Fumadocs - learn about Fumadocs