How to Launch and Maintain a WordPress Site for Only $10.44 a Year (Domain + Hosting Included)

This isn’t about some particular promo fee or utilizing a coupon code. The catch is that this answer does require a bit extra effort and tech savviness to tug off in comparison with signing up for some easy shared internet hosting plan with pre-installed WordPress. It additionally has some limitations (although there are workarounds) and won’t be your best option for each kind of website.

Nevertheless, you probably have the endurance to work via the information in entrance of you and your website doesn’t want sure functionalities, then you’ll not solely save some huge cash, however additionally, you will be rewarded with an extremely fast-loading, ultra-secure WordPress website that may deal with just about limitless site visitors with out slowing down.

And with out preserving you in suspense any longer, what I’m going to indicate you right now, is methods to construct a WordPress website by yourself pc utilizing Native by Flywheel, convert it to static HTML recordsdata utilizing the Merely Static plugin, after which host these recordsdata utterly free on Cloudflare Pages. Your solely ongoing value? The $10.44 per 12 months that Cloudflare expenses for a .com area.

If all that sounds good to you, then let’s get began.

Understanding what you’re actually stepping into

As I simply talked about within the intro, going the static website route is a superb selection for some forms of websites, however not all. It largely comes down as to whether the strengths and limitations related to launching a static WordPress website are particularly relevant to you. So let’s evaluate these first after which if you happen to’re nonetheless on board, I’ll stroll you thru the method.

Advantages of static websites

• Lightning-fast load occasions – Static websites serve pre-rendered HTML recordsdata on to guests with out database queries or server-side processing. This implies your pages load virtually immediately, which guests love and search engines like google and yahoo reward with higher rankings.
• Rock-solid safety – No database? No PHP? No drawback! Nearly all of WordPress hackers goal vulnerabilities within the database or PHP code. By eradicating these components out of your manufacturing website, you’ve primarily eradicated most potential assault vectors. Hackers can’t breach what isn’t there.
• Just about limitless site visitors dealing with – Conventional internet hosting plans typically buckle underneath sudden site visitors spikes (like when your content material goes viral). Static websites on Cloudflare Pages can deal with huge site visitors surges with out breaking a sweat – or charging you additional.
• International CDN distribution – Your static website on Cloudflare Pages is robotically distributed throughout 275+ knowledge facilities worldwide. This implies guests from Tokyo to Toronto all get the identical blazing-fast expertise.

Limitations of static websites

• No dynamic WordPress options – That is the largest trade-off. Feedback, consumer accounts, search performance, and call kinds don’t work out-of-the-box with static websites since they sometimes require server-side processing. You’ll want third-party options for these options.
• Handbook replace course of – You may’t simply hit “Publish” and have your modifications immediately seem. This course of takes a minute or two moderately than just a few seconds. Every time you replace your website, you’ll must:
  • Make modifications in your native WordPress setup.
  • Generate new static recordsdata.
  • Run a script to deploy the up to date website.
• Restricted plugin compatibility – Many WordPress plugins depend on server-side PHP and database entry to perform. Whereas the Merely Static plugin does an important job changing most content material, plugins with heavy dynamic components received’t work within the static model.
• Steeper studying curve – This strategy requires familiarity with a number of instruments (Native by Flywheel, WordPress, GitHub, Cloudflare) and ideas that learners may discover difficult. It’s not rocket science, however it’s undoubtedly extra concerned than a one-click WordPress set up.
• Content material limitations – Membership areas, ecommerce performance, customized content material, and different superior options that require consumer state monitoring are extraordinarily tough (if not unimaginable) to implement with a purely static strategy.

The perfect use instances for this strategy

The WordPress-to-static answer works finest for the next forms of web sites:

• Private blogs – In case you publish content material comparatively occasionally (lower than every day) and don’t want native feedback, this setup is ideal.
• Portfolio web sites – Showcasing your work hardly ever requires dynamic options. A static portfolio website hundreds lightning-fast, letting your designs or images take middle stage with out ready for database queries.
• Small enterprise web sites – Most small companies want a digital storefront with details about providers, contact particulars, and maybe a weblog. The static strategy handles these completely whereas making certain your website hundreds rapidly for potential prospects.
• Documentation websites – Technical documentation or data bases that don’t require consumer logins are glorious candidates. You may nonetheless use WordPress to arrange advanced info hierarchies, then ship them as ultra-fast static pages.
• Brochure websites – Any “set it and neglect it” informational web site that doesn’t change often will profit from the simplicity and efficiency of this strategy.
• Advertising touchdown pages – When velocity and uptime are vital to conversion charges, static websites ship dependable efficiency that dynamic websites battle to match.

