mark a bunch of posts as featured

content/posts/alloy.md

@@ -5,6 +5,7 @@ description = "Making models in Alloy is fun and useful!"
 
 [extra]
 project = "learning Alloy"
+featured = true
 +++
 
 [Alloy](http://alloytools.org/) is a tool for modeling software. It's best at representing things like databases or data structures, but in my experience it does fine with things like UI states or processes as well.

content/posts/digital-gardening-in-obsidian.md

@@ -2,6 +2,9 @@
 title = "Digital Gardening in Obsidian"
 date = 2022-12-26
 description = "Observing growth in my notes without being overwhelmed."
+
+[extra]
+featured = true
 +++
 
 I have been using [Obsidian](https://obsidian.md) for all my notes for something like 6 months now. That's really *everything*, from temporary measurements to journaling to serious documentation work. I've tried Obsidian a couple of times before and bounced off of it, so I decided to try to do things differently this time. Instead of starting out by figuring out a system for where everything lives in advance, I've just thrown almost everything in the default folder and sorted it out with linking and search.

content/posts/elo-anything.md

@@ -2,6 +2,9 @@
 title = "elo-anything"
 date = 2020-11-24
 description = "using the Elo rating system to sort items in our backlog."
+
+[extra]
+featured = true
 +++
 
 Part of my job as a team lead is dealing with a big list of work that my team is responsible for, but which we're not going to do immediately.

content/posts/modeling-database-tables-in-alloy.md

@@ -5,6 +5,7 @@ description = "chasing out edge cases in a schema"
 
 [extra]
 project = "learning Alloy"
+featured = true
 +++
 
 Formal methods tools like Alloy are not just for proving correctness properties in distributed systems (or whatever) but can be a useful tool for mere mortals like me! [As I mentioned previously](@/posts/alloy.md), I've been using Alloy to help me avoid data modeling mistakes before they're encoded in hard-to-change places, like database schemas. In this post, I'll show my thought process as I use Alloy to model the schema for a project for my makerspace, including some of the mistakes that Alloy helped me avoid.

content/posts/nix-script.md

@@ -1,6 +1,9 @@
 +++
 title = "nix-script"
 date = 2021-02-23
+
+[extra]
+featured = true
 +++
 
 I like writing quick little scripts to avoid having to remember how to do things.

content/posts/state-transition-tables.md

@@ -2,6 +2,9 @@
 title = "state-transition tables"
 date = 2020-10-13
 description = "A simple exercise to check our thinking about state."
+
+[extra]
+featured = true
 +++
 
 I was reading Wikipedia the other day (as you do) and found out about [state-transition tables](https://en.wikipedia.org/wiki/State-transition_table).

content/posts/tree-grepper.md

@@ -2,6 +2,9 @@
 title = "tree-grepper"
 description = "search by AST nodes instead of strings"
 date = 2021-08-31
+
+[extra]
+featured = true
 +++
 
 A while ago I wanted to build an import graph from all the frontend code at NoRedInk to build some developer tools.

templates/posts.html

@@ -9,6 +9,7 @@
   <dt>{{ year }}</dt>
   {% for page in pages %}
   <dd>
+    {% if page.extra.featured %}⭐️{% endif %}
     <a href="{{page.permalink | safe }}">{{ page.title | markdown(inline=true) | safe }}</a>{% if page.date %}, <em>{{ page.date | date(format="%B %-d, %Y") }}</em>{% endif %}
   </dd>
   {% endfor %}