Sites BAU FAQ

BAU stands for Business As Usual tasks and these include: copy updates, page refreshes and page rebranding. The portion of BAU that we distribute across the web team are copy updates and page refreshes only.

Copy updates are menial changes requested on a copy document. It does not require Design and/or UX reviews and should be an easy code change. A code and QA review is required.

Page refreshes are changes that do not match existing templates and they often require Design and UX reviews, alongside with code and QA reviews.

Guide to copy updates and page refreshes.

Asset requests should be handled by our Visual and UX team (currently @elaineliman, @mattea-turic, @kim-isaac). Our design team will be able to provide you an asset link that should fit your needs.

We have a ~web-code-review channel on MM where you are able to ping @baureviews for a code review.

Reach out to Project Management and they will be able to help out.

If the design uses a Jinja pattern in a configuration that is not already supported, please do not create a one-off solution or avoid using the pattern. Instead, immediately notify the designer who provided the mock up. They will adjust the design to align with the patterns capabilities.

It is still possible that you will have to update the pattern, but this will be made clear by design.

Currently, we do not have the mechanisms in place to take everyone’s calendar availabilities into account when assigning BAU tasks. This distribution mechanism is done on the Project Management side. We suggest you reach out to your team to re-delegate the task.

We have a ~BAU channel on MM where you can reach the team directly and drop any BAU-related queries.