The widespread thread amongst all of those is that their content material doesn’t change often they usually don’t require advanced consumer interactions or personalization. In case your website falls into any of the above and also you implement what I’m about to show you, then you’ll save an entire lot of cash whereas really bettering your web site’s efficiency.

Launch a static WordPress website: step-by-step information

To get began, you’ll must obtain Local by Flywheel and register for accounts with GitHub and Cloudflare. You’ll additionally want the Simply Static plugin however you’ll be able to set up and activate it in your native WordPress website so there’s no must obtain it beforehand.

🥳 All of those instruments and accounts are free (or have a free model).

You’ll additionally want a domain name. In case you don’t have already got one, you should purchase a brand new one proper inside your Cloudflare account:

And with that out of the way in which, listed below are the steps (at a excessive degree):

• Create a neighborhood WordPress website
• Set up and configure the Merely Static plugin and a few wp-admin settings + export your website recordsdata to your laborious drive
• Arrange a GitHub repository and join it to your native repository (i.e., your exported website)
• Switch your WordPress website to Cloudflare Pages
• Create an environment friendly replace workflow

Part one: create a neighborhood WordPress website

After you obtain Native by Flywheel and open it, you’ll see an interface just like the one under. On the underside left there’s a + icon inside a circle. Click on it to start:

It will launch a setup wizard. Click on on Create a brand new website after which Proceed on the underside proper.

On the subsequent display screen (not proven right here), it’ll ask you if you wish to set up the Most popular setup, or if you wish to use a Customized one. Except you’ve got some compelling motive to go along with Customized, simply select Most popular.

The next step is the place you’ll give your web site a reputation.

You may at all times change this later, however I like to recommend placing the title that you simply really plan on utilizing. One of many causes is as a result of many configuration recordsdata in WordPress reference your website title and URL. Once you finally migrate your website to Cloudflare Pages, having constant naming from the start reduces the variety of database search-and-replace operations wanted to replace these references.

On the ultimate display screen, you’ll be requested for a username, a password, and an e-mail handle.

Faucet on Add Web site on the underside proper if you’re completed:

Along with your fundamental WordPress website arrange, the subsequent step is to entry it so you can begin constructing. You are able to do that by clicking on the WP Admin button. Nevertheless, earlier than you do this, activate the One-click admin toggle. That is the not-so-secret tip I simply talked about, which is able to will let you bypass the login display screen and go instantly into your website:

Part two: configure the Merely Static plugin and wp-admin settings + export your website

1. Set up Merely Static

The “set up” a part of this step is similar as putting in another plugin:

• From the wp-admin interface, go to Plugins → Add New Plugin.
• Then kind “merely static” into the Search Plugins window.
• Once you see the plugin populate within the outcomes, faucet on Set up Now → Activate.

As soon as the plugin has been activated, entry its settings from the sidebar by going to Merely Static → Settings.

2. Configure the final settings

Within the Normal part, you’ll see three important areas: Changing URLs, Embody, and Exclude.

You’ll additionally discover a collection of extra choices on the left. Most of them can be found within the free model, aside from three: Varieties, Search, and Optimize. You may click on on them, however the entire options are hidden behind Merely Static’s paywall. Fortunately, a few of them have workarounds (e.g., you’ll be able to optimize your pictures earlier than including them to your website with Optimole’s free image compressor).

However again to the three sections you could maintain…

Changing URLs

There are 4 subsections right here. Right here’s methods to deal with them:

• Changing URLs: The default setting right here is Relative Path. Change it to Absolute URLs.
• Scheme: Be certain that https:// is chosen. Cloudflare Pages goes to provide you a free SSL certificates in your website so https:// is the proper selection.
• Host: Write no matter your last area title goes to be if you deploy your website on Cloudflare Pages.
• Drive URL replacements: Flip this on. This ensures all situations of your WordPress URL (together with these in CSS and JavaScript) are correctly transformed to work in your static surroundings.

Embody

This part helps seize content material that Merely Static may miss throughout its computerized crawl:

