Another option is that all we do is just to just keep a list of interesting/community examples and let all of that be self maintained by the authors.

The downside of that is that it's harder to curate things and make sure examples are not broken or outdated.

Finally, I think the best option is to leverage pyscript.com and have examples hosted there.

To me this is the best way to go but my thoughts can be summarized as such:

• we don't want to test examples if these are community examples ... it's not our responsibility and it causes friction to whoever would like to just showcase PyScript for this or that specific case
• the rest of the Web write demos / examples in codepen or any other fully public and free space ... pyscript.com provide all the tools already to create awesome examples and we should make it simple for anyone to create these PyScript examples. This means we should really publish on npm our project and let anyone integrate it with ease anywhere they like and, if that's pyscript.com, it's even better but it shouldn't be the only way to demo PyScript (npm also automatically translates into multiple CDNs to grab the project, not just one)
• there are repositories maintained by the community with links to all the things ... one example when picking a CSS lib for VP was https://github.com/troxler/awesome-css-frameworks but there are many others and it should be the go-to page for examples. Since PRs will likely arrive from contributors, it's also contributors duty to keep these demo alive but it takes little effort to file an issue saying a link is broken and it shouldn't be hard on us to address those issues
• beside a CoC Idon't think we should create any friction in submissions ... a template with a link and a quick description should be all it takes to review and merge new entries

Maybe I am making this easier than it is but if create any unnecessary friction developers don't care dealing with in the wild (see code pens, builder.io or any other) we'll simply receive less examples to showcase and the repo will stall in purpose and usefulness.

Also +1 to what hood said around tests but that's probably worth a specific discussion beside this one.

It took me a while to give my 2cents here, but here goes.

Collective

I think partly of the reason why the collective didn't get more traction was caused by me being busy with other things since I told Paul that I would help there. The collective still feels like a great way for us to curate examples and let folks contribute to pyscript but there are a couple of things that I am concerned:

• The maintenance of an example relies on the maintainers of the collective
• We have a very strict policy to get an example merged, and we have pushed some changes to a contributor PR to make it in the style we want plus writing tests

Perhaps we should be less strict on the contributions, obviously, we want the examples to be of good quality and have tests so we know they work, but it feels like we may need to have a bit of balance, maintainers can't do it all.

Should we revisit the collective again and perhaps decide on a loose structure for it? @pauleveritt is likely to have some thoughts here.

I think an alternative proposal/flow would be better on people learning python and using PyScript. Maybe some basic checks to keys and such would be required. Also, if users could tag or classify their examples, it would help as the examples grow.

I like that idea, we could tag examples with beginner, intermediate, advanced or something 🤔

Awesome lists

there are repositories maintained by the community with links to all the things ... one example when picking a CSS lib for VP was https://github.com/troxler/awesome-css-frameworks but there are many others and it should be the go-to page for examples.

We currently do have an awesome list in the collective and after our last community call, I created this PR in pyscript.net but it still waiting for a merge.

Perhaps we could start with an Awesome List where folks could contribute their projects, tutorials and talks to the list and if they wish the contributors could use pyscript.com to host their projects - we probably just need to have a good PR issue or readme telling users how to host their projects if needed.

I guess the takeaway from this is that we probably should meet up (community call?) and decide what we want to do with examples and contributions because it's clear we do have users that would like to contribute to the project by sharing their creations.

Perhaps we could start with an Awesome List where folks could contribute their projects, tutorials and talks to the list and if they wish the contributors could use pyscript.com to host their projects - we probably just need to have a good PR issue or readme telling users how to host their projects if needed.

I think that's a good starting point that would move us a bit closer to the final goal without having to pick the home for examples yet (which, I know, is the core of this discussion 😅 ). +1

• The maintenance of an example relies on the maintainers of the collective
• We have a very strict policy to get an example merged, and we have pushed some changes to a contributor PR to make it in the style we want plus writing tests

Perhaps we should be less strict on the contributions, obviously, we want the examples to be of good quality and have tests so we know they work, but it feels like we may need to have a bit of balance, maintainers can't do it all.

That really is the core of the matter.

Maybe you are right and would be beneficial to have a community call on the matter... let's try to have one soon then!

Apologies for an OT fanboy moment, but... @WebReflection it's wonderful being in a thread with you. I spent last summer, at a beach on northern French coast, reading all your stuff. Repeatedly. And imagining how to project your ideas into a Python-based SSG. I'd say Ryan Carniato and you are the two I've studied the most. Thanks for your years (decades?) of web platform advocacy.

Ok... Trying to move this discussion forward to a point that we can actually agree on something and turn that into action items.

From the conversations, I feel like there is overall convergence towards:

• a collective that maintains and curates a set of examples and a curated list of external examples is a good thing 👍
• we don't want to keep the current examples tests in the same "core" tests suite
• we don't want to keep and maintain most [if not all] of the examples in core
• we still want to be able to run examples tests before we release, for overall visibility on how a release may impact users code, but we don't want to keep it as part of the process of merging every PR. A nightly or before-release cadence and possibly as part of some automation outside of the core codebase should do

In addition to these, I'd also like to propose the following (not necessarily discussed before, so I'm separating these in their own list):

• we create a "PyScript Collective" account on pyscript.com that can be used to share and manage all the examples curated by the collective (directly tied into the first item of the list above)
• We automate the process of updating projects on pyscript.com once they have been updated on the pyscript-collective Github Repo via a GH action and the pyscript.com CLI
• we change the examples page on pyscript.net/examples to point directly to the pyscript.com examples mentioned in the item above. (alternatively, if pyscript.com is advance enough to support it, we can also just point to the "PyScript Collective" profile page and replace the OSS Examples page completely

FYI, create a new repo as a container for community examples, maybe is a good idea, community examples can be used as a reference and maintained by the author; I think there are only a few examples available now.