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.

Sign up for GitHub

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

Jump to bottom

Have a nice looking page in the default che plugin registry #13836

Open
sunix opened this issue Jul 12, 2019 · 4 comments
Open

Have a nice looking page in the default che plugin registry #13836

sunix opened this issue Jul 12, 2019 · 4 comments
Labels
area/plugin-registry good first issue Community, this issue looks easy to start with for a new contributor. Just take it. We'll help you! kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
7.x (Later, Futur...

Comments

@sunix
Copy link
Contributor

sunix commented Jul 12, 2019 •
edited

Is your enhancement related to a problem? Please describe.

When landing to the plugin registry https://che-plugin-registry.openshift.io/, the page being shown is the README file in plain text.

Selection_338

Describe the solution you'd like

It would be nice to show a nice looking page (with a nice CSS) for all the che plugin registries with these informations, in that order:

  • what this is about (this is the che plugin registry, provide plugins for che, link to documentation, link to che)
  • a link to the list of plugin (or the list embedded in a nice view with json text highligts)
  • how to change that list of plugins, how to contribute to the default registry.
  • how to add one of these plugins in a existing workspace or devfile.
  • how to deploy your own plugin registry in your instance of che.
@sunix sunix added kind/enhancement A feature request - must adhere to the feature request template. area/plugin-registry labels Jul 12, 2019
@slemeur slemeur added this to the 7.x milestone Jul 15, 2019
@nickboldt nickboldt added the severity/P2 Has a minor but important impact to the usage or development of the system. label Jul 15, 2019
@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 15, 2020
@che-bot
Copy link
Contributor

che-bot commented Jan 15, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot closed this as completed Jan 22, 2020
@sunix sunix reopened this Apr 24, 2020
@sunix sunix removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 24, 2020
@sunix sunix added the good first issue Community, this issue looks easy to start with for a new contributor. Just take it. We'll help you! label Jun 26, 2020
@sunix sunix added status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Jul 13, 2020
@sunix
Copy link
Contributor Author

sunix commented Jul 13, 2020 •
edited

hey I am setting need-triage label so we reset a priority on that one as it has been there for a year: the landing page should help users to find useful informations about plugins and how to add a plugin in a devfile and where to contribute new plugins.
Also should be nice looking ... ;)

@ericwill ericwill removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jul 13, 2020
@che-bot
Copy link
Contributor

che-bot commented Jan 20, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2021
@sunix sunix removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2021
@ericwill ericwill added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jan 20, 2021
@sunix
Copy link
Contributor Author

sunix commented Jan 28, 2021

So a simple index.html with a JS client app that would use index.json to browse through the plugins of the registry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/plugin-registry good first issue Community, this issue looks easy to start with for a new contributor. Just take it. We'll help you! kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
7.x (Later, Future, Never)
Development

No branches or pull requests
5 participants
@nickboldt @sunix @slemeur @ericwill @che-bot