Some other thoughts (since I’ve been thinking about this too).
-
A monolithic publishing platform doesn’t feel right on the BEAM (or on the Internet). I’m probably heading down the ActivityPub federated path - even for my personal projects.
-
Instead of traditional plugins which load into the BEAM I’m planning to be more event-oriented and “plugins” can listen for and subscribe to events that can transform content. I don’t want to go the traditional route of loading modules because:
-
Doesn’t fit well with a distributed platform where there may be multiple nodes running the code
-
Risks the VM and I want to be long-running
-
Inherently less secure
-
-
Definitely going to support many languages and cultures as first-class citizens (as you plan)
-
Makes use of a new image library I’m writing based upon libvips since photography is a big thing for me
-
Will aim to statically publish as much content as possible (automatically)
-
Will have a configurable workflow along the lines of IFTTT
Given how my brain works I’m building from the bottom up while I think about architectural issues some more. Internationalization mostly done (where did those three years go?). Image processing is under way. Workflow engine (not just for publishing) is being designed. I’m also going to bite the bullet and build an OpenID compliant privacy-oriented authentication platform (because why not).
You can imagine this isn’t shipping next week but more than happy to be part of the conversation. I think Elixir and the BEAM can make for a very good next-gen publishing platform that learns from the good things places like Medium brings without the many business model and platform issues that come with it.
