<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>WordPress Tips on JErickson.net</title><link>https://jerickson.net/categories/wordpress-tips/</link><description>Recent content in WordPress Tips 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/wordpress-tips/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><item><title>WordPress Menu CSS Customization</title><link>https://jerickson.net/wordpress-menu-css-customization/</link><pubDate>Sun, 13 Oct 2013 11:31:23 -0400</pubDate><author>joe@jerickson.net (Joe Erickson)</author><guid>https://jerickson.net/wordpress-menu-css-customization/</guid><description>&lt;p&gt;WordPress isn’t always the friendliest thing in the world to style and the WordPress menus are no different. To get at the WordPress menu CSS takes a couple of hoops to jump through, but I’ll walk you through them now to illustrate how it can be done.&lt;/p&gt;</description></item><item><title>Requiring Authentication for WordPress Feeds</title><link>https://jerickson.net/requiring-authentication-wordpress-feeds/</link><pubDate>Wed, 09 Oct 2013 19:05:08 -0400</pubDate><author>joe@jerickson.net (Joe Erickson)</author><guid>https://jerickson.net/requiring-authentication-wordpress-feeds/</guid><description>&lt;p&gt;Someone asked this over at &lt;a href="http://wordpress.stackexchange.com/" target="_blank" rel="noreferrer"&gt;http://wordpress.stackexchange.com&lt;/a&gt; and I put a lot of research into it, so I figured I&amp;rsquo;d post it here too.&lt;/p&gt;
&lt;p&gt;Someone had asked how to go about securing RSS feeds behind a firewall in WordPress. It&amp;rsquo;s not an overly easy process so I dug in to try and figure it out.&lt;/p&gt;</description></item></channel></rss>