I’ve now got a Hugo module (so others can easily incorporate into their themes from a canonical source, rather than the problem of copying the code as boilerplate and the associate divergence) that implements the original idea only, I think, better.
FYI I’ve done a ‘bunch’ more work on this, and like the results. I’ve parameterized the the table generation so that hopefully it will be easier to add/remove fields as Hugo gains/loses variables. In addition I’ve added classes to the html elements and created a basic static CSS for testing. I think the test CSS actually improves the readability of nested tables (by ‘popping’ them up and enlarging when opened).
Hopefully I can now be satisfied enough with this that I actually get back to the theme I was originally working on…
Thank you, and sorry for taking so long to respond (I’m working on updating the exitwp-for-hugo Python script for Python 3 to move my WordPress sites to Hugo; the script also was rather dated and wasn’t doing everything I want). I’m definitely interested in taking a look to see if there is useful stuff there.
So, much later than planned, I am circling back to Hugo tasks.
I have created a new
repository and will be pointing the old version at this version and archiving the old version.
I have done this because things got a little bollixed when tried to do my own git hosting, plus I got away from the minimal theme with my minimal test theme, so I’m reworking (and renaming) the various repositories which are, and will remain on, GitHub, for my hair’s sake (what’s left of it).