tags: tufte, blog
Well, tonight is the night. I got the site design to where I'd like it to be. It's simple, easy to read and very fast. I tried looking at it in a couple of different view ports using Safari's Responsive Design Mode and it made me even more sure about what I'm doing here.
This is a message to me that I can complete the goals that I set out to do. It might take me a while but this has been so worth it.
Well, the initial design is done but there are a couple more things that I should probably finish up.
- Finish the rest of the tags (marginimage, columnimage)
- Add the analytics Not a real priority because I don
- Clean up the Archive page
- Create a 404 page
- Decrease the spacing between multiple footnotes1
- Clean up the regular expressions used to parse for the plugins During the process of trying to figure out how to do this theme, I spent a lot of time whether to do this in pelican as a plugin or the python markdown. I am happy that it is working but I am not happy with how fragile it is.
- Discuss Comments
- Create options to make it easier to go to categories and tags
I've done a couple comparisons with other pelican templates and I feel that I should have some of this ready for other users who want to try out the Tufte style without worry so much about how it fits with what a website is supposed to do2.
Well, it is getting kind of late for me here and I've got to push the button to make this public to the world.
When I was first introduced to markdown, one of the things I thought was the coolest was the fact that you could have these little babies to put on the bottom of the page. If you look through my archieves you'll see that I use them off and on to do my writing. Some websites have them at the end or use a popup to show them when you click on them. I think I'll probably move to side and margin notes. Either way, when you get two or more they really start eating up space. ↩
It took me a lot of time to pick a template when I first came to pelican and even then I found myself modifying it. ↩