@manton After working with Tiny Theme, I have two big feature requests.

1. A way to save theme/plugin data across updates.
2. Better shortcode support.

Expanding on 1: This would make an all-in-one type of plugin/theme possible. Instead of having multiple plugins for a specific theme (as is the case with Tiny), I could build in all the options to the theme itself. And when it gets updated, the user wouldn't have to reconfigure all settings.

Expanding on 2: The way it's currently built, there are multiple potential issues. (1) Conflicting Shortcodes, (2) Deprecated Shortcodes, (3) Inactive Shortcodes. Depracated/Inactive Shortcodes can lead to critical builds errors as it is now.

@Mtt Agree with both. #1 is a limitation that I've been wanting to fix. For #2, Micro.blog has a way now to auto-install a plug-in if it's needed for a shortcode, but it's something I have to wire up manually because there's no field in plugin.json for it yet. That doesn't totally solve what you're saying, but maybe more features like that.

@Mtt I'm not sure if this is a good time to talk about the management of customization to a theme provided with a plug-in. If a plug-in gets updated, the customization by the MB user my block any further improvements to the base theme. Conciliation needs to be done manually.

@numericcitizen Yes, that’s the working concept of “child themes” (called custom themes here). Anything you do in a custom theme, by design, will overwrite the matching theme file. What you do will always have priority over what I do (as the developer). Same goes with custom CSS.

@numericcitizen There is! In fact, your last few replies have basically invented Github. You've described Forks, Pulls, Merges, Diffs in your last two replies. And Micro.blog works wonderfully with Github. Here's the official Tiny Theme Github Repo where you can do all of those things.

@Mtt Just installed Github Desktop and cloned this repo on my machine. It will be much easier to track! 👨🏻‍💻