Some of the table of contents scss was recently used in the new Series navigation feature. (resulting in duplicated css)
My first thought was to try and eliminate some of the class based attributes entirely, however having some classes can also be a good thing where it makes sense because they allow you to reuse code where semantic html would actually result in duplicated code.
I think the first step is to create a minimal class structure for side blocks, eg: table of contents, recent posts block, or series navigation block, or any new blocks for that matter. They can all use the same class definitions.
In the process any superfluous classes or attributes should be removed.
Jieiku
commented
9 months ago
The table of contents originally came from juice: https://juice.huhu.io/
Some of the table of contents scss was recently used in the new Series navigation feature. (resulting in duplicated css)
My first thought was to try and eliminate some of the class based attributes entirely, however having some classes can also be a good thing where it makes sense because they allow you to reuse code where semantic html would actually result in duplicated code.
I think the first step is to create a minimal class structure for side blocks, eg: table of contents, recent posts block, or series navigation block, or any new blocks for that matter. They can all use the same class definitions.
In the process any superfluous classes or attributes should be removed.