Add 3x extensions #1497
Add 3x extensions #1497
Conversation
| - name: bluesky-comments | ||
| path: https://github.com/coatless-quarto/bluesky-comments | ||
| author: '[James Joseph Balamuta](https://github.com/coatless/)' | ||
| description: > | ||
| Quarto Shortcode Extension to Embed Comments from Bluesky |
There was a problem hiding this comment.
I am seing now that @gadenbuie already listed his in #1491
We now have two extensions with the same name in the list.
I saw thread continued on bluesky at https://bsky.app/profile/grrrck.xyz/post/3lbwos6y4c227
this is a really good extension and this makes me think as you seem to be willing to both work together, that we should have one with best of both. What about keeping only one extension for this called bluseky-comments and "merge" your feature ?
I would offer to have it as quarto-ext/bluesky-comments at @quarto-ext. We could make both of you maintainer for this extension in the @quarto-ext org. And we could then list as an official option through an extension in https://quarto.org/docs/output-formats/html-basics.html#commenting with other commenting solution
What do you think ?
There was a problem hiding this comment.
For now, can we just list it along side? I can just use quarto-bluesky-comments or switch to quarto-bluesky. I'm planning on adding a few other items outside of comments as time progress.
If not, no worries. I'll drop it from the PR.
There was a problem hiding this comment.
If not, no worries. I'll drop it from the PR.
Don't drop it - we can list both. I don't think the name will cause problem in the table.
I was just trying to offer a solution to move forward to only have one extension for this feature. I'm quite confident @gadenbuie would work with you, starting from your version. It would be really cool to have this feature a part of options for https://quarto.org/docs/output-formats/html-basics.html#commenting and so having a dedicated extension to it seems nice !
switch to quarto-bluesky. I'm planning on adding a few other items outside of comments as time progress.
If you have some more broad plans for bluesky support, I can understand you don't want a scoped extension. What do you have in mind out of curiosity ?
There was a problem hiding this comment.
@cderv are you okay if I add you as a maintainer and let you move it over into quarto-ext?
Feature-wise, off the top of my head:
- Feed
- Personal last ~10 bluesky thread posts
- #rstats tag monitor
- Post
- Style
- Maybe a custom interface for bsky comments or better syncing with Quarto's underlying theme system.
More as I explore the public API.
There was a problem hiding this comment.
Let's keep the bluesky comments consolidation conversation over in quarto-ext/bluesky-comments#3.
@coatless I'd love to collaborate but I'd also completely understand if you'd like to take your extension in other directions beyond comments.
There was a problem hiding this comment.
@gadenbuie will do; no worries on that. Trying to quickly answer @cderv in the midst of fall break being over.
Though, could gently move that repo over? The longer it sits, the more URLs might get setup to point to it. Easier to announce "Better extension" please bookmark blank. 😉
There was a problem hiding this comment.
With new work on documentation for 1.6 I tried to ordered the extension by name. It is supposed to be visible, by I know this changed compated to before where it was in order.
Could you just move in the right place colab and tabby ?
Thanks !
There was a problem hiding this comment.
Sure, I'll also add in stamp.
|
/deploy-preview |
|
🚀 Deployed on https://deploy-preview-1497.quarto.org |
No description provided.