-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
doc: add addons #1895
base: main
Are you sure you want to change the base?
doc: add addons #1895
Conversation
✅ Deploy Preview for slidev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@slidev/client
create-slidev
@slidev/parser
create-slidev-theme
@slidev/cli
@slidev/types
commit: |
repo links are missing the for example
must be
|
repo: 'https://github.com/Smile-SA/slidev-addon-sync', | ||
}, | ||
{ | ||
id: 'slidev-component-pager', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be better to have a components category then? What do you think @KermanX?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about adding some tags/keywords to each addon? For example, Component
/Intergration
/Tool
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to add some context, the first add-ons I created were named slidev-component-*
because I was working on them before we released the add-on feature in Slidev (released with v0.32 on May 20th).
The name "addon" was not official at that time, so I chose "component" and was too lazy to change the name later.
But yes, it can still be interesting to have tags 👍
No description provided.