How do y'all do unit tests?

create helpers.js for status logic

make theme specific roadmap colors, move icon logic to function

The x-overflow thats causing this is from the H2 image being to wide, so can adjust that in another diff I guess, take the new overflow rule off here and make a task to make position sticky work later

Also, doesn't need to be fixed here, but the "eCash" in the top left of the nav bar looks shitty when it is over content, as in the above screenshot. Maybe show just the hex e logo without the text after the user starts scrolling? Would apply to desktop as well. Need a task.

In D13874#309377, @bytesofman wrote:

width-chopping issue is back at 320px width

Also, doesn't need to be fixed here, but the "eCash" in the top left of the nav bar looks shitty when it is over content, as in the above screenshot. Maybe show just the hex e logo without the text after the user starts scrolling? Would apply to desktop as well. Need a task.

Change atoms index.js to have one export

add files

Rename files, put layout in its own folder, create atoms

@bot preview-e.cash

remove extra import

fix small screen issue

In D13862#309119, @bytesofman wrote:

should be responsive to a min width of 320px

Right now, widths of < 400px are messed up

improve gradient transition

import h2, rename homepage body

rebase

add background image

adding the background context for the h2 instance

remove unneeded function, change timing to 0.4

@bot preview-e.cash

convery class to styled componet

In D13811#308096, @Fabien wrote:

Can we have a hover effect, like increasing the glowing ? no blocker

improve comment detail, make link a styled component

changed the breakpoint for hiding, and links will be visible in the footer eventually and I made an issue to add them to the mobile menu

change breakpoint for hiding social links

remove text transform rule

Fix extra lines and css rule

Remove uneeded React import and fix styling flicker on load by adding next config and _document.js outlined in the nextjs example for styled components
https://github.com/vercel/next.js/tree/canary/examples/with-styled-components

fix classname

edit global css file to remove unneded color variables

Updated as discussed. See new description and test plan

expanding the scope of the diff to include both themes and applying the themes to the exisiting components

Ah good call, I didnt realize that was such a dated package. I saw it in an example and it seemed like a succinct way to define the theme object, as you can have the different theme values in the same object...but really at the end of the day doesnt add that much in terms of readability and not worth having another package. Can achieve the same thing with just styled components, just need to make a separate theme object for ecash and stealth