Node-solid-server: Decouple homepage front-end from node-solid-server

[RubenVerborgh]

So we can have a decent homepage

[megoth]

As part of this we need a good way of managing the front page. One use case could be that a user wants to change their frontpage. Another is to allow apps prompt users to make the app their frontpage. This could of course be abused easily, so we need to consider how we want to limit abuse.

Do we want to implement the management tools "fully" (e.g. serve some locally stored HTML-files), or are server APIs enough? Or do we want some other mechanisms to handle this?

Need to think of update management strategies for this as well, I suppose?

[RubenVerborgh]

My goal is to make the front-page an app generated from a Turtle file, so all of the above should be possible (using another app as well).

[csarven]

Just to share an idea from dokieli (which is in part a work in progress):

dokieli can "open" individual resources as well as containers (and "collections" as per AS2) eg: one can see it in action through an URL with dokieli (handled on the clientside) https://dokie.li/?open=https://rhiaro.co.uk/2018/12/ or using the "Open" feature from the dokieli menu and entering a container URI. It will basically construct a view of user's activities wherever they are.

One of the ideas for opening a container in dokieli was on route to generating an index/homepage of some sort (live in the DOM at that point) and then the user proceeding with a "Save" or "Save As" - depending on their context. Again, just exploring around..

I'm mentioning this because there are obviously many different ways of doing this. Possibly a small application with a similar feature to generate a feed or possibly even auto-updating one's activities would serve well towards a common homepage type of thing.

[rimmartin]

Also instead of a page per say; a z-index layer that app developers can set in to their own pages. This way never leave the page or be treated as a popup

[scenaristeur]

Could this post be relative to this issue ? https://forum.solidproject.org/t/index-html-in-a-pod-folder-and-keeping-browser/1113
Keeping index.html & browser

[megoth]

@scenaristeur that thread seems very relevant, thanks for the heads up. But I'm unable to locate which post you're referring to, as ?page=3 gives me "Oops! That page doesn’t exist or is private." =/

[RubenVerborgh]

Relevant thinking work for the actual app (there could be multiple): https://github.com/solid/solid/issues/18

[scenaristeur]

@megoth
Sorry, here is the link https://forum.solidproject.org/t/index-html-in-a-pod-folder-and-keeping-browser/1113

I can't find in what file the server do the test " if I have an index.html, I render it, else I show the browser" .
In solid-server ? Solid-gui ? Mashlib ?
Does anyone could drive me ?

[megoth]

We probably also want to decouple the account-related views into separate apps as well. With that we might want to expose certain configurations for the server to the client, e.g. does the server handle WebID, is it a multi-user server, does it enforce Terms & Conditions, does it enforce strength of passwords, etc. (The last example might also be something we want more levels on - right now it's only on or off.)

Is this something that should be described in the Solid vocabulary?