Preferences

dtedesco1
Joined 27 karma
https://dtedes.co

  1. > 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.

  2. Thanks for calling out. I’ve opened [an issue to look into this](https://github.com/dtedesco1/nextjs-markdown-boilerplate/iss...).
  3. 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
  4. This is great! Thanks for sharing.
  5. 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.
  6. 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.
  7. 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.
  8. Yep, but I still want to use React components sometimes. That’s my biggest holdup.
  9. 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.
  10. Can I still bring my React components when I want them? Haven’t tried out HTMX yet.
  11. Intriguing. Does it render React components when you want to add them?
  12. Ha! I would love that.
  13. Haven’t gotten this feedback from anyone else. Are you using a browser extension(s) that might be affecting how it renders?
  14. Agreed! Give me a better option that supports React components?
  15. but nextjs is in the title… :)
  16. Does Obsidian support React components when you want to add them? That’s my biggest issue.
  17. 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.
  18. 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.
  19. 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 React components *sometimes*.

    3. I want it to be really easy to deploy and monitor. Nextjs is really easy for those things.

    Solving the first issue and third issues don’t require React, but the second definitely does. So I’m still stuck.

This user hasn’t submitted anything.