DNNCommunity / DNNDocs

The documentation site for the open source Content Management System DNN (formerly DotNetNuke).
https://docs.dnncommunity.org
23 stars 51 forks source link

Bring back "Developer quick start series" #343

Open valadas opened 5 years ago

valadas commented 5 years ago

There used to be a series of blog posts or wiki articles in the past for each new major Dnn release. This outlined all the important changes, new APIs, deprecated APIs, etc. that affects developers and is kinda what we refer to when talking about best practices...

Examples: https://www.dnnsoftware.com/wiki/dnn-80-developer-quick-start https://www.google.com/search?q=dotnetnuke+developer+quick+start&oq=dotnetnuke+developer+quick+start&aqs=chrome..69i57j33.4295j0j7&sourceid=chrome&ie=UTF-8

I think this was great for existing developers to catch up on what's new and helped a lot improving modules.

Is there interest in developing a branch to start collecting such documentation here and publish that when we release Dnn 10 ? If so, ping me up.

dnndev commented 5 years ago

Is this a duplicate of #293 ?

valadas commented 5 years ago

Hmm, I would say it is related...

I think we should have a general list of best practices for developments/theming, etc. And separately a "what's new" for each major release focused on developments/theming. So if you are a existing developer used to develop for Dnn9, when 10 comes out, you have a nice list of the new APIs available, what changed, what is deprecated, changes in best practices, etc.

But yeah, some content will be similar. I am not sure but maybe a best practices section per version? But something that was recommended in Dnn6 may be for from current best practices for 10 and if you are an existing developer, you may not want to go through the basic stuff and just want to get up to date...

valadas commented 5 years ago

It could be a blog post, but I think it is better to live in the documentation to quickly find it back when you want to re-check something. Maybe a blog post and a link in the documentation best practices to those blog posts that are "what's new"...