routify
Tailwind CSS
Our great sponsors
routify | Tailwind CSS | |
---|---|---|
12 | 1,275 | |
1,823 | 78,166 | |
-0.1% | 2.1% | |
9.4 | 9.4 | |
13 days ago | 1 day ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
routify
-
How's routing done in Vanilla Svelte?
Been using Routify in all my projects since I started with Svelte like 3-4 years ago.
-
SvelteKit: How do you handle largish projects with so many +page & +page.server files?
Anyway, it seems you have a problem with Sveltekit routing. You can still use Svelte with other SSR frameworks, such as Astro, a router like https://routify.dev, or switch to another framework altogether.
-
Svelte and abandonware?
Routify is still active and new version in the works. Version 3 can be used https://github.com/roxiness/routify/tree/next
-
Tauri with Svelte or SvelteKit?
I would have to say Svelte with a router like https://routify.dev . My recent blog post originally used sveltekit but I swapped it out last minute
-
Is there a way to restrict access to certain routes using svelte-spa-router
Consider https://github.com/roxiness/routify
-
If anyone can help me with my noob questions
Regarding some suggestions on here recommending SvelteKit: Learning SvelteKit might be a big ask depending on what you're trying to do. If you just want to stick with svelte only for now, and you want to add SPA routing capabilities, consider checking out https://routify.dev there's a ton of documentation for it and it's fairly simple to pick up. ✌🏼
-
State of the Sveltejs Ecosystem?
Routing: We have a few third party ones such as routify, svelte-spa-router and svelte-routing as well as the clientside routers included in SvelteKit and Sapper.
-
Sveltekit - to use or not to use?
if Next.js/Nuxt like needs are not something you're looking for yet, you can definitely go ahead with Svelte's default client-side app approach, with svelte-spa-router or routify for SPAs.
-
Learning to cook at home with Parsnip - built entirely with Svelte!
We chose Routify for client-side routing because this was around the time that Sapper seemed like it was being sunset in favor of Sveltekit which doesn't seem production-ready quite yet. We also have plans to statically pre-render the app so it can more-or-less work entirely offline and Routify makes that relatively straightforward (but see below).
-
Comparing Svelte and React
Since svelte does a lot of compile time stuff, I would like to mention Routify, which is compile time SPA routing. For me it worked awesome to accomplish projects with many routes and the need for hash based routing.
See https://routify.dev/ and https://routify.dev/guide/installation/install-to-existing-p...
Tailwind CSS
-
ChatCrafters - Chat with AI powered personas
This app was built with Svelte Kit, Tailwind CSS, and many other technologies. For a full rundown, please visit the GitHub repository
-
Mojo CSS vs. Tailwind: Choosing the best CSS framework
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.
-
Collab Lab #66 Recap
JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite
-
Show HN: Brutalisthackernews.com – A HN reader inspired by brutalist web design
- 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...).
-
Ask HN: Who is hiring? (April 2024)
- 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.
-
Deploy a Golang serverless function for a demo form with htmx
Instead of Booststrap, I used Tailwind CSS as the CSS library.
-
Shared Tailwind Setup For Micro Frontend Application with Nx Workspace
Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.
-
Building a Dynamic Job Board with Issues Github, Next.js, Tailwind CSS and MobX-State-Tree
Basic knowledge of Tailwind CSS and MobX-State-Tree
-
CSS Styling (Next.js)
Tailwind is a CSS framework that speeds up the development process by allowing you to quickly write utility classes directly in your TSX markup.
-
Open-source timepicker components for Tailwind CSS
Tailwind CSS
What are some alternatives?
awesome-sveltekit - Awesome examples of SvelteKit in the wild
flowbite - Open-source UI component library and front-end development framework based on Tailwind CSS
svelte-routing - A declarative Svelte routing library with SSR support
antd - An enterprise-class UI design language and React UI library
SvelteKit - web development, streamlined
unocss - The instant on-demand atomic CSS engine.
svelte-spa-router - Router for SPAs using Svelte 3
windicss - Next generation utility-first CSS framework.
svelte-starter-kit - Svelte with brilliant bells and useful whistles
emotion - 👩🎤 CSS-in-JS library designed for high performance style composition
Sapper - The next small thing in web development, powered by Svelte
Material UI - Ready-to-use foundational React components, free forever. It includes Material UI, which implements Google's Material Design.