Repository navigation
Replies: 7 comments 1 reply
|
Thanks @rmdes for sharing your extra features and fixes. I would appreciate any extra features for the Markdown editor and the auto complete with existing tags (I've set up the json list of all my categories (ie tags) used in the config but it never worked). I actually have a question about the editor not sure if you fixed it in your fork? There are red squiggly lines for what it thinks are spelling errors (eg US vs GB spelling, or genuine typos) but right clicking does nothing and I can't turn it off. I tried messing in Firefox about: config (turning everything related to spell check off) but I don't think it's related. These red lines only show up in the Indiekit Markdown editor text field. And running your plugin in the meantime to fix the 404 on old posts and getting the content sort has been great! Would love to see it in the official plugin. Thanks for everything Ricardo. 👍 |
|
In relation to markdown editor improvements, I have this :
this means I can write a long form article and I can invoke some basic formatting right from the selection, no need to go up the page to reach basic tooling, also, there is a new button next to image/media upload, which allows you to browse existing media files server side and insert them directly on the current text, its quite handy ! in relation to the red squiggly lines - I think these appear because we have spellcheckers enabled on our browsers, this is a "client" / browser config, nothing related to the editor in itself, but I do agree its confusing, even with the spellchecker properly configured, at least in Vivaldi browser, I can see errors but when I right click I don't have any suggestions to fix the error, this is confusing for me too Honestly, If I could choose, I would migrate to something like Carta https://beartocode.github.io/carta/ because I think this markdown editor is just much better, minimal, slick, extendable with more plugins, but that's a different path than a improvement of the existing markdown editor and its Svelte related, so not sure this could fit indiekit, but there are other markdown editors out there And in relation to categories suggestions, what I have now allowed me to merge a lot of duplicates categories I had created over the last few months with different spelling, having it suggest when I start typing is a real improvement worth bringing to indiekit ! |
|
As a broad sense of direction, and for getting to a place where we can release v1.0.0, I would prioritise as follows:
On that last point, I’d like to transition the frontend to use something like Web Awesome. That would mean this project no longer needed to build and maintain it’s own suite of frontend components and patterns. It may also make it easier for plugin authors to provide extensions to the interface. There’s likely an unending category of improvements that can be made to make Indiekit a full-fledged CMS, and maybe that’d be welcome over time. But it could also be a distraction. I’d be open to revisiting this once the foundations – including an extensible UI framework – are in place. |
|
That ordering is useful, and it settles more than it looks like it does — several things in my list were only debt because I didn't know whether they had a future here. Knowing they don't is worth as much as a yes. Against each category, with what I actually have: 1. Bugs. Where I've been aiming: 21 merged in the last three weeks, 11 open, one bug per issue per PR. The bug backlog in my fork is essentially extracted now — what's left in it is features, not fixes. 2. Documentation. Only #942 so far. I'd rather take direction here than guess: you're closer to where new users get stuck than I am. 3. Foundations. #917 is a spike at the id-casting seam, #915 is the store-file-system write that disappears silently. Your note on #900 about dropping MongoDB for SQLite changes what I'd build, so I'll hold anything larger until #821 has a shape. 4. Compatibility. #938 is open — profile scope and 5. Protocols. Microsub part one is now #944 — same commits as #829, reopened from a branch on this repo so CI can run, which it never could from the fork. The remaining six parts are written behind it. That move paid for itself immediately: CI got past 6. User interface. Parking all of it behind Web Awesome — editor toolbar, media browser, vertical navigation, category typeahead. One thing worth carrying into that work: the vertical navigation isn't really a menu problem. Plugins have no way to say where they belong, and the horizontal bar is just where that surfaces first. The CMS-shaped things — homepage builder, site-config, theming — I'll treat as a permanent fork. They only work as a bundle with a matching theme, which makes them a distribution rather than a plugin, and not Indiekit's to carry. One practical question: 11 open PRs against one reviewer is a lot. If that's more than you want in flight, name a number and I'll hold the rest — a queue too long to review isn't help. |
|
I should have some time this coming weekend to review outstanding PRs; it’d be helpful if we can reduce/stop the number of incoming issues and PRs until then and instead focus on clearing those already in flight. |






Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I've been running a heavily modified Indiekit for a while. Rather than keep carrying the forks quietly, here's what's in them — partly so I know which ones can be retired, and partly because some of it might be worth having in the project.
Happy to be told no on any of it. That's useful too: it tells me a fork is permanent and I'll stop treating it as debt.
Writing posts
A real markdown editor. The post form uses EasyMDE with a floating selection toolbar — select text, get formatting. More usefully, the toolbar has a media browser: you can browse everything you've already uploaded and insert it while writing, instead of leaving the form to find a URL.
Multi-file uploads. Upload several files at once rather than one at a time.
Category typeahead. Start typing a tag and get suggestions from what you've already used, so your taxonomy stops drifting into
indieweb,IndieWebandindie-web.Content warnings, pinned posts, layout hints — additional controls in the post form's advanced section.
Finding posts again
The post list becomes usable at scale. Filter, search and sort. Once you have a few thousand posts, the current list is difficult to navigate.
Older posts stop 404ing. Post lookup goes through MongoDB
_idrather than a?q=sourceround trip — this is the bug @eclecticpassions hit in #843.Permanent delete and bulk purge for soft-deleted posts.
Syndication
Reply to anyone, not just your own instance. Today, replying to a post that isn't on your own Mastodon server throws and the whole syndication fails. The fork resolves the remote status through Mastodon's
v2/searchand threads to it properly. RSVPs too, since they carryin-reply-to.Opt in or out of external likes and reposts — the configurable behaviour I mentioned in #843.
Bluesky posts get rich previews. Link facets so URLs are clickable, OG card selection, reply threading with root/parent resolution.
Webmentions
Moderation. A blocklist by domain, hide and unhide individual mentions, and a dashboard. Spam webmentions are currently something you have to live with. There's also h-card discovery, which fills in author avatars that webmention.io returns empty.
This one is the biggest departure — it stores mentions locally and syncs, rather than reading through to webmention.io. More a feature proposal than a patch. I've written 99 tests for it.
Under the hood
Service worker fixes. Auth and preview pages no longer get cached, which was causing stale login state. Cross-origin requests are skipped rather than intercepted. Stale-while-revalidate with update notifications.
Micropub query filtering by category and search term.
Syndicator update/delete hooks — the CRUD idea from #581, so a syndicator can react when a post changes or is removed, not just when it's created.
Where things stand
endpoint-authandendpoint-syndicateare nearly retired already — most of what I carry is merged or in #884, #891, #893.endpoint-files,endpoint-shareandpreset-eleventyare small and mostly additive.The bigger ones —
frontend,endpoint-posts,syndicator-bluesky,endpoint-webmention-io— replace upstream logic in places rather than only adding to it, so those are conversations rather than patches.I'll keep this updated as things land. Tell me which of these you'd actually want and I'll start writing PRs with tests.
All reactions