Added a blog post by @michalmuskala

There is an example phoenix 1.3 application, with contexts and absinthe here

https://seanclayton.me/post/phoenix-1-3-and-graphql-with-absinthe/?utm_source=hashnode.com

Which obviously is inspired by this one

https://ryanswapp.com/2016/11/29/phoenix-graphql-tutorial-with-absinthe/

It is a full example, easy to follow on how contexts can interact.

I added a link to your post in the wiki

Added a blog post by @Qqwy

Added @chrismccord’s ElixirConf EU Keynote talk

All explanations from this thread worth mention:

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…

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…

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

Worth watching. 'nuff said.