[BLOG] Add metadsl.md

[MarsBarLee]

Link to blog post, successful build.

Links to other Quansight blogs:

There is no need to check for Blog2Blog links due to updated website build.

Text styling

• The blog is written with plain language (where relevant).
• If there are headers, they use the proper header tags in order to do so (with only one level-one header).
• All links describe where they link to (for example, check the Quansight labs website).
• Any kind of styling that the author uses (for example, bold for emphasis) is consistent throughout the blog.

Non-text contents

• All content is represented as text (for example, images need alt text and videos need captions or descriptive transcripts).
• If there are emojis, there are not more than three in a row.
• Don't use flashing gifs or videos.
• If it were to be read as plain text, the blog still makes sense and no information is missing.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
consulting	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 21, 2023 at 10:52PM (UTC)
labs	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 21, 2023 at 10:52PM (UTC)

[gabalafou]

Something's not right.

The preview build of the blog post at this slug metadsl is actually showing the blog post at slug metadsl-talk.

Probably a bug in the blog post slug routing machinery.

[MarsBarLee]

I've renamed the blog title from metadsl to metadsl-2019-05, following the solution suggested in #552. It now successfully directs to correct blog post, not metadsl-talk anymore.

Here's the built blog gallery and here's the built blog page itself.

[gabalafou]

Comparing this with the post on the old blog, I think it has the same issue that we are tracking in #679.

This doesn't look right to me. Here is a screenshot showing a portion of the blog post on the new site. Sandwiched between plain prose text, there is a code block and immediately following the code block, there is a single line, add(from_str('a'), from_str('b')), which should be formatted to look like the output from the code block, but to my eyes it looks like it is indistinguishable from the surrounding prose:

[MarsBarLee]

@gabalafou You're right, that is a code output. I've added this PR to the tracking issue. Thanks for catching that!