I also just wanted to respond to your curiosity about what Arachne is by saying in my own words what problem it aims to solve.
Web frameworks which are 'easy' to get started with are often difficult to customize when the built-in features are insufficient to solve the problem at hand. Arachne intends to remain highly customizable, allowing you to alter low-level aspects of the framework by transacting changes to the shared config value, a data-centric extension point for all things. A running app is made up of a collections of modules which can all integrate via the config value.
It's also like a framework of frameworks, where the collection of modules you prefer might be materially different than my preferred stack.
When we talk about 'Arachne', we'll have to remind ourselves that there's no one preferred collection of modules, that the essence of Arachne is more of a way to organize, than a thing itself. In that way, Arachne has the potential to be more than a web framework, and will likely be used for desktop apps, command line apps, and so on.
You might enjoy this article by Luke: http://arachne-framework.org/posts/2016/frameworks-libraries-and-templates/