We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The tag pages don't inherit the styles properly.
For example https://tlienart.github.io/FranklinTemplates.jl/templates/hyde/tag/syntax/
Suggested fix: Change the line from <div class="{{div_content}}"> to <div class="franklin-content"> in _layout/tag.html.
<div class="{{div_content}}">
<div class="franklin-content">
_layout/tag.html
The text was updated successfully, but these errors were encountered:
thanks for reporting, {{div_content}} by default inserts franklin-content so I need to investigate why that wasn't the case for you.
{{div_content}}
franklin-content
Would you mind pointing me to a commit before you applied your resolving fix so I can experiment with hit?
Sorry, something went wrong.
Thanks for your response. I don't have a commit to point you to yet, because I was trying it locally. But if needed, I can create a dummy repo.
But I am wondering, are they working as expected in your own repo? For example https://tlienart.github.io/FranklinTemplates.jl/templates/hyde/tag/syntax/ . I am seeing this page broken, as shown in the screenshot.
Thanks, actually that link was all I needed to look at, I should have looked at your first comment properly.
So here the problem is that the {{div_content}} is not properly filled, I'll look into it. Thanks (and indeed now your fix makes sense).
No branches or pull requests
The tag pages don't inherit the styles properly.
For example https://tlienart.github.io/FranklinTemplates.jl/templates/hyde/tag/syntax/
Suggested fix:
Change the line from
<div class="{{div_content}}">
to<div class="franklin-content">
in_layout/tag.html
.The text was updated successfully, but these errors were encountered: