JSONFeed VS mdx

If you have a web feed, be it RSS or Atom or JSON Feed, help others discover it!

Imagine you have an RSS feed similar to this. The objective is to obtain that RSS feed, analyze the data it contains, and take action with it. RSS is an XML format, whereas JSON is arguably easier to work with than XML. While many APIs provide JSON results, RSS is less likely to receive them, despite their existence.

At least for now, Astro clearly falls short in this category. Its built-in ability to provide RSS feeds is rather limited, and it doesn’t yet enable JSON feeds at all.5 In the meantime, some users, including Yours Truly, have gotten around this by using the third-party feed package, which supports RSS and JSON feeds.6

want to also support JSON Feed?

-------- # Metadata comes from _data/metadata.json permalink: "{{ metadata.jsonfeed.path | url }}" eleventyExcludeFromCollections: true -------- { "version": "https://jsonfeed.org/version/1", "title": "{{ metadata.title }}", "home_page_url": "{{ metadata.url }}", "feed_url": "{{ metadata.jsonfeed.url }}", "description": "{{ metadata.description }}", "author": { "name": "{{ metadata.author.name }}", "url": "{{ metadata.author.url }}" }, "items": [ {%- for post in collections.posts | reverse %} {%- set absolutePostUrl %}{{ post.url | url | absoluteUrl(metadata.url) }}{% endset -%} { "id": "{{ absolutePostUrl }}", "url": "{{ absolutePostUrl }}", "title": "{{ post.data.title }}", "tags": [ {%- for tag in helpers.removeCollectionTags(post.data.tags) -%} "{{tag}}" {%- if not loop.last %}, {%- endif %} {%- endfor %}], "summary": "{{ post.data.description }}", "content_html": {% if post.templateContent %}{{ post.templateContent | dump | safe }}{% else %}""{% endif %}, "date_published": "{{ post.date | rssDate }}" } {%- if not loop.last -%} , {%- endif -%} {%- endfor %} ] }

Your wish is my command.

Semantify was made for content creators, marketers, and anyone looking to enhance their long-form written content. Currently only supporting MDX-based content, It automates the enrichment of MDX blog posts by adding AI-generated Q&A sections that summarize the content, and recommendations for semantically similar posts. This not only makes the content more accessible and engaging but also helps in establishing deeper connections between different posts, ultimately keeping the reader engaged for longer periods.

https://mdxjs.com/

> We thought this would be a no-brainer and that there would be some CMS/SSG libraries out there that made this Markdown conversion process easy and facilitated integration with any number of frontend frameworks.

You thought correct:

- NextJS MDX integration: https://nextjs.org/docs/pages/building-your-application/conf...

The example above uses react-markdown, but you can use any library you want to render the markdown content. You can also use a transform function to modify the markdown content during the build process. Here is an example that uses MDX to compile the markdown content.

MDX is a js library that allows us to import a markdown file as a react component and use it anywhere.

/blog/ - This directory contains all the markdown files, of your site blogs, you can simply add a new blog by using markdown, or simply remove a blog file by deleting its file, you can combine the markdown with MDX, resulting a well-written blog post.

Hey HN!

This is a little personal project I've been hacking on for the past ~week, somewhat inspired by this blog post [0] ("My Wonderful HTML Email Workflow").

Basically I just wanted an easy way to create email templates in MDX [1] (Markdown + JSX), using React Email [2] components.

It's still a bit of a work in progress (and a bit slow at the moment) but wanted to share in case anyone else finds it interesting!

[0] https://www.joshwcomeau.com/react/wonderful-emails-with-mjml...

[1] https://mdxjs.com/

[2] https://react.email/

That’s why formats like Markdown (MD) and MDX (MD with support for JSX) are so popular for use cases like documentation, knowledge bases, or technical blogs. They allow you to use any kind of custom formatting or elements and then process the content for publishing. On top of that, they’re great for implementing a docs-as-code approach, where your documentation lives right beside your code (i.e. in a Git repo).

MDX