Improved theme management in Micro.blog today, including disabling previous theme plug-ins when installing a new theme. Makes it faster to try new themes because they don’t need to be uninstalled right away. 🔌

@manton A much-needed change and works well with assumptions people had. Thanks!

@pratik Good to hear!

@jeffperry If the plug-in is added to the directory, Micro.blog will automatically check for new versions and show an “Upgrade” button to pull from GitHub again. For other custom themes and plug-ins, it doesn’t do that, but something similar might be possible.

@manton You’re making all the right choices; what an improvement!

@sod Thanks!

@manton loving how this world is shaking out. one thought for the future might be to separate out the plugins that are about changing the design and plugins that add functionality - currently all mixed up.

@manton lots of great momentum building here. Exciting!

@JohnPhilpin Thanks! We need some filters. I haven’t decided if it should be categories, tags, just themes vs. non-themes, or something else.

@manton to me … right now themes and functional plugins would be the immediate change .. tho design plugins would be best served on ‘design’ page … usability should not require a visitor to know if the new design they want is either a plug in or just on the design page?

@JohnPhilpin Good feedback. Thanks.

@manton I’ll probably expand on this is the forum, but to me customisation on M.b needs to reworked. Right now there’s overlap between design and plugins. I am often confused about where to start making any changes etc. Maybe it’s worth thinking of design and themes as an “appearance” bucket and plugins as an “extend” bucket?

@purisubzi Thanks. I’m hoping when the plug-ins are more organized it will be clearer. Some plug-ins don’t neatly fall into one type.

@purisubzi 💯

@manton works great for trying themes… site rebuild is fast. you’re on a roll these days with all those improvements…