nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q
We're working on:
* a WYSIWYG component with inline-preview and toolbar
* implementing the basic-level markup parsing in the Reading View, so that publications and wiki pages also get fully parsed
* updating https://gitcitadel.com/repos to use the same parser on all events, including issues and kind 1111 replies
* disambiguation page for the wiki, which will also gather some other kinds referencing the same subject, and list them at the bottom of the page (working name "Talk of the Forest")
* universal viewer for all event kinds, so that we can remove all Njump links and replace them with internal links.
Discussion
Our wiki disambiguation pages will also be topic aggregators for events on TheForest.
That means, whenever someone uses #Alexandria, with a community relay, the wiki pages will perform that service for that relay. That way, you can easily find other people in your community, who are interested in the same topic.
Since you can reply to wiki pages with kind 1111 comments, they can become sort of bulletin boards for that topic.
And highlights, of course.
What's a "wiki page" in that sentence?
Wiki-entry event?
Because you can't reply to the slug, right? Or can you?
Good question. 😂 🤔
I was actually thinking a composite of replies to the individual wikis, but maybe there should be a header for every topic that we can pull.
Just an easy way to tag the [[wiki-slug]] would go a long way for me.
We could just use a 30040 index, actually. :thinking:
I'm thinking that you might see 3 different wikis for the topic d-tag `french-cooking` and if you just want to talk about French cooking, in general, but not someone's idea of French cooking, in particular, you could reply to the generic header.
And you don't need one for every topic, just for any topic on your community relay.
Or something. We need to think through the workflow.