AstonJ

AstonJ

Wonder if we can compile a list of learning resources, blog posts, talks, threads etc to help those who are just learning about Contexts.

This is a wiki - so please add anything you feel is missing…

What are Phoenix Contexts?

In short:

Phoenix Contexts are just dedicated modules that expose and group functionality.

In depth:

Books

Programming Phoenix - due to be updated for Phoenix 1.3.

Screencasts

Talks

Blog Posts

https://panache.nu/blog/giving-phoenix-contexts-some-context

http://www.resurgens.io/2017/06/26/phoenix-1-3.html by @dlively (thread)

https://robots.thoughtbot.com/lessons-from-using-phoenix-1-3

Understanding the concept of a context in Phoenix (2017-08-16)

Threads

And more:

https://forum.elixirforum.com/search?q=contexts

Misc

Showing Posts 12 to 3

marciol

marciol

Great article by @devonestes suggesting some rules to guide the design of Contexts:

http://devonestes.herokuapp.com/a-proposal-for-context-rules

Recommended to me by João Brito of @Plataformatec.

dokuzbir

dokuzbir

thanks @peerreynders really nice video. I was feeling overwhelming about modules, functions… Looking a app from big picture really opened my mind. I feel like i found missing puzzle. Especially User in different contexts section. Since long time i was searching informations for designing apps.

peerreynders

peerreynders

Building beautiful systems with Phoenix contexts. Andrew Hao - ElixirDaze 2018 (March 1,2)

Worth watching. 'nuff said.

AstonJ

AstonJ OP

With the recent Phoenix 1.3 release, Phoenix introduced Contexts, which are dedicated modules that expose and group related functionality. One frequent question that has come up is where to handle authorization for domain operations. Should authorization be handled in the Web layer at the controller, or within the context? Both are valid approaches, so let’s find out which approach is better and when…

AstonJ

AstonJ OP

http://www.resurgens.io/2017/06/26/phoenix-1-3.html

by @dlively (EF thread)

Since this is an app I built in order to further my education, I opted to venture out on the bleeding edge and use Phoenix 1.3.0-rc. Don’t let the what seems like a minor version change fool you. While there are no real breaking changes or significant new features being introduced in 1.3, alterations to the directory structure and new code generators introduce a seismic shift in how a developer approaches a Phoenix project. Chris McCord provides an overview of these changes in the Lonestar Elixir keynote address, his Elixir Forum post, and his more recent ElixirConf EU keynote. Those were all essential for me to getting started, but I found the concepts easier to grasp once I began building my project…

marciol

marciol

All explanations from this thread worth mention:

AstonJ

AstonJ OP

Added @chrismccord’s ElixirConf EU Keynote talk :023:

AstonJ

AstonJ OP

Added a blog post by @Qqwy :023:

AstonJ

AstonJ OP

I added a link to your post in the wiki :023:

Where Next? Top

Trending in Wikis Top

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews