Since this site is itself a demo of the guild theme, I thought I’d make this post also a collection of my ongoing todo list for the theme.
features
- button shortcode
- youtube shortcode
- default one is great for normal stuff, consider one for embedding the channel, certain playlists, etc.
- twitch embedding?
- maybe img shortcode with left/right/fit option
- the figure shortcode can be used, but doesn’t seem any shorter or better than using raw html
<img>
tags.
- the figure shortcode can be used, but doesn’t seem any shorter or better than using raw html
- disqus integration with frontmatter toggle
- image/vid gallery (photoswipe + template to embed a dir, external galleries?), instagram, battle.net, etc.
- relref shortcode that automatically pulls in title (I miss wikilink syntax)
- make the discord and (maybe) warcraft logs widgets auto-refresh / update status without a page reload.
layout
- Make description show in list/summary views on home page, etc.
- Add tag/category display (and create terms templates)
- fix css and semantic html for taxonomy groups in content-taxonomy-groups.html : it’s pretty odd to have unordered lists that don’t contain any list elements themselves, just additional unordered lists…
- anchor padding fix for sticky navbar height (kinda fixed - hacky : would prefer a less brittle solution)
- fixed/parallax scroll for bottom image
- pagination for news and other lists
- home page organization - first N news posts, followed by first Y non-news posts, depending on pagination
- Actually, that should be half a check… Need to restrict the sections to the correct types.
- check for sanity on non-existent taxonomy and case sensitivity (currently case sensitive, which is probably bad - accidentally set category to ‘news’ instead of ‘News’ and it doesn’t show… looks like v18 vs. 18.1 vs 19 issue)… Looks like urlize() lowercases the tag, but in hugo v0.18 it builds the actual dirs with the actual taxonomy name and term name. Until can be sure of building with v0.19, make sure to put lowercase names in taxonomy names and term names.
- News sorting: first N news posts, sorted by weight, then time (therefore allowing pinning by setting weight higher) - turns out, already was.
- Actually, that should be half a check… Need to restrict the sections to the correct types.
- padding after read more on lists and on home page posts in general
- create css class for hugo/blackfriday/markdown rendered github tasklist syntax
- css classes are
task-list
andtask-list-item
- also consider whether to extend the checkbox / listitem css support in general beyond the +label version that is in there.
- css classes are
- consider list item padding after indented lists, such as shown right here. Fairly large top padding… reduce? Also, wrap around checkbox indent vs. left justify
- font awesome tag, category, author icons
- go through main.css, review Descendant selectors for sanity
- ul.alt li for example vs. ul.alt > li : using alt to style summary post divisions led to li in the actual post footer having borders … have done a quick round of looking at it, but needs review and specific attention
- if disqus comments are enabled and there are any, give count in summary
- in post footer, better align the taxonomy lists and the read more button
- On iPad, layout switched to sidebar below even though it didn’t used to, and doesn’t when using responsive design testing emulating iPads. Figure out what’s going on with the viewports and media selectors
- Make menu switch to dropdown menu instead of vanishing at smaller widths (added navpanel from Archetype back in …)
- convert from navpanel to doing it as a dropdown menu?
- expand navbar support for config menu specified multilevel menus
- font sizes at different screen sizes/resolutions… looking pretty small on a phone… update media selector sections as needed.
- add support for posts flexbox multiple article mini-pane type display variant for home page, etc.
other
- demo non-farsight images and gradients for banners, etc.
- header_custom and footer_custom documentation (plumbed already - document)
- create demo page for other css elements (See “Banners, logos, and fonts (oh my!)”)
- consider gulp/grunt/brunch/etc. and minify workflow (see http://www.pghale.com/post/hugo--brunch-goodbye-jekyll/)
- cleanup guild.js
- check site speed / optimization
- check hugo warnings
- fix
.Now
warnings- check that using the template
now
is going to work with hosting provider (it doesn’t pre v19 which isn’t released yet, so rolled back to .Now)
- check that using the template
- fix
- doublecheck all the urls for relURL issues, and root vs. subdir hosting issues
- consider issues with using relURL with anchor tags, as in navbar, etc.
- document findings…
- consider behavior of specifying urls in config.toml, etc., in relation to
safeHTMLAttr
issues, anchor tags, etc. as described here - implement the featured image stuff for posts, or remove the left overs
- theme docs, from git and hugo on down through css examples
- shortcodes in config.toml strings… punting for now, but is it a good idea? How could it be done? Example usage would be about string containing a figure or youtube shortcode, etc.
- li content view: make better, include taxonomy data
- review css again and clean up extras, esp. examining the media selector sections
- Hugo is not setting
.Truncated
to false when expected. Debug. - BlackFriday/smartypants is not correctly doing a smart doublequote from a quote inside the description param in a page’s front matter.
- add navigation elements for seeing all news and all posts, etc.
- bounds/sanity check missing params in templates, ex. missing author, etc. basically anything set in config.toml or the front matter
- Go through everything again, with DRY in mind. Use partials with
(dict "content" . "anotherparam" $whatever "yetanother" $theOtherThing)
etc. or use.Scratch
- Make sure everywhere that uses info from the config file like Description, About, etc. is rendering the markdown if appropriate vs. sticking raw markdown in rendered fields. Example, the og: stuff in headers, etc.