We introduce the course, state some expectations, check on your development environment and then install our plugin from a template.
We also add some notes about git, a very useful tool for developers and pretty much an essential for Moodle Developers.
The example plugin uses renderers to separate the output from the plugin logic as is good practice in any kind of development. We briefly re-visit the $PAGE and other output components and refactor our code to use simple permissions. We set up a couple of features: styles.css and a local class.
This week covers Moodle forms to an advanced level. We will briefly recap the material from the level 1 course before getting into the complexities associated with saving form data and upgrading a plugin by adding a new table. Finally we save some data to the table using a form, including dealing with an editor type form element.
We have some tidying up to do this week. We can now add one page but we need to be able to add more pages and navigate between them, edit pages and delete them. We will introduce a page management "console" similar to those you already see in Moodle for managing courses. All in all, another busy week.
Each of those does not involve writing a lot of code. But you should be familiar with namespaces and class loading. Tasks are straightforward in code, but are really a bit tricky to debug. I suggest you stick pretty close to the code given, to avoid having to track down bugs. Logging and events are two sides of the same coin, and by now you have probably seen them in Moodle code.
Have we finished out plugin, is it ever finished? Code checking and the plugins database. Some additions we might make to increase interactivity.
An extended task for you to attempt: Adding a comments section to the plugin. This will involve researching the comments API, upgrading the database, adding new capabilities, updating mod_form, and admin settings. Haere rā (farewell) from the course.