Wordpress Post vs Page, Best Practices

I'm new to creating WordPress templates, so I apologize if this is a dumb question :)

As an example, I have a template page "About.php" which I've named "AboutUsPage".  

So I create a new page called About and it uses "AboutUsPage"

On this page, I need to display 2 user profiles.  Each profile contains a Name, Description and Image.  So I see 3 ways of accomplishing this, but I'm wondering what the best practice is.

Option 1.  Copy my the html verbatim into the html editor for the About,  This is fine, but there's html to worry about and I wonder if users editing this page will have to worry about too much.

Option 2.  Create a page for each profile, and use a custom field for the image and display both posts on the about page.  In this case, I could control where each element goes on the AboutUsPage template.

Option 3. Create a category called About, and 2 posts, 1 for each profile, under that category.  List each post in the category on the AboutUsPage template.

So the question is...  which option is best?  Or am I missing something.

Thank you for your help and opinions!
LVL 1
slightlyoffAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Jason C. LevineConnect With a Mentor No oneCommented:
Option 1.  Copy my the html verbatim into the html editor for the About,  This is fine, but there's html to worry about

The WordPress visual editor should handle the HTML and let the users edit without dealing with the code side.  Generally speaking, you will have to train users about HTML (albeit minimally) in order for them to be successful.  

Option 2.  Create a page for each profile, and use a custom field for the image and display both posts on the about page. Option 3. Create a category called About, and 2 posts, 1 for each profile

Both of these options make things unnecessarily complex.  Unless the About Us page is going to change frequently and thus require more than a quick edit, you would be better off just making it a normal page and placing the elements in there.

When planning out a WordPress site, it's helpful to keep the following in mind:

Pages = are meant for mostly static/timeless site content and can have hierarchy, but take no taxonomy (tags, categories).

Posts = are meant for content associated with a time/date and support both hierarchy and taxonomy but the latter is only supported with tags and categories.

Custom Post Types = are a subset of posts where you can redefine how the default Post works and add/remove meta information as well as create different types of taxonomies aside from tags and categories.  Custom Post Types are also organized separately from posts in the admin which makes them easier to expose/hide from different user roles.

Custom Fields = contain data independently of the Post/Page/CPT structures and can be recycled and reused as you see fit.

So in this specific case, you would have no real reason to use anything other than a page given only two objects.  Just lay it out and publish.

But if you were creating a company-wide directory and wanted to make it searchable as well as having a specific format, that would lean more towards creating an "Employees" custom post type with a new template and possibly using custom fields in the template to organize the placement of data.  Instead of categories and tags, you could create new taxonomies such as "Title" and "Department" and use those to help organize the employees.

Make sense?
0
 
slightlyoffAuthor Commented:
Yes, perfect.  Thank you for taking the time to help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.