A World In App component

A WorldInApp is an App with a react-router-component Router defined and passed in as its content.

An App is a composition of { AppContainer, AppHeader?, AppContentContainer, AppFooter? }. An App may receive some content as its React.children.

• Move an icon back in: See: https://github.com/the-economist-editorial/component-win-app/blob/6c87920c0784ea720fba0a478696601c76ebbb22/index.es6#L42
• <StickyMasthead> should be used to help create the <AppHeader>. It will require fixes first. header.es6 should probably expose this. This is how it used to be done: https://github.com/the-economist-editorial/component-win-app/blob/6c87920c0784ea720fba0a478696601c76ebbb22/index.es6#L38
• header.es6 should use component-win-navigation which is should supply with some (1) fake data, and then (2) data received from calling the API on the server.
• handlers/{handler-name}.es6 should exist for [ 'home', 'article' ]. In fact, if not already each should be its own repo. Probably better. For example, see: https://github.com/economist-components/component-win-homepage See separate issues below.
• Lose the share icons styling and some other cruft which does not relate to us.
• Write tests.
• Import component-win-articlepage and component-win-homepage styling, etc.
• Decide how we are going to create the country list page.

• Most of the styling should be rewritten.

• Small commit of missing package.json code.

• [?] Upgrade to [email protected] and the newest stable devpack.
• [?] Upgrade to the latest react-sticky.
• Fix this incorrect PropType: https://github.com/the-economist-editorial/component-stickymasthead/blob/master/index.es6#L11
• Write tests.

• [?] Upgrade to [email protected] and the newest stable devpack.
• Fix the improper PropType: https://github.com/the-economist-editorial/component-masthead/blob/master/index.es6#L11
• Add logo PropType.shape: https://github.com/the-economist-editorial/component-masthead/blob/master/index.es6#L6
• Microcomponent for logo: https://github.com/the-economist-editorial/component-masthead/blob/master/index.es6#L43-L51
• Rename to titleEl to distinguish from propType string: https://github.com/the-economist-editorial/component-masthead/blob/master/index.es6#L27
• Write tests.

• Consider standardisation of a better name than articlepage, but whatever we do, be consistent with component-homepage.
• Link to your latest component-articletemplate or publish the latest version.
• Pass in the variantName. Map to this from the sectionName.
• Pass some fake data into the article.
• Use Dan's component to fetch the data.
• Write tests.

• Import the correct variant-group name styling.

• Fix the issues raised in the PR.
• Create a variantify component.
• Write README.md for variantify, teaching people what problems it solves and how it solves them. The README should also give insight of which components to wrap - my principle is that variation should (1) be lazy: you should make rendering/behaviour choices as close to the action as possible, instead of dependency injecting them in very deep.

• Consider standardisation of a better name than homepage, but whatever we do, be consistent with component-articlepage.
• Look into helping Russ by creating a variant-specific component-teaser-list and component-teaser so that it is possible to specify a heroic teaser or whatever we're going to call it. A refactor.
• Look into advertising approach for both the articletemplate and the homepage. To begin with hardcode it at a specific point. Then use flex box to order it. Then create some wrapper logic to define programmable <PlacementContainer>s that can choose where to put an advertising element given some logic.
• Pass fake advertising and articles data in.
• Use Dan's component to fetch the data.
• Write tests.

• Generate urls from a two-pass transformation of the navigationData with the routing JSX of react-router-component as the paths.