At NoRedInk we have one of the largest Elm apps in the world. It serves millions of teachers and students, and our frontend code is almost exclusively written in Elm. In this post, we will explore the structure of our codebase and the patterns that we use to stay sane. One of the most common questions I get about Elm is:

“Does it scale? And if so, how?”

I don’t think that there can ever be a comprehensive answer to that question, but I hope this post can be a useful reference to resources and techniques we’ve used to solve real-world problems, so you can dig deeper at your own leisure.

Table of contents

• A wild monorepo appears
• Rails conventions
• Our Elm programs
• How we write Elm files
• Nesting the Elm Architecture
• When to nest TEA modules
• Interacting with JavaScript
• Testing
• Tooling

Read in full here:

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