Great!
Would love to read about the reactor(mby for something like handling a booking a class with limited spots or payment process) as well as multitenancy in addition to the topics you mention.
Both the reactor and multitenancy seem very powerful if used correctly and including them would compliment the topics in the Pragmatic Bookshelf Ash Framework book very nicely.
Just recently paid for your book btw, looking forward to reading it!
Kallee
1
shankardevy
@josh.nz @MikaelFangel
I haven’t read Pragmatic Bookshelf Ash Framework book yet so my sharing might not be accurate but looking at the table of contents available online, it might cover Ash core and non-core GraphQL, REST APIs, AshAuthentication which are separate Ash libraries. So in a way Pragmatic book gives an authoritative usage (as it comes the library authors) on a wide variety of core and non-core functions in Ash.
I’m covering primarily Ash core extensively (in the context of Ash Postgres for all db related stuff). So it give me more space to dive deeper and narrow on the core topics. So I think both books complementing each other.
1
MikaelFangel
I’m very exited to see another book about the Ash framework! How does this book complement the Ash framework book by Rebecca Le and Zach Daniel? Does it aim to go into more detail or cover different aspects? 
0
josh.nz
Thanks for the details. I can appreciate not wanted a demo site when you don’t focus on the UI. And I think it’s a nice idea to not focus on the UI, gives you more room to focus on the domain concepts Ash helps with, as you state. A good decision.
I’m looking forward to the sample chapter. I have the Pragmatic Bookshelf Ash Framework book and need to determine if your book goes into more detail or covers most of the same ground. It would be very helpful if you could include a detailed table of contents (for the full book) with the sample chapter, or add this to your site.
0
shankardevy
@josh.nz, yes the book goes beyond building a simple crud app. It doesn’t deal with the UI part at all but focuses entirely on building the core business model with Ash. This gives enough room for diving deeper into the subject of Ash domain modeling without getting caught with explanations of Phoenix layer. The book is structured around the core Ash concepts in the following structure for each concept taught from the lens of an imaginary company Tuesday that sells project management software.
- Explanation of an Ash Concept (A)
- A business domain problem (B) addressable by concept (A)
- Solution for this business problem (C)
- Explanation of the solution (D)
- How to write test cases where applicable (E)
- Exercise to write a solution for a similar problem (F)
- Exercise to debug a solution that’s not working (G)
There will be sample chapter available beginning of April for you to download and see. Regarding the demo site, I’m still considering. For my first book series, I had this demo site: https://mango.shankardevy.com/ but now since I focus completely on Ash, I don’t want a demo site similar to this to misrepresent what I teach in the book giving the readers a wrong assumption that it teaches Phoenix as well. Everything in the book can be used in a Phoenix app but it doesn’t teach Phoenix on its own.
Hope this answers your questions. Let me know if you need anything more.
1
Nefcairon
Hello Shankar,
I remember you from the phoenix book, which I enjoyed. Then things got a little quiet around you.
So a book from you about Ash? That’s an instabuy.
2
josh.nz
Can you please provide a summary of the features that the project management app will have by the end of your book, so I can better understand the scope of complexity your book will cover. I’m hoping it goes beyond a simple app with a few resources.
Even better, is there a site with a demo of the final app that we can look at?
5
asianfilm
I’ve only been skimming the Igniter docs, but a workshop or book appendix on using it for code generation would be great.
There’s new code generation tooling in Elm, for example, and a lot of interesting stuff is coming out of that, in large part because Elm lacks macros.
Elixir of course has macros, but Igniter still has a lot of potential in Elixir beyond being a smarter mix install. But of course you know that!
1
arcanemachine
I’m relatively new here, and I am unfamiliar with your previous work. But the comments in the thread from your other book/series seem to be quite positive, so I’ll give this a shot.
Cheers
2
shankardevy
Thank you @zachdaniel . A lot of gratitude and respect for your great work with Ash Framework and your continuous support to the community.
2