Blogeuropean456

1. Netlify Wordpress Gatsby
2. Netlify Headless Wordpress
3. Wp Profit Builder Free

600GB /month (then $20 per 100) Build minutes. The time it takes Netlify to build your site—to run site generators, compile JavaScript, and perform other tasks. 300 minutes /month (then $7 per 500) 1000 minutes /month (then $7 per 500) 1000 minutes /month (then $7 per 500) Websites. Description Easily deploy static sites to Netlify using WordPress as backend. This plugin builds your static website using Netlify webhooks to trigger the deploy process.

TL;DR: I migrated my homepage fromWordPress.com to GitHub Pages for speed and flexibilty,then to Netlify for HTTPS support.

Update (5/1/2018): Github Pages now supports HTTPS for custom domain:https://github.blog/2018-05-01-github-pages-custom-domains-https/ so netlify is not necessary for HTTPS

1. Anyone (to include technical team members) can create a post, edit an existing post, or edit an.
2. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Mauris pulvinar, urna placerat mattis laoreet, quam massa tincidunt felis, sed ullamcorper sem ex a massa.

Table: Comparison of the 3 platforms.

1. From Wordpress.com …

I have been using WordPress.com to host my homepage athttp://dataninja.me for almost a year.It was a good solution for quickly spinning up the site, butI hit the limit as I was planning to put in more professional contents (python and R markdown stuff).Overall, for my use cases, WordPress.com was too:

• slow (heavy overhead),
• ugly (espeically Korean and highlighted codes), and
• inflexible (e.g. cannot change fonts easily; adding custom pages are hard).

2. Moving to Github Pages …

So, I considered GitHub Pages / Jekyll again.Last time when I tried to use it (~3 yrs ago),the static site build process was clunky and it took some work to make the site look pretty.It seems the situation has changed a lot over past couple of years.Now, the default theme (minima)looks OK and the build process is simpler and faster.So, unlike WordPress.com, GitHub page is:

• fast to load,
• pretty by default,
• flexible, and
• free.

