-
Notifications
You must be signed in to change notification settings - Fork 24
Fix stray HTML tags. #324
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
base: master
Are you sure you want to change the base?
Fix stray HTML tags. #324
Conversation
✅ Deploy Preview for neo4j-docs-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
{{!-- <img class="navbar-logo" src="https://dist.neo4j.com/wp-content/uploads/20230926084108/Logo_FullColor_RGB_TransBG.svg" alt="{{ site.title }}" /> --}} | ||
<a href="/graphacademy/online-training/" class="navbar-item no-left-padding page-name-white" aria-label="GraphAcademy"> | ||
GraphAcademy | ||
</a> | ||
{{else if (eq page.attributes.theme "graphgists")}} | ||
<img class="navbar-logo" src="https://dist.neo4j.com/wp-content/uploads/20231023102534/neo4j-logo.svg" alt="{{ site.title }}" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Content is still published with themes that have a dark header background so we do still need to use this image
eg
- https://neo4j.com/graphgists/ (graphgists theme)
- https://neo4j.com/developer/genai-ecosystem/ (developer theme)
- https://neo4j.com/developer/kb (kb theme)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ouch, thanks. The commented out lines probably confused me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, all the different themes and layouts are confusing for sure. There's probably files in there that should be deleted as well, but I keep thinking - is it worth the effort, or are we better off starting from scratch with a new version?
Pages currently have two stray tags - major browsers seem to render them well anyway, but there's no good reason to rely on that.
To fix the missing closing
</a>
in the logo link, I also incorporated the fact that we've retired developer guides, so that an extra logo (white logo on black background) is not needed anymore. If this assumption is not valid, I'll revise.