I’ve never heard them being combined. How do you decide when to use which? Or is it more of a progression from one to other?
I almost exclusively use Tailwind with @apply, sometimes I first try it out on the HTML and then copy it to a dedicated class.
Doing it like this forces me to write more logical CSS and be more DRY (for example having consistent logical margins instead of just adjusting arbitrary elements until it looks good)
I'm indeed writing my own CSS using the BEM approach. I'm not crazy about it, but it definitely beats my old way of doing things which lacked any structure at all. At least BEM provides some general strategy.
Lately I'm becoming more intrigued by utility-first CSS frameworks like Tailwind CSS. I have yet to actually try it though, but the overall concept makes a lot of sense. Especially after reading this article.
I've also heard a lot of good things about it. @Jankeesvw, do you mind chiming in with your experience?
If I do this users who share their nl url with someone from en the en user
will visit the wrong page.
I think this is true for any page, correct? If I as a Dutch user visit your site and up tweeting a link, my Twitter followers will end up on a Dutch page. Correct?
I'd lean towards using a URL parameter even though Google recommends against it. The cons they explain don't include bad SEO ranking as far as I can tell. Personally, I could live with the cons. Also, since your site doesn't seem to be content-heavy and the language setting tends to refer mostly to user interface elements (I think?) I don't think it's much of an issue anyway.
I also recommend looking at how other sites have solved this. Specifically those that have a similar setup as yours. (user generated content, etc)
Currently I'm working on a v2 of sayhi.dog and it includes breed pages where a lot of content has been created (by the community). So it will be content heavy and those pages are going to be very different for several languages. It's a difficult decision but I will do some more research.
Thanks for answering Marc!
What's your favorite color, @Jankeesvw?
@marc there is no auto-complete... :D
Yeah I think "developer tools" is very broad. When I looked at the section that's relevant to me (Ruby) I saw only 3 tools, which isn't very compelling. I think it would be very hard to create a collection for dozens of categories. Better to focus on one category first and do it right. Then expand from there.
Will fix. Thanks!