feat(website): style View Campaign page

[ace-n]

Fixes #64

[ace-n]

Test failures look unrelated.

(FYI @dinagraves I think there's a bad filename somewhere.)

[dinagraves]

It's failing b/c the trigger is looking for the test config in the main branch but it hasn't been merged yet (#94). It will also fail anyway because you didn't write any tests :).

[dinagraves]

Now it fails because you have no tests :)

Starting Step #2 - "Unit Tests"
Step #2 - "Unit Tests": Already have image: python:3.9-slim
Step #2 - "Unit Tests": ============================= test session starts ==============================
Step #2 - "Unit Tests": platform linux -- Python 3.9.6, pytest-6.2.4, py-1.10.0, pluggy-0.13.1
Step #2 - "Unit Tests": rootdir: /workspace/website
Step #2 - "Unit Tests": collected 0 items
Step #2 - "Unit Tests": 
Step #2 - "Unit Tests": ============================ no tests ran in 0.01s =============================
Finished Step #2 - "Unit Tests"
ERROR
ERROR: build step 2 "python:3.9-slim" failed: step exited with non-zero status: 5

[grayside]

Discussion: We've generally been using HTML4 markup in this project, I think we should consider using more semantic HTML5 markup. For example, using main, section, aside, header, and footer in lieu of many divs.

Raising this because I think we're approaching a stage where it goes from "revising to meet a new standard" to "planning a refactoring strategy"

[ace-n]

I agree, but I think this is best addressed as a codebase-wide refactor (since other already-styled pages do the same thing).

I filed #106 to track this effort.

[ace-n]

@dinagraves - @engelke and I will have to discuss a larger frontend/website testing plan going forward.

That's probably not going to be addressed for a few weeks, though. (Ideally, I'd like to get the website fully styled first.)

[dinagraves]

@dinagraves - @engelke and I will have to discuss a larger frontend/website testing plan going forward.

That's probably not going to be addressed for a few weeks, though. (Ideally, I'd like to get the website fully styled first.)

Sure - you have a few options then. Either someone who has override power can merge the PR, or you can write a simple "test" that just does assert True, so it keeps the pytest check happy.