Simplify, mofo!

[badlydrawnrob]

UPDATE 2023: Why should I give a fuck?

e.g: 4 days worth of work and I feel like I've barely scratched the surface:

• Installing the software required
• Refactoring code and minor updates to files
• Copious amounts of Google searches and document reading
• Issues, issues and more issues (documentation)
• Note taking and abstract thinking about problems
• And on, and on, and on, ...

... Little wonder Computer Science drop-out rates seem to top the charts!

CSS it too damn slow (to create)

It takes forever just to get a simple CodePen working, unless the css is super simple. Anything with a butt-load of html starts to get more time consuming — especially if you're trying to reason about and override someone else's code (like Pandoc's Skylighting)

It's quite infuriating. 💩

WSIGAF?

Currently the only repos including print-first-css is Anki themes which, I don't think is sticking to the baseline grid; and Print First CV

Why should I give a fuck? That's a great question to ask yourself whenever you consider working on a new feature/update. The file system is a bit nebulous and I'm beginning to wonder if humans really want to print out a webpage anyway. Do I really need to create a CV page created in code? Does it really need to be designed? Does anybody actually give a shit about this repo?

No, no, and probably no.

On Design Systems

A general rule is Reduce, Reduce, reduce!!! (succinct and distilled)

• [ ] Don't make me think!
• [ ] It's weird how design systems are so rote, yet so difficult Y combinator thread
• [ ] ⭐ Pico CSS and Tailwind
• [x] Material Design is a monster of a design document. Yikes.
• [x] Brutalist design — ugly or elegant?
• [x] Use boring technology where appropriate!
• [ ] Using the right Typography for the job (a CV or an Anki tool)

  • 49 (Typography has a lot of sizes)

• [ ] What happens with a new font? (font-size / line-height combinations)
• [ ] #42 (use stock CSS wherever possible)
• [ ] #40 it's difficult to stick to as a design develops, such as the font you use or components.
  • [x] Things like --font-tracking are a luxury I don't need.

On Writing Styleguides

• [ ] Don't make me think!
• [ ] #10 (improve this document**

Some other considerations:

• [ ] #24
• [ ] Look to simple, easy to build guides for inspiration.
• [ ] Accessibility in writing?
• [ ] Boxes and child themes (see below)*

[badlydrawnrob]

I need to consider which "box" this repo fits in; which purpose it solves.

• [ ] Only the essentials (print-first-css)
• [ ] Possible additions (for each other box)
• [ ] Best route to add "child themes"
  • search other examples (like Pandocs templates)
  • see syntax highlighting library as an example here and here
  • or, one repo for each individual purpose

You'd need Markdown styleguides, as well as .less or .css files

The default print-first-css ...

Potential child themes ...