My intention is to make it an 11ty site so that I can blog using markdown and git alone. Also, I want to build a repository of resources about certain topics to refer people to when they ask me questions.
Why does it look this way?
There is no CSS defining the styles. Everything you see will be based on your own default preferences in your browser. It will be that way until I get things working properly in terms of templating for pages and blog posts.
It’s just a very basic layout at the moment. I was playing around with learning some CSS grid for a bit, but realised that that can all wait. I prefer darker themes and one day you’ll get a toggle option to go to light or dark, but that’s a long time in the future. This site uses variable fonts , but not well… yet with some feature settings enabled..
Also, the site still needs some kind of footer.
Principals for this site
- WCAG 2.1 AA+ accessibility
- Rule of least power (described by Tim Berners-Lee and Noah Mendelsohn)
- Function over form
- Keep learning
- Low barrier to contribution
- Build in public
Markdown as default “word processing”
Principle 5 exists to make it as easy as possible for me to add things to this site. I started to find the WYSIWYG interface of WordPress too frustrating for me. In my every day work I write in Markdown if I’m not writing in longhand.
11ty uses markdown-it as its default Markdown parser. So I make use of it to save me some time and help me with some shortcuts like the footnotes you see on this page.
This site is hosted on Netlify which, if I’ve set this up correctly, will automatically build the site when I push changes to my git repository.
Right now, this whole site is about learning and there’s really a lot to learn. For best-use of variable fonts, I look to my friend Jason Pamental. He literally wrote the book on Responsive Typography. Another great book on the topic is Flexible Typesetting by Tim Brown (who is not my friend, but maybe because we haven’t met yet.) ↩︎
I still recommend WordPress. It’s all explained in the note about WordPress on the “About” page. ↩︎