I mentioned my concerns of using WordPress as a CMS in a previous post, but now it is getting to be the time to find solutions to our problems. We have installed a test wordpress site and have begun working on it. The style is still bare, but I am looking at functionality issues. I used those links from the previous post plus some other sites found on Google to find potential solutions. I haven’t made any final decisions yet on what should work for us, but I’ll document some of my considerations
Events and Recipes
One issue we will have is needing custom data fields for the events and the recipes. WordPress has custom fields built in, but it would be best if the fields could be there automatically, without them having to add them and get the names exactly right each time.
Flutter is one plugin solution that looks nice. It allows custom write panels to be created in the admin section, so that events or recipes could be managed and added separately from the normal posts. It allows custom fields to be defined for each panel as well. It even allows data types to be defined, so dates for the events could be entered easily. It does have some issues, such as some bugginess and rumored slowness when post numbers get high. This did sell me on the custom write panel idea though.
Continue reading post "Stearns: Using WordPress as CMS"