classless-css VS rendertron

I dug through a ton of these for several days before finally deciding to just make my own...

All the lesser known ones tend to not be very extensible or themable beyond basic color changes, and they're a little too extreme about pure semantic HTML.

This guy has a really good roundup with last commit and GitHub stars info:

https://github.com/dbohdan/classless-css

Currently working on getting some issues with their test case ironed out to get mine (https://eternityforest.github.io/barrel.css/) included.

No style attributes. You just use HTML markup and use a classless CSS framework to take care of making it look nice. My favorite is Marx, but there are others you can find here: https://github.com/dbohdan/classless-css

Water.css, MVP.css, sakura, and Tacit are among the most popular.

Literally as easy as:

https://github.com/dbohdan/classless-css

And before you say I should do that myself, again, if you want your work to be comfortable to read for the world, the bare minimum involves legibility.

Not op but classless CSS frameworks are awesome. The idea is to keep it simple and use the appropriate HTML tags where there were generally meant to go, and the framework will theme the page to improve usability and add flair. I've developed some great little sites with no classes at all!

Obviously this approach has its limits, but it works well for proof-of-concept sites or sites that don't need to be very complex or dynamic. Just a sensible font size, nicer looking form elements, etc.

Here is a list of classless CSS frameworks: https://github.com/dbohdan/classless-css

Skip the CSS bit and use classless CSS framework: https://github.com/dbohdan/classless-css

I have used water.css, simple.css and Tufte.css and all of them are great.

Create a folder inside /output called assets. Move the stylesheet.css inside. You can also use an external css like bootstrap, or use a single file css. There is even a css based on Nier!

Rendertron is deprecated

Please note that this project is deprecated. Dynamic rendering is not a recommended approach and there are better approaches to rendering on the web.

Rendertron will not be actively maintained at this point.

https://github.com/GoogleChrome/rendertron

GoogleChrome/Rendertron proxy https://github.com/GoogleChrome/rendertron.

Are you worried that rendertron isn't being maintained? (https://github.com/GoogleChrome/rendertron/issues/865 and https://github.com/GoogleChrome/rendertron/issues/801) Have you thought about using anything else or doing it yourself with Puppeteer or Playwright?

Rendertron, quite old now.

Googlebot: SSR a non-responsive mobile version only for the Googlebot User Agent, to get SEO. But do Client-Side Rendering (CSR) for users, to get full responsivity. Could be done with manual user-agent sniffing, or with a GoogleChrome/Rendertron proxy. Though Google may not like being fed something different than users (different initial markup, even though resulting markup after React’s first CSR should be the same). But it might be problematic long-term to SSR only for the Googlebot, since it’s effectively serving the Googlebot something else than what the users get.. Google might crack down on it, since it could be abused.

This might be another one: https://github.com/GoogleChrome/rendertron (not sure if it does everything that prerender does or not).

Still prefer CRA with Dynamic Rendering with rendertron over Next.js and Gatsby...

A demo Rendertron service is available at https://render-tron.appspot.com/. It is not designed to be used as a production endpoint. You can use it, but there are no uptime guarantees.