I'm concerned why sass was included in the project when most of what it offers can be achieved using postcss and plugins (postcss-nested, postcss-import, etc.).

Tailwind CSS uses scss to build it it's classes @heywhy

It’s not compulsory, I use tailwindcss without any preprocessor like sass, less, stylus and so on. And the reason I don’t use any preprocessor is because most of what they provide can be achieved using a corresponding postcss plugin.

I don’t know if I’m allowed to make modification to this same branch/PR. I can make the modifications needed

I feel most of the classes defined in this file will be useful since we are working with LiveView. What I will suggest is to create a new file liveview.css and import it in app.css (see https://github.com/beamkenya/beamkenya_site/pull/6/files#r579540971). And a new file, called components.css, can be created then move the import of tailwind directives into, that way the app.css is less bloated.

yeah, like for tailwind css, a separate file will work, the tailwind directives can grow with time with much customizations and creating custom components as we grow