Michael Sebel: The “Adopt a WordPress Made By Someone Else” Checklist

Continue the discussion

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Published

May 14, 2016

In our first year at comotive we’ve had a few experiences, where a company asked us to support and further develop their WordPress sites. But those weren’t small pages, but rather old and extensive sites and in one case (What I’ll talk about the most), a page of the swiss government, which was a very severe case. I’ve already learned a lot at blogwerk in the last four years and will talk about the caveats when you take over support for code that you didn’t write yourself. A soap opera in four acts: Slowness. Bugs. Support. Security.

Presentation Slides »

Rate this:

Event

WordCamp Switzerland 2015 10

Speakers

Michael Sebel 2

Tags

code 42
Support 45

Language

English 4028

Download
MP4: Low, Med, High
OGG: Low
Subtitles
Subtitle this video →
Producer
%d bloggers like this: