<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Super Summit &#187; WordPress</title>
	<atom:link href="/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>https://supersummit.co</link>
	<description>Online Events that are Free to Watch Live</description>
	<lastBuildDate>Tue, 08 Jul 2014 11:02:55 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.1</generator>
	<item>
		<title>2012: How to Optimize, Secure and Speed up your WordPress, with Jason Cohen (WPEngine)</title>
		<link>https://supersummit.co/video-archive/wordpress-jason-cohen-wpengine/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-jason-cohen-wpengine</link>
		<comments>https://supersummit.co/video-archive/wordpress-jason-cohen-wpengine/#comments</comments>
		<pubDate>Mon, 12 Nov 2012 15:20:06 +0000</pubDate>
		<dc:creator><![CDATA[supersummit]]></dc:creator>
				<category><![CDATA[Video Archive]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[google authenticator]]></category>
		<category><![CDATA[jason cohen]]></category>
		<category><![CDATA[Mullenweg matt]]></category>
		<category><![CDATA[WordPress (Software)]]></category>
		<category><![CDATA[wordpress hosting]]></category>
		<category><![CDATA[wordpress managed hosting]]></category>
		<category><![CDATA[wpengine]]></category>

		<guid isPermaLink="false">http://www.techalchemist.com/?p=74</guid>
		<description><![CDATA[Do you use WordPress (yes you&#8217;re in good company&#8230;57,337,325 sites use WordPress in the world!)? But how to secure, optimize and speed up your wordpress? Just watch this interview with Jason Cohen cofounder and CEO of WPEngine ;) About Jason Jason is the founder of four companies including Smart Bear and currently WPEngine. He took Smart Bear from]]></description>
				<content:encoded><![CDATA[<p><iframe src="//www.youtube.com/embed/Sk9NSVWINus" height="360" width="640" allowfullscreen="" frameborder="0"></iframe></p>
<p>Do you use WordPress (yes you&#8217;re in good company&#8230;<a href="http://en.wordpress.com/stats/">57,337,325</a> sites use WordPress in the world!)?</p>
<p>But how to secure, optimize and speed up your wordpress?</p>
<p>Just watch this interview with Jason Cohen cofounder and CEO of <a href="http://wpengine.com/">WPEngine</a> ;)<br />
<strong><br />
About Jason</strong></p>
<p>Jason is the founder of four companies including <a href="http://smartbear.com/" target="_blank">Smart Bear</a> and currently <a href="http://wpengine.com/?a_aid=asmartbear" target="_blank">WPEngine</a>.</p>
<p>He took Smart Bear from start to multiple millions in profit, without debt or VC, then <a href="http://blog.asmartbear.com/rich-vs-king-sold-company.html">sold it</a> for cash.</p>
<p>Jason is also a mentor at <a href="http://capitalfactory.com/" target="_blank">Capital Factory</a> (like TechStars or Y-Combinator in Austin) and investor in a few companies.</p>
<p>He is the author of <a href="http://codereviewbook.com/" target="_blank">Best Kept Secrets of Peer Code Review</a>, the most popular book (50,000 copies) on modern, lightweight methods for doing peer code review effectively without everyone hating life. He&#8217;s also the co-host of <a title="Ask questions about startups; get answers from the world, including me!" href="http://answers.onstartups.com/" target="_blank">OnStartups Answers</a> along with Dharmesh Shah.</p>
<p>Jason lives in Austin, Texas with his wonderful wife, a chef and entrepreneur who blogs about <a href="http://dailyfillblog.com/" target="_blank">cooking healthy at home</a>, and his precious baby daughter Abigail.<span id="more-1430"></span></p>
<p><strong>Raw transcription:</strong></p>
<p>Marco: Hello everyone Marco Montemagno the Tech Alchemist and here<br />
with me today is Jason Cohen, co-founder and CEO of WPEngine. Hi, Jason.<br />
How are you doing?</p>
<p>Jason: Hey, thanks for having me.</p>
<p>Marco: All right, Jason. The reason why I wanted you on my show is<br />
first I am a customer a WPEngine customer. This is always embarrassing on<br />
one side, but very good, because you talk exactly of something you try and<br />
test every day.</p>
<p>The topic generally is a very interesting topic. I have tons of people<br />
asking about tapes and advice about Word Press and where to explore Word<br />
Press, security and all of the problems around. In my experience, who<br />
better than you could help us understand more.</p>
<p>Could you imagine if I was a totally unhappy customer and this was a trap<br />
to talk badly about WPEngine? It would be genius. It would be a mess, but<br />
no. I think the main problem here for me, I am running digital stuff for I<br />
don&#8217;t know 15 years and for the last 10 years doing stuff on Word Press.</p>
<p>The big pain that WPEngine came to solve, or WPEngine allowed companies, is<br />
to give managed hosting where I don&#8217;t have to think about upgrading<br />
security and this kind of stuff. I think this is a good asset. Can you for<br />
first explain in your words, what WPEngine does and why you are different<br />
from any other hosting companies?</p>
<p>Jason: Sure. We host Word Press which means if you have a Word Press<br />
blog, of course if a browser goes to your site, it has to go somewhere. We<br />
run the servers that that browser is in fact connecting to.</p>
<p>What makes us different is that we are more expensive than Dream Host and<br />
Blue Host. It does cost more, yes. What do you get for that? First of all,<br />
the blogs go a lot faster. On average our customers see a four-times speed<br />
improvement.</p>
<p>Second, it scales under traffic. If you get some nice press your blog won&#8217;t<br />
go down.</p>
<p>Number three we handle security and if in fact you are ever hacked, we will<br />
fix it for free as a part of our normal tech support.</p>
<p>The fourth and probably most interesting one is that we have more tech<br />
support members who know Word Press on staff than anyone else per thousand<br />
customers which means we actually have the time and human beings to help<br />
you with Word Press specific questions even down to things like which plug-<br />
ins should I use for this and that sort of thing.</p>
<p>Our service by investing in human beings for our service our service can be<br />
both really responsive but also deep. We have the time to get on the phone<br />
with you. You get your monies worth.</p>
<p>Marco: Automattic, the founding company of Word Press, did they invest<br />
also in WPEngine or I&#8217;m wrong?</p>
<p>Jason: They did and last year when we raised some money Automattic was<br />
an investor in that round. You have to be careful, Automattic works with<br />
lots of hosting companies. You shouldn&#8217;t read into that that we are favored<br />
or read into any other hosting company as a result. That would be not true,<br />
but certainly it is a vote of confidence in what we are doing, how we are<br />
doing it, and whether it is something that they approve of or like or sort<br />
of correct for Word Press. Obviously, it is a nod from them.</p>
<p>Marco: The Speed promise that WPEngine was doing, I was very<br />
fascinated about. Also, checking around, I saw your fabulous t-shirt you<br />
got written, &#8220;My blog is 4x faster than your blog&#8221;, so, I thought this guy<br />
is very arrogant or he knows his stuff, you know. Let&#8217;s try to test.</p>
<p>The first question that I have for you is how about speed. How can you<br />
promise and deliver, because then you do it to make a Word Press site<br />
faster, because people and businesses are used with tons of cache plug-ins<br />
or cloud flare or this kind of services cache CDN and this kind of stuff.<br />
How can you handle this part of the hosting?</p>
<p>Jason: Sure. There are many aspects to making a site fast or scale or<br />
secure. In the same way that you ask, how do you make a car fast? The<br />
engine is important, but obviously it is not the only thing. Spark plugs<br />
can be important. The size of the engine is important. The gas that you put<br />
in is important. The oxygen mixture of the carburetor is important and so<br />
forth, right? If you put a super charger that&#8217;s important.</p>
<p>Like that, it is not one thing. Everything from having superior hardware,<br />
having those hardware resources dedicated to your site and not shared with<br />
let&#8217;s say a thousand other blogs. Then having systems around your blogs to<br />
cache pages and so on. You mentioned cloud flare.</p>
<p>Cloud flare for example caches static content, meaning things you&#8217;re your<br />
images and CSS, but it does not cache pages like your homepage or a<br />
particular other page or a post. Those are the things that are actually<br />
typically the slow thing and the thing that doesn&#8217;t scale. The other stuff<br />
is usually not the problem.</p>
<p>Though it does make it incrementally faster for the other stuff, it doesn&#8217;t<br />
address the hard part which is dynamic stuff. There is also the database.<br />
In the same way that there is many, many pieces that go together,<br />
sometimes, it&#8217;s just in plug-ins that we say you should not use because we<br />
know that those plug-ins slow your site down and we have alternatives for<br />
those.</p>
<p>There are many ways. What is interesting is again, I hate for this to just<br />
turn into an ad for WPEngine, so maybe a story about speed which is not so<br />
obvious but kind of fun.</p>
<p>We had a customer move to us and got instantly a 20% increase in revenue,<br />
because he got a 20% increase in page views. He got that because people<br />
stopped bouncing off the site as much or by 20%. Bouncing meaning, the<br />
browser came to the site and then left.</p>
<p>Here is the interesting part, those statistics were not in Google<br />
Analytics. This is why and this is the neat part. This is true of any<br />
website anywhere so it&#8217;s kind of fun. You know, when you click a link in<br />
Google search results, there&#8217;s a white page and it&#8217;s spinning and you get<br />
tired of waiting and you hit back, right?</p>
<p>Obviously, you just bounced off the page. Obviously, that was a potential<br />
page view that did not happen, right? But, here&#8217;s what&#8217;s interesting,<br />
because the page didn&#8217;t load, Google Analytics didn&#8217;t load either. Which<br />
means Google Analytics, or any tool that you might use won&#8217;t know that that<br />
happened. That is a bounce rate that is invisible to tools, sort of by<br />
nature.</p>
<p>When your page goes faster you get those kinds of bounces less, because the<br />
pages does appear, so you do get it and even if they do run [it] right<br />
away, at least you know it, right? It&#8217;s in a bounce rate you can see in<br />
your tools. Of course, in general, this is common knowledge with all of the<br />
studies that are out there, people tend not to bounce off of sites as much<br />
when they are fast.</p>
<p>What&#8217;s interesting is that you can&#8217;t measure how many people are doing that<br />
sort of by its nature. All you can do is make the site a lot faster and<br />
see. That&#8217;s what happened exactly to this customer that I am referring to.<br />
It&#8217;s an interesting effect that sometimes these things are hard to<br />
quantify. There are things people know, like, faster sites get higher<br />
search rank position.</p>
<p>Or, in general, people will stick around sites that are more responsive<br />
stands to reason as well, besides the fact that there are studies. But<br />
there are even, like, little holes like that which I think are also very<br />
interesting.</p>
<p>You ask, &#8220;How can we guarantee what will happen?&#8221; Well, we don&#8217;t. All we<br />
know is there is some effect and it is what it is and it will depend on the<br />
site and lots of things. We don&#8217;t. We just do many, many things to make the<br />
site fast and those other things. More things than you&#8217;re going to do by<br />
yourself just because who has the time? Even if you are technical, it&#8217;s<br />
interesting, but who has the time?</p>
<p>Marco: What is the best tip that you can give to business owner that<br />
OK, has to take a decision and is maybe not hosting on WPEngine or similar<br />
web services? What is the most important thing? Just go on those kind of<br />
plug-ins with cache and CDN and so on or any tip that you could give<br />
specifically?</p>
<p>Jason: Make sure you have a caching plug-in like W3 Total Cache or WP<br />
Super Cache, something like that because it will cache the dynamic content<br />
and that is the slowest part, number one.</p>
<p>Number two, there are very inexpensive CDNs like Max CDNs or Cloud Flare<br />
which is free. I highly recommend that you go use Cloud Flare. It will<br />
cache a whole lot of stuff for you and there are a lot of other controls<br />
and its basic version is free. That also affords you some security. Which<br />
is also very good so no reason not to get Cloud Flare.</p>
<p>Number three, you can use something from Yahoo called &#8216;Yahoo Smush It&#8217;. It<br />
is a free tool that will make your images smaller without making the<br />
quality less. We can go into why if you want to, but that&#8217;s what it does.<br />
It gives it back to you in a format that&#8217;s very easy to then upload again<br />
to your website so, that&#8217;s permanent.</p>
<p>You only have to do that once every time you change your theme, so no<br />
reason not to do that, again, it&#8217;s free.</p>
<p>Another thing to do that is free, is to use a tool either like W3 Total<br />
Cache or a plug-in like WP Minify and these are plug-ins which take all of<br />
your style sheets and Java scripts so that means the stuff ending in .CSS<br />
and stuff ending in JS and they combine them into one.</p>
<p>One style sheet instead of ten. One Java script file instead of four. Also,<br />
it makes them smaller. Both of those actions, I could go into detail if you<br />
want, but both of those things make your site download much faster and that<br />
cache plug-in, W3 Cache plug-in, and again, it&#8217;s free. Again, there is no<br />
reason not to do it.</p>
<p>Those are three things that you could do on any hosting provider that will<br />
make Word Press faster. The final thing I will say about that is there is<br />
an online tool called WebPageTest.org, also free, where you can put in your<br />
blog URL or really, any URL and get a very detailed analysis of what is<br />
fast or slow.</p>
<p>If you do that first, then do some of the things I said, you will literally<br />
see the difference. Also that tool may be able to help point out other<br />
things that you may be able to do to increase speed.</p>
<p>Marco: Right. A few years ago, I launched a web network in Italy and<br />
finally did 3.5 million visitors a month. The funny thing is the biggest,<br />
biggest problem, it was before the cloud, so one of the biggest problem was<br />
going down. Every time that there was a peak of traffic everyone happy on<br />
one side and one the other side every one very sad, because you know you<br />
have to pay for additional service and so on.</p>
<p>Now, with cloud it is different. But, still, a website going down is<br />
something that happens often. By the way, I think also, the right moment<br />
when I migrated my website, the WPEngine went down. I say, gosh I just<br />
changed providers, but it was just 10 minutes, something like that.</p>
<p>What can you suggest on this topic? Do you think it is related with<br />
caching? If you cache good&#8230;</p>
<p>Jason: No.</p>
<p>Marco: &#8230;then if the site goes down you still have the cache in place<br />
or is it something else?</p>
<p>Jason: Uptime in data centers is rough. There is literally no hosting<br />
provider that I know of and no WordPress provider that I know that has 100%<br />
uptime in the last 12 months, not one. It&#8217;s hard.</p>
<p>When Amazon has their big data center failure at Virgina as they&#8217;ve had a<br />
couple of times in the last couple of years, all kind of services that you<br />
use just go down. You say, &#8220;Wait a minute, I thought it was cloud. I<br />
thought it was high availability. I thought they had backups. I thought<br />
they were redundant in various ways&#8221;, whatever.</p>
<p>Yet, all of these various players that invest countless dollars in<br />
infrastructure on things like Amazon and Cloud and all that sort of stuff<br />
fail anyway. It&#8217;s, very unfortunately, life in hosting is that it&#8217;s not<br />
perfect.</p>
<p>Now that doesn&#8217;t mean that you throw your hands up and say, &#8220;There is<br />
nothing we can do about anything&#8221;. Not true of course. There are many<br />
things. One thing it does point out that is interesting is it&#8217;s very, very<br />
expensive to get high uptime. Even multiple servers isn&#8217;t enough, because<br />
if they are all in one data center, the data center can have problems. Like<br />
for example, I don&#8217;t know, a hurricane hitting the West Coast and taking<br />
out your data center on the West Coast, which happened to a couple of data<br />
centers, right. This happens.</p>
<p>You have to have multiple data centers. That&#8217;s tricky, because keeping your<br />
data synchronized between them is a project. It&#8217;s hard enough that, again,<br />
a lot of those tech savvy companies that have one application that they<br />
have to keep running are unable to do it or there&#8217;s trouble. When you are<br />
able to do it, it&#8217;s very expensive, because you need multiple servers in<br />
one data center to survive single server issues.</p>
<p>Then you need multiple data centers, so you need servers everywhere, all<br />
dedicated for you. You have to test that stuff. It is very complicated.<br />
Honestly, for almost anyone, it&#8217;s not worth it. It&#8217;s a horrible thing to<br />
say, because you hate to say, &#8220;Tough&#8221;. The truth is you pay for what is<br />
necessary to get that. It is not the right cost benefit trade-off for most<br />
people.</p>
<p>Services like us or indeed our competitors, any of us, we have a lot of<br />
measures in place for high availability, there are still going to be some<br />
events. Fortunately, we did not go down with that storm even though we do<br />
have hundreds of servers in Newark. We do have some high availability stuff<br />
and so we did survive that.</p>
<p>There are other things, especially in our past when we were less<br />
sophisticated, a couple of years ago where a data center failure did take<br />
us down for a little while. Now we are more sophisticated, but even so, I<br />
can still devise a scenario where we are going to go down, right?</p>
<p>Where there are lots of service providers. The other day GoDaddy&#8217;s DNS went<br />
down famously. A ton of sites went down. Our phones rang off the hook, &#8220;How<br />
come our site is down?&#8221; Of course we weren&#8217;t down, but their DNS provider<br />
GoDaddy was down. So, their site was down.</p>
<p>There is a chain of service providers actually, that all have to be working<br />
for your site to go down. So, failures anywhere in there will take your<br />
site down. It happens, again, very expensive, in fact too expensive for<br />
almost anyone to try to get, to design for 100% uptime.</p>
<p>Marco: Jason, do you think that this scenario will change sooner or<br />
later as technology progresses around? Because as you say and I totally<br />
agree, there are so many players in the chain and you can be great but the<br />
DNS goes down or the DNS can be OK but the hurricane is coming so it is so<br />
difficult to get everything together.</p>
<p>Do you think it will improve the situation or it will stay like this<br />
forever and ever?</p>
<p>Jason: It will definitely improve. It has already improved. Cloud does<br />
improve things. You can have a failure in a single piece of hardware and<br />
not go down, because your thing can float over to another piece of<br />
hardware. You could have built that 10 years ago and it would have been<br />
much more expensive. Now, it costs money, but it is much cheaper and much,<br />
more accessible.</p>
<p>In the same way, that all of this stuff will become easier and more<br />
accessible and less expensive. At the end of the day, high availability<br />
means redundancy. It means there are multiple things that know how to do<br />
this and are doing this at all times, that&#8217;s what it means. There&#8217;s always<br />
some expense for having resources allocated for you in multiple places.<br />
That&#8217;s always going to be more expensive than not having those resources.</p>
<p>I think that the extra cost will come down, the difficulty of setting it<br />
up, will come down. I do believe that it will be less expensive over time<br />
to do that. In fact, there&#8217;s even an offering that we are working on right<br />
now that will provide something like that very thing but in a way that is<br />
more affordable. We are going to try to do that. Even so, in 10 years, it<br />
will be a whole different story just like cloud is, but cloud doesn&#8217;t<br />
automatically mean you go down. That is certainly not true as you can see<br />
by things going down.</p>
<p>Marco: Jason, security, this is another hot topic, because on the one<br />
side you are worried that the web site goes down, on the other side you are<br />
worried about being attacked somehow. The two fears are what can I do with<br />
my security? My password, my long password, this kind of stuff and what<br />
does my provider do with security? Could you elaborate on that? I think<br />
that there is a lot of confusion when we talk about security and Word<br />
Press.</p>
<p>Jason: There is a lot of confusion with security and Word Press. I<br />
think it is accurate to say that almost none of the security issues that<br />
people have, almost none of the hacks that people have are due to Word<br />
Press itself or the hosting provider. I include all of my competitors in<br />
that. In other words, it&#8217;s very, very rare for one of my competitors for a<br />
security vulnerability on their side to be the cause of an attacker<br />
succeeding.</p>
<p>That is the same if you look at Word Press itself. There is of course a<br />
third-party organization whose job it is to track security problems and fix<br />
this. If you look at Word Press, you can see that there is almost none.<br />
That is almost never the problem. Even the very, very few things that they<br />
find, the attacker wasn&#8217;t successful in doing it. They patched it<br />
themselves before anyone else had even found it.</p>
<p>In short, Word Press is about as ironclad as you can have for any web<br />
application. In general the service providers don&#8217;t have problems. Again,<br />
you can always pull out &#8220;Well, one time this happened with this one&#8221;. Yes,<br />
one time, but people get hacked constantly all day long. If there was one<br />
problem one time somewhere that obviously is not the main problem here.</p>
<p>Marco: The problem is the user in the end.</p>
<p>Jason: Well, sometimes it is the user. Word Press, remember, you can<br />
install any theme and any plug-in. Well, that means that you can run any<br />
code. That means all kinds of problems happen as soon as you say, I can run<br />
anything. Well, OK. Guess what, then they are all potential security<br />
vulnerabilities. Just like speed there is a myriad of things with<br />
passwords that happen.</p>
<p>Here&#8217;s the biggest mistake that people have about security, they say every<br />
day, &#8220;I won&#8217;t get hacked, because I have a little site where I sell lawn<br />
gnomes and nobody wants to hack a site that sells lawn gnomes&#8221;, because who<br />
cares. They are absolutely wrong. Those are exactly the sites that get<br />
hacked. Not because they care about lawn gnomes, it&#8217;s because the hackers<br />
want to do something else like send spam email or use your server to then<br />
do something else to another machine but mask their identity, because it<br />
comes from your machine.</p>
<p>In other words, the hackers have some other aim. They want to hack your<br />
site in order to do that other thing that they really want to do. They<br />
don&#8217;t care who you are. They just want to hack you so they can use you to<br />
do stuff like a puppet. Everyone is vulnerable and people get scammed<br />
constantly for these things, because hackers will literally write code that<br />
runs around the internet looking for sites they can do this to. They don&#8217;t<br />
know either who you are. They don&#8217;t care.</p>
<p>Marco: Do you agree, Jason, to give a practical tip, I&#8217;m thinking of<br />
the most common way of hacking may be to get good passwords, changing<br />
passwords, limit login at times, there is a plug in. By the way, I think<br />
WPEngine has got it by default so that when somebody tries to look in your<br />
WP admin dashboard after three logins or whatever that IP is blocked.</p>
<p>Is there anything else that somebody can do by themselves?</p>
<p>Jason: Yeah. There are a few things. Again, I would use Cloud Flare.<br />
They do have a layer of security. We do have customers with Cloud Flare<br />
that get hacked, but security is something where every little bit that you<br />
do does help. If you use Cloud Flare some number of attacks will be blocked<br />
not 100%, but whatever they are it&#8217;s a number. Who cares, it&#8217;s free. Do it,<br />
right?</p>
<p>Number two, use the fewest number of plug-ins possible. Use themes and plug-<br />
ins that are generally well worn. Just because they are used a lot doesn&#8217;t<br />
necessarily mean that they are safe. There have been some famous examples<br />
like admin and a tool called &#8216;Tim Thumb&#8217; which were vulnerable. However,<br />
the ones that are often used when they are vulnerable, it&#8217;s big news.<br />
There&#8217;s often a patch out quickly.</p>
<p>In other words, you&#8217;ll find out and you&#8217;ll be able to fix it. Ones that are<br />
not used, if they are vulnerable, you&#8217;ll never know, all right? Using well<br />
worn code and as little of it as possible. The same goes with themes.<br />
Themes that are used by a lot of people, same thing. That is maybe the<br />
number one thing that you can do to be safe.</p>
<p>I would suggest something that you talked about, it&#8217;s called &#8216;Login Lock<br />
Down&#8217;. That&#8217;s a plug in. It&#8217;s free. If you see someone attempting to log in<br />
a number of times unsuccessfully, it locks them out for a little while.<br />
That prevents people who are trying to guess your user name or password.<br />
So, that&#8217;s nice. Again, that&#8217;s just one little thing. One little piece of<br />
your armor, right, but every little bit helps.</p>
<p>I would say finally on passwords changing the passwords is probably not all<br />
that important, because that assumes that someone is getting your password<br />
and knowing it and again they are not targeting you that specifically they<br />
are trolling around, so just having a really good password that is long and<br />
has some punctuation in it and stuff, that&#8217;s better.</p>
<p>If you are really paranoid, use two-factor authentication. For example,<br />
there is a free plug-in from Google where to login to your Word Press blog,<br />
you type in a password but then Google sends a number to your cell phone,<br />
it texts you and you type it in. That&#8217;s something that of course a hacker<br />
would have to be pretty amazing to get. That kind of thing you can use.</p>
<p>One more thing that is important, when you log into Word Press it is<br />
insecure. That is, when you go to your login page it is http://, not https:<br />
like when you go to your bank and so on. It is not secure. That means when<br />
you type your name and password, when you are in a coffee shop, everyone<br />
who is in the coffee shop who wants to, just got your name and password.<br />
Now, again that is a hacker who is sniffing around a little bit more than<br />
what I was describing earlier, but that absolutely happens.</p>
<p>Number one, two-factor authentications, fixes that. Number two use a<br />
hosting provider in which that is secure like WordPress.com. We have that<br />
option. A couple of our competitors do too though. It is not completely<br />
unique. You are sending your password over completely unencrypted unless<br />
that is not the case.</p>
<p>Marco: That is super interesting. By the way, I am a fan of double<br />
authentication, Google I have been using it for a while I am super happy<br />
with that. I didn&#8217;t know that there was a plug-in for Word Press, so I will<br />
install it. When we finish, I will just install it. How about FTP hacking<br />
for security, something to be worried about or not?</p>
<p>Jason: Again, strong passwords.</p>
<p>Marco: Can you imagine that when I launched my [Web Works] network,<br />
I&#8217;ve been choosing movable type, because the Word Press community was not<br />
there yet. I thought, &#8220;Well, not so much&#8221;. I think now, wow, there are so<br />
many things. How about themes and designs? There is such a large choice, a<br />
lot of times people start to change design and theme and then use a<br />
framework and then us another theme. It&#8217;s a very chaotic situation. Do you<br />
have any guidelines for themes and designs to do a good job?</p>
<p>Jason: Not really, in that there are a lot of really good players with<br />
quality themes and support behind it as you say, frameworks with trial<br />
themes. I would say if you&#8217;re developing a single blog you have a large<br />
range of choices for what you can pick. I would say pick a theme where<br />
there are people you know who have experience there so you can ask<br />
questions of is probably the best thing, because there&#8217;s lots of different<br />
choices.</p>
<p>If you are a designer and you are making lots of Word Press blogs and this<br />
is your career, then you could learn a lot of different themes, but that is<br />
probably not the best use of your time. As the designer of the blog you get<br />
to pick more or less what the theme of the framework is, so it&#8217;s probably<br />
best that you specialize in a couple or even in one framework and go super<br />
deep in that framework.</p>
<p>So you become really competent in delivering sites quickly, especially for<br />
the more simpler common stuff and also for a facility for yourself of more<br />
complicated features. Some of these frameworks like Woo with Canvas,<br />
Genesis, Thesis, and all these things. They are a whole thing unto<br />
themselves. You can almost think of them as application or products in<br />
themselves. They have tons of hooks. They have their own way of doing<br />
things. You make child themes. There are plug-ins that work with them.</p>
<p>It&#8217;s a whole ecosystem within itself, each one is a little one. I think it<br />
makes sense to specialize in one or two of those. A couple of these have<br />
very large followings with lots of design and stuff behind them. Learning<br />
that, probably allows you to generate websites faster and deeper rather<br />
than just pulling random themes off the shelf and having to get inside that<br />
theme author&#8217;s head each time. It&#8217;s probably best to specialize if that&#8217;s<br />
your career.</p>
<p>Marco: I&#8217;ve be using Genesis and Thesis. I&#8217;m a big fan of framework,<br />
because as you said, I think there is more stability and support and so on.<br />
What would happen in the next year for Word Press? We recently watched Matt<br />
talking, the founder of Word Press talking about how amazing Word Press is<br />
going to be more and more. What are you expecting? What would happen from a<br />
technical point of view? In one year, big changes, more or less the same?<br />
Is there any particular thing that would be a game changer for Word Press?</p>
<p>Jason: I think you would have to ask the people at Automattic who are<br />
literally making those decisions. Some trends that we are seeing, number<br />
one, you could say that Word Press is getting some what you could say, some<br />
software maturity. That is there are things like unit tests and<br />
documentation and things like that which in the regular software<br />
development world back into Java and .net and stuff, are part of what you<br />
might call a software maturity process. That is sort of being back filled<br />
into Word Press now which I think is very good.</p>
<p>I think you will see that being pushed into plug-in theme developers to<br />
participate in that. That will help with things like Word press upgrades<br />
where currently that can break lots of things and vice verse. That&#8217;s a<br />
whole thing and with more process around that especially automated testing<br />
and continuous integration and stuff like that, hopefully, you will see<br />
improvements there.</p>
<p>There&#8217;s this goal of having Word Press automatically upgrade continuously<br />
like Chrome. I feel like that is a very good thing to do, upgrades. ON the<br />
one hand we want upgrades, on the other they are events every time for<br />
everyone. Again, as part of the [type] process means that you can start<br />
doing that as well. I think that is a terrific goal.</p>
<p>It will help Word Press grow in whatever way it wants to grow because it<br />
will grow more easily being more continuous development and deployment.<br />
That will enable Word Press itself to succeed in whichever way it wishes. I<br />
think you will see more applications built on Word Press. In the old days<br />
Word Press was &#8220;blogging software&#8221;, now, Word Press is websites or CMS.<br />
It&#8217;s just anything. We see the same thing. I might actually say the<br />
minority of our customers is just their blog.</p>
<p>It is their website whatever that means, the company website, the marketing<br />
website and so on. That will not only continue, but I think it will move<br />
into the realm where it is also a shopping cart. It&#8217;s got more dynamic<br />
functionality.</p>
<p>Applications which are currently built on Ruby on Rails, more and more<br />
might be built on top of Word Press, because after all it&#8217;s got that CMS<br />
stuff built in and so theming it is so much easier and having non-technical<br />
people being able to edit text and behavior is so much easier.<br />
It is kind of a logical place for certain types applications to go to. I<br />
think you&#8217;ll be able to see it move into application.</p>
<p>Another trend that I think you will see is more enterprise level features.<br />
Some of which means things like, performance and scale on internal stuff<br />
which would matter if you had 100,000 posts or 100,000 users and wouldn&#8217;t<br />
matter if you were smaller than that. Some of that is internal. I think you<br />
will see some external features as well.</p>
<p>Most of the stuff that I am saying is speculation, because Automatic and<br />
the Foundation of course together are the ones that in fact drive that<br />
stuff. I am going kind of off what we are seeing, kind of off what they&#8217;ve<br />
said, kind of what Matt said in the last &#8216;State of the Word&#8217;, is what his<br />
goals were. I think that they are more or less in line with what has been<br />
publicly stated as the direction of Word Press and we&#8217;ll see.</p>
<p>Marco: Excellent. Jason Cohen. Thank you so much. WPEngine, co-founder<br />
is here. Jason, good luck for everything and keep in touch.</p>
<p>Jason: Thanks for having me.</p>
]]></content:encoded>
			<wfw:commentRss>https://supersummit.co/video-archive/wordpress-jason-cohen-wpengine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
