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 - forem/forem-docs

BranchesTags
Open more actions menu

Latest commit

 

History

294 Commits
294 Commits

Folders and files

NameName
Last commit message
Last commit date
.github
.github
 
 
docs
docs
 
 
src/css
src/css
 
 
static
static
 
 
.gitignore
.gitignore
 
 
.node-version
.node-version
 
 
.spectral.yml
.spectral.yml
 
 
README.md
README.md
 
 
api_v0.yml
api_v0.yml
 
 
api_v1.json
api_v1.json
 
 
babel.config.js
babel.config.js
 
 
docusaurus.config.js
docusaurus.config.js
 
 
netlify.toml
netlify.toml
 
 
package.json
package.json
 
 
sidebars.js
sidebars.js
 
 
yarn.lock
yarn.lock
 
 

Repository files navigation

Forem Developer Docs

Welcome to Forem's developer documentation! The docs are built using Docusaurus 2, a React and Markdown based documentation website generator.

Our developer docs are meant to be used as a way to find instructions to setup a local instance of Forem, documentation on the architecture of Forem, how to contribute, and many other useful documents.

If you have launched a Forem community of your own and are looking for documentation on how to manage that community, please see our Admin Docs

Technical Overview

Most of the configuration here is not too different from the basic preset-classic of Docusaurus. The main folders are:

  • docs: where the documentation lives
  • src: any custom CSS, components or pages
  • static/img: any image files

Installation

git clone https://github.com/forem/forem-docs.git
yarn install

Local Development

Once installed:

yarn start

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

All relevant Markdown files are in docs/. To update any docs, simply update the Markdown file with your favorite Markdown editor. You can also add new files to the relevant sections.

For other types of contributions outside of text changes to Markdown files, please see Docusaurus' docs for additional info.

Search

On production, search is run by Algolia, specifically their DocSearch service. The service scrapes the website every 24 hours or so, so new contributions to the docs may take about that long to update.

Testing Production Builds

To see if your changes will build (for ex. you made added some screenshots) you can run:

yarn build

Alternatively, you can make a pull request and use the corresponding deploy preview that builds.

About

No description, website, or topics provided.

Resources

Readme
Activity
Custom properties

Stars

50 stars

Watchers

8 watching

Forks

70 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.