{ "version": "https://jsonfeed.org/version/1", "title": "The Lab", "icon": "https://www.gravatar.com/avatar/5fd63e67639747af45ecf8f3b8c47b06?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png", "home_page_url": "https://ttscoff.micro.blog/", "feed_url": "https://ttscoff.micro.blog/feed.json", "items": [ { "id": "http://ttscoff.micro.blog/2026/09/12/this-is-an-example-of.html", "content_html": "

This is an example of what a post can look like when shared on social media. Thanks to the new Open Graph generator, links get a nice “card” preview with the headline of the post in the image, and a summary in the description.

\n

Marked Share is meant for, well, sharing. So making your documents look as inviting as possible is an important part of that. Hopefully these new features will make both of us look good!

\n", "date_published": "2026-09-12T09:37:45-05:00", "url": "https://ttscoff.micro.blog/2026/09/12/this-is-an-example-of.html" }, { "id": "http://ttscoff.micro.blog/2026/09/09/development-log-rich-media-apex.html", "title": "Development log: rich media, Apex fixes, and highlight cards", "content_html": "

A short tour of what just landed on Marked Share — with live examples in this post so you can see the plumbing instead of only reading about it.

\n

Apex 1.0.20

\n

Share renders with Apex. 1.0.20 fixes two bugs that showed up on real documents:

\n
    \n
  1. Mermaid fences with edge labels like A -->|Yes| B no longer get a fake table separator injected into the diagram source.
    2. \n
  2. Definition lists next to fences and callouts keep their order — prose after a DL stays before the diagram, not after it.
    3. \n
\n

Older shares that were stored with broken HTML can heal on open via on-read refresh.

\n

Definition lists

\n

MultiMarkdown / Kramdown-style definition lists work as styled <dl> blocks again:

\n
\n
Term
\n
The thing you are defining.
\n
Mermaid
\n
Diagrams from fenced mermaid blocks, drawn in the browser.
\n
SVG
\n
Inline vector markup that survives sanitization.
\n
Math
\n
TeX hooks from Apex ($…$ / $$…$$), typeset when MathJax is enabled on the page.
\n
Another term
\n
A second definition to show stacking.
\n
Yes, multiple definitions per term are fine.
\n
\n

Mermaid

\n

Labeled edges used to corrupt the fence. This graph should render cleanly:

\n
graph TD\r\n  Publish[Publish Markdown] --> Apex[Apex HTML]\r\n  Apex -->|Yes| Mermaid[Client Mermaid]\r\n  Apex -->|No| Plain[Plain pre block]\r\n  Mermaid --> Share[Share page]\r\n

SVG

\n

Inline SVG is allowed through sanitization (with dangerous bits scrubbed). A simple mark:

\n\r\n \r\n \r\n \r\n MS\r\n\r\n

Math

\n

Apex emits math hooks for inline and display TeX. With MathJax on the document page, these typeset; without it you still see the TeX source rather than nothing.

\n

Inline: the identity $e^{i\\pi} + 1 = 0$ still hits.

\n

Display:

\n

$$\n\\int_{-\\infty}^{\\infty} e^{-x^{2}},dx = \\sqrt{\\pi}\n$$

\n

Fenced math blocks are supported the same way Mermaid is (source in a math fence until the client runtime picks them up):

\n
\\sum_{n=1}^{\\infty} \\frac{1}{n^{2}} = \\frac{\\pi^{2}}{6}\r\n

Callouts

\n

GitHub-style callouts are enabled in the renderer:

\n
\n

[!NOTE]\nFront matter (YAML / MMD / Pandoc) is stripped from the HTML view only. Raw download and TextBundle still include your source.

\n
\n
\n

[!TIP]\nA paragraph that starts with Note: under an H1 is not MultiMarkdown metadata anymore — it stays on the page.

\n
\n

Front matter and the Word: bug

\n

Two related fixes:

\n\n

Highlight share cards

\n

Click a text highlight → share icon on the floating bar → live PNG preview with Download and Copy image.

\n

The card is square (1080×1080): document title, gradient quote (coral → purple), attribution. Handy for pasting into Slack, Notes, or social without screenshot gymnastics. Open Graph images for ?hl= links are still a follow-up.

\n

What else

\n\n

If something still looks wrong on an old link, open it once (refresh heals many cases) or republish. Bugs with a Raw vs rendered diff are especially helpful on support.

\n", "date_published": "2026-09-09T11:11:39-05:00", "url": "https://ttscoff.micro.blog/2026/09/09/development-log-rich-media-apex.html" }, { "id": "http://ttscoff.micro.blog/2026/01/31/this-is-a-weird-one.html", "title": "Third Test Post", "content_html": "

This is a weird one. Where do the titles come from?

\n", "date_published": "2026-01-31T11:05:58-05:00", "url": "https://ttscoff.micro.blog/2026/01/31/this-is-a-weird-one.html" }, { "id": "http://ttscoff.micro.blog/2026/01/31/test-post.html", "title": "Test Post 2", "content_html": "

How about one with categories? Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

\n\"\"\n", "date_published": "2026-01-31T09:45:43-05:00", "url": "https://ttscoff.micro.blog/2026/01/31/test-post.html", "tags": ["Test Posts"] }, { "id": "http://ttscoff.micro.blog/2026/01/31/this-is-just-a-test.html", "content_html": "

This is just a test post. I want to add Micro.blog support to BlogBook, so I need some posts to test with.

\n", "date_published": "2026-01-31T09:42:29-05:00", "url": "https://ttscoff.micro.blog/2026/01/31/this-is-just-a-test.html", "tags": ["Category 2"] } ] }