elm-spa-example VS classless-css

About 7 years ago, in the midst of writing Elm in Action, Richard Feldman developed rtfeldman/elm-spa-example, wrote Tour of an Open-Source Elm SPA and graciously shared both of them with the Elm community. The community's response was overwhelmingly positive and it was clear that he had addressed a major need. If you were one of the many web application developers asking "Where can I find an open-source example of an Elm Single Page Application?", then, the Elm SPA Example instantly became the canonical example that everyone was going to point you towards. This was a landmark achievement in the history of Elm.

One accidentally nice thing about that book is the elm version is still the same, so everything is still relevant. As for the SPA, I think the book had to keep things simple, but you'd probably want to look into the author's elm-spa-example next, there's a talk on youtube that goes along with that and he also also a related course on frontend maters worth exploring.

I'm following along with the update behavior of https://github.com/rtfeldman/elm-spa-example/blob/master/src/Main.elm. But I'm not sure how I propagate a message from Main.elm to User.elm to Table.elm (or deeper). How do you manage Msg passing like this?

I am building my first Elm app just following the docs from the official web site. I don't see any direct mention of styling there. Looking around, I see the elm-ui project is one, elm-css is another approach, and the example SPA that Richard Feldman made just uses a stylesheet from Bootstrap, i.e., just plain CSS. If it exists, what's the canonical way of styling an app?

A good example of this is the Elm-SPA example from Feldman: the Main.elm file is basically just glue code for the rest of the project (https://github.com/rtfeldman/elm-spa-example/blob/master/src/Main.elm).

After all that I've managed to reach my goal of being able to run Richard Feldman's Elm SPA Example in my system! 😃 Here's a working implementation compiled to WebAssembly. And for comparison, you can also check out the same code compiled to JavaScript. (Unfortunately the publicly available APIs don't seem to be returning very much data at the moment but there's not much I can do about that!)

Looking at the Real World application I could see that there were better ways to structure my modules using nested TEAs and keeping the Main module as a hub for everything in the app.

If you want to see Elm code, you might look for example projects on GitHub. (https://github.com/rtfeldman/elm-spa-example comes to mind.)

https://github.com/rtfeldman/elm-spa-example is a good example app. I'd also recommend https://codebase.show/projects/realworld in general if you're looking for example apps in various frameworks and languages. I sadly can't share anything from work as it's all private.

- How to properly structure the project. I differentiate between my core utils and the actual gui. Iced states in the documentation that it's inspired by the Elm architecture. So naturally I've read a little bit about the proposed Elm project structure. So I basically end in a structure like this spa example directory recommended by the Elm communicty: Repo

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!