buttercat1791 on Nostr: I'd like some design feedback on Alexandria. I'm working on an article editor ...
I'd like some design feedback on Alexandria.
I'm working on an article editor feature. A screenshot of an early draft is below. The overall goal is to be able to type AsciiDoc-formatted text, preview it in rich text form as it would appear in the Alexandria reader view, then publish it as a cluster of kind 30040 and 30041 events.
My thinking is to break the content down into sections. The content of each section will be published as a kind 30041 note. Each section will be indexed by a kind 30040 note, which will reference the content of the section as a kind 30041 and any subsections as 30040 notes.
Question: How would you like to preview your published events?
I see two options:
1. There are two preview steps: one is a "quick preview" you can see with a click while editing. It doesn't break the content down into 30040 and 30041 events, but it shows you what the nicely-formatted AsciiDoc content would look like. The second preview steps shows the content as it would appear in reader view, after it's been broken down into its constituent 30040 and 30041 events. This preview would have a confirmation dialogue that lets you approve or cancel publishing the events.
2. There's just one preview, and clicking the preview button while editing shows you the content as it would appear in reader view, broken down into 30040 and 30041 events. There would be no separate screen with a confirmation dialogue, and a publish button on the editor page would publish the events.
I'd love to hear people's thoughts!
#asknostr #alexandria #gitcitadel #nostrdev #nostrdesign
Published at
2024-09-05 04:32:27Event JSON
{
"id": "095549496355699f8e02070fed20539361dcd97f13f054f3ec86dfbadf4701f6",
"pubkey": "70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9",
"created_at": 1725510747,
"kind": 1,
"tags": [
[
"t",
"asknostr"
],
[
"t",
"alexandria"
],
[
"t",
"gitcitadel"
],
[
"t",
"nostrdev"
],
[
"t",
"nostrdesign"
],
[
"zap",
"846ebf79a0a8813274ec9727490621ad423f16a3e474d7fd66e6a98bfe4e39a4",
"",
"80"
],
[
"zap",
"70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9",
"",
"20"
]
],
"content": "I'd like some design feedback on Alexandria.\n\nI'm working on an article editor feature. A screenshot of an early draft is below. The overall goal is to be able to type AsciiDoc-formatted text, preview it in rich text form as it would appear in the Alexandria reader view, then publish it as a cluster of kind 30040 and 30041 events.\n\nMy thinking is to break the content down into sections. The content of each section will be published as a kind 30041 note. Each section will be indexed by a kind 30040 note, which will reference the content of the section as a kind 30041 and any subsections as 30040 notes.\n\nQuestion: How would you like to preview your published events?\n\nI see two options: \n\n1. There are two preview steps: one is a \"quick preview\" you can see with a click while editing. It doesn't break the content down into 30040 and 30041 events, but it shows you what the nicely-formatted AsciiDoc content would look like. The second preview steps shows the content as it would appear in reader view, after it's been broken down into its constituent 30040 and 30041 events. This preview would have a confirmation dialogue that lets you approve or cancel publishing the events.\n\n2. There's just one preview, and clicking the preview button while editing shows you the content as it would appear in reader view, broken down into 30040 and 30041 events. There would be no separate screen with a confirmation dialogue, and a publish button on the editor page would publish the events.\n\nI'd love to hear people's thoughts!\n\n#asknostr #alexandria #gitcitadel #nostrdev #nostrdesign\n\nhttps://image.nostr.build/2328fa70d7207dfbfa0196a869dadae7cb03925005786456a00e6107b905438e.png",
"sig": "52192477382ffa3b021967ad64d4de7730cc38ad59d2fb352f2a9c21ab7b194f798ffb82641c8ac72ca2155f56d3be7798ff948af1f7706b15b1554619589572"
}
