[ad_1]
I have a client that owns one business with multiple locations and roughly 20 “employees” that rent space from them. They requested to have a page that lists each employee that also includes 2-3 pictures of them and their space, a short bio and contact information. My client has no intention of creating a blog, so my first thought is I can create a blog post for each employee and style everything so it doesn’t appear as a blog so much (hiding post author, published date, category and other meta data). Has anyone out there done this and regretted it for any reason. I can’t think of any negative impacts off the top of my head, but not sure if there is something I’m not thinking of. Thanks!
[ad_2]
Can’t you just create a page instead of a post?
This is better suited to use a custom post type. Manage employees in one area. Have a page with query loop block listing out employees and enable employee single posts to display their info.
I agree with u/Breklin76. While you’re on the right track — nothing at all wrong with “misusing” posts with their super useful, filterable categories and tags.
You might instead look at using a plugin like ACF or CPT-UI to create a super simple custom post type for employees. No need for custom fields. Use them like posts but they’ll be easily separated if the client ever gets smart and starts blogging.
But, eh, it’s not *wrong* to use posts. Just give them a unique category so you can filter for them.