[RFC] UX examples initiative

[t-richard]

This come from a discussion started on the Symfony slack.

Someone asked about adding new UX packages for common use case: modal, lightbox, date pickers, WYSIWYG, etc

This has low value for Symfony UX because most of these usecases have well maintained libraries that would be trivial to integrate with Stimulus and Turbo, and it have a high maintenance cost to have those inside the UX initiative.

Enough context, what is this about ?

@weaverryan gave a super interesting idea, instead of creating individual packages with low value, we could have an examples section on ux.symfony.com

This allows for:

• Greater flexibility with less efforts, we can add or remove examples with little consideration for covering every usecases or even BC
• Greater surface coverage for frontend needs: surely date pickers are useful but providing an example with a 10 lines stimulus controller is probably enough
• Inspire the community: this will be a learning resource, seeing those examples will help developers see what they can do with Stimulus and the ecosystem to build awesome experiences for their users

Some challenges

• We need a base section with design on the UX website to enable contributing examples
• We would want a LOT of examples for this to be useful, so it needs to be easy to contribute, maintain but mainly it should be easy to explore when on the website
• We need to curate libraries used on the examples, even though it's just an example, we want users to be able to use them in their projects with confidence

Some inspiration

• https://stimulus-use.github.io/stimulus-use/
• https://www.stimulus-components.com/
• https://twitter.com/ilrock__/status/1631315562390519809

Let's gather feedback, examples and make it happen ✨

[weaverryan]

Let’s get this party started :).

The live components section of the site already has demo pages, so we can use that design at least as a starting point. We’ll also need a /demos page - I can get a design for this if needed, but that shouldn’t stop someone from bootstrapping that.

The code for each demo should be as standalone as possible: probably a dedicated controller class for each (so a user can easily see its code in an uncrowded way if seeing the controller is relevant).

There are other details to figure out, but nothing scary. We just need to get it started so we can load it up with demos.

[t-richard]

Yes, we just need to do it.

Started something today to get the ball rolling.

I based the design on live components and we can iterate from there.

Expect a PR soon 🤞

[weaverryan]

Yes please! It can be rough - 💯 to iteration!

[excitedbox]

I suggested something similar in 2 recent issues. One is advocating for a symfony ecosystem section and another is for a unified component controller. Sadly not many people responded even though those that did liked the idea.

If we had an example for something like Turboframes integrated with a goldenlayout type component, it would make it trivial to change the code you load inside those frames. It would offer a great starting point for beginners to build web applications, dashboards, and one page apps.

[weaverryan]

unified component controller

Can you explain this concept?

If we had an example for something like Turboframes integrated with a goldenlayout type componen

Yea, that sounds like a cool example :)

[carsonbot]

Thank you for this issue. There has not been a lot of activity here for a while. Has this been resolved?

[carsonbot]

Hello? This issue is about to be closed if nobody replies.

[carsonbot]

Hey,

I didn't hear anything so I'm going to close it. Feel free to comment if this is still relevant, I can always reopen!