-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🎬 MDX landing page #444
Comments
Suggestion: Two-pane layout at the topLeft pane is typed out via something like react-typist (and syntax highlighted) and the right pane is the auto-updated (in sync with typing) rendered result (with a small link at the bottom to view the HTML output) It animates between ~5 examples of cool things that are possible via MDX and transitions to each one, via the typing animation. The examples are shown in labeled tabs. Ideally, each example is modifiable -- either inline or otherwise. If the user modifies the code, the animation is stopped. If the animation feels too slow, then only animate the first time and subsequently show the other examples without animating. Left pane:import TomatoBox from 'tomato-box'
export author = "Fred Flintstone"
export default = props => <main {...props} />
# Hello, world!
Here is a paragraph
<TomatoBox /> Right pane:
If you scroll down, then it shows the sections you mentioned. Happy to build a prototype of this suggestion you'd like! |
@Jarred-Sumner I think that'd be great! Would be especially awesome if the functionality was style agnostic so we could reuse in a couple places in different contexts. This would overlap with #220 as well. |
There’s a new WIP home page out, here: https://v2.mdxjs.com. Along with a new RC that could use feedback! |
MDX landing page
It's prolly about time MDX got a landing page. Here's some rough thoughts on what I've been thinking about. Would love to hear other's thoughts as well.
This is intended to start a discussion on what type of content would go nicely and what the basic structure could look like. We're interested in any and all thoughts.
Goals
The primary goal is to better describe MDX in a more accessible way. For less tech-savvy users it's a rough landing to visit mdxjs.com and end up directly in docs. We currently don't explain it well either (that's definitely on me).
It'd also be better to go more in depth on why MDX was created: to empower authors to write dynamic, engaging, and immersive content.
Terms
The following things I think might be good to emphasize (or something like it):
Sections
The following sections would be nice to have (maybe some are overkill or I'm missing better possible sections):
Playground
It might be better to show than tell so we could have a live editable MDX editor.
How it works
I think it'd be cool to show the three "stages". Ideally the HTML section will be actually rendered. Maybe this could even be dynamic?
Features
Something based on the content from the features section on mdxjs.com
Use cases
Testimonials
Might be worthwhile talking to some happy users and get some quotes.
Why?
Something that illustrates or describes the motivation for writing MDX.
Projects
Tooling
Works with the tools you already use
Plugins
Talk about the remark/rehype ecosystem and interesting things you can do with plugins. Potentially could even show an example.
Showcase/gallery
Images of some awesome MDX sites (#414).
Important links/data
Search
Think we can use algolia for this, but would be great to incorporate a search bar since the docs are growing and should grow immensely with the new content planned for v1. Though this doesn't have to be part of the MVP.
The text was updated successfully, but these errors were encountered: