Try reading the article on notestack.com, the way i handle titles and images is a little more sane in imo, it accounts for the title and cover image so that they aren’t shown on the article page.
that way everything can be contained in the content.
As an example checkout this article on both notestack and habla:
https://notestack.com/liminal@gitcitadel.com/mfayffebPrMI520ftzIlE
https://habla.news/u/liminal@gitcitadel.com/mfayffebPrMI520ftzIlE
you’ll notice that the cover image is not included in the article (because it’s not in the content) which is similar to how medium does things. It also parses out the first top level header if it matches the title tag so they aren’t duplicated.
Also if you like the editor in comet notestack uses basically the same one, I’m keeping them in sync until i can provide the editor as a resuable library/component that other longform sites can use.
Definitely makes sense. Thanks for the explanation.
Since these articles are appearing on my website (powered by npub.pro), I have to format them in a way that it will display them properly.
Still really like how easy the flow of writing in Comet and publishing when ready is, though. I will probably just continue to publish from Comet initially and make a few refinements in Habla as needed.
Also maybe i can see what the creator of npub.pro thinks about my approach, maybe we can get everything in sync. I’m willing to change how comet works when publishing so that it parses the first h1 markdown title and allows you to choose a different image as the cover image if we’re all agreeing that’s the standard.
That'd be nostr:nprofile1qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uq3xamnwvaz7tm0venxx6rpd9hzuur4vghszythwden5te0dehhxarj9emkjmn99uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzpmhxue69uhkummnw3ezumt0d5hsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9uq3wamnwvaz7tmzd96xxmmfdejhytnnda3kjctv9uqs6amnwvaz7tmxxaazu6t09uqzqv6kmesm89j8jvww3vs5pv46hqm7pqgvpm63twlf9hszfqzqhz7a0hw5s7 . Also Habla would be nostr:nprofile1qythwumn8ghj7enjv4h8xtnwdaehgu339e3k7mf0qy88wumn8ghj7mn0wvhxcmmv9uq3samnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5hsz9mhwden5te0vd5xzerx9ehx7um5wgcjucm0d5hsz9rhwden5te0v9kxwmeww468smewdahx2tcpzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpzpmhxue69uhkztnwdaejumr0dshszgrhwden5te0vf5hgcm0d9hx6ctcd9kkzmrfwd68xtn0dekxjmn99uq36amnwvaz7tmzdaehgu3wvf5hgcm0d9h8g7r0ddhjucm0d5hszrmhwden5te0gphx7uewd3hkctcqypl62m6ad932k83u6sjwwkxrqq4cve0hkrvdem5la83g34m4rtqegh35495 . May as well get nostr:nprofile1qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgdwaehxw309anrw73wd9hj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9uqjqamnwvaz7tmzd96xxmmfdekkz7rfd4skc6tnw3ejummwd35kuef0qy8hwumn8ghj7srwdaejumr0dshszyrhwden5te0vyhxummn9ekx7mp0qythwumn8ghj7cnfw33k76twv4ezuum0vd5kzmp0qy2hwumn8ghj7ct9va5hxtn4w3ux7tn0dejj7qgawaehxw309a3x7um5wghxy6t5vdhkjmn50phkkmewvdhk6tcqyrafsj7hmweg9ur7zmn6apajdg48hxuskujx53rhrux0ttjcqx84yef2jta in on the conversation since he's got Highlighter, and the guys over at nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3xamnwvaz7tm0venxx6rpd9hzuur4vghszxnhwden5te0dehhxarj9eax2cn9v3jk2tnrd3hh2ep0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpr4mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mf0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qyd8wumn8ghj7un9d3shjtn8v46xzmrz0yhxxmmd9amrzqghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qgawaehxw309ahx7um5wgknqv3w09skk6tgdahxuefwvdhk6tcqyqsfsmac8em4m9k33r99e803pnndvylqadl9w69q7zcjkd7d4ssmxld2um7, too.
I have no experience with markdown/long-form editors, and not sure why one approach would be more beneficial than the other. AFAIK all nostr long-form apps expect title/image in tags, not content, so if we decided to make changes here we'd have to convince at least half-dozen apps to comply, which is not trivial. Can you please repeat the benefits of it?