• Further URLs: Solely add pages that aren’t linked from wherever else in your website, comparable to thanks pages or hidden touchdown pages.
• Further Recordsdata and Directories: You sometimes don’t want to change this until you’ve got customized asset directories or obtain “lacking file” errors after your first technology try.
• Generate 404 Web page: Flip this on however verify your web site’s theme to see if the 404 web page incorporates a search bar. Search isn’t supported by default in static websites, which implies that in case your theme does have one, you then’ll must both exchange it with a workaround answer (Simply Static has a nice tutorial) or take away it altogether. To verify in case your theme’s 404 web page has one, merely go to a web page in your website that doesn’t exist (i.e., mysite.com/this-page-does-not-exist). It will trigger the 404 web page to seem and you may verify if there’s a search bar on it. If there may be, use the answer under to take away it.

<fashion>
.error404 .search-form, 
.not-found .search-form,
physique[class*="404"] .search-form {
  show: none !vital;
}
</fashion>Code language: HTML, XML (xml)

• Embody Feeds: This ought to be left off. RSS feeds (which is what ‘Embody Feeds?’ refers to) are solely crucial in case your website has subscribers who observe your content through RSS readers or if you happen to’ve arrange e-mail subscriptions that depend on these feeds. Most trendy web sites don’t rely closely on RSS feeds anymore, so preserving this selection off will cut back pointless recordsdata in your static export.

Exclude

For simplest WordPress websites, you don’t want to change the exclusion settings. The Merely Static plugin already handles excluding WordPress-specific admin areas robotically, and the Diagnostics verify helps determine incompatible plugins:

Solely add exclusions you probably have particular content material you don’t need in your static website.

3. Configure the integrations settings

The Integrations part reveals how Merely Static interacts with different plugins in your WordPress website. Any plugins that you simply see listed right here and that you simply even have put in might be toggled on by default – aside from the paywalled ones.

The one motion you actually need to take right here is to toggle on the Admin Bar (Core) on the high.

It will add a small Merely Static icon to your WordPress admin bar on the high of the display screen. It is going to present the present standing of your static exports and offer you fast entry to Merely Static settings.

4. Configure the deploy settings

Now we have to arrange the place Merely Static will save your static website recordsdata – after which generate them.

Navigate to Deploy within the sidebar.

From the DEPLOYMENT METHOD dropdown, choose “Native Listing.” This tells Merely Static to save lots of all of your static recordsdata to a folder in your pc.

Beneath that, select a path in your static recordsdata within the PATH area. In easy phrases, you could specify the place in your pc the static recordsdata ought to be saved.

At first look, it would look like the best factor to do is nothing and let the plugin robotically create a folder for you. Nevertheless, I’ve personally discovered that creating the listing manually beforehand and inserting it outdoors your WordPress set up gives probably the most dependable outcomes.

• In case you’re utilizing a Mac, open up the Terminal app and sort in: mkdir ~/Desktop/static-site.
• For Home windows customers, open Home windows Command Immediate and sort: mkdir %USERPROFILEpercentDesktopstatic-site.

It will create the listing in your desktop, which is able to make it simpler to seek out. Nevertheless, you’re welcome to create it some other place. Once you’re completed, return to Merely Static’s Deploy settings and enter the complete path to your newly created folder:

• For Mac customers: /Customers/yourusername/Desktop/static-site
• For Home windows customers: C:UsersyourusernameDesktopstatic-site

Substitute “yourusername” along with your precise username.

Lastly, on the backside you’ll see Clear Native Listing. It ought to be turned off by default. Depart it that method and click on Save Settings.

5. Customise wp-admin settings

You’re virtually able to export your website, however there may be one vital mini-configuration you could make beforehand.

It’s to disable feedback as a result of they aren’t supported on static websites.

Out of your WordPress dashboard, go to Settings → Dialogue. Then within the very first part titled Default put up settings, merely uncheck all three choices. Scroll to the underside and click on Save Adjustments when completed.

6. Generate (export) your static website to your laborious drive

🎉 Now comes the thrilling half – producing the precise static website!

Earlier than you faucet the purple Generate button although, do a fast verify in that Diagnostics part I confirmed you earlier than. That is to make sure that the plugin isn’t flagging any points. In case you do encounter some, I might suggest trying out the troubleshooting section of Merely Static’s docs web page or drop a remark on the backside of this put up and I’ll do my finest that will help you.

In any other case, if every part seems good, you’ll be able to click on Generate. You can even watch all the course of unfold and get the small print by going into the Exercise Log part beforehand:

As soon as the method finishes, you’ll discover all of your static website recordsdata within the native listing path you specified earlier within the Deploy settings. These recordsdata signify an entire, static model of your WordPress website prepared for deployment.

