You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
inorder for this to work, we would need to collect logos for the majority of colors, I would argue that they shouldn't be visible by default, but rather being activated by using a toggle.
We currently store information about colors in /data/brandColors.js so I would say that
logos should be placed in /data/logos/.svg.
We could then write a script that would, based on if there is an logo, generate base64'd versions and
inject them on the static page.
Also, it might be problematic since all logos aren't squared, meaning that it might reduce the simplicity of
our current design.
The text was updated successfully, but these errors were encountered:
@kjbrum that is really cool! Do you think this fits the current design? I really like the simplicity and is afraid the introduction of logos might add to much noise.
But please feel free to fork and investigate if one can introduce logos while keeping it simple.
Might be cool if you were to make the grid of colors fill the screen and then when someone clicks on one, it fills the viewport and displays the additional information.
inorder for this to work, we would need to collect logos for the majority of colors, I would argue that they shouldn't be visible by default, but rather being activated by using a toggle.
We currently store information about colors in /data/brandColors.js so I would say that
logos should be placed in /data/logos/.svg.
We could then write a script that would, based on if there is an logo, generate base64'd versions and
inject them on the static page.
Also, it might be problematic since all logos aren't squared, meaning that it might reduce the simplicity of
our current design.
The text was updated successfully, but these errors were encountered: