Typing all that stuff is a pain not because it’s difficult to understand the syntax, but because it just takes so much time to type all that out. The biggest reason to use Markdown is that it’s essentially shorthand HTML. Why would I want to type out all that code- John Siracusa style-just for images? I even considered omitting image captions entirely, as the ‘standard’ Markdown image syntax of !(image link) is parsed perfectly by markdown-it. Here’s what I found: Are You Getting It? Ĭasey was using regular-old HTML HTML5 for his images.Īt first I scoffed at this. for the past year, I peaked at the source for one of his posts containing an image with a caption. Unsure of what image syntax Camel would support, I followed Casey’s lead. In order for those posts to get parsed correctly by markdown-it, I would have to make changes to the image syntax. But that didn’t make the old posts formatted with MultiMarkdown 3 syntax play nice with Camel. Using Byword for future posts was an excellent prospect. This nullified my reliance on MultiMarkdown Composer and made it so that I could go back to using Byword. So the easy image syntax I used in the example above would not work using markdown-it and Camel. ![]() markdown-it, even with plugins, does not support any of the nifty image syntax offered by MultiMarkdown 3 and MultiMarkdown Composer. Within Camel, perhaps Byword could find a new purpose? Images In Camel ¶Ĭamel uses an npm package called markdown-it, which is what actually takes the Markdown files and parses them to HTML. Moving to Camel was an opportunity to re-examine my writing workflow. Still, I was stuck with the latter due to my dependence on the full MultiMarkdown 3 spec for easy image captions. Metaclassy did a great job with gradients and shadow effects, as well as other pleasing design touches. But it’s true: Byword’s UI/UX is just better than MultiMarkdown Composer’s. Yes, I realize how weird it may seem for me to describe a plain-text editor as homey. While MultiMarkdown Composer surely got the job done, it never quite felt like home. MultiMarkdown Composer was the only way to achieve easy image captions, so I started using it instead of Byword. The template files are based on Handlebars for auto-table-of-contents, and most importantly, lots of nifty image syntax.įor instance, if I wanted to embed an image with caption in MultiMarkdown Composer, this is all I would have to write: !Īnd this is the resultant HTML: Caption īyword, for whatever reason, doesn’t offer easy image-captioning. These template files specify page attributes such as page headers, page footers, etc. Casey designed his blogging engine such such that camel.js generates all the posts and the rest of the website using these template files. ![]() Unlike Squarespace, in Camel, having metadata within the actual Markdown files is absolutely necessary. I wish Camel supported metadata in the format that Byword supports, but it doesn’t out of the box. The metadata’s there when viewing the Markdown source, but disappears when parsed to HTML. Byword's MultiMarkdown-style metadata and HTML parseīyword’s metadata support is everything I would want in a plain text filing system. Byword would then omit that when parsed to HTML. Byword is smart enough to know that properly-formatted text placed at the top of the document denotes metadata. ![]() All of my posts since TheOverAnalyzed 2.0 had Title:, Date:, and Link: metadata. Metadata ¶ Previously On TheOverAnalyzed ¶īefore transitioning to Camel, I adopted a hybrid metadata system inspired by both Byword’s MultiMarkdown guide, and, perhaps fortuitously, Camel itself. In preparation for the move, I made tweaks to metadata, images, and footnotes. It was, however, extremely time-consuming. ![]() Modifying my plain text files for use with Camel wasn’t particularly difficult. Not only would redirects have to get sorted out, I also needed to make sure that the old posts looked correct in the new platform. Introduction ¶Ī goal of mine from the beginning was to port over the ~250 posts I had accrued while using Squarespace. And when you’re done with this post, you can read the next one as well. If you haven’t already done so, you should read the first post in the series. This is Part II of the series entitled Leaving Squarespace, in which I outline how I left a traditional CMS and dived deep into Casey Liss’s static blogging engine, Camel.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |