Braad

If your site uses the Genesis framework, it’s likely that you’re making use of Genesis hooks like genesis_before_content or genesis_entry_footer. When using the WP REST API, any content that has been added to these hooks is not included in the response by default.
This plugin filters the response from the API to include any content added via Genesis hooks. It adds this content to the post object response, which means you don’t have to do a separate request or modify your request to get the data. Simply ask for a post in the standard way like /wp-json/wp/v2/posts/1 and you’ll get the extra content from the Genesis hooks.
<a href="https://www.diffchecker.com/v9ttyrq7" rel="nofollow ugc">Example diff showing the response with and without the plugin active</a>
The Genesis hook content that is returned is generated with respect to the context of the specific post being retrieved. The context will match what it would be on the single post page for the given post, page, or custom post type. This means that if you’ve got some code like this:
<pre><code>add_action( 'genesis_before_entry', 'mytheme_output_special_content' );
function mytheme_output_special_content() {
 // Only on posts in a specific category
 if ( in_category( '5' ) ) {
 echo 'Some Content';
 }
}
</code></pre>
You’ll get back ‘Some Content’ as the value of the property ‘genesis_before_entry’ on the response object only if the post is actually in category 5. All of the standard conditionals like is_archive(), is_single(), has_tag(), etc. will be respected.
By default this plugin only adds properties to the response object for hooks that have output, but you can modify this behavior using a filter like so:
<pre><code>add_filter( 'genesis_rest_api_return_empty_hooks', '__return_true' );
</code></pre>
By default this plugin adds the extra properties to posts, pages, and all custom post types, but you can specify which post types you want to include the extra data with another filter:
<pre><code>add_filter( 'genesis_rest_api_supported_post_types', 'mytheme_genesis_rest_api_supported_post_types' );
function mytheme_genesis_rest_api_supported_post_types( $post_types ) {

 // Only add data to the movie post type.
 $post_types = array( 'movie' );

 return $post_types;
}
</code></pre>
NOTE: In v2 of the REST API, custom post types need to have the extra properties <code>show_in_rest</code>, <code>rest_base</code>, and <code>rest_controller_class</code> set on their post type objects in order for the API to start serving data for them. I’ve included a filter in this plugin for adding these properties so that you can declare REST API support for CPTs and add the extra Genesis data in one step, but the filter is off by default and won’t override properties that are already set (because if core doesn’t assume you want all your CPTs publicly accessible by default, I don’t think I should either). To turn this functionality on, use the included filter like this:
<pre><code>add_filter( 'genesis_rest_api_register_cpt_api_support', '__return_true' );
</code></pre>
If you do this, you’re CPTs will be available at routes that match the official name of the post type found on the post type object, so if your post type is ‘movie’ and you have a movie with an id of 8, the movie will be accessible at /wp-json/v2/movie/8. It’s probably a better idea to match the core convention of /posts/ and /pages/, so if you want to make the route available at /movies/ instead of /movie/ you just need to specifically set the <code>rest_base</code> property like so:
<pre><code>add_action( 'init', 'mytheme_change_cpt_routes', 11 );
function mytheme_change_cpt_routes() {

 global $wp_post_types;

 $wp_post_types['movie']->rest_base = 'movies';
}
</code></pre>
Here’s the full list of all the Genesis hooks that are currently supported:
<pre><code>genesis_before
genesis_before_header
genesis_site_title
genesis_site_description
genesis_header_right
genesis_after_header
genesis_before_content_sidebar_wrap
genesis_before_content
genesis_before_loop
genesis_before_while
genesis_before_entry
genesis_entry_header
genesis_before_entry_content
genesis_entry_content
genesis_after_entry_content
genesis_entry_footer
genesis_after_entry
genesis_after_endwhile
genesis_after_loop
genesis_before_sidebar_widget_area
genesis_after_sidebar_widget_area
genesis_after_content_sidebar_wrap
genesis_before_footer
genesis_footer
genesis_after_footer
genesis_after
</code></pre>
And naturally, there is a filter to control which hooks are supported:
<pre><code>add_filter( 'genesis_rest_api_supported_hooks', 'mytheme_genesis_rest_api_supported_hooks' );
function mytheme_genesis_rest_api_supported_hooks( $genesis_hooks ) {

 // Only include certian hooks.
 $genesis_hooks = array(
 'genesis_before_entry',
 'genesis_after_entry',
 );

 return $genesis_hooks;
}
</code></pre>
NOTE: The hooks genesis_header and genesis_loop are not included by default because they mostly call other hooks that are included, but you can always add them back in using the genesis_rest_api_supported_hooks filter.
NOTE: Returning formatted HTML over the REST API is not the best way to make use of a REST API to build a website. It would be preferable to return only the raw object data and build all of your HTML on the client side using the object data. With this plugin you can do exactly this with a little help from <code>json_encode</code>:
<pre><code>add_action( 'genesis_before_entry_content', 'mytheme_pass_array' );
function mytheme_pass_array() {

 if ( is_single( 124 ) ) {
 $json = array(
 'a_key' => 'some value',
 'another_key' => 'another value',
 );
 echo json_encode( $json );
 }
}
</code></pre>
Or the object version:
<pre><code>add_action( 'genesis_after_entry_content', 'mytheme_pass_object' );
function mytheme_pass_object() {

 if ( in_category( 2 ) ) {
 $json = new stdClass();
 $json->some_key = 'some value';
 $json->another_key = 'another value';
 echo json_encode( $json );
 }
}
</code></pre>
Passing arbitrary objects and arrays like this really opens up some interesting possibilities.
If you have any ideas for new features or find a bug, please open an issue <a href="https://github.com/BraadMartin/genesis-rest-api-integration" title="Genesis REST API Integration" rel="nofollow ugc">on Github</a>. Pull requests are also encouraged :).

