Replies: 1 comment
-
Hi 👋 ! Yeah I think it's more practical for the user to just create multiple jobs for different SVGs output if they want to create linkable SVGs in their markdown. An even better way would be to use the markdown template instead. <%- await embed(`repositories`, {repositories:true, plugin_repositories_starred:1}) %> Some plugins also have a markdown version, this plugin could be a good candidate for this plugin |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The repositories plugin mentions that due to limitations, svgs cannot link to individual repositories.
Perhaps, it could be an idea to have an option to basically separate each repository as its own SVG to wrap into a
<a>
tag?The obvious downside would be that the beackend would need to do a lot more in terms of processing as the there would be more SVGs to generate.
It's just an idea and I understand if the drawbacks outweight the benefits and it wouldn't be realized.
Beta Was this translation helpful? Give feedback.
All reactions