a UI library needs some demo

The website itself is made with Sycamore!

There are also a bunch of examples at https://github.com/sycamore-rs/sycamore/tree/main/examples

You can see the deployed versions at https://examples.sycamore.dev/<example name>/ for instance: https://examples.sycamore.dev/todomvc/

▲

ecshafer 4 hours ago | parent | next [-]

The website is an entirely static website, and the frameworks main pitch is how good it is with reactive websites. This website could be entirely the same with html and css.

	▲	lukechu10 4 hours ago \| parent [-]
		That's true... but there's also plenty of other examples with more reactive elements.

▲

catapart 5 hours ago | parent | prev | next [-]

in case you don't understand what GP is suggesting: your website does not actually describe what you're providing. A "next generation Rust UI library powered by fine-grained reactivity." could mean a UI for native apps - something like egui or Dioxys - or it could mean a way to use rust to output HTML, CSS, and javascript. Or a bunch of other things. And, regardless, there's no way to look at your website and determine how to get that output using sycamore. I can inspect and see your HTML or your CSS, but there's no Rust code for me to compare that against without going and looking it up somewhere.

To be more succinct: you don't even have an image of your UI running on your websites landing page. Not one single image of the library which is, again, a UI library. People have an interest in knowing "does this look and feel like I want it to?" as well as "can I use this in the projects I'm working on?". Both of those questions should be answered by your landing page. For me, at least, it doesn't do that.

▲

lukechu10 5 hours ago | parent [-]

Hmm thanks for the feedback. The front page definitely has lots of room for improvement.

▲

fnikacevic 5 hours ago | parent [-]

A great example is the shadcn site

https://ui.shadcn.com/

Shows you how good it looks out of the box on the first page.

	▲	0x457 an hour ago \| parent [-]
		That's a component library, Sycamore is no that. I agree that it have better showcase of what you can build with it, but components library isn't it.

▲

silon42 6 hours ago | parent | prev | next [-]

I get: Uncaught (in promise) ReferenceError: WebAssembly is not defined

	▲	lukechu10 6 hours ago \| parent [-]
		Umm which browser are you using? Did you disable webassembly somehow?

▲

luckydata 2 hours ago | parent | prev [-]

I will say it bluntly because it needs to be said: that website is not enough for anyone to be interested in the library.

	▲	lukechu10 2 hours ago \| parent [-]
		There are also plenty of other examples as mentioned in the comment above. Also many other projects using Sycamore which you can see by looking at GitHub’s reverse dependency page.