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 #1400

Closed
talves opened this issue Jun 1, 2018 · 3 comments
Closed

[Discussion] Custom Widget Library #1400

talves opened this issue Jun 1, 2018 · 3 comments
Assignees

Comments

@talves
Copy link
Collaborator

talves commented Jun 1, 2018

Feature Request:

Allow for users to make PR's to add their custom widgets to the NetlifyCMS site to keep track of published widgets out there.

Proposal:

Requirements might include having a custom widget be published to npm. The collection would allow someone to add a configuration entry into frontmatter that would be added to the site page showing all available widgets with targeted SSG, categories and features for the developer to be able to find what they need.

cc/
@Benaiah
@erquhart
@tech4him1
Maintainers: Make updates to this request as you feel is needed based on comments and ideas.

@talves
Copy link
Collaborator Author

talves commented Jun 1, 2018

We have been discussing creating a place for people to publish information about their custom widgets on the NetlifyCMS site somewhere. You are right, and a plan to have a full information format will help quite a bit. I am sure we will get there. We just need someone in the community to take it on when they get time. I might tackle it with some other stuff I am doing, but it is lower on the priority at the moment.

References:
#325 (comment), #325 (comment)

@hennessyevan
Copy link
Contributor

This is kind of a neat implementation https://www.gatsbyjs.org/plugins/ I think would be worthwhile looking at as well, from what I can tell it just searches for NPM packages related to gatsby-plugin and then sorts them based on their popularity, or make it more curated, something like what I assume is that case with netlify's own headlesscms.org. That would put more work on the reviewers' end though.

The widget starter does encourage custom widgets to be named netlify-cms-widget-<name> already.

@talves
Copy link
Collaborator Author

talves commented Jun 2, 2018

Closing based on duplicate https://github.com/netlify/netlify-cms/issues/1286

@talves talves closed this as completed Jun 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants