Hacker News new | ask | show | jobs
by rchaud 1689 days ago
My experience is with WYSIWIG tools like Dreamweaver and more recently, Bootstrap Studio, which includes all the UI elements of the BS library. Those let you build standard websites where HTML and CSS are separated.

What was the reason for going with React components? I thought those were for web apps with a lot of interactivity and changing states. I don't know much about React/Vue beyong the fact that they use a virtual DOM, so I'm curious.
1 comments
putrikarunia 1689 days ago
Oh hmm I'm not familiar with Bootstrap Studio, but from what you described, it's quite different because our users don't interact with the underlying HTML/CSS of their sites.

We use React because our editor is built in React (which does have a lot of interactivity and changing states), and so, since it's a WYSIWYG editor, the user will be seeing how their site is rendered as they are editing it, so we render their site in React as well. Also, we are using this React framework, Next.JS, which have a functionality to generate static pages from our React component. At the end of the day the React does get compiled into static pages in HTML/JS/CSS. I'm not sure if this answers your question though, would be happy to answer more questions

link
rchaud 1688 days ago
Yes, I think I understand. Thanks for explaining. Does this mean that the sites won't render if JS is disabled?

I have stopped/started learning React several times, because I always end up preferring go back to simple HTML/CSS pages. Bootstrap Studio is something that works for me because it's has that nice split between pure WYSIWIG view and code editing view.

link
lucas_codes 1688 days ago
NextJS static pages do render if JS is disabled.
link