This is the slide presentation I prepared for my “Node for PHP Developers” talk that I gave at CampJS IV.

Wiring up the model and rendering output

In Part 10, I looked at the design of the model class I used to handle the “data” for the application. In this tutorial I’m going to look at how I wired it all up to finally produce my changelog.

A model for the application

In Part 9, I looked at extending the Joomla Framework’s Github package. In this tutorial I’m going to look at a model for the command line application that will do the most of the data gathering “work” the application is supposed to do.

Joomla 3.2 introduces the ability to save a history of the changes made when editing an article. The following guide walks you through this new feature.

Extending the Joomla Framework’s Github package

In the Part 8, I looked at to adding a logging service provider with the help of a third-party package called Monolog. In this tutorial I’m going extend Joomla’s Github package to integrate some missing (at the time of writing) functionality.

Adding a logging service provider using Monolog

In the Part 7, I looked at how the Github service provider could access configuration and command line input parameters using the DI container. In this tutorial I’m going to look at how I added a logging service provider.

Using services providers within service providers

In the Part 6, I looked at how to make a simple configuration service provider. In this tutorial I’m going to look at how to use that configuration data in another service provider.