Open Online / Drupal for Gemeenten (DvG) - their CMS - will not be ready before September. We therefore need to focus on letting it work on a subdomain.
Currently, there's some demo website header, footer, menu around the forms when used via open forms (ie. not use the SDK yourself).
[ ] The demo scaffolding must be removed (css, html) The form/list should still be in a container of the current width.
[ ] The list page showing all the available forms can still be there
[ ] Allow the forms to work under a cname dns entry, like formulieren.utrecht.nl
Verduidelijk met team en gemeenten
Now, to make the form show a little like the municipality layout we can do 4 things:
1) Allow the form in an iframe (I'm doubting alit + I'm not sure if they can use iframes in their CMS)
2) Deploy some static files per municipality containing a blank page (with their menus, styling, footer etc) containing the SDK snippet
3) Allow to upload a blank page via de admin (css, HTML)
4) Allow to upload a logo only and add a (configurable) link back to their main website.
In all cases I assume we can already use a design token to style the form itself.
joeribekker
commented
3 years ago
Open Online / Drupal for Gemeenten (DvG) - their CMS - will not be ready before September. We therefore need to focus on letting it work on a subdomain.
Currently, there's some demo website header, footer, menu around the forms when used via open forms (ie. not use the SDK yourself).
Verduidelijk met team en gemeenten
Now, to make the form show a little like the municipality layout we can do 4 things:
1) Allow the form in an iframe (I'm doubting alit + I'm not sure if they can use iframes in their CMS) 2) Deploy some static files per municipality containing a blank page (with their menus, styling, footer etc) containing the SDK snippet 3) Allow to upload a blank page via de admin (css, HTML) 4) Allow to upload a logo only and add a (configurable) link back to their main website.
In all cases I assume we can already use a design token to style the form itself.