phivk/gradu.al

Gradual - Here to learn.

gradu.al's Issues

transition from Tachyons to Tailwind

On community pages (i.e. /mozfest & /storytellersunited/) and their sub pages, styling is done using the Atomic CSS framework Tachyons. We're in the process of transitioning from Tachyons to Tailwind.

Work is ongoing in this (draft) PR: #84

Some recommended background reading: https://dev.to/nejremeslnici/migrating-tachyons-to-tailwind-css-iii-learnings-57d

Since we have a small code base and some of us are still learning the Tailwind class name 'API', we decided to not use any automated script, but do the conversion from Tachyons to corresponding Tailwind class names manually. I personally use regex's in my text editor.

Two non trivial things to consider:

Different Spacing Scales

Different Breakpoints

The full transition will take a while, and that's OK. We can pick up this in between other work. We'll probably achieve most consistency by converting all instances (e.g. ma, mt, mr, mb, ml, as well as their responsive variants, see 7f3fb80) of a particular class name in one go.

So far the following classes have been updated:

• all text-align classes
• all padding classes
• all margin classes

the created_at field is not set from the form on any of the supabase tables

Add validation to check session resources for valid links

Preventing " " values being treated as embeddable resource

Display learned by and shared by fields on SessionPreviewCard only if present