Scott [:thecount] Downe Assignee
	Description • 6 years ago

We need to ID and implement the minimal set of components needed for these experiments, and we need to modify any existing components also needed for these experiments.

We need to ensure it gets rendered in the correct spots.

We need to ensure it's configurable for our experiments need, with an emphasis on the rapid nature we need for these.

	Ed Lee :Mardak
	Comment 1 • 6 years ago

From https://www.figma.com/file/NOf8M1rh8InfVEVbUO23GHo2/Home-wireframes

It looks like each view/component will have different behaviors depending on if it's in the full vs 2/3 vs 1/3 area (bug 1513253). We'll probably want individual bugs for each, but overall approach we can discuss here. Potentially the differences can all be covered by just CSS and cascade whether it's the full vs each column…

Top sites
full: 1 row of 8 sites
2/3: 1 row of 6 sites
1/3: 2 rows of 4 sites each

Hero
full: 1 large image (~2.5 columns wide) then 4x smaller
2/3: 1 large image (~2 columns wide) then 4x smaller
1/3: invalid?

Card
types: floating (bordered) and borderless
full: 3 columns
2/3: 3 columns
1/3: invalid? (example shows sponsored, but this particular one might be its own special component…)

List
full: 3 columns with images
2/3: types: 2-column and 1-column both with images
1/3: types: numbered, first hero with images, no images
(first hero maybe should just be the 1/3 hero view…)

Section header
types: "best of the web", "recommended by pocket", "from across the web" all with topics
full: only valid for full it seems?

	Jessilyn Davis
	Comment 2 • 6 years ago

Notes from our mtgs thus far:
https://docs.google.com/document/d/1mdQwsJa6ZYVUyT5jCNEp_Xy0lCGegV_oRCdLj6Rlcq0/edit?ts=5c12e6f8


New Tab Module and component options spec:
https://docs.google.com/document/d/1RCVxPGY2EbOr3tG19MIpfAaA59ZOApt303XUI0-RMoM/edit#