Hello,
Thank you for having an interest in church website data portability.
The only thing the plugin does is register the custom post types, taxonomies and custom fields of your choosing (this is covered in the documentation).
There is nothing in the plugin to assist with the actual showing of content so there is nothing on that topic in the documentation. Presentation is the responsibility of your theme. You would show the post types, taxonomies and custom fields in the same way that any other theme would. The WordPress Codex covers this so we don’t reiterate it.
http://codex.wordpress.org/Theme_Development
You will need to be familiar with the post types, taxonomies and custom fields that you will use in your theme. The only way to become familiar with them is to look at how they are registered (the names in particular). The code that does this is linked to on GitHub from the plugin’s starter guide.
http://churchthemes.com/guides/developer/church-theme-content/#post-types-taxonomies-and-fields
Please let me know if you have any questions.
I updated the documentation to make this more clear in the Showing Content section. Thank you for pointing out that that section was not totally clear.
Thanks for the quick reply. I really like the plugin and I understand all about accessing the taxonomies, and using the cpt’s, etc. What I was referring to was that there’s no documentation on what data is available and how I can access it in my theme. For instance, what are the custom post type names?, what taxonomies and meta fields are available for each and what do they mean?
This information is needed to get rudimentary benefit from the plugin, so the more accessible it is, the better, IMO. Yes, all this information is in the source code, which I can peruse through and figure out, but it’s less than ideal and it does not replace documentation. That’s why I though it should’ve been part of the documentation, but perhaps I’m wrong.
Thank you, I will consider adding a table that lists basic details about the data. That would serve as a good introduction. The code could then be referred to for full details.
