Google Git
Sign in
apache / mynewt-site / 372893736ed7c1ec11de9717e4ed6491d4217e3a
commit372893736ed7c1ec11de9717e4ed6491d4217e3a[log] [tgz]
authoraditihilbert <aditi@runtime.io>Fri Nov 04 12:05:50 2016 -0700
committeraditihilbert <aditi@runtime.io>Fri Nov 04 12:05:50 2016 -0700
tree3998c79b80f80019b6cbea4ccd58ffd13591cc7e
parent86826179622460c869c0b561350d2d85ffc90547 [diff]
added a presentation and modified section titles on landing page
2 files changed
tree: 3998c79b80f80019b6cbea4ccd58ffd13591cc7e
  1. custom-theme/
  2. docs/
  3. extras/
  4. .editorconfig
  5. .gitignore
  6. build.py
  7. deploy.sh
  8. mkdocs.yml
  9. README.md
  10. serve.py
README.md

The Apache MyNewt site is built using MkDocs.

Setup

For all contributors:

  • Install MkDocs on your system.

Additionally for committers:

  • pip install GitPython
  • pip install sh

Submitting updates

  1. Fork the repo.
  2. Work on the develop branch.
  3. Preview your changes using MkDocs.
  4. Submit a pull request.

Releasing a versioned set of MyNewt documentation

When a new release of MyNewt OS and its associated tools occurs, the documentation in the git develop branch of this repository should be in sync with the released version. The following steps will create a documentation branch for the release and make it available as the default documentation from the mynewt-site.

Build

  1. Merge develop to master.
  2. Switch to the master branch.
    • git checkout master
  3. Create a new stanza in mkdocs.yml to reflect the new version.
    • and update the latest flag, only one release should be marked latest.
    • and update version to match the new branch name.
  4. Commit this change.
  5. Create a branch from master to reflect this new version.
  6. Run: ./build.py

Test

  1. Run: ./serve.py
  2. Visit http://localhost:8000

Deploy

  1. Run: ./deploy.sh
  2. This will leave you on the asf-site branch.
  3. Commit & push the changes.

Links to Documentation

For the deployed site a version prefix is added to the URL for each mkdocs page. When developing there is no version prefix. If you want to link from a site page to a documentation page you should prefix the URL with /DOCSLINK/ so that the user is taken to the correct location when browsing in production.

Link Checking

  1. Grab a link checking tool like Integrity
  2. Run: ./build.py --test-build
  3. Run: ./serve.py
  4. point the link checker at http://localhost:8000/