d302fc94e0 | ||
---|---|---|
.. | ||
components | ||
flight-manuals | ||
i18n-languages | ||
images | ||
.nojekyll | ||
CNAME | ||
README.md | ||
devops.md | ||
how-to-catch-outgoing-emails-locally.md | ||
how-to-open-a-pull-request.md | ||
how-to-setup-freecodecamp-locally.md | ||
how-to-use-docker-on-windows-home.md | ||
how-to-work-on-coding-challenges.md | ||
index.html | ||
index.md | ||
reply-templates.md |
README.md
All our documentation and contributing guidlines are available on a dedicated site here: https://contribute.freecodecamp.org.
Looking to edit the contributing guidelines?
To work on the contributing guidelines, you can edit these files available here. When your changes are merged, it will be made available automatically at the documentation site linked above.
You do not need to setup anything locally for working on the documentation.
How is the documentation site generated?
The documentation site is generated using docsify
, and served using GitHub pages. Typically you would not need to change any configuration, or build the site locally, but incase you are interested here is how it works:
-
The guideline homepage's source is
index.html
. GitHub Pages serve this file as a SPA usingdocsify
. -
The
docsify
script generates the content ofmarkdown
files in/docs
directory on demand when you are browsing the documentation site. -
The home page is genrated from the
index.md
and sidebar navigation is generated fromcomponents/sidebar.md
. -
To serve the docs locally:
Clone freeCodeCamp:
git clone https://github.com/freeCodeCamp/freeCodeCamp.git docsify serve docs
Install
docsify
:npm install -g docsify
and serve the
/docs
directorydocsify serve docs
Alternatively, if you have installed freeCodeCamp locally (see the local setup guide), we bundle the CLI with the development tools so you can run
npm run docs:serve
from the root of the repo.