{"id":4015,"date":"2020-07-03T21:05:48","date_gmt":"2020-07-04T04:05:48","guid":{"rendered":"http:\/\/www.eaf.net\/mvp\/?p=4015"},"modified":"2020-07-03T21:05:48","modified_gmt":"2020-07-04T04:05:48","slug":"create-a-custom-wordpress-page-template-for-html-content","status":"publish","type":"post","link":"https:\/\/www.eaf.net\/mvp\/2020\/create-a-custom-wordpress-page-template-for-html-content\/","title":{"rendered":"Create A Custom WordPress Page Template for HTML Content"},"content":{"rendered":"

Problem:<\/strong> You have an HTML-only web page, carefully designed, that you want to bring as-is into WordPress without investing hours on redesign.<\/p>\n

Compounding problem:<\/strong> This page uses three includes as well as a responsive layout and stylesheets that are entirely different from anything offered by the WordPress you are using.<\/p>\n

Solution:<\/strong> Create a special single-use custom WordPress page template.<\/p>\n

Good news:<\/strong> I’m about to tell you how to do this.<\/p>\n

Additional good news:<\/strong> The concept below can be modified into additional WordPress page templates for bringing in other HTML content into WordPress-powered sites. <\/p>\n

Bad news:<\/strong> I don’t know of any (related to this particular subject). Wait. There’s just a bit of bad news: I have some background to tell you about before showing you the WordPress page template. If you’re not interested, you don’t need me to tell you to just scroll past the next section.<\/p>\n

Background<\/h2>\n

My oldest website just turned 25. Yes, twenty-five years old. That’s almost prehistoric on the Web. Do you realize how many websites existed in mid-1995? Not many; as in, 23,500<\/a>.<\/p>\n

That site is entirely hand-coded in static HTML. I’m wanting to migrate it to WordPress. At the rate I’m going, I’ll be dead a long time before I get the project done. We’re talking hundreds of pages!<\/p>\n

I have WordPress set up and running on the site. I haven’t converted any old content, but recent content additions<\/a> I’ve done in WordPress.<\/p>\n

Actually, several days ago I also brought my old home page into WordPress. I created a php-free template to generate an exact replica of my original hand-coded static-html home page. The screen capture here shows you what the page looked like before I brought it into WordPress…and what it looks like now that it is generated by WordPress.<\/p>\n

\"Anabaptists<\/a><\/p>\n

Exciting News:<\/strong> I’m about to tell you how I accomplished that. \ud83d\ude00 \ud83d\ude2f \ud83d\ude33<\/p>\n

Mark Roth’s One-Use Theme-Agnostic WordPress Page Template<\/h2>\n

As I recall, I used Notepad to create this template. I used page-html-home.txt<\/em> as the name for my new document. (There’s WordPress-logical reason for the name, which I’ll reveal in a bit.)<\/p>\n

My custom template requires only one line of PHP code. That’s the line that gives the template its name. It goes at the very top. Here it is:<\/p>\n

<?php Template Name: HTML Home ?><\/pre>\n
Actually, I added some comments to my template as well, but they aren’t required. Curious? OK, Here you are:<\/p>\n
\"WordPress<\/p>\n
Below that PHP code I simply pasted in all the HTML code for the original hand-coded page. Yes, I mean all the code<\/strong><\/em>, beginning with the very first line and ending with the very last one. For me, that’s these two:<\/p>\n
<!doctype html>\r\n<\/html><\/pre>\n
After closing the document, I renamed<\/strong> it page-html-home.php<\/em> so WordPress could use it. Then I uploaded<\/strong> it to the proper WordPress directory on my site’s server. (I use GeneratePress<\/a> and a child theme, but this should work with any WordPress theme.)<\/p>\n
Some Modifications to Make to the Custom Page Template<\/h2>\n
If you are still with me so far in the development of your own template, log into your WordPress admin site and edit<\/strong> your new page template.<\/p>\n
One type of change I had to make was to update some of the script, stylesheet, and link paths<\/strong>. For example, since my home page uses CSS stylesheets that are not part of WordPress, I had to make sure that I used the correct paths in my special template.<\/p>\n
Since my home page also uses three HTML includes<\/strong>, I had to change those since WordPress wouldn’t process those (of course). If you want a truly PHP-free solution, replace the includes with the full text of the files they insert. Otherwise, add some PHP code to do the including for you.<\/p>\n
Instead of HTML code like this:<\/p>\n
<!--#include virtual="\/chunks\/footer.html" --><\/pre>\n
Use PHP code like this:<\/p>\n
<?php include ".\/chunks\/footer.html" ?><\/pre>\n
Save your modified template and take it for a test drive.<\/p>\n
How to Use Your New Custom Page Template<\/h2>\n
Create a new page. I titled mine HTML Home<\/em>. Notice the resemblance to the name of the template and its file.<\/p>\n
As you can see in this image, I added no content to the page. That’s because all the content is in the template I created just for this purpose.<\/p>\n
\"WordPress<\/p>\n
Also notice in the image above that I didn’t assign my custom template to this page. I could have. But I don’t really need to. That’s because WordPress does it automatically since I used those matching names I mentioned earlier. Let me see if can explain…<\/p>\n
When WordPress serves up a page…<\/p>\n
    \n
  1. It first checks to see if a template was assigned to it. If there is, it finds and uses it.<\/li>\n
  2. If the page does not have a template assigned to it, WordPress then checks to see if there’s a page template that matches the page’s slug. WordPress finds page-html-home.php<\/em> and serves up this page based on that template. (For more about this kind of stuff, check out what WordPress has to say about its template hierarchy<\/a>).<\/li>\n<\/ol>\n
    So, save your new page as a draft and then preview it.<\/p>\n
    Don’t Forget This!<\/h2>\n
    Since my custom template was supposed to serve up a replacement home page, I had to change my site’s WordPress Reading Settings<\/em> to use my HTML Home<\/em> page as the home page.<\/p>\n
    Then I had to FTP into my site’s root directory and delete<\/strong> the original index.html<\/em> file there.<\/p>\n
    And that’s it.<\/p>\n
    I hope you found this helpful. If there’s anything I need to clarify or correct, please let me know.<\/p>\n
    PS: I figure to use this basic approach to create another page template to use for hundreds of “Applications of Truth” meditations<\/a> I want to add next to my Anabaptists<\/em> site.<\/p>\n","protected":false},"excerpt":{"rendered":"
    A fast, easy, simple way to effectively bring old HTML pages into WordPress<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"Create A Custom WordPress Page Template for HTML Content","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[13],"tags":[909,716],"class_list":["post-4015","post","type-post","status-publish","format-standard","hentry","category-tech-stuff","tag-tips","tag-wordpress"],"jetpack_publicize_connections":[],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/prJUJ-12L","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.eaf.net\/mvp\/wp-json\/wp\/v2\/posts\/4015","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.eaf.net\/mvp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.eaf.net\/mvp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.eaf.net\/mvp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.eaf.net\/mvp\/wp-json\/wp\/v2\/comments?post=4015"}],"version-history":[{"count":0,"href":"https:\/\/www.eaf.net\/mvp\/wp-json\/wp\/v2\/posts\/4015\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.eaf.net\/mvp\/wp-json\/wp\/v2\/media?parent=4015"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.eaf.net\/mvp\/wp-json\/wp\/v2\/categories?post=4015"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.eaf.net\/mvp\/wp-json\/wp\/v2\/tags?post=4015"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}