Routing in lively.next
#1479
Labels
📚 documentation
Improvements or additions to documentation
✨ enhancement
New feature or request
💬 ideas welcome
For feature ideas where more input on design decisions and conrete direction are warranted.
This is more of a brain dump as of now, as I do not have a good solution to the problem yet. However, the following is something I want to continuously think about while working on the relaunch of the lively web page:
When building static websites, as opposed to truly interactive applications, one needs the capability to route between different URLs. The two most important benefits this brings is that
For SPAs such as lively applications, the easiest and most flexible way of doing is by using hash routing.
The current way I implement this in the website is by instantiating multiple
HashRouter
instances (a class I implemented inside of the website project) which manage different prefixes of the page (e.g., there is a router solely responsible for all things under the /blog prefix). Then, I write specific bindings for every UI elements that should route somewhere.The question this bags is twofold:
The text was updated successfully, but these errors were encountered: