We’ve done it 100% with Wappler. It currently counts 1630 server action files :-). At the moment we’re implementing a forum for one of our clients.
We have a complete login procedure with password remember functionallities, cookie saving etc. A registration process for different access levels, combined with newsletter registration. We can add the newsletter/user registration to every form on any page. So the system checks if an email is already in the system and if not adds it and if yes checks if it’s activated, etc… Registration activation can be done automaticly or by the admin. Double opt-in is supported.
We have client sided and server sided data table with sophisticated filtering, export data, print details out of modals with detailed data. The data table also allows multiple update and delete.
All deletes include remove of files on the server and related database data if applied. So if you delete a news record for example, also the fotos, files and other related data are also being deleted. All image uploads (also multiple uploads) include database controlled image manipulation. So you define the size of the images in just one table for the complete system. Its placeholders can be generated within the cms by one click. All actions are logged. All important website/cms info can be maintained from within the cms. Like defining categories and it’s image sizes, cleaning webserver from old images (from data migrations), languages, email addresses. All submitted website form content, like contact forms, can be accessed from the cms.
We have news, blog, events, website content maintenance, slideshows, services, company informations, exhibitions, animal database, a powerful newsletter and press tool, faq, website notification and many many more content. The cms supports multiple languages and also has extranet support, which can very easily be implemented.
We “just” have to dump the database and clone the cms and can start with a new website. No more work on server sided form logic or client sided forms or data tables is needed (except for new requests of course).
The user only has to edit the content of the website not the page itself. So it’s very easy to handle, as it just like working with excel tables and form pages. Everything is explained, conditions show new fields if needed or hide them. Fields get only required for example when the user wants content to be shown in a specific language on the website (like a news title in english if showinenglish == 1). And many more little helpers
It would really take some time to explain all of it. Maybe I’m gonna make some videos when I find some time.