Material no longer rendering awesome-pages config correctly
See original GitHub issueDescription
Hi, I’ve been using awesome-pages for a while now, but only with material docs v4. I tried upgrading to v7 but even the latest awesome-pages does not render out like the old way. Is there something wrong with my config or is this a clash with material docs.
What’s interesting is that the ordering is actually still working
I’ve created a sibling card on awesome-pages https://github.com/lukasgeiter/mkdocs-awesome-pages-plugin/issues/41
.pages
nav:
- index.md
- ...
- contributing.md
Old material docs
new
all links are tabs now
Expected behavior
I expect with the supplied .pages config, that my tab are rendered like the first image
Actual behavior
See image 3, the last image
Steps to reproduce the bug
- Set up directory with with the following structure
docs
├── contributing.md
├── developement\
├── getting-started.md
├── guides\
├── img\
├── index.md
├── office\
├── operations
- place other md files in sub dirs
- run mkdocs serve
Package versions
- Python:
Python 3.9.2
- MkDocs:
mkdocs, version 1.1.2
- Material:
Version: 7.0.6
mkdocs==1.1.2
mkdocs-awesome-pages-plugin==2.5.0
mkdocs-git-revision-date-plugin==0.3.1
mkdocs-material==7.0.6
mkdocs-material-extensions==1.0.1
Project configuration
static_templates:
- 404.html
# Don't include MkDocs' JavaScript
include_search_page: false
search_index_only: true
theme:
icon:
repo: fontawesome/brands/git-alt
name: 'material'
palette:
scheme: preference
primary: 'deep orange'
accent: 'light blue'
features:
- navigation.instant
- navigation.tabs
extra:
social:
- icon: fontawesome/brands/github
link: site
- icon: fontawesome/brands/slack
link: site
docs_dir: src
site_dir: 'target/'
plugins:
- search
- awesome-pages
- git-revision-date
# Extensions
markdown_extensions:
- meta
- smarty
- admonition
- codehilite
- footnotes
- pymdownx.arithmatex
- pymdownx.betterem:
smart_enable: all
- pymdownx.caret
- pymdownx.critic
- pymdownx.details
- pymdownx.emoji:
emoji_generator: !!python/name:pymdownx.emoji.to_svg
- pymdownx.inlinehilite
- pymdownx.magiclink
- pymdownx.mark
- pymdownx.smartsymbols
- pymdownx.superfences
- pymdownx.tasklist:
custom_checkbox: true
- pymdownx.tilde
# Required to load the MathJax javascript for the mdx_math.py
extra_javascript:
['https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS_HTML']
System information
- OS: MacOS BigSur 11.2.2
- Browser: Chrome
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Material icon not rendering properly - Stack Overflow
Caused because I was importing the material theme before the fonts in my theme.scss. Should be: @import url( 'https://fonts.googleapis.com/css?
Read more >Best Practices: Render Performance and Materials | Revit 2019
To balance performance, in Realistic views and Simplified accuracy in Render Quality Settings, Revit still uses low resolution textures.
Read more >Configuration - MkDocs
Configuration . Guide to all available configuration settings. Introduction . Project settings are configured by default using a YAML configuration file ...
Read more >Styling Components - Cypress Documentation
This guide will help you setup your test infrastructure to render your component's styles properly. Depending on how your application is built, the...
Read more >ASP.NET Core Razor components - Microsoft Learn
Non -page components are frequently placed in the Shared folder or a custom ... is used to switch to the correct context and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah I did, however it appears this is an awesome-pages issue as the supplied nav fix doesn’t work. This isn’t then a mkdocs issue but rather an awesome-pages issue. I’ll notify the developers of that plugin.
Have you read the comment I linked? It explains how to achieve the same result >= 6.2.
The code example applies to the community edition as it does to Insiders. It was merged some time ago.