You’re now prepared for the subsequent stage of the workflow – establishing a GitHub repository.

Part three: arrange a GitHub repository and join it to your native repository

GitHub goes to function the bridge between your native improvement and Cloudflare’s internet hosting platform.

It is going to do this by storing your static website recordsdata in a repository, which Cloudflare Pages will then hook up with, to be able to robotically deploy your website everytime you make modifications. Let’s stroll via the method of establishing this repository.

1. Set up Git (if you happen to haven’t already)

Earlier than making a repository, ensure Git is put in in your pc:

• Home windows: Obtain and set up Git from git-scm.com
• Mac: Open Terminal and sort git --version. If it’s not put in, you’ll be prompted to put in it

2. Initialize a Git repository in your static website listing

Open your Terminal or Command Immediate and navigate to the listing the place Merely Static saved your static website recordsdata by typing:

cd path/to/your/static/website/listingCode language: JavaScript (javascript)

Substitute path/to/your/static/website/listing with the precise path you configured in Merely Static’s Deploy settings.

💡 Keep in mind the short tip I supplied about copying it and setting it apart someplace? This was why.

When you’re within the right listing, initialize a brand new Git repository:

git init

You need to see a message like “Initialized empty Git repository in [your directory path].”

3. Create a .gitignore File

Earlier than including recordsdata to your repository, it’s an excellent follow to create a .gitignore file to exclude pointless recordsdata from being tracked:

• On Mac kind: contact .gitignore into Terminal.
• On Home windows kind: echo. → .gitignore into Command Immediate.

Subsequent, you could reveal your system’s hidden recordsdata. It is because .gitignore received’t present by default.

On Mac, kind this into Terminal:

defaults write com.apple.finder AppleShowAllFiles true
killall FinderCode language: CSS (css)

On Home windows, kind this into Command Immediate:

dir /a

Then discover the .gitignore file in your file listing and open it with any textual content editor (e.g., Notepad, TextEdit, Sublime Text, and many others.). Paste the next into the file and reserve it:

.DS_Store
Thumbs.db


.thought/
.vscode/
*.swp
*.swo


*.log
tmp/Code language: PHP (php)

4. Stage and commit your recordsdata

Now it’s time so as to add all of your static website recordsdata to the repository (excluding these in your .gitignore file):

git add .

Subsequent, create your first commit with a descriptive message:

git commit -m "Preliminary commit of static website"Code language: JavaScript (javascript)

With that out of the way in which, it’s head on over to GitHub and create a brand new repository to retailer your recordsdata.

5. Create a brand new repository on GitHub

Go to github.com and check in (or create an account if you happen to don’t have one). Click on the + icon within the high proper nook and choose New repository:

Identify your repository (e.g., my-static-site). For the needs of this tutorial I’ve named mine “mydirtcheapsite.”

Mark the repository as Personal (until you’ve got particular causes to make it public – comparable to utilizing it for instance of your work for a job software).

⚠️ Don’t add a .gitignore file, README file, or a license. We already created our personal .gitignore file earlier and it will likely be imported into the repository. The opposite two aren’t crucial both since this might be a personal repository and never an open-source venture meant to be shared with the web.

Click on Create repository if you’re completed:

6. Join your native repository to GitHub

Subsequent it can ask you ways you wish to create this new repository.

You’ll use the third choice (push an present repository from the command line), however earlier than you do this, you first must generate an entry token. That is to confirm that you’ve permission to import the recordsdata into the repository.

Generate an entry token

Click on in your profile picture (or the placeholder avatar if you happen to haven’t added a profile picture) on the highest proper of the display screen. Within the sidebar menu that slides out, faucet on Settings:

On the subsequent display screen (not proven right here), you’ll see one other sidebar menu – this time on the left facet of the display screen. Scroll down till you get to the very backside choice, which is known as Developer Settings. Click on on it.

As soon as contained in the Developer Settings, faucet on Private entry tokens on the left, and choose Tokens (basic). Then click on on Generate new token and select Generate new token (basic) from the dropdown menu:

GitHub will ask you to re-authenticate your self by way of your chosen 2FA methodology. After you achieve this efficiently, you’ll be requested to supply some particulars about your entry token. There’s rather a lot there, however you solely really want to fret about three issues:

