Tech

Best practice says we shouldn’t be committing vendor, core or contrib projects to a repo, (see https://getcomposer.org/doc/faqs/should-i-commit-the-dependencies-in-my-...)

As a result I have had to go through the process of removing the files on several sites.
This can be done by running:

I did a little exploration into Event dispatchers and Event subscribers for Drupal 8 and found some helpful articles which I am saving here for future reference:

I watched a Webinar recently and while its not in my direct area of interest, it did raise some interesting points
(Webinar availble at: https://magento.com/resources/optimize-your-checkout-with-magento-commerce)

Cart abandonment rate is:
// Bariliance, 2016 and 2015 cart abandonment data
(https://www.barilliance.com/shopping-cart-abandonment-guide/)

When I logged into my EC2 instance, I had the warning:

*** /dev/xvda1 should be checked for errors ***

We can't fsck /dev/xvda1 because it is mounted and in use, so I need to check this disk on startup as it is mounted, however there are a couple of things that need to be done first before you can do this on my Ubuntu EC2 instance.

First I need to enable FSCKFIX, which is off by default

sudo nano /etc/default/rcS

find the line:
#FSCKFIX=no

And change it to:

FSCKFIX=yes

CAVEAT EMPTOR
This is still a very rough start to the D8 setup instructions, more will be added as I progress and full english will be added rather than the rough notes that exist at present.
Also as I am just starting out on this process, this page will be updated as I find modules that are not fully available or as I add functionality.
Please be aware that the D8 Twig version of the Boldy theme is on its way.

I am trying out embedding a pdf on a webpage using google drive previewer.

Basically create an iframe with the src set to "http://docs.google.com/gview?url[insert the url of the pdf]&embedded=true"

<iframe src="http://docs.google.com/gview?url=http://79.170.44.209/craigalmondscouts.co.uk/30th/wp-content/uploads/Scout-Programme-Spring-2015.pdf&#038;embedded=true" style="width:560px; height:790px;" frameborder="0"></iframe>
gives us:

I have been using git merge quite a lot at work as a part of the my workflow, because the powers that be outlined how we should be working prior to deployment, but it means that looking at the history in a graphical tool you get a messy web of branches, so I asked the question
"Should we be using rebase more in our workflow?"

Here are some of the arguments for rebase:

The Case for Git Rebase

I really liked this webinar from Atlassian which contains a special mention of using git with Jira and Jenkins for continuous integration (CI), all of which I use at work, bonus.
http://www.youtube.com/watch?v=9SZ7kSQ2424
Utopia == A seperate build for each branch and automated testing with CI.

I listened to this podcast recently and found the chat about workflows really interesting, especially relevant is the chat about git/jenkins/jira automatically coming together and might be worth looking into:
http://www.lullabot.com/blog/podcasts/workflow-uh-what-it-good

https://www.getpantheon.com/blog/12-tips-get-your-drupal-website-humming-holidays

Its focus is on drupal, but the concepts can be applied elsewhere. It is all standard stuff, but with some QA and load testing links at the end.