refactor(plugins-list): implement plugins list cards display #5
Conversation
- Deleted the old Markdown file for the plugins list. - Created a new MDX file for the plugins list, utilizing the PluginCard component for better presentation. - Updated the global CSS to include styles for the plugin card grid layout.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
travi
left a comment
travi
left a comment
There was a problem hiding this comment.
i like it!
one question for maybe a future iteration after this is merged. could the list of cards be built dynamically? i worry that this may present a barrier for contributors wanting to list their plugin because it is more involved than just adding to a markdown file. if not familiar with front-end tech, this might feel intimidating. if we could could have the community plugins defined in data in a json or yaml file and then pulled in to generate the comments dynamically, that feels more approachable
|
one other thought related to community plugins. the list has grown pretty long and is likely hard for anyone to really find a useful plugin in there. ive been thinking for a while that they at least need to be resorted, but more likely grouped into some logical categories. which one supports package manager x or registry y or ci provider z, etc. that gets complex for the ones that could be in multiple categories. maybe some dynamic sorting/filtering could be useful, but even static groupings could be a be improvement. dont worry about these thoughts before merging this PR, but it feels worth us considering as a further iteration later |
I like this one exactly 💯, it is very practical and infact a cleaner way to manage plugins submission. It infact creates a fine foundation for the grouping/sorting/filtering too. We should definitely talk more about this. |
2 participants
This pull request introduces a new
PluginCardcomponent and supporting styles to the codebase, laying the groundwork for a more modular and visually appealing presentation of plugin information. Additionally, the previous static Markdown list of plugins has been removed, likely in preparation for a more dynamic or component-based approach.The most important changes are:
Component Addition:
PluginCard.astrocomponent, which displays plugin information (name, URL, description, and steps) in a styled card format. The component supports expandable sections for each plugin step and includes responsive, accessible design features.Screenshot/Screencast
screen-capture.30.webm