Integrate proposal for heading split

1. Figure out how to neatly split off any preface

2. Account for third-level ##

nostr:nevent1qqsgt3gd6ylu9jq3qclcdae70ch33gmfe50mxse74jcmreu36ur3plcpp4mhxue69uhkummn9ekx7mqzyzdy4n0tj7zktcn5jrw2vhyra8m9w302aswe5pq955k3nrq53xgnkw0u8zr

Reply to this note

Please Login to reply.

Discussion

I haven't forgotten this, but I'm taking a 2-week vacation. Top prio, when I get back.

Maybe the guys will be further along with the Alexandria viewer, by then, so we can actually visualize the uploaded data.

nostr:npub1nf9vm6uhs4j7yaysmjn9eqlf7et5t6hvrkdqgpd995vcc9yfjyas0pxa3x

What he said! ^

Header 1 (=) is the publication title

Header 2 (==) is the section title

Headers 3-6 (=== to =======) are discrete headers (the equivalent to Markdown headers, so they do not result in a section-event split and are not included in the table of contents

Header 7 (=======) throws an error, for two many headers.

Finally figured out what to do with extra headers.

yeah, it's like my answer to more languages than just Go and JSON

>ERROR

Preamble will be automatically created, as a new section, if present, and given the header "Preamble".