awesome-appwrite VS Tailwind CSS

A big part of growing Appwrite’s developer ecosystem is providing the right platform for our builders to showcase their works with Appwrite to our community so that they can gain better visibility, feedback, and usage. For the last couple of years, that has exclusively been the awesome-appwrite repository we have on Appwrite’s GitHub organization.

You should now have a good understanding of how Appwrite works, its features, and services. You can join Appwrite's Discord community here. to learn more about it. You can also visit its webpage. or repository .for additional information and resources.

Hacktoberfest may be over, but you don’t have to stop contributing! We have lots of open issues that you can find on our GitHub repo. Moreover, many of our Hacktoberfest issues are still open for assignment! You can also write articles, create tutorials, or build demo apps and add them to our Awesome Appwrite repo. There are always new ways to support the community, and we truly love all the contributions you make. If you need help with Appwrite or would like to explore some interesting ways to contribute, join us on our Discord server and connect with the Appwrite community ❤️.

You can check out our relatively new Youtube channel: https://www.youtube.com/c/Appwrite - there also more video tutorials available by community members and more resources on: https://github.com/appwrite/awesome-appwrite

Our list of awesome tutorials, videos, and demos keeps growing. Head to the awesome-appwrite repo to check them out.

Appwrite Resource Showcase

30 days of Appwrite is now updated, have you checked them out already? 30 Days of Appwrite - Appwrite 30 Days of Appwrite is a month long event focused at teaching you about all of Appwrite's core concepts and getting you ready to build production ready apps with Appwrite. 30days.appwrite.io We are awaiting to see what you build, be sure to drop them here .

We are awaiting to see what you build, be sure to drop them here.

We have a bunch of Appwrite related resources over at https://github.com/appwrite/awesome-appwrite which you can also check out

Hacktoberfest may be over but you don’t have to stop contributing! We have lots of open issues that you can find on our GitHub repo. Moreover, many of our Hacktoberfest issues are still open for assignment! You can also write articles, create tutorials or build demo apps and add them to our Awesome Appwrite repo. There are always new ways to support the community and we truly love all the contributions you make. If you need help with Appwrite or would like to explore some interesting ways to contribute, join us on our Discord server and connect with the Appwrite community ❤️.

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.

This app was built with Svelte Kit, Tailwind CSS, and many other technologies. For a full rundown, please visit the GitHub repository

Unlike Tailwind, which has over 77,000 stars on GitHub, Mojo CSS has about 200 stars on GitHub. But the Mojo CSS documentation is fairly good and you can find most of the information you’ll need there.

JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite

- Performance is a feature.

Another common interpretation of brutalism is aesthetic, reacting to overly complicated user interfaces by creating simpler, more direct ones. Tailwind CSS (https://tailwindcss.com), one of today's most popular CSS libraries, promotes this approach in its component examples. There's also a neat library I've seen recently called "Neobrutalism Components" for React that I like (https://neobrutalism-components.vercel.app), providing components with a similar look and feel to Gumroad. This might more accurately be called 'Neo-Brutalism,' as noted in the comments.

A more engineering-centric interpretation of Brutalism focuses on form, structure, and efficiency, drawing significantly from brutalist architecture principles. Apart from the user interface itself, most mobile, desktop, and web applications are extremely bloated and often perform worse than sites from 10 years ago did. While one HTML file might be "less brutalist" than the original HN site, it is substantially more brutalist than any HN mobile app in existence, and offers nearly identical functionality.

A broader interpretation of brutalism, which could be termed 'Meta-Brutalism,' is embodied in the overall experience on this site through UX flows. Yes, in the strictest sense, the original HN site is more Brutalist in many ways, but it only shows 30 articles at a time and does not function as a PWA. For this site, the experience of reading 10 stories is arguably less brutalist, but for quickly browsing through several pages and skimming articles (which is how I read HN) it is a lot faster, and in my opinion, more Brutalist.

My primary inspiration was addressing software and tool bloat in UIs rather than strictly adhering to every principle set forth by David Bryant Copeland. I don't find it convincing that this site "isn't brutalist" compared to really any other experience apart from the Main HN site, and I would argue the overall experience is more brutalist in its performance and scrolling behavior.

As a side note: I generally don't like Brutalist architecture that much although I believe it is unfairly maligned. I visited the Salk Institute once and enjoyed it though (https://www.archdaily.com/61288/ad-classics-salk-institute-l...).

- Staff Software Engineer ($275k/yr): https://tailwindcss.com/careers/staff-software-engineer

We're small, independent, and profitable, with a team of just 6 people doing millions in revenue, and growing sustainably every year. You'd work directly with the founders on open-source software used by millions of people.

If you like the idea of working on a small team that cares about craft and isn't trying to achieve VC scale, I think this is a pretty awesome place to do your best work.

Instead of Booststrap, I used Tailwind CSS as the CSS library.

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

Basic knowledge of Tailwind CSS and MobX-State-Tree