I use GitHub and Markdowns,especially, R Markdown,almost daily anyway. So why not??So, I decide to switch back.The process looked like this on OSX.(Replace https://github.com/jaimyoung/jaimyoung.github.io with your own GitHub Pages repo.)

1. Backup the old GitHub Pages repo, if you had one already.
   • (In my case, this meant moving https://github.com/jaimyoung/jaimyoung.github.io to https://github.com/jaimyoung/jaimyoung.github.io-old)

2. Install brew-maintained ruby not to pollute the OSX system ruby(Of course, your OSX must have homebrew installed already):

3. Install Jekyll per Jekyll Quickstart Guide, i.e.

4. Create github page repo https://github.com/jaimyoung/jaimyoung.github.io, and make the jaimyoung.github.io directory to track the github repo:

5. Serve the test site on http://localhost:4000/ by running:

6. Import old WordPress.com contents per WordPress.com to Jekyll import guide.

   1. First you need to install jekyll-import (https://github.com/jekyll/jekyll-import):

      and a couple other dependencies.

   2. Then, export the old WordPress.com contents per direction to some xml file. (In my case, I exported from https://statkwon.wordpress.com/wp-admin/export.php to datasciencefun.wordpress.2017-12-25.xml).

   3. Copy it over the the blog directory and import to the page like:

   4. Browse the imported files (mostly under _pages folder in my case), clean them up as needed, and move them to correct folders or collections.
7. Modify theme files as needed.
   • In my case, I had to overwrite:
     • _includes/head.html : to add font-awesome
     • _includes/header.html : to use custom navigation menu at the top
     • _includes/footer.html : to add linkedin contact as well

   • Find the theme files https://jekyllrb.com/docs/themes/ by running:

     copy the files to your repo, and make necessary changes. See my github repo for the changes I made to above files.

8. Use Jekyll Collections to organize “따라 하며 배우는 데이터 과학” (my Korean data science book) pages under _ipds-kr/ directory.

9. Set up redirect for a few pages, using Redirects on GitHub Pages. In my case, I wanted to move ipds-kr-slides-ppt to ipds-kr/slides-ppt, etc.

10. Set up and add Disqus for comments.

11. Set up and add Google Analytics for site analytics.

12. Transfer dataninja.me custom domain from WordPress.com to GitHub Pages per directions.
    • github help page is a bit unclear; google is your friend here, which gives you a more thorough instructions on specific name provider. For namecheap.com for example, this page was helpful.

3. Then to Netlify…

Now everything almost works.But it turned out that github pages doesn’t support HTTPS for custom domain.This is a huge problem for me since:

1. There already are quite a few https://dataninja.me domain names on the Facebook, LinkedIn, etc.,
2. Chrome browser doesn’t handle https to http change easily,
3. Google search engine indexing values https a lot higher than http sites, and
4. there seems to be no plan to support https for custom domtain in github

Now, Netlify(https://www.netlify.com/) comes to the rescue.It is mentioned in the above github thread,as a great (free) solution that provides HTTPS support for custom domains.I also found it mentioned in some R markdown/bookdown/blogdown sites, so it looked reputable.

The process was pretty simple and took ~10 minutes:

1. Set up netlify account and hook it up to github repo and start building.

   1. Initially, the build failed (of course) but it was easy to troubleshoot thanks to the build logs like this:

      So, that’s a lot more transparent than github (+1).

   2. Thanks to the logs, I could track the build failure to the wrong ruby version. To fix, I added .ruby-version with 2.4.2 per help page and the build succeeded.
   3. Now, the page is up and running at https://${random_words}.netlify.com/.
2. Set up DNS. Netlify provides their own nameservers, so it was pretty simple to follow their directions.
3. Final step is, the original requirement, to get HTTPS working. Again, this was super simple and HTTPS certificate was up and running in a few minutes.

After these, the site is now up and running at https://dataninja.me/.Pretty sweet!

Making Disqus comments working on Netlify

To use Disqus comments, one adds the following line in _config.yml:

This works in github pages, but Netlify version doesn’t activate the comments.It is because minima theme has the following lines

until it activate disqus comments. The environment is set by Github Pages when the site builds,but Netlify doesn’t, hence no Disqus comments.To fix it, per Netlify config directions,set this environment variable in the site deploy setting:

(The URL looks like https://app.netlify.com/sites/pensive-keller-afeae1/settings/deploys#build-environment-variables in my case).

Voilà, now the comments works on Netlify.

Conclusions

I described how I migrated my homepage fromWordPress.com to GitHub Pages for speed and flexibilty,then to Netlify for HTTPS support.

Update in 3/11/18

Netlify Wordpress Gatsby

After notebook migration,my xcode build pipeline broke,which prevents me from installing jekyll =(After 2 hrs of trying to re-install xcode,I concluded it’s not worth it and got lazy(!)and decided to use Docker (of course).Per https://github.com/BretFisher/jekyll-serve,This is all I need:

Lesson: spend at most 1 hr on your own IT; Look for Docker solution after that.

References

Netlify Headless Wordpress

• Getting started with Jekyll - Series by CloudCannon

Wp Profit Builder Free

• Good morning,

  I am interested in exploring the options available to use a WP site with Netlify. I would like to keep the WP backend for familiar/easy editing.

  I see a couple of WP plugins that trigger an auto deploy to Netlify upon a WP edit. I also see WP2Static that is now on Github.Is one of these a good way to go?

  I now see another approach using the WP API (https://www.smashingmagazine.com/2020/02/headless-wordpress-site-jamstack/).

  In setting up using one of these ways, I assume I have to do some upfront work to get the WP site over to Netlify. What methods are available to accomplish this. If possible, I prefer not to use an SSG. Is WP2Static considered an SSG?

  So many choices, lol.

  Thanks

  • This topic was modified 6 months, 3 weeks ago by .
  • This topic was modified 6 months, 3 weeks ago by .
  • This topic was modified 6 months, 3 weeks ago by .
  • This topic was modified 6 months, 3 weeks ago by .

• Yes, WP2Static is a SSG. And since they removed that plugin from the repository, we don’t support it here. I’m not sure I understand the difference between WP2Static and the plugin they had here: https://wordpress.org/plugins/static-html-output-plugin/ which they have in a different GitHub repository. (Maybe that’s the original name, and they are moving forward in a new repo with WP2Static name.)

  The trick with making a static site with WP is you need two separate places: one for the PHP to run and the other to serve the static output. (so where does your domain name point?)
  If you have your host for the PHP, you might as well simply serve the result as normal, since it is still online and vulnerable to hacks. So it makes sense to use WP locally, and deploy to Netlify (usually via GitHub). Or use one of the services to host WP behind a firewall, and deploy for you. (Sitesauce, Shifter, Strattic)
  Running it as headless still requires a PHP backend, so it’s no faster or more secure than normal, although you can host on a service that does this for you.

  Consider the interactive parts of your site: comments, forms, search, login, ecommerce before you switch. You have to remove all of that (or find static substitutes) before you deploy what WP2Static generates. I found a plugin Remove WP Overhead recently, which helps with some of the stuff in the <head> section.
  I’ve been working on a plugin for generating a static search index for the Lunr search since I don’t want a branded external search on my client’s site.

  it makes sense to use WP locally, and deploy to Netlify (usually via GitHub). Or use one of the services to host WP behind a firewall, and deploy for you. (Sitesauce, Shifter, Strattic)

  Does “in-house computer” equate to “use WP locally”? If so, yes, that’s what I was referring to. (install WP on your computer)

  No, by putting WP on your computer, you are removing it from its online presence. You would have the only access to it. You would make whatever changes you want locally, and then run WP2Static to generate the static files that are then deployed to GitHub, where Netlify picks them up. Your domain name would point to where Netlify tells you to point it, to serve the static files from their CDN.

  The interactive features of WP have to be replaced with Javascript interacting with external APIs, for things like sign-in (MemberSpace, MemberStack), contact forms (FormKeep, or just use a mailto link), searches (Algolia or Google), forums (maybe Discourse).
  A static site is not a good fit for all. It just depends on what interactive things your site does.

  I assume you mean groups of people. If you are doing some sort of membership site, it’s not a good match for static.
  Take a look at https://www.tnd.dev/ for resources.
  https://jamstackfns.com/ also has some.
  You can write interfaces yourself, see https://functions.netlify.com/

• The topic ‘WP to Netlify’ is closed to new replies.