Skip to content

LinxiFan/Sphinx-theme

master
Switch branches/tags
Code
This branch is 25 commits ahead, 920 commits behind readthedocs:master.
Contribute

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
js
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Sphinx themes based on readthedocs.org

  • Stanford theme: stanford_theme
  • Updated RTD theme: neo_rtd_theme

Modification

Design

Online demo of the theme: linxifan.github.io/Sphinx-demo/

Stanford web color specification: [1] and [2]

Add new fonts

  1. Edit bower.json, add ubuntumono-googlefont to dependency list.
  2. Edit Gruntfile.js, add font paths like the others.
  3. Edit sass/_theme_font_local.sass, note that font-weight: 400 corresponds to normal font while 700 correspoonds to bold.
  4. Make sure the font files are copied to sphinx_theme/<mytheme>/static/fonts/

SASS

  • bower_components/wyrm contains the SASS for the original WYRM core. You can override variables in it to use customized color.
  • sass/_theme_variables.sass defines most of the colors.
  • sass/_theme_rst.sass defines how to render any reStructuredText file. All customizations are marked with mydef in the code comment.
  • sass/_theme_layout.css defines how to render menu, navigation bars, etc.

Workflow

  1. Work in sass/ folder and Grunt will auto copy the generated files into test_theme
  2. Once done, copy sass/ to sass_<newtheme> and copy test_theme to sphinx_theme/<newtheme> subdir.
  3. Update sphinx_theme/__init__.py to include the new theme.

To modify existing theme:

  1. Run ./swap sass sass_neo_rtd and work in sass/ folder. Changes will be reflected in test_theme/
  2. Run ./cptheme neo_rtd to copy test_theme/ files into sphinx_theme/neo_rtd_theme.
  3. Run ./swap sass sass_neo_rtd again to restore the files.
  4. Commit all changes.

Modify directives

Directives like .warning, .example, can be added to sphinxcontrib-napolean.

Currently support:

Style Directives
info (blue) .note, .seealso, .references
tip (green) .tip, .hint, .example
warning (orange) .warning, .caution, .attention, .admonition-todo
danger (red) .danger, .error, .important
  • Refer to sphinxcontrib-napolean2/directives.py for how to add new directives.
  • Add new parser methods to sphinxcontrib-napolean2/docstring.py. Refer to lines marked with 'ADDED'.
  • Add app.add_directive('example', ExampleDirective) to setup() function in sphinxcontrib-napolean2/__init__.py
  • Modify sass/_theme_rst.sass to support the new directives in the theme.
  • Original designs are located in wyrm/sass/wyrm_core/_alert.sass

Installation

Via package

Download the package or add it to your requirements.txt file:

$ pip install sphinx_theme

In your conf.py file:

import sphinx_theme
html_theme = "stanford_theme"
html_theme_path = [sphinx_theme.get_html_theme_path('stanford-theme')]

# All available themes:
print(sphinx_theme.THEME_LIST)
# >> ['stanford_theme', 'neo_rtd_theme']

Via git or download

Symlink or subtree the sphinx_theme/sphinx_theme repository into your documentation at docs/_themes/sphinx_theme then add the following two settings to your Sphinx conf.py file:

html_theme = "stanford_theme"
html_theme_path = ["_themes/sphinx_theme", ]

Configuration

You can configure different parts of the theme.

Project-wide configuration

The theme's project-wide options are defined in the sphinx_theme/<mytheme>/theme.conf file of this repository, and can be defined in your project's conf.py via html_theme_options. For example:

html_theme_options = {
    'collapse_navigation': False,
    'display_version': False,
    'navigation_depth': 3,
}

Page-level configuration

Pages support metadata that changes how the theme renders. You can currently add the following:

  • :github_url: This will force the "Edit on GitHub" to the configured URL
  • :bitbucket_url: This will force the "Edit on Bitbucket" to the configured URL
  • :gitlab_url: This will force the "Edit on GitLab" to the configured URL

How the Table of Contents builds

Currently the left menu will build based upon any toctree(s) defined in your index.rst file. It outputs 2 levels of depth, which should give your visitors a high level of access to your docs. If no toctrees are set the theme reverts to sphinx's usual local toctree.

It's important to note that if you don't follow the same styling for your rST headers across your documents, the toctree will misbuild, and the resulting menu might not show the correct depth when it renders.

Also note that the table of contents is set with includehidden=true. This allows you to set a hidden toc in your index file with the hidden property that will allow you to build a toc without it rendering in your index.

By default, the navigation will "stick" to the screen as you scroll. However if your toc is vertically too large, it will revert to static positioning. To disable the sticky nav altogether change the setting in conf.py.

Make the theme compatible with ReadTheDocs

Currently if you import stanford_theme in your local sphinx build, then pass that same config to Read the Docs, it will fail, since RTD gets confused. If you want to run this theme locally and then also have it build on RTD, then you can add something like this to your config. Thanks to Daniel Oaks for this.

# on_rtd is whether we are on readthedocs.org, this line of code grabbed from docs.readthedocs.org
on_rtd = os.environ.get('READTHEDOCS', None) == 'True'

if not on_rtd:  # only import and set the theme if we're building docs locally
    import sphinx_theme
    html_theme = 'stanford_theme'
    html_theme_path = [sphinx_theme.get_html_theme_path('stanford_theme')]

# otherwise, readthedocs.org uses their theme by default, so no need to specify it

Editing the theme

The theme is primarily a sass project that requires a few other sass libraries. I'm using bower to manage these dependencies and sass to build the css. The good news is I have a very nice set of grunt operations that will not only load these dependencies, but watch for changes, rebuild the sphinx demo docs and build a distributable version of the theme. The bad news is this means you'll need to set up your environment similar to that of a front-end developer (vs. that of a python developer). That means installing node and ruby.

Set up your environment

  1. Install sphinx into a virtual environment.
pip install sphinx
  1. Install sass
gem install sass
  1. Install node, bower and grunt.
// Install node
brew install node

// Install bower and grunt
npm install -g bower grunt-cli

// Now that everything is installed, let's install the theme dependecies.
npm install

Now that our environment is set up, make sure you're in your virtual environment, go to this repository in your terminal and run grunt:

grunt

This default task will do the following very cool things that make it worth the trouble.

  1. It'll install and update any bower dependencies.
  2. It'll run sphinx and build new docs.
  3. It'll watch for changes to the sass files and build css from the changes.
  4. It'll rebuild the sphinx docs anytime it notices a change to .rst, .html, .js or .css files.

About

Sphinx themes ("stanford" and "neo-rtd") based on readthedocs.org

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • CSS 84.9%
  • HTML 7.7%
  • JavaScript 3.7%
  • Python 2.6%
  • Makefile 0.9%
  • Shell 0.1%
  • Ruby 0.1%