umbraco-community/awesome-umbraco

A curated list of awesome Umbraco packages, resources and tools

awesome-umbraco's Issues

Review list

Review the list, make sure everything is still relevant.

Also review the recent Our Umbraco post, there are some gems in there...
https://our.umbraco.org/forum/using-umbraco-and-getting-started/81789-what-would-be-your-top-5-plugins-for-an-umbraco-website

Review entire list for Umbraco 9

'nuf said ;)

Anyway, here's a starter list for Umbraco 9 (full disclosure - some of these are ours):

Multi-targeting Umbraco 8 & 9

• OpenOrClosed: https://github.com/YourITGroup/OpenOrClosed
• Our.Umbraco.GMaps (release 2.0 imminent): https://github.com/ArnoldV/Our.Umbraco.GMaps
• MemberListView: https://github.com/YourITGroup/MemberListView
• Vendr*: https://vendr.net/
• Contentment: https://github.com/leekelleher/umbraco-contentment

Umbraco 9 only

• Koben.Iconic (release 3.0 in the works and under testing for Umbraco 9 by Mario Lopez): https://github.com/KOBENDigital/Iconic

Suggestion: Remove "Umbraco products" category

Suggestion to remove the Umbraco products category, by relocating Umbraco Forms to the Form Builder subcategory (under Backoffice Extensions) and Courier to a new subcategory (under Developer Tools) called "Deployment".

Content Node Icons

This package has a tiny footprint in scope. I wrote it to allow my content editors and myself to set specific icons on specific content nodes without the need to duplicate content types.

I haven't released v10 yet - probably something I'll do by the end of the week.

Should/could this be listed?

https://www.youtube.com/watch?v=kNhqLtaExuA

Grouping of Property Editors

Hi Lee,

Just a thought on grouping, specifically of property editors. Based on your talk with Marc at CG18 on atomic design, should it you extend the grouping of property editor plugins to match the periodic table idea? 😃 #atomicdesign

Addition of Meganav

Property Editors / Website utilities

Url: https://our.umbraco.org/projects/website-utilities/meganav/

Addition of StyledTextbox

Review entire list for Umbraco 8

Since it's Hacktoberfest, these is a great opportunity to review the entire Awesome list, to see what is still relevant for Umbraco v8.

A copy of the Umbraco v7 list has been archived off, (in PR #57), so there are should be no concern about anything being missed out or lost.

Please note: there are no expectations for this to be a single task for an individual. Small incremental suggestions are perfectly acceptable, (although trivial grammar tweaks may not count as Hacktoberfest approvals).

Addition of uEditorNotes

Addition of Terratype

Update links to Our Umbraco with HTTPS

Addition of Courier/Deploy Contrib Resolvers

This is essential for any UmbracoCloud project.

Validate pull requests with Travis

Hello, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request.

It is currently being used by

• https://github.com/vsouza/awesome-ios
• https://github.com/matteocrippa/awesome-swift
• https://github.com/dkhamsing/open-source-ios-apps

Examples

• https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴

If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.

See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment 😄

Content Apps?

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 😄