Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
elm-format
elm-format formats Elm source code according to a standard set of rules based on the official Elm Style Guide
Regarding user experience and tooling, I'd suggest you use an editor that is compatible with the elm language server: https://github.com/elm-tooling/elm-language-server VSCode is a good default choice. You'll also be interested in other toolings. elm-json (https://github.com/zwilias/elm-json) is great to simply install and uninstall dependencies. elm-format (https://github.com/avh4/elm-format) is a must since most active people in the community use it, and simply viewing your code being moved around on save is a good sign that you wrote something with a good syntax.
I can still give you some pointers here. First I'd suggest you read the elm guide: https://guide.elm-lang.org/ It's the best place to start with elm. When you have a question about any specific subject, you should head to the slack, or ask a question on the elm discourse: https://discourse.elm-lang.org/ . The best way to get a useful answer, is to have a concrete question, and to prepare an example of what is wrong on Ellie (https://ellie-app.com). As such people can modify your Ellie to answer you.
Regarding user experience and tooling, I'd suggest you use an editor that is compatible with the elm language server: https://github.com/elm-tooling/elm-language-server VSCode is a good default choice. You'll also be interested in other toolings. elm-json (https://github.com/zwilias/elm-json) is great to simply install and uninstall dependencies. elm-format (https://github.com/avh4/elm-format) is a must since most active people in the community use it, and simply viewing your code being moved around on save is a good sign that you wrote something with a good syntax.
I can still give you some pointers here. First I'd suggest you read the elm guide: https://guide.elm-lang.org/ It's the best place to start with elm. When you have a question about any specific subject, you should head to the slack, or ask a question on the elm discourse: https://discourse.elm-lang.org/ . The best way to get a useful answer, is to have a concrete question, and to prepare an example of what is wrong on Ellie (https://ellie-app.com). As such people can modify your Ellie to answer you.
Regarding user experience and tooling, I'd suggest you use an editor that is compatible with the elm language server: https://github.com/elm-tooling/elm-language-server VSCode is a good default choice. You'll also be interested in other toolings. elm-json (https://github.com/zwilias/elm-json) is great to simply install and uninstall dependencies. elm-format (https://github.com/avh4/elm-format) is a must since most active people in the community use it, and simply viewing your code being moved around on save is a good sign that you wrote something with a good syntax.
The last advice I could give is to try elm-ui (https://github.com/mdgriffith/elm-ui) for your user interface. It's amazing how great that is compared to traditional ways of building a frontend layout.