• Within the Notice, write down the aim of the token. You can also make this no matter you need. For many of you studying this, it will likely be the one token in your GitHub record so it’s unlikely to get misplaced within the shuffle. Nonetheless, if you happen to begin deploying a number of websites utilizing this methodology, it’s a good suggestion to make the be aware one thing you’ll bear in mind as being related to the actual website you’re engaged on.
• For the Expiration, you’ll be able to select some set time or you may make the token final perpetually if you happen to don’t really feel like making a brand new one each so many months.
• Lastly, for the Choose scopes, verify the repo field and go away all of the others under it unchecked.

Once you’re completed, scroll down and click on on Generate token.

When you see your token, copy it by clicking on the little box-within-a-box icon subsequent to it:

Set it apart someplace and bear in mind the place you place it since you received’t be capable of see it once more after you permit this display screen.

Use the entry token to hook up with GitHub

The subsequent step is to make use of the entry token to determine a connection between your website because it exists in your laborious drive and your GitHub repository. Pay shut consideration right here as a result of you will need to do a whole lot of handbook substitutions to the command in order that it’s related to your website and credentials. The command is:

git distant add origin https:Code language: PHP (php)

So in my case, primarily based on the instance I’ve proven you, it could seem like this:

git distant add origin https:Code language: JavaScript (javascript)

To adapt this to your personal setup:

• Substitute YOUR-USERNAME (twice) along with your GitHub username.
• Substitute YOUR-TOKEN with the non-public entry token you copied earlier.
• Substitute YOUR-REPO-NAME with the title of your repository.

Kind or paste the edited command into your Terminal (Mac) or Command Immediate (Home windows) and press Enter.

Set the principle department

Subsequent, we have to set the default department title to “important”:

git department -M important

Push your recordsdata to GitHub

Lastly, push your dedicated modifications to GitHub:

git push -u origin important

The -u flag (brief for --set-upstream) tells Git to recollect these settings, making future pushes easier.

If every part labored accurately, you’ll see output indicating that your recordsdata are being uploaded to GitHub. When the method completes, you’ll be able to refresh your GitHub repository web page to see all of your static website recordsdata now out there on-line:

Part 4: switch your native WordPress website to Cloudflare Pages

That is arguably probably the most rewarding step since you lastly get to see all of the fruits of your labor when the positioning is deployed. It’s additionally the best and quickest step and largely consists of clicking your method via some buttons.

To get began:

• Log into your Cloudflare account.
• Use the left sidebar to seek out Employees & Pages. Faucet on it after which click on on the submenu merchandise that has the identical title (Employees & Pages).
• Click on on Pages (subsequent to Employees) close to the highest of the display screen.
• Click on the Hook up with Git button.

On the subsequent display screen (not proven), faucet on Join GitHub.

After that you simply’ll must authorize the connection.

You may select to provide permission for your entire repositories or solely the actual repository that incorporates your website. For many of you studying this, this selection in all probability received’t matter an excessive amount of initially, however I like to recommend selecting solely the particular repository that has your website recordsdata.

Once you end making your choice, faucet on Set up & Authorize on the backside of the display screen:

The subsequent web page has an odd, minor quirk.

In case you selected the particular repository as I beneficial, you then’ll see it robotically populated within the Choose a repository window. Nevertheless, the Start setup button might be unavailable to click on.

Merely click on into the Choose a repository window, and that can raise the maintain on the button so you’ll be able to faucet it and transfer ahead.

Subsequent, you’ll see Cloudflare work via the method. When it’s all completed, your website might be reside.

⚠️ Notice: It might take a couple of minutes for it to propagate so if you happen to click on on the hyperlink and also you get an error display screen – don’t panic. Give it ~5 minutes and it ought to work. Understand that this short-term hyperlink doesn’t matter anyway since you’ll be connecting your website to your area.

Click on on Add customized area on the underside left to finish that step:

Including the area could be very easy – kind it into the Area window and click on Proceed:

On the subsequent display screen (not proven) faucet the Start DNS switch button to let Cloudflare provoke the DNS switch. As soon as the DNS switch is full, you’ll be capable of add your customized area to your static WordPress website.

Part 5: create an environment friendly replace workflow

In case you’ve made it efficiently thus far, you is likely to be tempted to easily name it a day. In any case, your WordPress website is now reside. You’ve bought free internet hosting, a free SSL certificate, and all issues thought of, you’re in fine condition.

Nevertheless, until you don’t plan on updating your website greater than perhaps annually, then I might extremely urge you to stay with me for this final part of the tutorial.

