ericdouglas
Elixir Official Book(s) written and maintained by the community
I think that would be really interesting to have official books created by the community about all kinds of development we can do with Elixir.
E.g:
- Basic Elixir → teach how to create CRUD apps with Elixir
- Intermediate Elixir → teach how to create real-time apps with Elixir/Phoenix
- Advanced Elixir → teach how to create distributed, fault-tolerant systems with Elixir and OTP
and so on…
We could do it by everyone first suggesting topics that each book should have, organizing it in a didactic way and after it, we could see who want to write about each topic, with other members reviewing the content.
It’s not something super easy to do but certainly something really feasible.
I would love to help with the Elixir community in such way, maybe if we have more volunteers we can do such thing, more or less like “The Rust Book”.
What do you think?
Most Liked
ericdouglas
The place where those “books”, guides or articles will stay is not too much relevant, but for example, the Rust’s initiative to have such resources under the official organization is super interesting and something that should be copied by other languages/frameworks IMO.
It would be better to create such resources in an actual repository than in a wiki since we can have a better control of it using git. We can also use something like GitBook.
Elixir School is a great project and maybe it would be a good place to host such resources indeed.
One of the main points here is to join forces to create something really useful that one person probably would not create alone, even through a professional publisher.
NobbZ
I’m sorry if you took my last post as offensive. I didn’t wan’t to hurt you or anyone else.
And even if I do share your mindset about educational resources, in the sense that they should be free and available for everyone, I do not think, that learning elixir still qualifies as education.
Of course, that is possible, but as I said, those writing the book, need to make sure they stay up to date to the released version of elixir while at the same time making sure, that the published version of the book does not cover things that are only available on master.
José does always take the effort necessary to maintain a feature or enhencement into account. And very often he denied features because of the burden of future maintenance and keeping a whole book up to date is quite a burden.
But I think I will leave this discussion, I have said what I have to say. I do not think we will change each others mind. But of course, I wish you luck when you search for contributors and even more luck when you ask Jose to create that repository for you.
BarelyFunctional
I think this is great idea, but perhaps rather than start with books, we could create this content in the wiki.
If there’s enough content there, and it’s kept up-to-date enough, then it could be ordered as cheap paper book versions. Perhaps that last idea is redundant as I’m not sure how many would do this.
But having wiki entries that cover the app examples you give would be a huge boost for users beyond having to pick through the docs, search this forum and the internet to try to find what the language/framework author’s intentions/guidance is.
Popular in Chat/Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









