Closed pungggi closed 1 year ago
I suggest the first widget to add should be that from the blog https://www.netlify.com/blog/2017/06/20/extending-netlify-cms-part-one-custom-widgets/ What do you think?
@verythorough @erquhart What do you think of this?
I think there are some cases where it would make sense to add a widget to the default widgets in the repo (like the multiselect widget in development now).
In other cases where the widget is less generic, we could add a "community-created widgets" section of the widgets doc, where people can link gists, repos, and/or tutorials for custom widgets they have created. I figure this makes for discoverability in a central location, while still allowing widget creators to store and maintain their code in a way that works for them.
Agreed, I'd love to see major improvements in discoverability. Featuring community extensions is a big part of the current extensibility initiative.
Yes, what really matters is discoverability.. First, what for me would feel 'natural' is doing a search like this> https://yarnpkg.com/en/packages?q=netlify%20widget&p=1
So suggesting a default name convention to widget developers would help, like: The Widget name should start by ...
Second, a linking section would also help for non-default named widgets.. Maybe there are some ideas to borrow from https://github.com/gatsbyjs/gatsby/issues/3003 .
sorry if my english is not that good I am not a native english speaker..
Thanks @pungggi - your English is great, no problems there :)
I agree with establishing a naming convention, probably netlify-cms-widget
. And building the kind of discovery that Gatsby is building right into the website would be awesome!
Maybe the ecosystem would benefit from a third party app/site? Im thinking something similar to rusts package manager site https://crates.io/, or maybe even like a https://js.coach/, or https://vimawesome.com/.
I'd like to see it built into netlifycms.org. I'm super inspired by this: http://nivo.rocks/#/components
Not only is it a great interface for discoverability, the individual pages are visual playgrounds that allow you to configure components live and generate React component code (among other things) as output. Plus the public Storybook. Love love love.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Closing in favor of decaporg/decap-website#1
It would be nice to have a folder where the community can contribute to custom widgets...or does this exists already, i could not find anything in this repo..