#60 Non-default theme with Departure Mono 19 days ago

Comment by ~amolith on ~amolith/willow

If we currently, or plan to, rely on any font features like tabular figures, we need to make sure Departure Mono supports them before pulling it in. Same for any fonts we use for other first-party themes.

#60 Non-default theme with Departure Mono 19 days ago

Comment by ~amolith on ~amolith/willow

I like the idea of both baking a couple/few themes in and allowing the user easily to override everything.

The former could be implemented by templating some more CSS and threading a new config value from TOML to templates.

For the latter, I'm inclined to have a new config value for a user-provided static dir. We could serve everything in the dir and their entrypoint could be an overrides.css. That allows the admin to pull in various self-hosted resources like fonts, CSS, and images.

#60 Non-default theme with Departure Mono 19 days ago

backend added by ~amolith on ~amolith/willow

#60 Non-default theme with Departure Mono 19 days ago

frontend added by ~amolith on ~amolith/willow

#60 Non-default theme with Departure Mono 19 days ago

Ticket created by ~amolith on ~amolith/willow

As a fun side thing in the future (I'm feeling inspired, so maybe soon), I'd like a second, non-default theme that uses Departure Mono and changes some of the CSS values to adopt an aesthetic similar to what's shown on their site.

https://departuremono.com/

#48 Move to a single column layout with Popover dialog 23 days ago

Comment by ~amolith on ~amolith/willow

Forgot to update the usage instructions according to the new UI

RESOLVED IMPLEMENTED REPORTED

#48 Move to a single column layout with Popover dialog 29 days ago

Comment by ~amolith on ~amolith/willow

Amolith referenced this ticket in commit 6a997f0.

REPORTED RESOLVED IMPLEMENTED

#59 Format frontend source 29 days ago

Comment by ~amolith on ~amolith/willow

Amolith referenced this ticket in commit 8cbd018.

REPORTED RESOLVED IMPLEMENTED

#59 Format frontend source a month ago

Comment by ~amolith on ~amolith/willow

it has options to control the formatting and that's where personal preferences and argument can creep in :)

Hah I intended to just leave all of prettier's settings at default, aside from the plugin ;)

It's also useful to have editors do the formatting whilst coding so configuring Prettier via an .editorconfig would be nice.

I see that prettier respects style settings from an editorconfig, but nothing about making it aware of plugins or configuring those plugins. Is it just the styling aspect you're referring to, or did I miss some docs?

#59 Format frontend source a month ago

v0.0.1 added by ~amolith on ~amolith/willow