Hi, could you tell me if a backend application like the one of Watch & Learn with repeaters :

https://watch-learn.com/making-websites-with-october-cms/making-websites-with-october-cms-part-12-repeater-field

...could work as is, and with the same look and functionalities in the frontend ?

Thanks

Hi! Yes, the functionality will be the same as in the backend, if you do not create something very complex in functionality (see other topics):

• with slight restrictions on the nesting of elements (https://octobercms.com/plugin/support/linkonoid-backtofront/repeater-inside-the-nestedform)
• a small bug in relations related to finding an item in a list (problem at the level of the ajax engine)
• several Uploads per 1 form do not work (the problem is related to one definition of the alias of the main form)

Visual the view will be the same as in the backend (subject to the use of standard css), you can customize for yourself by redefining the css styles.

In any case, you need to understand that there is no 100% guarantee for full work with your settings (see the list above) - unfortunately, this is the architecture of the CMS. In general, I think that separating backend and frontend is a mistake, starting from separating widgets in the backend and components in the frontend (which is essentially the same, with some big caveats) and ending with users ... this imposes big restrictions on big projects (for example, with personal accounts of frontend users, although as you can see, this is solvable). That is why in my projects I try to use CMS only for the backend (like a wrapper for Laravel) + REST API with authorization for the frontend on Vue or even Webassembly if I write on Golang (because this allows you to quickly sketch the logic of application)... For small and low-speed applications, CMS is optimal.