You know how the API design guidelines [1] talk about designing for a
concrete use case? It applies to talks, too. If you can talk about how
you're using Elm, or something interesting you've done with it (either an
experimentation or a shipped project) you're going to have a much better
chance
Taxonomy of components.
How can we expand on the elm-lang/html and the Elm Architecture in a way in
which we can create reusable components that fit well together.
elm-parts is a project that came out of the elm-mdl effort.
Maybe you could talk about something like that.
On Mon, Jun 27, 2016
With the simplification of Elm since 0.17 it seems like there are far less
intermediate+ possible talks. I imagine the best talks will be about
tooling and not so much about the using the language.
What are some topics worth speaking about that are "beyond the basics"?
--
You received this me
