- Use namespaced class names to prevent accidental name collisions in
the future
- Clean up whatever the hell I was doing with the flex config on the
outer series list. I have no clue why it's set up as a wrapping row,
or what the border radius is for. It seems to look the same if I just
make it a page-list that gets its gap overridden.
- Remove page.series wrapper around the summary card render which was
accidentally left in after 8eb343132c6b57f692f87a72a5aca1bc9c563d1b.
- Rename feature-figure.html and its class from post-media to
featured-media
- Move all <figure> formatting to a separate section
- Put the .featured-media CSS next to the rest of the figure formatting
as it's sorta a special case of regular figure
Originally I was using gap on a flexbox to separate the .sections
container from the rest of the page list. But it's simpler if I just use
block layout and a bottom margin, then I don't need an extra layer of
div.
Any element that can't stand on its own as a self-contained component
should have its naming nested under whatever parent it's supposed to
have.
Fixes#109
This must've gotten out of sync somehow throughout the history. It
slightly changes the margins by disabling the default one on h1, which
is slightly larger than the breadcrumb nav margin-block's.
Just in case I ever want to use the footer tag anywhere else on the
page. I'm not sure if I'm reading this right, but it sounds like it
would make sense to put all the buttons at the bottom of the content
pages as a footer as well. I will have to reconsider this again in the
future.
I think this version has the newest features that I'm using. Hopefully I
didn't miss/forget about something when skimming through the Hugo
release history just now.
Not sure what I planned to use this for. It has since become outdated
and out of sync with the new margins I set on body recently in
4e753395ba and
6b729c6acf.
When all related posts fit on the same screen, there was a useless
scrollbar. I never noticed this because Firefox incorrectly hides the
scrollbar automatically. The issue is visible on Chromium.
- Separate baseof.html elements from styling code for general elements
used everywhere
- Rename some of the fold titles
- Include related posts section styling in the content styling section
I think this may have changed in Hugo's history, but now description and
summary are considered different things. The description is what goes in
metadata (and what search engines see), while the summary is the blurb
about the article that should be displayed when rendering a summary
(what I should've been using always here).
This makes them more specific. For example, section.html can't
accidentally be a fallback for taxonomy.html, and page.html can't for
term.html.
Fixes#88
It's probably better structure-wise to have it all consolidated in
bobatheme. Then bbaovanc.com is only concerned about content, not stuff
that I declared to be specific to my site. This came from when I had
multiple sites running bobatheme in the background, so now it's just an
arbitrary, legacy distinction.
Fixes#86
