> "Inspired by @evan 's recent article on advancing long-form text in the social web, we've taken the leap and developed our first prototype for publishing and reading articles on Bonfire, based on the FEP-b2b8 draft specification."
Here the article on how we are implementing articles in bonfire 馃槄
also as a heads-up, <a> elements in summary properties tend to be rather messy on other servers (and in clients), so you're probably better off sanitizing those out of any summary property before sending it over the wire
url and id props of the object at https://bonfire.cafe/pub/01JYRX7HCGME693BGCZF6AGGK1 are both https://bonfire.cafe/pub/objects/01JYRX7HCGME693BGCZF6AGGK1, so that other URL without /pub/ in it is not present on the article. For consistency you probably wanna use https://bonfire.cafe/pub/objects/01JYRX7HCGME693BGCZF6AGGK1 as the id and https://bonfire.cafe/post/01JYRX7HCGME693BGCZF6AGGK1 as the url.
@bonfire I think the top-level summary prop should probably just be Long-form content in Bonfire: Part 1 馃 But that's just an opinion
@bonfire text area probably makes sense. On a ux level you probably want to have people enter either a summary (for articles) or a cw/summary (for notes). I'd say if no user-entered summary is present on an article, use the first x characters with ellipses at the end (converted to plaintext from the interpreted html). Just my onion though!
A space for Bonfire maintainers and contributors to communicate
