[why]
The previous fix broke the instances of the subtitle circle in all the
other topics (Downloads, CheatSheet, Backers, ...) because it rendered
the circle too wide horizontally, while the vertical size was ok.
[how]
The previous previous fix with a concrete circle hight and width and
adequate line spacing for the filling font works better. The circle is
not absolutely circular, but roughly it is.
Unless there is a Web magician who can fix this in a better way I
believe the not-really-circular in one place (all-icons-divider) is
better than absurdly wide circles in all section subtitles.
Fixes: #1384
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Testing with Firefox 113 and Chromium 118 the eveness of the round
circle might be improved a bit by using a slightly different font size.
Well, I did this on Linux, maybe the rendering is different on other
Platforms? We will see.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
This reverts commit 20da768954.
The problem is solved more elegantly by the next commit
Issue with Subtitle Circle and Layout on Smaller Screens #1384 fixed
[why]
The Star and Fork buttons sometime show nicely, sometimes they are just
plain linked tect with no count and no icon and nothing.
[how]
The reason is not completely clear, sometimes it works and without any
change after a complete reload it does not work anymore.
The most likely candidate is the Github rate limit that we run into for
cross repo access. To avoid that we just copy the button script into our
repository. The rate limit will now not apply anymore.
But of course we will also not get any updates. That needs to be checked
from time to time manually - as with the Github actions.
Strange is already that the current script from github.io is version
2.27.0 while the latest release on the repo is 4.2.2. The date is the
same (Dec 2022).
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The navbar should only be one line, switching to smaller and smaller
items, until we reach a very small size (the smallest) where we finally
allow it to overlow into the next lines.
But that is not the case, the navbar switches between one and two lines
already at medium sized screens.
[how]
Correct the width point when the navbar titles switch from long-titles
to short-titles.
Introduce new width switch point that reduces the cell widths of the navbar
one they become very full and further reduction in width would result in
overflow into the next line.
Tested on Netscape and Chromium; the later needs bigger numbers (hmm)
Fixes: #1375
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
In the small screen version the all-icons section divider becomes
ellyptic or something, not round anymore.
[how]
When scaling down we do not scale the line spacing down enough.
Fixes: #1376
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Some code has been commented out. This can be removed. We can use git if
we want to access the code again in the future.
Furthermore the banner still is on the page, below the Sanky diagram (in
the small screen rendering position).
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The link on the floating Github button explicitely opens the master
branch. We could instead just link to the default branch (which is
technically more correct anyhow).
[how]
Drop branch specification from URL and use default branch.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Keep the dependencies as small as possible.
We already have the github icon in our own set which we import anyhow,
so there is no need to fetch fontawesome's CSS.
[how]
Replace fa-github with nf-fa-github.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
the subtitle-icon class is added in div.row elements for the features section and i also foun the some issue the terminal fonts so a media query is added to fix the same in terminal font section
[why]
There are cases that I find myself into sometimes when I have the glyph
with me but not its name or codepoint. It would be nice to be able to
search for the codepoint and/or name of a glyph by literally putting it
into the search box of the cheat-sheet.
There are several reasons to know the name of the glyph, to use it in a
webpage, to look for alternatives when they get removed, etc.
[how]
Convert high codepoint-chars to codepoint text.
Fixes: #1307
Authored-by: ad-chaos
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
