Nostr

Does it necessarily have to be a 30040/41 combination? They will eventually be able to publish wiki pages, too right, or a 30040 that contains a wiki page or another 30040. So they need to be able to define which kind each section should have, with 30040/30041 simply the default.

I'm just thinking that it might make sense to go full modularity in the design, from the start. Also probably need to put a help text above the editing field, that explains where you will define a split. Like, what happens with the content in the preamble? Does it go into a summary tag or does it get a preamble 30041? Is the header where you type in stuff that will end up in optional tags? Which tags will you process and how do they need to type them in? Can they see that information in processed form in the preview?

liminal 🦠 1y ago

In the writing of an article, i think we should focus on the 30040/41 pair. Keeps it simple, the idea being 30040/41 is about as basic an object you can create for 'knowledge'. Blogs, docs, etc. can always be broken down into grouped 30041.

In the case for composing collages or grouping related ideas from different events, that's when we can think about what the process will be.

Reply to this note

Please Login to reply.

Discussion

Laeserin 1y ago

Okay, so hard-code everything to 30040/41 for the alpha release?

MichaelJ 1y ago

That would be easier to implement.

Laeserin 1y ago

What about also allowing 30041 alone?

I guess that already forces you to have a structure selection interface.

MichaelJ 1y ago

Yeah that's an option. I'll have to really knuckle down and figure out how to design/build the UI to make that possible. Flexibility is hard to code.

Laeserin 1y ago

And opens up bugs.

Maybe the structure just needs to be an Asciidoc field. 🤔 Like "top-level: 30041" or "top-level: 30040", and if they have nothing, then it's default 30040.