Showcase
·
2 min read
tl;dr: A demonstration of all MDX features available in this blog.
Text Formatting
This section shows bold text and regular text mixed together. You can also use inline links like Astro or GitHub.
Default highlighted text. Green highlighted text. Pink highlighted text.Code Blocks
Here’s a bash command:
nixpacks build . --name myapp
And a JSON configuration:
{
"providers": [],
"buildImage": "ghcr.io/railwayapp/nixpacks:ubuntu-1716249803",
"variables": {
"CI": "true",
"NODE_ENV": "production"
},
"phases": {
"build": {
"cmds": ["bun run build"]
}
}
}
Simple Bullet Points
- First item in the list
- Second item in the list
- Third item with a link
Bullet Points with Bold Labels
- Document everything. Future you will thank you.
- Sleep on it. Stuck on a bug? Sleep. Solve it at breakfast.
- Take breaks. Regular walks lead to better code.
- Version control. Git is your best friend.
Interactive Components
Decision Toggle
Lots of what. Zero why.
Now you actually know why.
Flip Cards
Click cards to flip
Gave 20% discount
tap to see the whyGave 20% discount. Customer had 3 unresolved critical tickets, similar deal got exception last quarter, VP approved citing churn risk
tap to flip backChanged button color to blue
tap to see the whyChanged to blue. A/B test showed 12% higher clicks, client approved in Figma comment, aligns with new brand guidelines v2
tap to flip backRejected candidate
tap to see the whyRejected. Strong technical skills but culture fit concerns raised by 2 of 3 interviewers, similar profile didn't work out last quarter
tap to flip backRemoved feature X
tap to see the whyRemoved feature X. 2% usage, 10hrs/week maintenance cost, team voted 4-1, CEO approved, migrated 12 affected users to workaround
tap to flip backCommit Compare
6 months later: "Why did we change this?"
Good luck figuring that out.
fix(auth): increase session timeout to 60min
Users on slow connections were getting dropped at 30min.
Support tickets up 23% this month from timeout issues.
Discussed with security team - low risk given we
already have refresh token rotation.
Closes #234
6 months later: "Why did we change this?"
You already know.
Agent Simulation
Checking customer history...
Checking open tickets...
Searching precedent...
Routing for approval...
Saving decision trace...
Energy Meter
Decision Form
Try it yourself
Save this somewhere. You'll thank yourself in 6 months.
Reveal Quote
Want the secret?
Call to Action
P.S. follow me on Twitter for more updates!