The explanation why is that updating a static website doesn’t work the identical method as updating a website on conventional webhosting.

Each time you make any form of change and regenerate the static recordsdata, you’ll must commit these modifications to GitHub, which then triggers a brand new deployment on Cloudflare Pages. In case you merely overwrite all of the recordsdata every time, your Git historical past will turn out to be bloated with unchanged recordsdata, making it more durable to trace precise modifications and doubtlessly inflicting slower deployments.

Fortunately, there’s an answer to this drawback.

Python to the rescue

Through the use of a Python script, you’ll be able to determine which recordsdata have really modified in your WordPress website when updating it. You then solely replace these particular recordsdata in your Git repository. This strategy retains your repository measurement manageable whereas sustaining an correct report of your website’s evolution.

Right here’s methods to do it:

Create and modify the Python script

• Make a folder in your Desktop to arrange your automation recordsdata. You may title it one thing like website-tools to make it straightforward to recollect.
• Open up a brand new doc in your most popular textual content editor. In case you’re undecided which textual content editor to make use of and also you’re on a Mac, you need to use TextEdit. For Home windows customers, you need to use Notepad. Each of them come pre-installed on their respective methods.
• Copy the Python script under and paste it into your textual content editor doc.

import os
import subprocess
import time

def run_git_commands(repo_dir):
    """Run git instructions to commit and push modifications if there are any."""
    
    os.chdir(repo_dir)
    
    
    git_status = subprocess.run(["git", "standing", "--porcelain"], capture_output=True, textual content=True)
    
    if git_status.stdout.strip():
        print(f"Adjustments detected, committing...")
        
        commit_message = f"Web site replace - {time.strftime('%Y-%m-%d %H:%M:%S')}"
        
        
        subprocess.run(["git", "add", "."])
        subprocess.run(["git", "commit", "-m", commit_message])
        subprocess.run(["git", "push"])
        
        print("Adjustments dedicated and pushed to repository.")
        return True
    else:
        print("No modifications detected. Repository unchanged.")
        return False

if __name__ == "__main__":
    
    REPO_DIR = "/Customers/yourusername/Desktop/static-site"
    
    
    run_git_commands(REPO_DIR)Code language: PHP (php)

• Modify REPO_DIR within the script to match your particular setup. In different phrases, exchange /Customers/yourusername/Desktop/static-site with regardless of the path is that you simply put into the Merely Static plugin Deploy part.

• Save the file as update_site.py in your website-tools folder.

Streamline the workflow

Quite than working the Python script manually each time you could use it, I’m going to indicate you methods to create a easy shell script (or batch file on Home windows) that performs all the replace sequence in a single step.

As soon as once more, open a brand new empty doc in your textual content editor. Copy and paste the code under (related to your working system) into the textual content editor and save the file with the suitable title and extension:

• For Mac: Save as update-website.sh
• For Home windows: Save as update-website.bat

Don’t neglect to save lots of these recordsdata in your devoted folder (like website-tools on this instance) to maintain your automation instruments organized and separate out of your static website recordsdata.

#!/bin/bash
python3 ./update_site.pyCode language: JavaScript (javascript)

cd ~/Desktop/website-toolsCode language: JavaScript (javascript)

chmod +x update-website.shCode language: CSS (css)

./update-website.sh

#!/bin/bash
python ./update_site.pyCode language: JavaScript (javascript)

@echo off
python C:pathtoupdate_site.pyCode language: CSS (css)

With this workflow in place, your replace course of might be extraordinarily easy:

1. Make modifications to your WordPress website in Native by Flywheel.
2. Generate a brand new static model utilizing Merely Static.
3. Run your batch script / shell.

End line

First, take a deep breath. You made all of it the way in which to the tip.

This information was not for the faint of coronary heart and is longer than simplest WordPress tutorials about methods to set up some plugin or use a characteristic within the block editor.

With that mentioned, transferring your WordPress website over to a static deployment is totally well worth the enterprise for my part. The few hours this course of takes the primary time you do it can pay you dividends for years to come back. You’ll have a sooner, safer website with world CDN distribution – and more cash in your checking account.

You’re welcome. 😃

💡 On a last be aware, if you wish to degree up your static WordPress website even additional, try my two follow-up guides. One will present you how to add contact forms to a static site and the opposite will educate you how to add a search page.

In case you have any questions or get caught on any step within the course of, simply drop a remark under. I’ll be blissful that will help you out.