GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - PoliNetworkOrg/docs

BranchesTags
Open more actions menu

Latest commit

 

History

59 Commits
59 Commits

Folders and files

NameName
Last commit message
Last commit date
.github/workflows
.github/workflows
 
 
.vscode
.vscode
 
 
app
app
 
 
content/docs
content/docs
 
 
public
public
 
 
scripts
scripts
 
 
.gitignore
.gitignore
 
 
.prettierrc
.prettierrc
 
 
README.md
README.md
 
 
eslint.config.mjs
eslint.config.mjs
 
 
package.json
package.json
 
 
pnpm-lock.yaml
pnpm-lock.yaml
 
 
react-router.config.ts
react-router.config.ts
 
 
source.config.ts
source.config.ts
 
 
tsconfig.json
tsconfig.json
 
 
vite.config.ts
vite.config.ts
 
 

Repository files navigation

PoliNetwork Docs

Welcome to the PoliNetwork documentation site. Here you will find guides, tutorials, and other resources to help you get started with contributing to PoliNetwork's projects.

Website

This website is built with Fumadocs on React Router, and exported as a static site.

Installation

pnpm install

Local Development

pnpm dev

This command starts a local development server. Most changes are reflected live without having to restart the server.

Build

pnpm build

This command prerenders every page into the build directory, which can be served using any static contents hosting service.

You can then serve your static build by running:

pnpm start

Deployment

This website is deployed using GitHub Pages. The deployment process is automated using GitHub Actions, and every pull request gets a preview deployment.

Writing docs

Pages live in content/docs/ as .mdx files: the URL follows the file path (content/docs/infrastructure/Guides/backups.mdx is /docs/infrastructure/Guides/backups).

  • Every page needs a title in its front matter (and optionally a description): it is rendered as the page heading, so don't repeat it as a # heading.
  • The sidebar order and folder names come from the meta.json file in each folder.
  • Link to other pages with their URL, e.g. [Backups](/docs/infrastructure/Guides/backups).
  • Callouts: <Callout type="note|tip|info|important|warning|caution|danger" title="Optional title">...</Callout>.
  • Code blocks take a title="file.yaml" and lineNumbers. Mark lines with a comment at the end of the line, or alone on the line before them with a line count: # [!code ++] (added), # [!code --] (removed), # [!code highlight], # [!code error], e.g. # [!code ++:3] marks the next 3 lines as added.
  • ```mermaid code blocks are rendered as diagrams.

About

docs.polinetwork.org

Resources

Readme
Activity
Custom properties

Stars

1 star

Watchers

1 watching

Forks

0 forks
Report repository

Releases

Packages

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.