Change Details

**Acceptance Criteria** * The code from the repository `wmde/FundraisingFrontend` is split into two repositories, one with the client-side code and one with the server side code. See naming suggestions below * 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 server. * 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 dev version in 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 To be discussed: * How do we replace the `skins_laika` container? * 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

**Acceptance Criteria** * The code from the repository `wmde/FundraisingFrontend` is split into two repositories, one with the client-side code and one with the server side code. See naming suggestions below * 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 server. * 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 dev version in 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 To be discussed: * How do we replace the `skins_laika` container? * 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

**Acceptance Criteria** * The code from the repository `wmde/FundraisingFrontend` is split into two repositories, one with the client-side code and one with the server side code. See naming suggestions below * 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 server. * 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 dev version in 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 To be discussed: * How do we replace the `skins_laika` container? * 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