The monkey patch made for sphinx 1.6 was not complete. In comparison
to the one done for previous versions (resolve_toctree), navbarify was
not called.
In the toctree, the sub-levels were turned into a link in 1.6 while
navbarify prevents this.
fix Sphinx 1.6 compatibility leading to the "tiles" on the home page
not working anymore: 1.6 replaces BuildEnvironment.reolve_toctree by
TocTree().resolve(), while the method still exists it's not actually
called anymore
Programmatically setting html_translator_class is apparently broken in
Sphinx 1.5 (which sorta makes sense, it's a bit of a hack, I'm not sure
why we even did that instead of going through the configuration object).
— Layout
* Create html templates to print breadcrumb's and submenu's lists.
* Remove ‘o_main_back’ ( no longer needed)
* Minimum mobile support for submenu. Note: The default website submenu
should be refactored in order to support mobile by default
— Style
* Create a less mixin to handle all doc’s dropdowns
* Add a specific style for breadcrumb when it’s placed inside the
submenu.
It was invisible because the doc’s website use material icons rather
then the ‘fa’ ones. Replaced the icon with the material one and styled
the “pressed” state.
* upgrade to bootstrap 3.3.6
* new Header, port website LESS
- Add the new header
- Modify sub-header in order to handle “back” button and version
switcher
- Port website’s Less:
* Use same variables’ names
* Review fonts and colours in order to fit the new style
* add new footer
* Review and optimise JS code in order properly handle the new header,
footer and card.top animations
* replace banner images
app.add_node doesn't work right for custom translators in 1.2, since
mementos are using ``h:div`` reimplement that in the
BootstrapTranslator.
Alternative would be to monkeypatch app.add_node for Sphinx 1.2, but
let's not do that...
Sphinx.set_translator is a Sphinx 1.3 API, and we only require Sphinx
1.2 at this point. Replace the use of set_translator with explicitly
setting the html_translator_class config setting.
Coming from the Odoo technical documentation, fix done by @xmo-odoo. See
odoo/odoo/commit/a139d81c46b669fa9186ceaf2a0ca43fb0601e1c.
Bootstrap forces the img-responsive images to be a block.
IMHO bootstrap should be killed and burned with fire but them it appears I know
nothing (John Snow) about CSS and making things looks nice so they have probably
their reason to do so.
Anyway, not that I care, let me use inline images for Flupke sake!
