<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bryan Quigley (Posts about converting)</title><link>https://bryanquigley.com/</link><description></description><atom:link href="https://bryanquigley.com/categories/cat_converting.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2026 Bryan Quigley 
&lt;a rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/"&gt;&lt;img alt="Creative Commons License" style="border-width:0" src="/licensebuttons/CC80x15.png" /&gt;&lt;/a&gt;</copyright><lastBuildDate>Fri, 28 Aug 2026 00:16:30 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Now powered by GitLab, Nikola, and Cloudlfare</title><link>https://bryanquigley.com/posts/converting/now-powered-by-gitlab-nikola-and-cloudflare.html</link><dc:creator>Bryan Quigley</dc:creator><description>&lt;p&gt;I just finished moving my website from Wordpress to Nikola (static site generator), GitLab (git and hosting), and CloudFlare (CDN, HTTPS and more).&lt;/p&gt;
&lt;h2&gt;Why Nikola&lt;/h2&gt;
&lt;p&gt;Their attitude in the handbook is "DON'T READ THIS MANUAL. IF YOU NEED TO READ IT I FAILED, JUST USE THE THING." 
That's my kind of software methodology. Don't blame the user, make the system better.&lt;/p&gt;
&lt;p&gt;It is also a great &lt;a href="https://getnikola.com/handbook.html"&gt;handbook&lt;/a&gt; that has had pretty much every question I've asked. Documentation is still essential, but it's nice if the commands are self explanatory.&lt;/p&gt;
&lt;p&gt;It just worked to import my Wordpress site (minus comments which I "inlined" or deleted for various reasons). I did do some manual HTML to markdown conversion for pages I want to edit more.&lt;/p&gt;
&lt;h2&gt;Why GitLab&lt;/h2&gt;
&lt;p&gt;I first tried and had Nikola working with GitHub, but &lt;a href="https://about.gitlab.com/"&gt;GitLab&lt;/a&gt; gives me:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Automatic building - I don't have to have a separate branch for output, I just git push my changes (or change on the website) - and GitLab will run a job to create my website. I know this is possible on GitHub, but GitLab just makes it easy.&lt;/li&gt;
&lt;li&gt;The option to upload SSL Certs. If I need to drop CloudFlare for some reason, I can have GitLab maintain my website using HTTPS (Which I need to because I'm on the HSTS preload list).&lt;/li&gt;
&lt;li&gt;Easier drive by contributions. GitLab lets you sign in with Google, Twitter, GitHub, or BitBucket. I'm thinking for suggesting changes to say a paper (or even this blog post!), that will make for a lower barrier to entry.  (Of course, I'd prefer any OpenID but it's better than requiring a new account)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I absolutely love that they have their &lt;a href="https://about.gitlab.com/handbook/"&gt;&lt;em&gt;company&lt;/em&gt; handbook&lt;/a&gt; maintained in Git and public to the world (with merge request welcome!).&lt;/p&gt;
&lt;h2&gt;Why CloudFlare&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://www.cloudflare.com"&gt;CloudFlare&lt;/a&gt;'s free plan rocks. And if I ever need to be able to handle more traffic faster, I can upgrade/downgrade as necessary.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Free (Good) SSL with TLS1.3 Beta too&lt;/li&gt;
&lt;li&gt;Free IPv6&lt;/li&gt;
&lt;li&gt;Free HTTP2&lt;/li&gt;
&lt;/ul&gt;</description><category>Converting</category><category>security</category><guid>https://bryanquigley.com/posts/converting/now-powered-by-gitlab-nikola-and-cloudflare.html</guid><pubDate>Wed, 15 Nov 2017 03:00:19 GMT</pubDate></item></channel></rss>