Looky1173

https://archive.is/Lj1RE

Open Rails is the modern successor to Microsoft Train Simulator (MSTS), and is fully backward compatible with all MSTS content. It has better graphics and focuses on realistic train physics.

Keep in mind that Vercel does not allow for-profit usage on its free Hobby plan. Netlify does, though.

They are partially off screen on my iPhone SE as well, I will certainly address this issue soon.

Yes; there are 7 CSS variables to tweak and play with. I might add more in the future (for example, for `border-radius`).

Thank you for adding Lissom.CSS to the list. Indeed, I think that all modern websites should account for `prefers-color-scheme`, now that it has been supported by virtually every browser for several years.

MVP.css is very complete and robust, but its styles and general feel do not resonate with me.

"data-*" attributes don't require any JavaScript; their values can even be accessed from CSS with `content: attr(data-*);`

Individually, yes.

I like it, it's very minimalist and purist!

Like `display: flex; flex-direction: column; width: 100%;`?

I've just added basic form styles. More to come soon...

Exactly! You shouldn't need to remember classes for styling native HTML elements, and neither should you be forced to type out <button class="button"></button>, where you would be repeating yourself.

It's mainly the latter. I did consider just using a class, but ultimately settled on this solution. This approach might facilitate usage with additional CSS compilers/tooling.

Oh, I see. That's quite unfortunate.

Lissom.CSS is indeed opinionated. Would you prefer to call it a framework instead, or a stylesheet?

I'm not against classes at all. I believe they are essential to constructing a well structured website, especially for creating layouts. However, I also believe that as frontend developers we should embrace native and semantic HTML elements instead of reinventing the wheel and rolling our own solutions. Going classless for basic elements results in cleaner HTML markup and avoids "class pollution".

I've stretched out the line height a bit so it should look better now.

That's curious. It's just a simple HTML page with CSS attached, hosted on GitHub Pages. I don't see why it would trigger such a warning.

Thanks for the feedback, I've just set the line height to 1.4.

Thank you! I haven't finished form elements yet but they are definitely in the works.

Hi, do you mean that the underline appears under the highlighted text? No, that's not expected, I will see what I could do to fix it. However, the underline is indeed supposed to grow slightly thicker on hover.

Happy new year HN from central Europe!