___________________________________________________________________________ |main page |add page button| | | ___________________ ___________________ ___________________ ||page1 | |page2 | |page3 | || | | | | | || | | | | | || | | | | | || ________________ | | ________________ | | ________________ | |||subpage1 + edit | | ||subpage1 + edit | | ||subpage1 + edit | | |||subpage2 + edit | | ||subpage2 + edit | | ||subpage2 + edit | | |||subpage3 + edit | | ||subpage3 + edit | | ||subpage3 + edit | | ||| ... | | || ... | | || ... | | |||________________| | ||________________| | ||________________| | || | | | | | ||edit (page1) | |edit (page2) | |edit (page3) | ||___________________| |___________________| |___________________| ... | |___________________________________________________________________________
we are about to develop this project and there are some main questions about structuring and code usage.
so if you like to, we’d be really happy:
the content should be saved in classic kirby-folder-scheme, that’s why there is pages and subpages for each.
i’ll try to keep it abstract, but:
pages are “projects” with basic information like title, description etc. and their subpages are like blog entries for capturing text, images and pdfs.
the content should be editable from frontend via forms(?).
so there is the main page to display its subpages (page1/subpage1s, page2/subpages, etc.) and to add new pages (e.g. page4) and give it the basic content.
then the page appears and has following editing possibilies:
so we’ve got it running without the edit functions (content input via panel) and it’s one foreach loop for subpages inside another one for the pages.
i tried uniform, because i think it would be easier to handle multiple forms, and was successfull for adding/changing some basic stuff on a basic site. (edit field data, uploading images,…)
the other question: is the foreach-structure maybe more complicating than simple (regarding the forms) because of the variable handling?
side question: forms would be allright and do the job, but as we have to learn how to get there anyways, maybe the “would-be-nice” feature of directly editing the content (e.g. by clicking into the text-containers and just write) could be similarly difficult.
(what i didn’t mention because i think it can be added afterwards or doesn’t matter at this point: password authentication; maybe users (40max.) / groups; kirby-content-folder-to-nextcloud-link)
i hope you understand basically what we want to achieve and maybe have some tipps on how to start it.