Auth will use session data. I haven’t gotten to work on session yet, but I’ve got a few ideas:
- session will be accessible through commands at all times and on page init (so only through the server for security reasons)
- stored in HTTP-only cookie or database
It would be possible to implement offline SPA if all pages are downloaded in a bundle and client storage is used. But I’m not targeting this behaviour in the initial phases. In the beginning, redirecting to a new page will require a connection with the server. But at least once the page is loaded it can work offline provided the client doesn’t load new data from the server through commands. Eventually, client storage (such as IndexedDB or local storage) could be used to improve this. It could work similarly to mobile apps - once there is a connection the app syncs the data with the server backend.
As for the Projects tab it’s not up to date, at one point I decided that it creates too much overhead at the moment since I work on this myself, and right now I’m using plain old OmniFocus for project management (this will change when there are contributors).
Note also that the roadmap is not up to date. For the past few months, I’ve been working on a rewrite full time, which fixed all pressing issues and actually, most of the syntax is already done. Sorry for the confusion! I’ll get back to the roadmap once I get to rewriting the browser tests of the features listed on the roadmap.
Yeah, I’ll probably use GitHub releases eventually.
Version 0.2.0 with full Elixir syntax support (except the stuff related to parallelism), with a demo app and with a basic “getting started guide” will be done this summer.
