**Acceptance Criteria**
* The code from the GitHub repository `wmde/FundraisingFrontend` is split into two repositories, on //GitLab//, one with the client-side code named `fundraising-app-frontend` and one with the server side code. See naming suggestions belowed `fundraising-app`.
* Both repositories have a CI set up. The `dev` environment of the server side code may still use the `assets-path` config entry to load the client-side assets from the client-side development serverpiepeline set up (replacing the existing Travis pipeline).
* The client-side repository has an automated build pipeline of a docker image that serves the JS and CSS assets.
* The deployment playbook is adapted - the repository name has changed and it has two additional tasks to clone the client-side repo and build the assets from there
* (Optional) Change data attribute in templates to script tag
**NOT in this MVP**
* Changes on how we render templates See {T248460} for future plans
* static html for a devdevelopment version inof the client-side code
* Automated builds of assets (JS and CSS files or docker image) for faster deployment and easier integration with the server side
* Replacing the `skins_laika` container
To be discussed:
* Naming: suggestions `fundraising-app-client`, `fundraising-app-frontend` (with `wmde/FundraisingFrontend` renamed to `fundraising-app-backend` or `fundraising-app-api`)
**Implementation notes**
`skins/laika/templates` needs to remain in the server-side code for now. See {T248460} for future plans
The `dev` environment of the server side code may still use the `assets-path` config entry to load the client-side assets from the client-side development server.