Geo - Move SCSS to page_bundles

Zack Cuddyrequested to merge
366610-page-bundle-geo-scss into master

What does this MR do and why?

Closes #366610 (closed)

This change moves the custom Geo SCSS to their respected page_bundles. I took the initiative to break the styles between each page. If it is better to keep one geo.scss page bundle I can revert them back into one file included in all geo pages.

Files created in this MR:

1. legacy_geo.scss => Used on /admin/geo/replicable/projects and can be removed as part of &4623 (closed)
2. geo_nodes.scss => Used for /admin/geo/sites
3. geo_form.scss => Used for /admin/geo/sites/new and /admin/geo/sites/${id}/edit
4. geo_replicable.scss => Used for /admin/geo/replication/${replicable_type} and /admin/geo/sites/${id}/replication/${replicable_type}

Important: Geo is currently working through a rename from Geo Nodes => Geo Sites. As of right now everything in the UI will reference Sites but the code may still references them as nodes. This follows the Facade Approach to renaming and more can be read here: &5725 (closed)

Screenshots or screen recordings

Before After
Geo Form Form_-_Before Form_-_After
Geo Form (CSS) Form_CSS_-_Before Form_CSS_-_After
Geo Sites Sites_-_Before Sites_-_After
Geo Sites (CSS) Sites_CSS_-_Before Sites_CSS_-_After
Geo Legacy View Legacy_-_Before Legacy_-_After
Geo Legacy View (CSS) Legacy_CSS_-_Before Legacy_CSS_-_After
Geo Replicable Replicable_-_Before Replicable_-_After
Geo Replicable (CSS) Replicable_CSS_-_Before Replicable_CSS_-_After

How to set up and validate locally

  1. Fetch and checkout this branch
  2. Setup Geo and access your Primary GDK (How to setup Geo)
  3. Go to Geo Form (/admin/geo/sites/new) and ensure CSS is correctly loaded
  4. Go to Geo Sites (/admin/geo/sites) and ensure CSS is correctly loaded
  5. Go to Geo Legacy Projects View (/admin/geo/replication/projects) and ensure CSS is correctly loaded
  6. Go to Geo Replicable View (/admin/geo/sites/1/replication/package_files) and ensure CSS is correctly loaded

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #366610 (closed)

Edited by Zack Cuddy

Merge request reports