GITHUB . COM {}

Detected CMS Systems:

Wordpress (2 occurrences)

Analyzed Page
Matching Content Categories
CMS
Monthly Traffic Estimate
How Does Github.com Make Money
How Much Does Github.com Make
Wordpress Themes And Plugins
Keywords
Topics
Payment Methods
Questions
Schema
External Links
Analytics And Tracking
Libraries
Hosting Providers

We are analyzing https://github.com/squidfunk/mkdocs-material/issues/5972.

Title:
Navigation indexes are not rendered correctly on the Blog index from the second page onwards · Issue #5972 · squidfunk/mkdocs-material
Description:
Context No response Bug description When using blog plugin with navigation.indexes feature, only the first page of the Blog index has the correctly rendered navigation. Other pages of the Blog index are rendered as if the feature is not ...
Website Age:
17 years and 9 months (reg. 2007-10-09).

Matching Content Categories {📚}

Social Networks
Books & Literature
Cryptocurrency

Content Management System {📝}

What CMS is github.com built with?

Github.com is built with WORDPRESS.

Traffic Estimate {📈}

What is the average monthly size of github.com audience?

🚀🌠 Tremendous Traffic: 10M - 20M visitors per month

Based on our best estimate, this website will receive around 10,666,346 visitors per month in the current month.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Github.com Make Money? {💸}

Subscription Packages {💳}

We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.

How Much Does Github.com Make? {💰}

Subscription Packages {💳}

Prices on github.com are in US Dollars ($). They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 5,347,483 paying customers.
The estimated monthly recurring revenue (MRR) is $22,459,429.
The estimated annual recurring revenues (ARR) are $269,513,148.

Wordpress Themes and Plugins {🎨}

What WordPress theme does this site use?

It is strange but we were not able to detect any theme on the page.

What WordPress plugins does this website use?

It is strange but we were not able to detect any plugins on the page.

Keywords {🔍}

blog, squidfunk, index, set, page, class, issue, bug, navigation, tags, commented, endif, rendered, minimal, features, indexes, correctly, pages, checked, path, label, open, sign, vedranmiletic, plugin, navigationindexes, reproduction, navitemactive, classmdnavlink, owner, resolved, projects, feature, enabled, posts, tagsextrafiles, indexmd, navitemchildren, expanded, smokedlinq, code, issues, pull, requests, discussions, actions, security, onwards, closed, description,

Topics {✒️}

md-nav__icon md-icon possibly related issues md-nav__link md-nav__container md-toggle--indeterminate open projects reproduce mkdocs serve bug resolved issue squidfunk closed bug reporting guidelines comment metadata assignees md-nav__item--section md-nav__item--pruned related links reporting md-nav__item--active md-nav__link--active bug takes place projects milestone correctly rendered navigation md └─ mkdocs discussions code blog index pages issue reported md-nav__item md-nav__link indexes feature indexes plugins bug setting bug report open blog/subset set tags_extra_files md extra index page blog index blog/index blog plugin blog archive blog link blog sites correctly check work correctly tags page called index group website intended navigate attached links posts directory nav-item {% macro render

Payment Methods {📊}

Braintree

Questions {❓}

Already have an account?
I guess I have the same error?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:Navigation indexes are not rendered correctly on the Blog index from the second page onwards
      articleBody:### Context _No response_ ### Bug description When using `blog` plugin with `navigation.indexes` feature, only the first page of the Blog index has the correctly rendered navigation. Other pages of the Blog index are rendered as if the feature is not enabled. Interestingly enough, this happens only when there is at least three pages of posts in the Blog index. Blog archive is affected the same way. I haven't checked if categories are affected since we don't use them. Additionally, if the `tags` plugin is enabled, the Tags page will exhibit the same behavior regarding the rendering of the Blog index in the navigation. I have not included this in the minimal example on purpose to keep it minimal, but it can be observed on [our group website](https://group.miletic.net/en/blog/tags/). I can prepare a less minimal example if needed. ### Related links - [Reporting a bug](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/) - [Setting up navigation](https://squidfunk.github.io/mkdocs-material/setup/setting-up-navigation/) ### Reproduction [9.2.8-navigation.zip](https://github.com/squidfunk/mkdocs-material/files/12526742/9.2.8-navigation.zip) ### Steps to reproduce 1. `mkdocs serve` 2. look at the navigation in first page of the Blog index 3. see it is rendered as intended 4. navigate to the second or the third page 5. see it is rendered as if it would be without `navigation.indexes` feature enabled ### Browser _No response_ ### Before submitting - [X] I have read and followed the [bug reporting guidelines](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/). - [X] I have attached links to [the documentation](https://squidfunk.github.io/mkdocs-material), and possibly related [issues](https://github.com/squidfunk/mkdocs-material/issues) and [discussions](https://github.com/squidfunk/mkdocs-material/discussions). - [X] I assure that I have [removed all customizations](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/#remove-customizations) before submitting this bug report. - [X] I have attached a __.zip file__ with a [minimal reproduction](https://squidfunk.github.io/mkdocs-material/guides/creating-a-reproduction/).
      author:
         url:https://github.com/vedranmiletic
         type:Person
         name:vedranmiletic
      datePublished:2023-09-05T18:06:22.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:7
      url:https://github.com/5972/mkdocs-material/issues/5972
      context:https://schema.org
      headline:Navigation indexes are not rendered correctly on the Blog index from the second page onwards
      articleBody:### Context _No response_ ### Bug description When using `blog` plugin with `navigation.indexes` feature, only the first page of the Blog index has the correctly rendered navigation. Other pages of the Blog index are rendered as if the feature is not enabled. Interestingly enough, this happens only when there is at least three pages of posts in the Blog index. Blog archive is affected the same way. I haven't checked if categories are affected since we don't use them. Additionally, if the `tags` plugin is enabled, the Tags page will exhibit the same behavior regarding the rendering of the Blog index in the navigation. I have not included this in the minimal example on purpose to keep it minimal, but it can be observed on [our group website](https://group.miletic.net/en/blog/tags/). I can prepare a less minimal example if needed. ### Related links - [Reporting a bug](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/) - [Setting up navigation](https://squidfunk.github.io/mkdocs-material/setup/setting-up-navigation/) ### Reproduction [9.2.8-navigation.zip](https://github.com/squidfunk/mkdocs-material/files/12526742/9.2.8-navigation.zip) ### Steps to reproduce 1. `mkdocs serve` 2. look at the navigation in first page of the Blog index 3. see it is rendered as intended 4. navigate to the second or the third page 5. see it is rendered as if it would be without `navigation.indexes` feature enabled ### Browser _No response_ ### Before submitting - [X] I have read and followed the [bug reporting guidelines](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/). - [X] I have attached links to [the documentation](https://squidfunk.github.io/mkdocs-material), and possibly related [issues](https://github.com/squidfunk/mkdocs-material/issues) and [discussions](https://github.com/squidfunk/mkdocs-material/discussions). - [X] I assure that I have [removed all customizations](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/#remove-customizations) before submitting this bug report. - [X] I have attached a __.zip file__ with a [minimal reproduction](https://squidfunk.github.io/mkdocs-material/guides/creating-a-reproduction/).
      author:
         url:https://github.com/vedranmiletic
         type:Person
         name:vedranmiletic
      datePublished:2023-09-05T18:06:22.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:7
      url:https://github.com/5972/mkdocs-material/issues/5972
Person:
      url:https://github.com/vedranmiletic
      name:vedranmiletic
      url:https://github.com/vedranmiletic
      name:vedranmiletic
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:7
      interactionType:https://schema.org/CommentAction
      userInteractionCount:7

External Links {🔗}(11)

Analytics and Tracking {📊}

Site Verification - Google

Libraries {📚}

Clipboard.js
D3.js
GSAP
Lodash

Emails and Hosting {✉️}

Mail Servers:

aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
alt3.aspmx.l.google.com
alt4.aspmx.l.google.com

Name Servers:

dns1.p08.nsone.net
dns2.p08.nsone.net
dns3.p08.nsone.net
dns4.p08.nsone.net
ns-1283.awsdns-32.org
ns-1707.awsdns-21.co.uk
ns-421.awsdns-52.com
ns-520.awsdns-01.net

8.96s.