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


Surprising, 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”

DAT501 – t3X: 3D Interactive Twitter Visualisation

Twitter visualisation
The Brief

You are asked to create and present an artwork or performance in public exhibition. Your project should explore a creative use of technology, be it digital, mechanical, biological or not yet invented. It should be a response to work and ideas which you have encountered during the module either in the presentation sessions, on the field trip, or in your own research. Continue reading “DAT501 – t3X: 3D Interactive Twitter Visualisation”

DAT503 – Urban API – Plymouth Bomb Sight

The Brief

Urban API is a live project. The project will generate an open real-time intervention or map of the city. The project should map or challenge the city as complex cultural, political and social phenomenon or the project should hack the city in its functions as a whole or aspects of it.

The Project has TWO components:

  1. Methodologies: A series of research, design and production methods will be presented along with practical mini projects to help students build an appropriate set of methodological design and research tools to complete the overall project. As part of this process, some key practical skills will be introduced such as hacking the Open Data and Google Maps API and Unity 3D.
  2. Planning: Following the introduction, students will be tasked to identify a site (used in the broadest sense) that will be the focus of their project.

Continue reading “DAT503 – Urban API – Plymouth Bomb Sight”

DAT501 – Creative Strategies: Process

Artists often start work without a clear idea of where they are going to end up. They react to what they have already made to expand their work, and they continue until it is finished. This methodology has a focus on the process.

The opposite, where you define where you want to be and then figure out how to get there, has a focus on the goal. This approach is more common in engineering. Continue reading “DAT501 – Creative Strategies: Process”