As in, doesn't matter if the site is using Trix or Lexxy or Tip Tap or Markdown, doesn't matter if it's ERB or React, I need the entire routing / controller / modeling process to be consistent without dropping the ball on quirks like URL slug generation, etc.

That’s the hope!

Bike tours are my favorite tourist activity because you cover so much ground but get to see it up close.

Especially on day one of a trip because it orients you for the rest of your stay.

I would really just love the unified inbox of iOS Gmail app in a desktop tab or client and it would be perfect on its own.

If you have an auto setting, I feel like auto should be the default, and you should let people 'override' via using the other two settings. Like - "I use AM light mode / PM dark mode in a bunch of places but I just don't want it in this app, please stick to light mode 24/7"

As a customer I appreciate that. If I want to run production on edge I have to embrace the sharp knives trade off it implies.

I have noticed that the "best" gems rarely seem to specify upper bound. I see it more on hobbyist gems, gems maintained by vendors who support dozens of languages, etc.

IIRC www.hotrails.dev/turbo-rails has a tutorial that is a To Do List app which feels like a similar pattern.

I think that depends on which pattern is already in your app. Like, it should be a higher level decision than just one component, unless that component is incredibly complex. But this feels like a turbo frame to me? IMO it’s an in-line edit, whether or not you choose to auto save.

An event has many event_notifications? So each row is a create/edit form on a given event_notification with something like type/duration values?

Maybe the edit element autosaves on user changes? Have to figure out whether to save when the entire event gets saved or when notification is edited.

Feels like a really common challenge/pattern in game development.

Manageable in a simple app I bet, but zero words vs minimal words is definitely a challenge.

For reference, here's what it does - the date strings eg "September 2025" don't shift left/right when the stable gutter space is reserved:

Looks like the arbitrary tag syntax version works great, however.

I'm actually not sure why this isn't the default scrollbar behavior to be honest... it's a better experience.

Nice. This one armed fella showed up in our garden last month and hung out for a few days in the rock garden.

And TIL, apparently they camouflage based on surroundings (and when molting). I had no idea. So yours might be matching the paint.

www.ipm.org/show/amoment...

Here is my CI - if you add `continue-on-error: true` at the job level and again at the step level, it will force your CI to pass and show ✅ even though you might have unresolved offenses.

At the pace Marco is going, I'm guessing this is useful short term before there is a `generate-todo`.

And if you don't have Claude Code filing Github Issues for you yet you should totally try it. It creates the cleanest markdown formatted Issues with acceptance criteria and tags and all that fun stuff.