Re: Pier Refactorings

Indeed, I use the same approach. Maybe it would help, if we had such a setup by default, with some explanatory text. Like this we would get a decent default configuration, but you would be still free to reorganize it however you like. One problem I see with having the environment in the structure itself (as opposed to having it on a separate page) is that it is virtually impossible to use relative links. And you need those links because you don't want your components in the same hierarchy as the page. The problem I face is that I need a different side-bar text for every page. And having a new layout for every page is not what I want. The thing with the Sidebar is just an example. When I edit a page I would not only like to be able to edit the document in the contents (as it is now) but also in some other areas, that are not necessarily connected to the main contents, e.g. the side-bar, some small printed text, some additional links in a box somewhere, etc. Well that was my idea (sort of). However I want it to be editable as part of the normal editing process. And keep the contents close to its page, as they closely belong together. The existing model with the default document is preserved, this is also where the Magritte editor (login, permissions, etc) are managed. Additionally we would get other parts that can be edited the same way. All structures would get an extra document for every PRDocumentWidget defined in its environment. These documents (depending on the settings) can then be inherited (if left blank) from the parent or include a default text. Thank you for sharing your thoughts. I hope I could make it clearer now. Regards, Lukas -- Lukas Renggli http://www.lukas-renggli.ch