How to Test Major Changes to CSS

Steps

Confirm identical build output for project(s) on default branch versus the branch to test.

When checking out branches, do not forget to git submodule update, otherwise the test will fail.

0. Clean out any previous testing following these steps.

   git rm -rf taccsite_cms/static/site_cms/css/build-for-compare
   rm -rf node_modules

1. Confirm old CSS build process works for frontera-cms.

   Follow main branch's instructions to build for Frontera CMS. (No need to collectstatic.)

2. Copy build output to new directory, and stage the change with Git.

   rm -rf taccsite_cms/static/site_cms/css/build-for-compare
   cp -r taccsite_cms/static/site_cms/css/build taccsite_cms/static/site_cms/css/build-for-compare
   git add taccsite_cms/static/site_cms/css/buid-for-compare

3. Confirm new CSS build process works for frontera-cms.

   Follow this branch's instructions to build for Frontera CMS. (No need to collectstatic.)

4. Replace that copied old build output with new build output (do not stage).

   rm -rf taccsite_cms/static/site_cms/css/build-for-compare
   cp -r taccsite_cms/static/site_cms/css/build taccsite_cms/static/site_cms/css/buid-for-compare

5. Compare the build outputs via git status.

   pwd # confirm you are at CMS repo root
   git status

6. Confirm you see only relevant staged changes.

   • (via git status) You should only see "Changes to be committed" for build-for-compare/.
   • (via git status) You should not see "Changes not staged for commit" for build-for-compare/.¹
7. Clean out new build process.

   git rm -rf taccsite_cms/static/site_cms/css/build-for-compare
   rm -rf node_modules

8. Confirm old CSS build process works for core-cms.

   Follow main branch's instructions to build for Frontera CMS. (No need to collectstatic.)

9. Copy build output to new directory, and stage the change with Git.

   rm -rf taccsite_cms/static/site_cms/css/build-for-compare
   cp -r taccsite_cms/static/site_cms/css/build taccsite_cms/static/site_cms/css/build-for-compare
   git add taccsite_cms/static/site_cms/css/build-for-compare

10. Confirm new CSS build process works for core-cms.

    Follow this branch's instructions to build for Frontera CMS. (No need to collectstatic.)

11. Replace that copied old build output with new build output (do not stage).

    rm -rf taccsite_cms/static/site_cms/css/build-for-compare
    cp -r taccsite_cms/static/site_cms/css/build taccsite_cms/static/site_cms/css/build-for-compare

12. Compare the build outputs via git status.

    git status

13. Confirm you see only staged changes.

    • (via git status) You should only see "Changes to be committed" for build-for-compare/.
    • (via git status) You should not see "Changes not staged for commit" for build-for-compare/.¹

14. Repeat as desired for each project.

---

¹ Files taccsite_cms/settings.json and taccsite_cms/.env will appear as new. You may ignore them. They are for main branch, but removed from this branch.