Saw a question in the general channel and it made me think. Given packages are such and important part of developing in and around the umbraco ecosystem , should there be a defined path. I know all of you who have done stuff have come from different angles and so forth and since we have a package team .. may be that’s a big some thing to address Ie almost a course or course notes 1. Package standards 2 build an extended property editor Buildings content app 3 extending a core function 4. Building new/ missing functions Tips on getting things approved 5 publishing and maintenance @User @User @User @User @User @User I apologise if some of this is old hat but it does make me think all that information could be collated and surfaced in a single area of docs if nothing else . I personally think it could be a decent exam.. //

Yeah - @User did a good workshop for this (for v8) while he was leading the package team. and we delivered it a couple of times at one of the candit contribs hackathons. we discussed if we could update this a few weeks back in the package team, but i think we all just felt we were a little short of time to put the resources required into doing it justice just now (it takes a long time to make a course/workshop!) that said everything you've said is right, it is a gap it does need something.

Hmm maybe that's an idea for a new blogpost series 🤔

All good thoughts. For me code is the most useful reference. How 'bout something like MS 101 ARM-templates? The package template is good enough, but maybe it could link to some more boilerplate to copy?

I think the tricky bit with packages is that so much is up to the implementor to decide. There is lots of best practise stuff, but sooo many different ways to achieve the same result, which could make it pretty tricky to bundle into something teachable

with .net we're pretty much aligned with "general" best practices, though. 🙂

.net yes. Have you seen the backoffice 😁

I think this would be a great course that Umbraco could deliver as an official course but for free. Perhaps get us as a community to collaborate on the content of it and then Umbraco roll it out as a half day course or something. Perhaps even with community members taking it in turns to run it each month?

Okay so may be set of blog posts that cover some pointers and pull the various blobs of documents and articles And then so,e kind of half day course that umbraco can run That way we cover getting the document and code together And we given it’s a major feature a paid course seems a sensible thing.. On @User note about we haven’t got a standard . By doing these documents and writing the course surely it will cause some one to realise where we are missing content if we are, and also learn how and where things are used ina practical sense Which could lead to better implementations down the road

I forgot about that in the heat of the moment, but I'd say backoffice best practice will have to wait for ui lib rewrite. Modules and loose coupling apply more than ever due to that. 🙃