Spades is a framework for Elm that helps you quickly start a Single Page Application (SPA) ready to the real world, with an opinionated structure that allows your app to grow easily and well organized.
It has a CLI generating all the necessary Elm boilerplate when adding new components to your application.
npm -g install git+https://github.com/rogeriochaves/spades.git
elm-generate app MyProject
elm-generate component Search
This is the coolest generator, it will create a Search
component under src/, update the main Model, Msg, Update, View and Routes for it
elm-generate route Contact
This will create a new Page type, route parser and route toPath case on the src/Router/Routes.elm file
Mostly not, at least much less than other programming languages, because Elm is already very focused on being the best language for frontend web development, has an enforced architecture and a lot of batteries included.
However, it is still a language, not a framework, therefore it can't define somethings such as how you organize your files, how you scale the architecture, how you deploy your app, which libraries to use, among other things which are usually a source of concern to beginners.
With time, it is possible that more and more things are implemented on the language and removed from this framework, leaving maybe just the initial boilerplate and the code generators.
Just like all other Elm apps, Spades follows The Elm Architecture, this architecture basically dictates all the state flow within Elm, but still allows multiple organizations as your app grows.
Spades then follows an organization with domain focus, similar to what is described on this blogpost.
Another important thing in a real-world Elm app is a solution for parent-child communication, for that part, Spades uses the NoMap pattern described on this other blogpost.
Some people find Elm code very verbose, and that the architecture needs too much boilerplate to work. This is the intentional trade-off that the Elm Language choose to leave the language as simple, readable and explicit as possible.
To have the readability benefits, without the verbosity pain, Spades comes with a CLI to help generate code.
Elm apps are usually rendered on the client, but Spades already come with a simple express server that renders the Elm app before sending the HTML to the client, improving performance for the user and SEO.
You can disable this option using the --serverless flag while creating your project:
elm-generate app MyProject --serverless
Thanks to Elm awesome type system and abstraction of the HTML the community could see things more clearly, and came up with a better way of layouting: elm-ui
We recommend watching this talk by Matthew Griffith, the creator of elm-ui, to understant how it works (elm-ui was still called style-elements back then):
https://www.youtube.com/watch?v=NYb2GDWMIm0
Spades comes with elm-ui by default, and although you can remove it and use the standard html library, we really recommend you to give it a shot, you won't regret!
(elm-ui was previously called style-elements, check out what changed here)
Aside from the advantaged mentioned above, Spades also comes with:
- Ready for Elm 0.19
- elm-test
- Routing and Navigation
- Webpack for better development experience and optimized build
- RemoteData for better handling of http request
- elm-return for better composition of update functions (learn more: https://elmtown.audio/a3e2133b after 38 min)
Just by using the framework and giving feedbacks you'll be helping a lot! You can give suggestions or report bugs on the issues page.
If you want to contribute with Spades development, take a look on the existing issues and read the CONTRIBUTING.md file.