amphtml VS Tailwind CSS

https://amp.dev/ is that. No one wants to use it because the very first line of the mandatory js file is about advertising metrics.

Google announced an open source HTML framework called AMP (Accelerated Mobile Pages) for better and faster experiences on the mobile web (Google said that) in 2015. This was created in an effort to play against Facebook Instant Articles.

Does Flutter web allow for AMP compatibility?

Without disclosing too much, I am fairly involved around this topic, and I would say it's definitely heading for deprecation this year. The key giveaway is that Google Analytics 3 will be shutting down in July[0] and AMP has made no progress towards supporting Google Analytics 4[1]. I think it'll be deprecated at first rather than shut down because there are still billions of AMP documents floating around the web.

[0] https://support.google.com/analytics/answer/11583528?hl=en

[1] https://github.com/ampproject/amphtml/issues/24621

Accelerated Mobile Page is a Google-backed open-source project that allows you to create fast-loading super mobile-friendly pages.

OK, so we've all probably heard about AMP HTML from Google by now.

No JavaScript will be allowed other than an off-the-shelf AMP library

Recently I came across the AMP website at https://amp.dev/ (after some years since first seeing it). It’s really remarkable how much Google wants to pretend this is an industry standard and not their own little fiefdom. I don’t see the word Google anywhere, not even on the About page.

More about AMP

Lastly, Tailwind CSS is a utility-first CSS framework packed with classes like flex, pt-4, text-center, and rotate-90 that can be composed to build any design, directly in your markup.

Tailwind CSS

Sidekiq is already configured along with assets, tailwindsCSS.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.