-
Notifications
You must be signed in to change notification settings - Fork 104
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
Move each plugin index page from Markdown to model-based doc #1503
Labels
Comments
@brian-mulier-p I see everything is checked :) can the issue be closed? |
Waiting for a Cloudflare ticket due to building issue |
Reopening because it's not done yet, the thing that's done is the task detail redesign |
all items were checked so... 😄 I'll let you manage + close, unsubscribing to alerts |
brian-mulier-p
added a commit
that referenced
this issue
Feb 17, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 17, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 17, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 17, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 17, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 17, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 17, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 17, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 18, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 18, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 19, 2025
brian-mulier-p
added a commit
that referenced
this issue
Feb 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Issue description
Currently the index of each plugin where for a given plugin we list every tasks / triggers / ... it includes (here) is a bit ugly. The goal is to move from an API-generated markdown page to a model-based generation. Basically the front-end will instead fetch the model data and will generate the page.
It will allow us to easily modify the content and introduce in an easier manner custom components.
What to do to achieve such result:
group
property (so for snowflake it's io.kestra.plugin.jdbc.snowflake for eg.)The text was updated successfully, but these errors were encountered: