<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on JErickson.net</title><link>https://jerickson.net/categories/posts/</link><description>Recent content in Posts on JErickson.net</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>joe@jerickson.net (Joe Erickson)</managingEditor><webMaster>joe@jerickson.net (Joe Erickson)</webMaster><copyright>© 2026 Joe Erickson</copyright><lastBuildDate>Thu, 07 Mar 2019 08:31:14 -0500</lastBuildDate><atom:link href="https://jerickson.net/categories/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>WordPress Post vs. Page</title><link>https://jerickson.net/wordpress-post-vs-page/</link><pubDate>Thu, 17 Oct 2013 20:09:59 -0400</pubDate><author>joe@jerickson.net (Joe Erickson)</author><guid>https://jerickson.net/wordpress-post-vs-page/</guid><description>&lt;p&gt;When building your WordPress theme, you might have been planning it to be used mainly as a blog theme or perhaps you lean in the web pages direction. Either way, to make a fully integrated WordPress theme, you need to make sure &lt;em&gt;both&lt;/em&gt; Pages and Posts are fully supported. And that means you should have a &lt;code&gt;single.php&lt;/code&gt; and a &lt;code&gt;page.php&lt;/code&gt; included in your theme and they shouldn’t look the same.&lt;br&gt;
You may think this is obvious, but I’ve seen many times when a theme is geared just toward web pages or just toward blogs (the most common) and then have a junky default &lt;code&gt;index.php&lt;/code&gt; for handling the other half because the theme wasn’t fully thought through. Posts and Pages are both first-class citizens in WordPress and should be treated that way. And your clients will love you if you do.&lt;/p&gt;</description></item></channel></rss>