RE: Write a Steemit Web App: Part 11 - Posting Content

[neuromancer]

Interesting, again. Of note:

"...length of the slug must be between 1 and 255 characters..."

A byte, path depth, ? Hmm...

"...provide this in the metadata without actually having an image in the blog post..."

Custom thumbnails, anyone?

..."format seems to be either "markdown" or "html", depending on the content..."

Interesting, but, I wonder; I've made posts with mixed markdown & html tag content, which is necessary if you wish to make use of <div>s, for example:

### [useful resource](https://steemit.com/@neuromancer)
<div class=pull-right>https://steemitimages.com/DQmQMZPRjgWkSdhQZMYrmtm6PU9sS1HKSpVHzmjTXp9j2Se/noteymcnoteface.png</div> I will show you how to make some text that will wrap the noteymcnoteface.png image but also has <b>bold</b> and <i>italic</i> HMTL tagged text in it. <br> <br> In fact, I'm about to publish an article on it to help you all achieve advanced formatting for your work :]

Produces:

useful resource

I will show you how to make some text that will wrap the noteymcnoteface.png image but also has bold and italic HMTL tagged text in it.

In fact, I'm about to publish an article on it to help you all achieve advanced formatting for your work :]

Comments

[jfollas]

Again, I'm not sure how much Steemit (or other apps) actually depend on the format metadata value, so you may get the same results with no format specified at all (because it looks like they preserve sanitized html within markdown when it renders). I noticed after I posted that eSteem provides "markdown+html" as the format value in its posts.

But, because each app renders markdown differently, I would be concerned that doing anything really fancy would result in a post that looks bad when rendered on different apps. eSteem, for instance, does a bad job rendering markdown code blocks (and I'm not even a fan of how Steemit renders code - my own app will use Prism.js to enhance the styling of code blocks).

[neuromancer]

There really needs to be a canonical approach if they want authors to put any effort into formatting their articles. Somewhere over the rainbow.

Thanks for your efforts investigating and clarifying, I think the inspection and insight will prove useful to devs and may result in further consideration (provided someone's watching this).