<robertknight> 1. The new homepage look and layout
<robertknight> 2. The changes to the navigation bar at the top and bottom (the content below the fold is not currently shown on that Trello card, conor will add that later)
<robertknight> Conor has said that the navigation needs to be consistent across the homepage and WordPress, so we should have either the new on both or the old on both.
<robertknight> I'd suggest that we start by using the current navigation, as it appears on WordPress and the homepage on both. For this PR, I would suggest using ngrok to demo it to conor before we merge anything so that he can see exactly what it will look like before it lands.
<nick> @wyan :wave: Welcome!
<robertknight> Regarding Bootstrap, we should figure out what it is doing for us at the moment.
<robertknight> I don't see much in the way of complex components or effects on the frontpage that couldn't be reproduced with very minimal CSS - but I may be wrong
<robertknight> @wyan: Hello :)
<wyan> :wave: hello everyone :)
<seanh> wyan: Hey!
<seanh> robertknight: For my currently in-progress pr I'm re-implementing the WordPress front page exactly as-is
<seanh> That'll be finished pretty soon, then let's take it from there
<seanh> I do wonder whether we're gonna want to move the rest of the WordPress static pages into the app, then just allow the blog to look different from the rest of the site, as otherwise keeping the two in sync all the time is gonna be a pain
<seanh> Yes the front page CSS should be fairly simple, main difficulty I've seen so far is the responsive stuff that it does, but hopefully that's just a straightforward use of bootstrap, and we can use bootstrap in the app as well right?
<nick> @seanh: sounds good to me. @robertknight/@conor: the new design looks awesome. I reckon let's separate the pieces -- so we can merge the homepage->app PR sooner and sort the infrastructure pieces that need sorting to deploy that.
<robertknight> Makes sense
<nick> As for other pages, I hear you about keeping the designs in sync, @seanh, but I think we should probably resist any attempt to turn `h` into a CMS. I think what I'd like to see is us moving all the non-app pages to `/project/` or something, and it can be given its own style and navigation.
<nick> There'll still be some work to do to keep things in sync, but I think WP, while a pain, is great because it means anyone on staff can contribute to improving the content and docs on the site (e.g. https://hypothes.is/education/)
<nick> Whatever we do we should endeavour to preserve that ability for our staff.
<robertknight> Agreed. Having speedy deployments lessens the difficulty of updating copy but having staff be able to contribute without going through Github is important
<nick> @wyan: You've joined us just in time for all the Americans to be off celebrating Thanksgiving, so you probably won't see them around today. How's London? As grey and dreary as Berlin today?
<wyan> @nick: it's not too grey today, actually! :)
<seanh> So there is a `logout()` view callable in `AuthController`, but it doesn't seem to be used?
<nick> @seanh: In `h.accounts.views`? It's used by the `/logout` route.
<seanh> Right, but do we use the `/logout` route anywhere?
<seanh> I mean, we will do, soon
<nick> Oh, that's a good question
<nick> I know I use it manually when testing things, but a brief glance suggests you're right.
<seanh> Oh dear, so with the new front page in the app, you can click on a log out link (link to /logout) and it'll log you out and redirect you to the front page again. But it also sets a "You have been logged out" flash message for the the next time you load the sidebar. If you now log in from the front page again it'll redirect you to the stream which will be the first time you've seen the sidebar since logging out. So you login and get a "You have logg