Rich_Morin
Although Elixir Forum and HexDocs (etc) are great resources, they don’t have the topic-bound organization used in a wiki. So, for example, looking for a current summary page on a particular tool or technique can be tedious.
If the Elixir community wanted to use an existing wiki engine, there are lots of freely available options. MediaWiki is clearly the elephant in the room, but it is unabashedly optimized for the needs of Wikipedia and so might not be a good fit for other projects.
Some other offerings (e.g., Foswiki, TWiki) offer less opinionated and more generalized support for “enterprise” wikis. So, for example, they offer access control, limited scripting capabilities, etc.
However, most of the available offerings are based on a single main server, possibly augmented by mirror sites. This seems rather inconsistent with Elixir’s distributed nature. More critically, they don’t offer the sort of Elixir scripting found in Livebook.
Also, the single-server approach typically leads to a “forced consensus”, where only one point of view is presented on each topic. One interesting exception, Ward Cunningham’s Federated Wiki, employs a distributed approach in an effort to encourage diversity of opinions.
In any event, I’m wondering whether some combination of Livebook and GitHub could form the basis for an Elixir-friendly distributed wiki. FWIW, the basic idea is that random users could download and run Livebooks on particular topics. If desired, the pages could be edited and perhaps submitted as updates.
Does anyone else find this notion interesting?
-r
Where Next?
Trending in Questions
Other Trending Topics
Latest Livebook Threads
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
hectorperez
Neat idea @Rich_Morin!
I’ve been thinking about this space for some time.
In case it gives you some ideas:
The federated wiki:
livemdfiles.hauleth
One interesting thing, you can actually manage GitHub Wikis as a Git repositories:
However I am not sure if it will support
.livemdfiles.derek-zhou
An Elixir livebook powered wiki can be very slick. However, I think the point of a wiki is that it enables a group of enthusiastic editors working together to produce high quality contents in an organized way. So I am not sure how attractive a distributed wiki would be.
aschrijver
I know Federated Wiki and it is quite cool. Less excited about Github for a host of reasons. What is interesting here are developments surrounding Code Forge federation which is being adopted by Gitea and an upcoming ecosystem around this. ForgeFed published today about Federated Merge Requests, for instance:
But in light of this idea federated Code Forge wiki’s come to mind. I don’t know about Github, but in Gitea these are just Git repositories.