In support of #2557, this issue aims to provide an initial task to help stakeholders get acclimated to the project.
Implement an updated login screen UI based on mockups by @AustinCondiff:
https://projects.invisionapp.com/share/3ATIRBHKW9F#/screens/380522637

@timmysmalls and I will be meeting up next week to nail the UI/UX implementation of this screen and document it in Storybook. ๐ช
@austincondiff to speed up the workflow, I've taken on your task if you don't mind. Attached below are the designs for the login screen w/o the netlify-identity-widget UI. This will be our starting point.

Today @timmysmalls and I will take an approach to implement the design and components in Storybook. We'll keep you guys posted.
We've decided on the following:
Pattern in Netlify UI

New design login page

We've made a lot of progress today, this is our current progress:
Together we decided on the following. Hopefully, this is alright:
packages/netlify-cms-ui-default/srcnetlify-cms-backend-test and netlify-cms-backend-proxy to be depending on packages/netlify-cms-ui-default/src/AuthenticationPage.js so we keep the login screen UI DRY length.magicNumber which we use in every _spacing_, _padding_, _margin_, _width_, and _height_ to keep the UI consistent. Right now this number is based on 48px, which is used in the Netlify design system. In my experience, having a base number while creating a Design System works flawlessly. For exampleconst NewComponent = styled.div`
min-width: calc(${lengths.magicNumber} * 5);
padding: calc(${lengths.magicNumber} / 2);
border-radius: ${lengths.borderRadiusCard};
background-color: white;
`;
All progress is pushed to:
๐Timmysmalls' fork
๐Danoszz' fork
webpack.config.js - @danoszz @timmysmalls I am ready to do a PR for this issue, how's stuff going with the external provider buttons? Can I assist with anything?
Once we have the buttons, we can resolve this issue ๐โโ๏ธ
Our first Storybook component is alive ๐ก

Most helpful comment
Our first Storybook component is alive ๐ก