Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discussion] Custom Widget Library #919

Closed
pungggi opened this issue Dec 12, 2017 · 10 comments
Closed

[Discussion] Custom Widget Library #919

pungggi opened this issue Dec 12, 2017 · 10 comments

Comments

@pungggi
Copy link

pungggi commented Dec 12, 2017

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..

@pungggi
Copy link
Author

pungggi commented Dec 14, 2017

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?

@tech4him1
Copy link
Contributor

@verythorough @erquhart What do you think of this?

@verythorough
Copy link
Contributor

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.

@erquhart
Copy link
Contributor

Agreed, I'd love to see major improvements in discoverability. Featuring community extensions is a big part of the current extensibility initiative.

@pungggi
Copy link
Author

pungggi commented Dec 24, 2017

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 gatsbyjs/gatsby#3003 .

sorry if my english is not that good I am not a native english speaker..

@erquhart
Copy link
Contributor

erquhart commented Jan 2, 2018

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!

@cwahlfeldt
Copy link

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/.

@erquhart
Copy link
Contributor

erquhart commented Jan 20, 2018

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.

@tech4him1 tech4him1 changed the title Custom Widgets Folder [Discussion] Custom Widget Library Jun 2, 2018
@stale
Copy link

stale bot commented Oct 29, 2019

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.

@stale stale bot added the status: stale label Oct 29, 2019
@martinjagodic
Copy link
Member

Closing in favor of decaporg/decap-website#1

@martinjagodic martinjagodic closed this as not planned Won't fix, can't repro, duplicate, stale Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants