Closed thombruce closed 1 year ago
Name | Link |
---|---|
Latest commit | b98e12586b2057a93a9a278f1024e35cebcb50e8 |
Latest deploy log | https://app.netlify.com/sites/toodles/deploys/64a05ff73e8884000883695c |
Deploy Preview | https://deploy-preview-96--toodles.netlify.app/ |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Status | Category | Percentage | Covered / Total |
---|---|---|---|
🟢 | Lines | 66.72% / 60% | 395 / 592 |
🟢 | Statements | 66.72% / 60% | 395 / 592 |
🟢 | Functions | 61.36% / 60% | 27 / 44 |
🟢 | Branches | 68.85% / 60% | 42 / 61 |
darkMode toggle should ideally have three options:
...meaning a toggle switch is sort of out of the question. Best options are dropdown select or radio buttons. I think radio buttons are the preferred way to do this, but they would clutter up the navigation interface. So if we do go that route...
Last push sorts CSS into more appropriate files by name (tailwind.css
for Tailwind imports, base.css
for base Toodles styles).
The intention is maybe to have discrete files (e.g. forms.css
) for grouped elements, thereby creating reusable styles... These can still be overwritten at the component level.
Rather than applying text-color-500
and dark:text-color-400
to elements like the ContextTag, consider applying both of these styles in a context-color
or similarly named class, so that just the one style needs to be applied. Do this in, for example, a tags.css
file.
Some colours might be more broadly reusable. For instance, priority colours being essentially red, amber and green; these might be our error, warning and success colours. If so, we should consider options to configure them as a shared sort of utility color. See Using the default colors and Aliasing color names here: https://tailwindcss.com/docs/customizing-colors#using-the-default-colors
If colors have several utilities and are likely to be modified together, consider something like that. But be wary of how forked projects might want to theme things differently. Just because I have priorities success-warning-error coded does not mean that descendant projects will as well. Put some thought into these choices.
Clear to merge if we want. Though it might be worth squeezing in saving the language setting to localeStorage as it should be similar to how we're storing darkMode setting.
Done.
All that might be left is to add...
These are all bonuses at this point though, and I'm happy to leave all three for a future effort.
Ready to merge!
closes #95
Internal use. Do not delete.