Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Navbar in the documentation site #870

Open
deka27 opened this issue Mar 18, 2024 · 3 comments
Open

Issue with Navbar in the documentation site #870

deka27 opened this issue Mar 18, 2024 · 3 comments
Labels
category:web category:Web

Comments

@deka27
Copy link
Contributor

deka27 commented Mar 18, 2024

Navbar display bug

The documentation site has a small issue. Only for the API reference page, the Navbar is showing a separate look than normal.

I am not quite sure why it is loading like that, navbar should be loaded based on configuration in conf.py for all pages.

This is Normal (other pages are all fine)

image

This is for API Reference page (tutorials also behaving same)

image

I will check this.

@skoudoro
Copy link
Contributor

good catch and thank you for looking into this

@deka27
Copy link
Contributor Author

deka27 commented Mar 20, 2024

@skoudoro I am not sure why but I am not able to reproduce this bug on local at all. I have tried cloning the repo again with a clean installation.

For me it shows like this, it doesn't have that old style of navbar.

API Reference Page
image

Tutorials Page
image

I am not sure how exactly to tackle this problem on local.


After looking around, I checked the GH-pages repo for the website. I see that some of the pages are not updated from the new build.

  • reference > index.html

image
image

  • auto_examples > index.html
    image
    image

I am assuming this might be why the api reference and tutorial pages are still using the same old style of things. (Because the build didn't get updated for those specific folders and the index.html file remained the same).

Please let me know if this might be the reason.

@skoudoro
Copy link
Contributor

I see, make sense, thank you for the analysis. this fix is part of the GSoc Project 1. Modernize FURY Codebase.

Meaning we need to update how we deploy the fury website. For now, it will stay like that unfortunatly

@WassCodeur WassCodeur added the category:web category:Web label Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:web category:Web
Projects
None yet
Development

No branches or pull requests

3 participants