Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dtedesco1
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
1.
▲
The Age of Decision
(threerulescompany.com)
1 points
by
dtedesco1
3mo ago
|
0 comments
2.
▲
When model distillation becomes a diplomatic incident
(underlines.news)
1 points
by
dtedesco1
5mo ago
|
0 comments
3.
▲
by
dtedesco1
1y ago
> taking care of all the hairy details around `<CustomComponent>...</...>` Precisely! Thank you. Can you share more about what you have in mind for frontmatter? I don’t really understand the need/use cases yet.
4.
▲
by
dtedesco1
1y ago
Bingo!
5.
▲
by
dtedesco1
1y ago
Thanks for calling out. I’ve opened [an issue to look into this]( https://github.com/dtedesco1/nextjs-markdown-boilerplate/iss... ).
6.
▲
by
dtedesco1
1y ago
Awesome work. Very snappy and crisp. For this project, I’m still stuck in React hell though because I want to use React components XD
7.
▲
by
dtedesco1
1y ago
This is great! Thanks for sharing.
8.
▲
by
dtedesco1
1y ago
I actually previously used Jekyll! Built this largely because I want full React component functionality sometimes . Also I think Jelyll gave me some issues with routing that I didn’t like.
9.
▲
by
dtedesco1
1y ago
These are great for adding more flavor to md -> html, but I want to be able to use React components sometimes, not just JS/CSS.
10.
▲
by
dtedesco1
1y ago
You’re getting close. The biggest thing is that I want to be able to use React components sometimes and anywhere on the page. If you just want md -> html, there are of course much better options.
11.
▲
by
dtedesco1
1y ago
Yep, but I still want to use React components sometimes. That’s my biggest holdup.
12.
▲
by
dtedesco1
1y ago
These look really promising! Can I bring existing React components with me to any of them? That might be the biggest hold up. I’d also worry about maintainability as web standards evolve, since these (mostly) seem like pretty small projects
13.
▲
by
dtedesco1
1y ago
Can I still bring my React components when I want them? Haven’t tried out HTMX yet.
14.
▲
by
dtedesco1
1y ago
Intriguing. Does it render React components when you want to add them?
15.
▲
by
dtedesco1
1y ago
Ha! I would love that.
16.
▲
by
dtedesco1
1y ago
Haven’t gotten this feedback from anyone else. Are you using a browser extension(s) that might be affecting how it renders?
17.
▲
by
dtedesco1
1y ago
Agreed! Give me a better option that supports React components?
18.
▲
by
dtedesco1
1y ago
but nextjs is in the title… :)
19.
▲
by
dtedesco1
1y ago
Does Obsidian support React components when you want to add them? That’s my biggest issue.
20.
▲
by
dtedesco1
1y ago
That’s good if I’m really *only* ever using Markdown. But what about wanting to use React components sometimes? That’s my biggest problem.
21.
▲
by
dtedesco1
1y ago
It’s the I-sometimes-want-to-use-React-components issue that is my holdup. They make it easy to do some visual/behavioral stuff and are often directly portable from other sites or oss projects.
22.
▲
by
dtedesco1
1y ago
This makes sense for one-way posting, but there are two issues for my main use case (personal and small company websites): 1. I want to edit the pages sometimes, and I want to do so using markdown without extra steps. 2. I still want to use
23.
▲
by
dtedesco1
1y ago
I agree, but it's just too difficult to get away from the React ecosystem... Do you have suggestions on a better alternative?
24.
▲
Next.js 15 Markdown Boilerplate
(github.com)
45 points
by
dtedesco1
1y ago
|
68 comments
25.
▲
by
dtedesco1
1y ago
I wanted a dumb & simple way to make a modern website with text files, so I made one. Small, static-first Next.js boilerplate, intentionally minimal, just markdown → website, with optional React components when you want them. Just updat
26.
▲
by
dtedesco1
2y ago
Given you have an existing website, it might be easier for you to add Markdown support to your site through a static site generator or server-side conversion step. Or you can even use a Markdown-to-HTML tool (I believe pandoc has this featu
27.
▲
by
dtedesco1
2y ago
Three main reasons, two functional and one practical: 1. Built-in MDX support means you can seamlessly mix Markdown and React components. (I previously had some trouble with the @mdx-js/react library and was in the market for more nati
28.
▲
Show HN: Minimal Next.js 15 Markdown Boilerplate
(github.com)
19 points
by
dtedesco1
2y ago
|
6 comments
29.
▲
Show HN: A *simple* Python interface for multiple LLM providers
(github.com)
2 points
by
dtedesco1
2y ago
|
0 comments
30.
▲
by
dtedesco1
5y ago
Since I don't post about myself much on social media and I'm a bad correspondent, it's been a really wonderful way to keep in touch. Also, seeing myself change over time and hearing back from long lost friends are added benef
More ›