# Understanding UI Components in Elm

**URL:** <https://forum.devtalk.com/t/understanding-ui-components-in-elm/58690>\
**Category:** Blogs/Articles/Talks/Podcasts\
**Tags:** elm, in-the-news\
**Created:** [9 June 2022 01:53 UTC](https://forum.devtalk.com/t/understanding-ui-components-in-elm/58690 "2022-06-09T01:53:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CommunityNews](https://forum.devtalk.com/user_avatar/forum.devtalk.com/communitynews/32/1113_2.png) [@CommunityNews](https://forum.devtalk.com/u/CommunityNews)\
**Post date:** [9 June 2022 01:53 UTC](https://forum.devtalk.com/t/understanding-ui-components-in-elm/58690/1 "2022-06-09T01:53:41Z")

</div>

> Since the Humio web client is built in Elm, I’d like to share some of our learnings with Elm over the years. Specifically, working with UI components — a common sticking point for new Elm developers.
> 
> The main points I’ll cover:
> 
> - Some architectural considerations and tradeoffs for components in Elm
> - Building vocabulary for describing and comparing components in Elm
> 
> This is based on best practices and insights we’ve learned with Elm, having many developers working on a single large application. The post assumes you have a basic understanding of the [Elm language](https://elm-lang.org/)1 and [The Elm Architecture](https://guide.elm-lang.org/architecture/).
> 
> Let’s dive in!

Read in full here:

[https://www.humio.com/blog/understanding-ui-components-in-elm/](https://www.humio.com/blog/understanding-ui-components-in-elm/)

_This thread was posted by one of our members via one of our news source trackers._