Widgets Repo

[KaneFreeman]

The idea here is to create a separate repo / package(s) with more specialized widgets for Static CMS. Here people could suggest new widgets to be added that could optionally be installed without needing to be bundled with the core product. Some of the more specialized widgets in the core product will likely be moved over as well, like Map for example.

Suggested: https://github.com/StaticJsCMS/static-cms/discussions/4#discussioncomment-4871709

Core Widgets To Move (Targeted for v5)

• [ ] Code
• [ ] Color
• [ ] Key / Value
• [ ] Map
• [ ] UUID

[denyskon]

Could at least the hidden widget remain in core? It's really useful for setting fixed parameters, for example in Hugo there's a type field you can use to specify which template should be used to render a page. I don't think it's that uncommon to do that...

[mnordhaus]

Moving less used core widgets is a great idea IMHO but I wonder: How is "less used" determined and what is the threshold? Maybe a little survey or might it be possible to search GitHub (or other public repos) to get a better idea on how often a widget is used?

[KaneFreeman]

Probably a better way to say it than less used is "more specialized".

Basically I want to leave in the core product only what most people will need out of the box to get started. Almost everyone will use the String widget, but the same cannot be said for Map.

Another criteria also will be bundle size. Since the additional widgets will be included one by one as needed, we can move large widgets (again like Map) to their own packages to reduce the core product's size.