You can edit the main page, the tutorial, the 404 page, and assets (e.g. CSS, JS, images) from this repo,
they're all in site/.
If you're making changes to the documentation, FAQ, design document, or something similar, don't edit docs/.
Instead, fork the fish-shell repo and make the changes in doc_src/.
The raw source of the documentation lives there.
The fish site is built via the Jekyll static site generator. Jekyll is used to populate the site with release versions, dates, tarballs, based on data from the releases API. You will need to install jekyll, gem install jekyll bundler should do it.
- Make the change in
site/ - Run
makefrom the top level directory. - Open
docs/index.htmlto see your change.
This assumes that the relevant release has been published in the fish-shell github page. These steps could obviously stand more automation.
- Update the docs
- From the tarball, copy
user_doc/htmlto thesite/docs/directory. - Name it with the proper major version number only (e.g. 2.7). The minor version number is omitted.
currentis just a copy of the most recent docs. Deletecurrentand replace it with a copy of the new directory.
- From the tarball, copy
- Run
make new-release. This downloadsreleases.jsonand rebuilds the site using it. - Open
docs/index.htmland check it. In particular ensure the tarball and Mac download links work.
The site is hosted via GitHub pages with a custom domain. The site is served out of the docs directory.
After building the site (see above), do the following:
maketo build the site.git commityour changes tomaster. Ensure the site is checked in.git push
The public site will update immediately.