npub1l5s…gx9z

2024-10-30 08:15:43

Update on the wiki front

It’s been a while, since we talked about #wikis, so I thought I’d make it a topic, again, with an update on the state of development of NIP-54.

fiatjaf (npub180c…h6w6) has identified the #Asciidoc rendering issue with special characters, so those weird “&bnsp” and similar errors should eventually disappear. 😊
I’ve been using Asciidoc, for a while, now, and it’s definitely a superior markup. Markdown is alright for plain articles (like this one), but a catastrophe, with anything even slightly more complex or professional.
I’ve found that the wiki events are excellent for project #documentation because they’re collaborative. Feels like using Confluence. We each fork from and deferr to, each others’ version, so it’s a similar experience to using git patches for documentation. (I store major changes as .adoc in git, tho, for versioning and backup.)
The current wiki clients are just missing a diff, kind 1111 comments, and highlights. Some of the formatting styles need to be tidied up, regarding fonts and spacing, and whatnot, and they need some more QC. I might do that for Wikistr, if I can find a lull in my GitCitadel tickets.
We have some ideas, for improving internal references (for example, footnotes), by making them into separate events, but that will be listed in the #NKBIP-03 page, that I’m about to write. (I will add a link to it, from here, later.) For now, I just use the Asciidoc syntax and it is rendered directly. I think this new event will take a long time, to structure properly, and we’ll pilot it in a later version of Alexandria.
If you have any factual/nonfiction information, that you think will be important to find, later, I would suggest you write it into a wiki page, not Kind 01. Not only does that improve its discoverability, it reduces the chance that relays will delete it.
We, at GitCitadel (npub1s3h…75wz) have decided that wiki functionality makes sense, to integrate into #Alexandria v0.2.0, so that has been added to the work breakdown structure. I don’t expect us to have as much functionality, as a dedicated wiki app, such as Wikistr, but it will render the pages and the internal links will work.

Author Public Key

npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z

Show more details

Published at

2024-10-30 08:15:43

Kind type

30023 Long-form Content

Event JSON

{ "id": "ccae9d5a8dfa2474125a66982b7ffd2f39b6ba5a88cbe82fc921d107ebe5ede2", "pubkey": "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1", "created_at": 1730276143, "kind": 30023, "tags": [ [ "d", "1730273431079" ], [ "title", "Update on the wiki front" ], [ "summary", "What is going down, with Kind 30818." ], [ "image", "https://i.nostr.build/HC2JLS2VPC5p9x8b.png" ], [ "published_at", "1730276136" ], [ "alt", "This is a long form article, you can read it in https://habla.news/a/naddr1qvzqqqr4gupzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqqxnzdenxqerwve5xvcnqdeeq87j94" ], [ "p", "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d" ], [ "p", "846ebf79a0a8813274ec9727490621ad423f16a3e474d7fd66e6a98bfe4e39a4" ], [ "t", "wikis" ], [ "t", "Asciidoc" ], [ "t", "documentation" ], [ "t", "NKBIP" ], [ "t", "Alexandria" ] ], "content": "It's been a while, since we talked about #wikis, so I thought I'd make it a topic, again, with an update on the state of development of [NIP-54](https://github.com/nostr-protocol/nips/blob/master/54.md).\n\n1) nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 has identified the #Asciidoc rendering issue with special characters, so those weird \"\u0026bnsp\" and similar errors should eventually disappear. 😊\n\n2) I've been using Asciidoc, for a while, now, and it's definitely a superior markup. Markdown is alright for plain articles (like this one), but a catastrophe, with anything even slightly more complex or professional.\n\n3) I've found that the wiki events are excellent for project #documentation because they're collaborative. Feels like using Confluence. We each fork from and deferr to, each others' version, so it's a similar experience to using git patches for documentation. (I store major changes as .adoc in git, tho, for versioning and backup.)\n\n4) The current wiki clients are just missing a diff, kind 1111 comments, and highlights. Some of the formatting styles need to be tidied up, regarding fonts and spacing, and whatnot, and they need some more QC. I might do that for Wikistr, if I can find a lull in my GitCitadel tickets.\n\n5) We have some ideas, for improving internal references (for example, footnotes), by making them into separate events, but that will be listed in the #NKBIP-03 page, that I'm about to write. (I will add a link to it, from here, later.) For now, I just use the Asciidoc syntax and it is rendered directly. I think this new event will take a long time, to structure properly, and we'll pilot it in a later version of Alexandria.\n\n6) If you have any factual/nonfiction information, that you think will be important to find, later, I would suggest you write it into a wiki page, not Kind 01. Not only does that improve its discoverability, it reduces the chance that relays will delete it.\n\n6) We, at nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz have decided that wiki functionality makes sense, to integrate into #Alexandria v0.2.0, so that has been added to the work breakdown structure. I don't expect us to have as much functionality, as a dedicated wiki app, such as [Wikistr](https://wikistr.com), but it will render the pages and the internal links will work.", "sig": "d563953b5bb9cdf4d035a187b2d7b583c9f8328e72eb824252e712dafdf564f57667e4155a66c916e5dd630d416a2319480a8d0bb915eb7192aa7359c8ff09f4" }