Refresh: repository page lockup

[AlicjaSuska]

MVP scope of work for making this page work with the redesign:

• Button group design
• Panels on the sub pages of tags, branches, etc.

[rrhyne]

@quinnkeast It looks like repositories shipped with a container that doesn't match our understood (and underdocumented) guidelines. See the example below. Are there plans to update it? Even if we don't get to other areas of that segment of the product, I think the breader should be outside of the container for the release.

[quinnkeast]

A basic QA is on Figma now here:

https://www.figma.com/file/NIsN34NH7lPu04olBzddTw/Design-Refresh-Systemization-source-of-truth?node-id=3943%3A6581

The biggest change on the main repository view is moving the header out of the container:

Contributors view is the biggest open need right now, I'm going to create a new issue for it.

[felixfbecker]

I wonder if the container being in a different place might feel weird when browsing a repo and switching between files and directories, as it would switch around. But would have to play around with that to see how it feels.

The other question is: What is the scrolling element? Is it the <Container>, or is it the parent element of the <Container> that contains the heading and button bar too? Currently the file content or directory content scrolls, which currently is equivalent to "the <Container> scrolls" as they are the same element, but if we start putting content outside the container that would be important to know. Having only the <Container> scroll would reduce the available screen space for the content as the header becomes sticky, but using the parent element would be a bit inconsistent with the file view and may look weird with visible scroll bars, so I'm not sure what the right answer is.