Design look and feel, UX guidelines, site-wide items

[mialondon]

Logo, microcopy, etc.

• [x] 1-2-3 step glyphs
• [x] Logo and strapline design
• [x] Logo and strapline design variations - stacked, mini, favicon, whatever
• [x] Colour scheme
• [x] CSS grid
• [x] Nav menu
• [x] Page footer
• [x] error pages for 404/500
• [ ] styling for error messages, e.g. no input on the form
• [x] set up Google Analytics account
• [x] Add Google Analytics code to base template
• [x] Update Analytics profile with final main URL when decided

  Google Analytics code for base template

<script>
  (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
  m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
  })(window,document,'script','//www.google-analytics.com/analytics.js','ga');

  ga('create', 'UA-42903011-1', 'serendipomatic.com');
  ga('send', 'pageview');

</script>

[briancroxall]

We can possibly kick the 404/500 page to outreach team for design and CSSing, given the style guide. Maybe they could use a quick logo from Amy or find a mustache and monocle to use.

[mialondon]

Totally agree! And this comment is really just to note that assignments here are pretty meaningless as github doesn't let you do both granular assignments and grouped tasks (unless I'd used labels to group things and it's too late for that).

[patrickmj]

@mialondon might also be too late, but we've handled this by having the line for each checkbox also have a link to an issue with the same name, then make assignments on those

[mialondon]

That's a good idea, we could do that going forward. I'll also set up a label for parents items.

[mialondon]

The first static page stub is set up (about) to base the other static pages on and Rebecca's shown Jack how to work git. I think the static pages are being written in a Google Doc and will assume that the Outreach team can mark it up in HTML for inclusion on the page.

[rlskoeser]

Pages for 404/500 should be created in the templates folder as 404.html and 500.html - django will automatically load them if a user tries to access a page that doesn't exist (404) or if there is an uncaught exception server side (500) as long as the site is not running in debug mode. (Implied todo: make sure dev/prod sites are NOT running in debug mode)

Note that the 404.html can and probably should extend from the site_base.html template (similar to about pages), but the 500.html page can NOT extend from anything and (I think) does not have access to any of the template context we would normally have (because something went wrong).

[mialondon]

I think these are all resolved?