Genesis REST API Integration

Adds content output from the Genesis framework hooks to the response data for posts, pages, and custom post types when using the WP REST API v2.

swinton

This plugin is primarily aimed at theme developers, and intends to ease the 
creation of semantic, usable pagination controls for WordPress listings pages, such as 
arhive, author, category, search, tag listings etc.
Inspired by <a href="https://codex.wordpress.org/The_Loop" rel="nofollow ugc">The Loop</a> and <a href="https://codex.wordpress.org/Function_Reference/WP_Query" rel="nofollow ugc">WP_Query</a>, this plugin stays out of the theme 
developer’s way, allowing her to create the markup needed by providing the 
following template tags:
<ul>
<li><code>pp_has_pagination</code> – determines whether the current ‘view’ has any pagination to display, i.e. whether the content being browsed spans more than 1 page</li>
<li><code>pp_the_pagination</code> – initiates the pagination context, should be called at the beginning of each loop iteration</li>
<li><code>pp_rewind_pagination</code> – resets the pagination context, so that the pagination loop can be iterated over multiple times</li>
<li><code>pp_is_current_page</code> – for use in the pagination loop, returns a boolean indicating whether the current loop iteration is for the current page</li>
<li><code>pp_has_previous_page</code> – for use in the pagination loop, returns a boolean indicating whether there is a previous page, e.g. when at page 1, there is no previous page</li>
<li><code>pp_has_next_page</code> – for use in the pagination loop, returns a boolean indicating whether there is a next page, e.g. when at page N of N, there is no next page</li>
<li><code>pp_the_page_permalink</code> – for use in the pagination loop, echos the permalink for the current page</li>
<li><code>pp_the_previous_page_permalink</code> – for use in the pagination loop, echos the permalink for the previous page</li>
<li><code>pp_the_next_page_permalink</code> – for use in the pagination loop, echos the permalink for the next page</li>
<li><code>pp_the_first_page_permalink</code> – for use in the pagination loop, echos the permalink for the first page</li>
<li><code>pp_the_last_page_permalink</code> – for use in the pagination loop, echos the permalink for the last page</li>
<li><code>pp_the_page_num</code> – for use in the pagination loop, echos the page number of the current page being iterated over</li>
</ul>
For example, the following arrangement of template tags would provide a rudimentary pagination control:
<pre><code><?php if (pp_has_pagination()) : ?>
 <div class="pagination">

 
 <?php pp_the_pagination(); if (pp_has_previous_page()) : ?>
 <a href="<?php pp_the_previous_page_permalink(); ?>" class="prev">newer stories</a>
 <?php else : ?>
 newer stories
 <?php endif; pp_rewind_pagination(); ?>

 
 <?php while(pp_has_pagination()) : pp_the_pagination(); ?>
 <?php if (pp_is_current_page()) : ?>
 <?php pp_the_page_num(); ?>
 <?php else : ?>
 <a href="<?php pp_the_page_permalink(); ?>"><?php pp_the_page_num(); ?></a>
 <?php endif; ?>
 <?php endwhile; pp_rewind_pagination(); ?>

 
 <?php pp_the_pagination(); if (pp_has_next_page()) : ?>
 <a href="<?php pp_the_next_page_permalink(); ?>" class="next">older stories</a>
 <?php else : ?>
 older stories
 <?php endif; pp_rewind_pagination(); ?>

 </div>
<?php endif; ?>
</code></pre>
The template tags on offer by this plugin provide the theme developer with an 
unlimited array of possibilities for marking up the pagination control in a 
semantic manner.
For more information, see the original <a href="http://www.nixonmcinnes.co.uk/2009/07/27/making-wordpress-navigation-more-usable-through-pagination-patterns/" rel="nofollow ugc">blog post</a>.

Proper Pagination

A flexible framework for creating semantic pagination controls for a listings page based on established usability patterns.

Genesis REST API Integration vs Proper Pagination