Setup blog

[patak-cat]

It would be good to announce the alpha of https://npmx.dev with a blog post so it can be easily re-shared in other places.

We could use something like leaflet, but in my opinion the best would be to have a npmx.dev/blog that matches the style of the website. We could generate https://standard.site events and add RSS.

I like a lot the way @danielroe did the setup of his blog: https://roe.dev/blog/the-golden-thread
I think it is worth having the comments integration with https://social.npmx.dev before launching.

[danielroe]

see danielroe/roe.dev#1793 (and subsequent fixes)

[fatfingers23]

I can help with the Bluesky part of this if that's a blocker for someone. If someone wanted to do the UI's and Nuxt content integration with a comment section with placeholder data I can come back in and hook up everything to posts. I can also do the standard lexicon part as well. I guess we may want that to be semi automatic and from the action runner?

For getting the post that is most likely the one wanted for comments section we can also get it with constellation and a did filter on social.npmx.dev's did to save walking the records to find which post we should grab the comments from. This will return the oldest bluesky post that has the link shown as a preview in the post, using Daniel's as an example.

The key parts of the URL is did and subject, with subject being the blog post full url like https://roe.dev/blog/the-golden-thread. Can set limit and reverse to make sure you always get the first one ever posted

https://constellation.microcosm.blue/xrpc/blue.microcosm.links.getBacklinks?subject=https%3A%2F%2Froe.dev%2Fblog%2Fthe-golden-thread&source=app.bsky.feed.post%3Aembed.external.uri&did=did%3Aplc%3Ajbeaa5kdaladzwq3r7f5xgwe&limit=1&reverse=true

[Kai-ros]

Scope

• UIs (plural I gather)
• anthony's alternative markdown solutionfor now and Nuxt content integration for later
• lexicons work
• automatic pulls or pushes from an action runner
• constellation
• records walkers
• bsky posts stuff
• TBD
• x

In Flight

• An UI, singular (Kairos)
• x

Resources

• GitHub Ish
• Working Branch
• Prior Art 1
• Prior Art 2
• Prior Art 3
• PDSls
• Constellation
• Tangled Lexicons
• Lexicon Community
• Bsky Account

[abbeyperini]

If this one's not claimed, I can take a stab at it

[fatfingers23]

If this one's not claimed, I can take a stab at it

Thank you! I think both @Kai-ros and @jonathanyeong have been working on it. If you're in https://chat.npmx.dev/ we're over in the social channel talking about it and hopefully they can chime in with sharing work.

[jonathanyeong]

Come join us @abbeyperini !!

[trueberryless]

Not sure if this is still relevant or already decided, but https://starlight-blog-docs.vercel.app/ would seem like the easiest solution to me. It has RSS included when the site option is defined, and to match the dark modern design of npmx we could use my theme plugin as well together with it.

My estimate is that I could set this up in around one hour… Just saying
Bluesky comments would be the only thing I would need to figure out 🤔

[whitep4nth3r]

I want to add that I think it'll be important to put faces to words. So rather than having blog posts written as "npmx", they should be written by authors (probably plural) with visible avatars and names with each blog post. This humanises the words more clearly and ensures the messages are perceived to be coming from the community and not from a new corporation.

[Kai-ros]

#632

[whitep4nth3r]

I have time this week to start drafting out the announcement blog post.

In the interest of efficiency, I wonder if it's useful for me to branch off #257 somehow so I can test the blog functionality in parallel (or maybe we need a dev branch or similar of the actual npmx repo to collaborate on longer term efforts like this?)

[serhalp]

Closing this one, but feel free to reopen if I've misunderstood!