Laravel – My Journey – Part 6 – A Basic GitHub Workflow

Getting Started with Laravel and Github

Perhaps it’s just me, but I initially struggled with integrating GitHub into my Laravel workflow. I wasn’t sure whether I should create a repository on first, then install my Laravel application and then push it to GitHub. Or should I install my application first or what? Anyway, through trial and error, I established a VERY simple workflow that seems to work for me.

As ever, the leitmotif for this series is: take everything I say with a pinch of salt. This is a BASIC workflow and does not cover all of the possible scenarios that you may encounter in your own workflow. Don’t forget to read the disclaimer!

Continue reading “Laravel – My Journey – Part 6 – A Basic GitHub Workflow”

Laravel – My Journey – Part 5 – Bootstrap 4


Surprisingly, I have more to say about Laravel. However, this time I’m going to talk a bit about integrating the Bootstrap framework into my Shopping List application.

Those of you who have slavishly followed my ineptitude from it origins in Part One of this series will know that my fledgling application has reached a point where we actually have to present some content to the user. Part 4 briefly touched upon Laravel’s Blade templating engine, and how it can be used to take data passed to it from a controller and return it to the user. Rather excitingly, I am now going to look at making that data look nice. Step forward Bootstrap 4 (beta … beta 2) …

Continue reading “Laravel – My Journey – Part 5 – Bootstrap 4”

Laravel – My Journey – Part 4 – Room With a View


No-one is more surprised than me that this series has reached its fourth instalment. So far, I’ve laid the groundwork for my Laravel Shopping List’s backend. I have a database, I have the models, I have the controllers. But I haven’t anything to show the user yet. I’ll need that. Let’s see how Laravel’s Blade templating system takes my data and presents it to the user …

Continue reading “Laravel – My Journey – Part 4 – Room With a View”

Laravel – My Journey – Part 3 – Controllers


In MVC architecture, controllers interact with data (via models) based on a user’s request and pass it to a view so that data can be displayed to the user. In my application, a user may request a list of products. Laravel will route this  request to a controller.  The controller will request all the products from the database and then return the results back to the user via a view.

In this article, I’ll look at the controllers required for my Laravel Shopping List application. I’ll also touch upon routing as this is integral to the application flow.

Continue reading “Laravel – My Journey – Part 3 – Controllers”

Laravel – My Journey – Part 2 – Model Relationships

The ‘M’ in MVC

The ‘M’ in MVC stands for model. What is a model? In object-oriented programming, a model is a representation of a real-world object, such as a person, a product, a car, or a list. The representation takes the form of data that is related to the object in question. Not only that, but that model includes rules that relate to the data that represents it.  My nascent Laravel shopping list application will require some models … but which models? Continue reading “Laravel – My Journey – Part 2 – Model Relationships”

Laravel – My Journey – Part 1 – Shopping List Application

LARAVEL Multi-user shopping list application

At the start of July 2017, I started a 12-month work placement as a web developer. The placement is with Two Superior Studios Ltd, a small studio based at Plymouth Science Park. Two Superior primarily work with the Laravel PHP framework. Prior to this placement, my PHP skills were a little rusty, and I’d not even heard of Laravel nor used an MVC framework.

It’s now October. Having worked on a number of client projects and got my feet wet, I decided it was time for me to create my own application. Continue reading “Laravel – My Journey – Part 1 – Shopping List Application”

DAT 504 – Assignment – Time Bank Web Application

The Brief: Time Bank Web Application

Your team has been contracted to produce an interactive PHP web application, for a newly set up Time Bank.

Key timebanking principles are:

  • People list the skills and experience which they can offer and those that they may need.
  • Everyone’s skills are valued equally – one hour always equals one time credit.
  • Everyone agrees to both give and to receive help, to earn and to spend their time credits.
  • A record is kept of all the time credits earned and spent.
  • Everyone is encouraged to spend their time credits to allow others the chance to make a difference and feel needed.

Continue reading “DAT 504 – Assignment – Time Bank Web Application”