Content Apps?

[abjerner]

As a follow up in this tweet and the conversation that followed it, should this repository be used to list existing and upcoming content apps as well? Or should be create a custom repository for listing content apps? Or both?

The "Awesome" format is mostly just linking to each package along with a short description, and it's in no way a complete list of all Umbraco's packages, so this may not be right format.

Creating a new repository also creates som separation, but it could be used to better showcase content apps - and as I suggested on Twitter, it could also be used to request help if you wish to build your own content app, but need a little help getting started.

It could also be that this repository would list the most used content apps, and a separate content apps repository could be used as a showcase and to coordinate contribution efforts.

I'm unsure what would be the best approach - hense this issue. So I'm looking forward to hear some feedback 😄

[leekelleher]

Thanks @abjerner! I think the Awesome list should remain as that... a curated list of Umbraco packages & resources.

I've been discussing with @warrenbuckley about bringing my Package Ideas repo over... but I'm not too happy with it's current format (there's a lot of work to make it work the way I intended).

Maybe there's scope for starting afresh with a new/clean "Package Ideas" repo on this org? With sections for Property Editors, Content Apps, etc.