···11+---
22+layout: post
33+title: Formatting Showcase
44+author: arthur
55+tags:
66+ - meta
77+---
88+99+This post exercises the theme's text formatting so you can see how everything looks together.
1010+1111+## Headings
1212+1313+# Heading 1
1414+## Heading 2
1515+### Heading 3
1616+1717+## Prose
1818+1919+Regular paragraph text sits at `1.125rem` with a line-height of `1.65`. It should be comfortable to read at length without feeling either cramped or too airy. Links [look like this](#) and are underlined by default.
2020+2121+**Bold text** and *italic text* and `inline code` all work as expected. So does ~~strikethrough~~.
2222+2323+## Lists
2424+2525+Unordered:
2626+2727+- First item
2828+- Second item
2929+ - Nested item
3030+ - Another nested item
3131+- Third item
3232+3333+Ordered:
3434+3535+1. Write the first draft
3636+2. Let it sit overnight
3737+3. Edit with fresh eyes
3838+4. Publish
3939+4040+## Blockquote
4141+4242+> Typography is what language looks like.
4343+>
4444+> — Ellen Lupton
4545+4646+## Code block
4747+4848+```ruby
4949+module Jekyll
5050+ class LinkPost < Generator
5151+ def generate(site)
5252+ site.posts.docs.each do |post|
5353+ next unless post.data["source"]
5454+ # fetch metadata and enrich the post
5555+ end
5656+ end
5757+ end
5858+end
5959+```
6060+6161+## Table
6262+6363+| Feature | Supported |
6464+|---------|-----------|
6565+| RSS Feed | Yes |
6666+| JSON Feed | Yes |
6767+| Dark mode | Via `theme.css` |
6868+| Pagination | Yes |
6969+| Archives | Yes |
7070+7171+## Horizontal rule
7272+7373+---
7474+7575+That covers the basics.
+25
_posts/2026-02-10-using-categories-and-tags.md
···11+---
22+layout: post
33+title: Using Categories and Tags
44+author: arthur
55+categories:
66+ - Notes
77+tags:
88+ - jekyll
99+---
1010+1111+Linus supports both categories and tags, and they work a bit differently from each other.
1212+1313+**Categories** are high-level buckets — broad enough that most posts could fit into one or two. They get their own archive pages at `/:name/` and can be assigned colors in `_config.yml`:
1414+1515+```yaml
1616+category_colors:
1717+ - name: Links
1818+ color: "#f0e68c"
1919+ - name: Notes
2020+ color: "#fa8072"
2121+```
2222+2323+**Tags** are more granular and exploratory. Use them for topics you want to be able to browse across, knowing that the archive page at `/tag/:name/` will pull everything together.
2424+2525+The practical difference: a post about a CSS trick might be categorized as *Notes* and tagged `css` and `design`. The category describes the post's format; the tags describe its content.
+8
_posts/2026-02-20-link-no-title.md
···11+---
22+layout: post
33+title: ""
44+author: arthur
55+categories:
66+ - Links
77+source: https://jekyllrb.com/docs/themes/
88+---
+32
_posts/2026-03-05-typography-and-the-web.md
···11+---
22+layout: post
33+title: Typography and the Web
44+author: arthur
55+tags:
66+ - design
77+ - css
88+---
99+1010+Web typography has a reputation for being hard to get right. In practice, most of the work comes down to a handful of decisions made early: a readable typeface, a comfortable line length, and enough vertical rhythm that the page feels settled rather than cramped.
1111+1212+## Line length
1313+1414+The classic guidance is 45–75 characters per line for body text. Much shorter and the eye is constantly wrapping; much longer and it struggles to track from the end of one line to the start of the next. This site keeps body text at around 420px, which lands in that range for most screen sizes.
1515+1616+## Vertical rhythm
1717+1818+Spacing between elements should feel consistent — not identical, but *proportional*. Setting a base unit (say, `1rem` or `1.5rem`) and deriving margins and padding from it keeps things coherent without needing to hand-tune every element.
1919+2020+## Typefaces
2121+2222+Linus ships with [Atkinson Hyperlegible](https://brailleinstitute.org/freefont), a typeface developed by the Braille Institute with legibility as the primary goal. Each character is designed to be as distinct as possible — helpful for anyone with low vision, and quietly pleasant for everyone else.
2323+2424+```css
2525+body {
2626+ font-family: "Atkinson Hyperlegible", system-ui, sans-serif;
2727+ font-size: 1.125rem;
2828+ line-height: 1.65;
2929+}
3030+```
3131+3232+The numbers are less important than the intention: make the text comfortable to read for a long stretch.
+8
_posts/2026-03-10-short-note.md
···11+---
22+layout: post
33+author: arthur
44+categories:
55+ - Notes
66+---
77+88+Switched from using `bundle exec` prefixes everywhere to setting `BUNDLE_BIN` in my shell config. Saves a few keystrokes per command, which adds up over a day of development. Small quality-of-life things compound.
+13
_posts/2026-03-15-link-post-demo.md
···11+---
22+layout: post
33+title: The Unreasonable Effectiveness of Plain Text
44+author: arthur
55+categories:
66+ - Links
77+source: https://www.plaintextproject.com/
88+tags:
99+ - writing
1010+ - tools
1111+---
1212+1313+A good overview of why plain text continues to outlast every productivity format that's come and gone. The point about longevity is the one that sticks: a `.txt` file written in 1985 still opens today without any compatibility dance.
+18
_posts/2026-03-22-on-writing-with-plain-text.md
···11+---
22+layout: post
33+title: On Writing with Plain Text
44+author: arthur
55+tags:
66+ - writing
77+ - tools
88+---
99+1010+There's something clarifying about writing in a format that has no toolbar. Markdown strips away the surface-level decision-making — bold or italic, which heading size, what font — and forces the question back to what the sentence is actually doing.
1111+1212+I've been writing in plain text for years now. Everything from notes to long drafts lives in `.md` files, version-controlled, backed up, portable across every device and editor I'll ever use. The format will still open in 2040.
1313+1414+The tradeoff is that rich media requires a bit more intention. Embedding a video or adding a caption to an image takes a line of HTML, not a drag-and-drop. I've come to see that friction as a feature. It slows me down enough to ask whether the thing I'm adding actually belongs there.
1515+1616+> The best writing tools are the ones that disappear while you work.
1717+1818+I keep coming back to this idea. A tool that stays invisible is one you've stopped fighting with. For me, that's a plain text file and a consistent publishing workflow. It might be something else entirely for you.
+42
_posts/2026-03-28-welcome-to-linus.md
···11+---
22+layout: post
33+title: Welcome to Linus
44+author: arthur
55+tags:
66+ - jekyll
77+ - blogging
88+---
99+1010+Linus is a minimal Jekyll theme built for personal blogs. It's designed to get out of the way and let the writing breathe — no heavy JavaScript, no complex build pipelines, just a Gemfile and a text editor.
1111+1212+## What's included
1313+1414+Out of the box you get:
1515+1616+- **Pagination** — posts are listed 12 per page
1717+- **Archives** — browseable by tag, category, month, and year
1818+- **Feeds** — both RSS and JSON Feed are generated automatically
1919+- **Link posts** — share links with optional commentary and rich previews
2020+- **Multi-author support** — define authors in `_data/authors.yml`
2121+- **SEO tags** — `jekyll-seo-tag` handles meta and Open Graph
2222+2323+## Getting started
2424+2525+Install the gem and add it to your `_config.yml`:
2626+2727+```yaml
2828+theme: linus
2929+```
3030+3131+Then run:
3232+3333+```bash
3434+bundle install
3535+bundle exec jekyll serve
3636+```
3737+3838+Your site will be live at `http://localhost:4000`.
3939+4040+## Customization
4141+4242+Drop a `assets/css/theme.css` into your site to override any styles — it's loaded last. You can also add `_includes/head.html`, `_includes/below-post.html`, or `_includes/end.html` to inject content at specific spots in the layout without touching theme files.