website VS mdx

Graphics programming analysis done using examples written in WebGL–genius. Hypertext that takes full advantage of the medium. This reminds me of something I'd see on https://pudding.cool/, but it goes far more in depth than anything there. Absolutely fantastic article.

I've been using MSAAx4 in my rendering engine for some time and only recently have considered switching to a FXAA / TAA implementation. I'm actually not sure I'm going to go through with that now. I definitely learned a lot here, and will probably use the analytical approach for UI items, I hadn't heard about that anywhere.

Not often you see graphics-programming stuff on HN. For anyone interested in more graphics write-ups, this list of frame breakdowns is one of my favorite resources:

https://www.adriancourreges.com/blog/

I think NY Times started long back and this style was kinda "cool" that goes well with the narrative. Then, there is https://pudding.cool that does this pretty well. Now, many just copy and tries without a meaningful treatment and is just there - kinda not working-out in most cases.

Tip: Try reading with Reader Mode.

Also check out https://pudding.cool if you’re unfamiliar and enjoy extremely high effort visualizations alongside editorial and educational text content.

Hello all, I am a JS beginner and I am passionate for creating data-driven stories on a website, like Pudding. I have watched some YT videos and learned that Python is a basic skill for dealing with data. However, I am confused about what Python does in such website? I know JS and it libraries like D3.js are used for front-end development and interactive data display, then what's the role of Python? For the website backend (such as Django)? Or is used for data cleaning and analysis? Or others? Or python is not actually required for making a data-driven story website?

https://pudding.cool/ ?

The main reason why I've got interested in frontend is that (1) it seems to be a field that can be much more diverse and collaborative across different fields (ex: working with designers) and (2) it directly interacts with users. Interactive journalism, data visualization, data storytelling (as in The New York Times or The Pudding) are my main interests currently, so it is more accurate to say I got interested in frontend with focus on those specific fields.

pudding.cool, statistical analysis of things like rap lyrics

Official MDX site

For anyone wondering, MDX is a mix of Markdown and JSX: https://mdxjs.com/.

Storybook simplifies working on those hard-to-reach spots in your codebase by providing an isolated workspace. It is a separate framework-agnostic app within your repository. You can do everything from developing components to documenting all different component states and showcasing them nicely using MDX with clickable demos and interactively changeable component arguments. You can also test your components within Storybook. Storybook's add-on API allows you to tailor it to your needs.

You might want to reconsider the name. MDX is already a well-known technology that combines markdown with JSX https://github.com/mdx-js/mdx/

MDX - write JSX in markdown documents!

I think this would be great as an evolution of MDX (https://mdxjs.com/). MDX is already pretty popular for documentation and it plays well with React but unfortunately there is no framework that adds interactivity to MDX which will enable use cases like data applications.

This is where MDX comes into play. It's essentially a hybrid of JSX / React and a well-specified dialect of Markdown. Essentially, this allows writing texts that are as simple as plain Markdown, as well as creating complex components as you might have done in full JSX.

MDX is great for this, you can intermix JS/TS, JSX, and Markdown

https://mdxjs.com/

You can write your components normally and pass them in to be available in MDX

MDX — Write React code within Markdown.

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.