Oddbean

▲ ▼

 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?

▲ ▼

 So, I'd go for #3:
have a pre-selection dialog for the kind pattern (currently 30040/30041s or each kind alone), and have a small drop-down label, above or next to each section, where they can adjust the kind, but that is currently disabled and read-only. (They'll eventually need to be able to add/remove sections, as well, but that's future music.)

30041 alone because they may already have a 30040 and just want to add something new to the list.
30040 alone because they may just want to create an index for things that already exist.

▲ ▼

 LOL changed my mind, after Reading what @Low Information Voter said. Want three steps, like a little wizard, so that they can follow what the client is "doing".

1) Pretty asciidoc preview
2) Kind structure selection dialog
3) Split view with disabled kind labels

▲ ▼

 I would just do the publish button, tho. No fourth dialog.

▲ ▼

 https://media.tenor.com/Dlc_glBnd6oAAAAC/good-omens-leigh574.gif

▲ ▼

 We could have a little confirmation pop-up as one final exit hatch in case the user changes their mind.

▲ ▼

 I would think that creating an index of things that already exist would be a separate workflow.  It might start while browsing in reading view.  The user clicks a button next to a note that says "remix" or "add to index," and they are taken to an editor/search view where they can find other notes to add to the index and/or write their own content.  I still need to think that through, since it's different from purely writing new content.

Kind selection also impacts how we might parse the AsciiDoc content.  If a user wants to publisj a wiki article, we probably wouldn't break down the content into smaller events.  Rather, it would be one large wiki event kind.  I'll have to think through how to represent that in the UI.  Changing kinds may cause sections to merge together and such.

▲ ▼

 Would probably need a draft, for that workflow. A kind 30042 or something, for draft 30040s.

▲ ▼

 I have a doll
To send you if that’s okay. If not, totally understand and respect 🫡 

Hugs 🫂 my beautiful 🤩 fren

▲ ▼

 30041 by itself is perfectly reasonable - something to group together later on, perfectly alignes with the idea of 'Zettel'. You can publish 20 events of random notes coming from spontaneous ideas, the benefit being that it's nostr native but explicitely won't flood your followers' feeds like wiki articles.

▲ ▼

 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.

▲ ▼

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

▲ ▼

 That would be easier to implement.

▲ ▼

 What about also allowing 30041 alone?

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

▲ ▼

 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.