darthmall / darthmall.net Goto Github PK

I don't feel like I've good a handle on all the bits of the site. It feels like I keep making one-off adjustments to the CSS when I write a new post with no idea how that affects older posts.

I think it may be worth revisiting Bread Frost's Atomic Design.

I'd like to create a pattern library in Eleventy alongside the site and either not have it publish, or just not link to it.

Write up some of the side projects I have in mind. Also, what bane side projects are.

For showing the evolution of code examples, it would be nice to present the old and new versions of the code with toggles to view the new version, old version, or the side-by-side diff.

The archive of posts should provide links to pages per tag.

The tags can help give people some idea of what the post is about (at least theoretically). They should be links to lists of articles with those tags so that people can find related articles.

Redesign the home page to list some number of the most recent articles instead of just being a navigation page.

• Convert posts list to a macro
• Convert date format to a shortcode
• Convert posts collection to a custom collection (instead of using tags)
• Create a recentPosts collection, configured in the site metadata
• Add a recent posts lists to the home page in lieu of the navigation

Partially to satisfy my own curiosity, partially to give an indication of the length of the post.

Write up a quick post about the new in-public redesign.

Begin the public redesign by stripping the styles down to the bare minimum for a readable site.

• Convert Sass to vanilla CSS
• Strip styles down to simple colors and basic typography

Display the tag cloud below the posts.

Display the tag cloud below the most recent posts. This provides some insight into the kinds of things that have been written about and also offers more links into the blog.

Generate social images for each page if they don't have one specified. It may be useful to override this with front matter so that some pages—such as portfolio projects—can set an image.

My philosophy behind using {% extends %}, {% include %} and macros (including the use of {% call %}.

I think markdown-it-anchor somewhat recently altered the way they handle markup to make it more accessible. I should make sure I'm generating accessible markup for those anchors, preferably with the plugin, rather than writing my own transformation to do it for me.