Thanks for jumping in,@kylecarbs.

I'm leaning towards optimizing syntax for the web interface rather than the CLI, because it's presently unclear in the syntax when description would be shown and when description_markdown would be.

TIL! I think that we have to highlight who is the more important consumer, CLI or site. We can use it as the rule of thumb that in our case it's always the site.

What do you think about making description markdown by default, then add a description_plaintext for the CLI?

If we're site-oriented, thendescription should be kept as is, even if it uses Markdown tags. Additionally, we can expose an extra generated field in the API that shows the rendered description,description_plaintext. I don't think that this is something we need to keep in the database, it can be rendered dynamically 👍 .

Let me know your thoughts.

That makes sense to me. I like it!

Maybe I will update examples to show that Markdown description is fine.