Good afternoon, first.
I'm an IT assistant in a company and I need to have a good foundation, but I'm having a hard time finding such material or clearly understanding what I've read.
The situation is as follows. The company where I work is with great strength behind being able to launch its own internal university soon. The courses are already all created, the groups of people (cohorts) already well configured by me and the former trainee (yes, I got it in the middle) (and I actually accept help if someone knows how to configure automatic synchronization of cohort members with Microsoft Active Directory groups.)
However, in order for the internal university to be finally inaugurated, some plugins were requested to be implemented (which, in my opinion, should all be developed by the IT professional himself here in the company, since they are not in the Moodle plug-in store ).
The point that is most important here in the text is that I was given the responsibility of looking for HOW to develop a plugin that will not stop working in a future moodle update (I believe it can be called "development guidelines"). Questions such as "what variables to use, what folders to put in" and anything that should be done by a programmer who already knows Moodle, is delivered to me and for this, I humbly ask for the help of the most interested and patient.
I accept links. The problem is I have gotten so confused among the thousands of pages trying to find something I'm rather lost with all of this.
Thank you in advance of all, and a good job.
I think that you should read Coding style and the links in the end. The main developer page is very important and each plugin type have some peculiarities, so it's good to read the page from plugin type too. They explain the structure and best pratices of developing for moodle.
There are a lot of things that we undestand better with time, but some tricks is always good to remember like:
- Don't change moodle core if you want to update it later;
- Don't try to reinvent things that exist in moodle (we can search a lot of functionalities and replicate it in our plugins);
- Try to undestand the main plugins in moodle 'cause you can solve a lot of problems with them;
- One homologation server is very important when we are developing new plugins. The homologation should be just like production for tests. You should try to install the plugins via interface too;
- Tests are very important and can prevent a lot of headaches;
- Install services for give us data are very important to undestand the enviroment and the users. We have a lot of reports in Moodle and they can help us too;
- Release notes are important to undestand the Moodle changes;
- And always remember that your problem can be the problem from other people, so sometimes searches can bring the solution or the people with the solution.
Thanks amigo, I'll read those articles.
That's it for now.
> The problem is I have gotten so confused among the thousands of pages trying to find something I'm rather lost with all of this.
Doesn't surprise me. Noticed that you joined moodle.org only yesterday!
So it all depends on how long the company can wait or how much resources it wants to put to accelerate the process. You'll find specialized know-how with Moodle Partners. If you want a second opinion, you can advertise on http://moodle.org/jobs/.