Casey Rodarmor

These are all pretty doable, I think. Attributes which can be set on gallery items can also be set on inscriptions. So, since there will be title and description attributes,...

Inscription metadata is free-form, whereas the metadata I'm talking about has a schema. Metadata with a schema is much more useful than free-form metadata, since it's actually machine readable. Also,...

See #4243 for a first stab at defining the schema for traits. It's broken down into attributes, a top-level struct with fixed keys, and traits, a member of attributes which...

> Do you expect attributes to essentially replace metadata for the majority of the inscriptions? I think so. I think that they are pretty complementary: Use attributes for anything structured...

@gmart7t2 Yah, good point. Options: 1. Have the top level `description` value be markdown, which is converted to HTML. 2. Allow a markdown value type for attribute values, which is...

@lifofifoX Really good idea! Added them to the CDDL.

Check out #4427. I'm working on traits, and I'm debating whether to encode them as-is, or if I should deduplicate keys and values. Deduplicating keys and values is weirder and...

This has been implemented. I opened #4442 to collect feedback.

Thanks for opening this issue! I would like to eventually support inline modules, which would allow submodules to be defined in a single justfile. We could allow `::` in recipe...

Yah, honestly I like it too, especially in terms of being easy to read. My preference for avoiding indentation-based syntax is mostly when it comes to writing and editing. For...