How will this theme structure work with the Shopify/GitHub integration? Will any of my files be overwritten when changes made in the Shopify editor are pushed to GitHub?
Hello, thank you for the video! Still, I keep receiving this error after the project launch and an automatically-created styles2.css file in the assets folder: 'ERROR >> update assets/styles.css: source sequence is illegal/malformed utf-8' The contents of the old styles.css file crack up. Do you have any idea how to fix this?
I don't get it, what's the benefit ? I think the strong thing about tailwind is its utility classes that can be outputted depending on your usage only, so if you use only 10 classes, it'll output only those 10 classes for you to work. But with the way i saw it in the video, you built it before adding any style? meaning you sent a predefined CSS that'll always get outputted no matter what you add, right? So my question is what's the benefit? be it a performance decision or dev experience decision, can you elaborate on why this can be useful?
Youness, Great video, thank you! Well, there are some areas that are in conflict, such as the grid, how did you solve them? For example, it can be seen from the video that the grid structure below is broken. [Screenshot: pasteboard.co/lDp3W7LT1P2K.jpg]
you saved my life, thank you
Great video, thank you!
Thank you for this! 🙏
Youness One thing to say Wonderful and bundle of thanks you made it easy.
Thanks!
What about creating a clean theme because right now in your tutorial have old style css from dawn and tailwind.
How will this theme structure work with the Shopify/GitHub integration? Will any of my files be overwritten when changes made in the Shopify editor are pushed to GitHub?
This will work seamlessly with Github Integration. just like before.
at 15:50 can you just add this script `npm run shopify:dev && npm run watch` instead of using that third party package to run multiple scripts?
Helpful video. Can you build shopify theme + Tailwind from the scratch ?
Hello, thank you for the video! Still, I keep receiving this error after the project launch and an automatically-created styles2.css file in the assets folder:
'ERROR >> update assets/styles.css:
source sequence is illegal/malformed utf-8'
The contents of the old styles.css file crack up.
Do you have any idea how to fix this?
I don't get it, what's the benefit ?
I think the strong thing about tailwind is its utility classes that can be outputted depending on your usage only, so if you use only 10 classes, it'll output only those 10 classes for you to work.
But with the way i saw it in the video, you built it before adding any style? meaning you sent a predefined CSS that'll always get outputted no matter what you add, right?
So my question is what's the benefit? be it a performance decision or dev experience decision, can you elaborate on why this can be useful?
can you share your notion file
Why do you prefer vite over the default tailwind install via tailwind CLI?
I also wonder this.
Since we're using Vite as the build tool, as he said in 6:16, it's ideal to watch for changes during development and minify the code for production.
King a sat
Youness, Great video, thank you! Well, there are some areas that are in conflict, such as the grid, how did you solve them? For example, it can be seen from the video that the grid structure below is broken.
[Screenshot: pasteboard.co/lDp3W7LT1P2K.jpg]
You can either use tailwind prefixes or rename the Dawn grid from ".grid" to ".grid-layout"
@@weodestry I already solve it using prefix. I just wanted to know how you handled it. thanks.
I also get it to play nice with Dawn with prefixes. Would love to not use them tho. Do you figure out another way of handling this?@@benhasanaltun