Geo Sites - Rename geo_nodes Vue components
What does this MR do and why?
This change is MR 2 of 5 for #393925 (closed)
Geo has rebranded the term Nodes => Sites. We have taken the Facade-first approach to rename only customer facing content while leaving all the technical content like file names, method names, variable names.
Now that the rebrand is mature and we are sure the term Sites is here to stay we are aiming to complete the rename for the technical side of things too.
Focus of this MR
This MR is focused on renaming the Vue Components inside of the geo_nodes scope. This includes all file names, the folder itself, and all component internals. The previous MR renamed all the Vuex usage: !113762 (merged)
Screenshots or screen recordings
No change or console errors
Find in files results
| geo_sites/ | spec/geo_sites/ |
|---|---|
 |
 |
notes about find results:
- in
geo_sites/the only result has comment explaining why (related to API) - in
spec/geo_sites/all results have comments explaining why (related to API)
How to set up and validate locally
- Fetch and checkout this branch
- Setup Geo (How to setup Geo)
- Access your Primary GDK UI
- Navigate to Geo Dashboard (
/admin/geo/sites) - Ensure everything looks as it has and no console errors
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.