jamstackpress

santiagocajal

guilledutra

JAMStackPress – Power-up you WordPress backend
This plugin extends the WP-JSON API by adding a new useful set of fields to the WP-JSON API response, this new set of fields will make your front-end development easier. JAMStackPress also applies some optional filters 
to the content in order to make it front-end ready (no need to make replacements or ad image width and height attrs at front-end level). Finally we also adds to more endpoints to the WP-JSON API (contact form and sitemap) very useful! 
We think about the possible scenarios of development for your static website, so in other words, we’ll try to make your life easier, so that you only think about developing your decoupled front-end.
<h3>Extra fields (jamstackpress object)</h3>
We include some extra fields that can be activated in the plugins administration page, that will make your front-end development easier:
<ul>
<li>
Human readable date field (uses the locale defined in your WordPress panel): 
<code>"readable_date": "March 26, 2018"</code>
</li>
<li>
Post’s full slug and front-end link respecting your WordPress permalinks selection: 
<code>"routes": { 
"slug": "/category/post-title/", 
"front_link": "https://frontenddomain.com/category/post-title/" 
}</code>
</li>
<li>
Featured image URLs one for every size:
<code>"featured_image": { 
"thumbnail": "http://example.com/wp-content/uploads/2022/07/thumbnail-150x150.jpg", 
"medium": "http://example.com/wp-content/uploads/2022/07/medium-300x200.jpg", 
"medium_large": "http://example.com/wp-content/uploads/2022/07/medium-large-768x512.jpg" 
"large": "http://example.com/wp-content/uploads/2022/07/large-1024x683.jpg" 
}</code>
</li>
<li>
SEO tags Title and Description – Compatible With Yoast and RankMath plugins: 
<code>"seo": { 
"title": "Post Title", 
"description": "Post SEO description" 
}</code>
</li>
</ul>
<h3>Extra endpoints</h3>
JAMStackPress includes 2 optional endpoints, always with the porpoise in mind of making your front end development tasks much more easier
/jamstackpress/v1/contact 
This endpoint acts as a contact form back-end resource. Will save a jp_contact custom post and send an email on every success submission.
How to use it:
<ol>
<li>Enable the custom contact form endpoint in the options panel. </li>
<li>Fill and save the rest of the options related to the contact endpoint: Contact email, Contact Fail Message, Contact Success Message and reCaptcha Secret Key (google reCaptcha V3). </li>
<li>
Send a request to the custom contact form endpoint, here is an example of a call to the contact form endpoint using js fetch()
<code>fetch('https://example.com/wp-json/jamstackpress/v1/contact?',{ 
method: 'POST', 
headers: { 
'Accept': 'application/json', 
'Content-Type': 'application/json' 
}, 
body: JSON.stringify({ 
name: 'Name', 
email: 'example@example.com', 
subject: 'Contact Subject', 
message: 'Body of the contact form message', 
recaptach_token: 'xxxxxxxxxxx'}) 
})</code>
</li>
</ol>
/jamstackpress/v1/sitemap 
This endpoint will return a full list of posts and categories slugs, here is a sample of returned list: 
 <code>["/sapiente/eveniet-velit-et-aut-est-et-inventore/","/sapiente/aliquid-aut-ut-eius-excepturi-magni/","/nulla-molestias/eius-ratione-mollitia-aliquam/","/uncategorized/aut-qui-repudiandae-nihil-iste/","/uncategorized/test/","/aliquam/","/ipsa-ratione/","/nulla-molestias/","/perferendis-modi/","/sapiente/","/uncategorized/","/unde-temporibus/","/ut-quo/"]</code>
<h3>Content filters & Deploy tools</h3>
Content filters 
– Replace your WordPress base URL with the front-end URL defined in the plugin settings. 
– Add image width and height attributes to every image placed at the content. 
– Add _blank target to every external link at the content.
Deploy tools 
– Trigger front-end build: You can specify a build webhook url for triggering a deployment in your front-end site, directly from your WordPress back-end. This 
is specially useful to keep your front-end site always updated with the latest content, without having to manually trigger a deploy.

JAMStackPress

Power-up your WordPress site and get it ready for JAMStack. Take advantage of useful fields, endpoints and filters extending the WP-JSON API.

mitchmac

The plugin creates zip files containing posts converted to Markdown. A WP-CLI command exists to handle exporting sites with a large amount of content.
<ul>
<li>Move WordPress content to Gatsby-friendly Markdown.</li>
<li>Customize the export! Remap and restructure exported fields.</li>
<li>CLI: Avoid PHP timeouts by using the command line with WP-CLI.</li>
<li>CLI: Export progress bar (great for large sites)!</li>
</ul>
<blockquote>
Reminder: always keep a backup of the WordPress database and files in case your export doesn’t work as expected!
</blockquote>
<h3>Working with Gatsby</h3>
If you’re just getting started with Gatsby, we recommend experimenting with a Markdown based Gatsby starter like <a href="https://github.com/tinacms/tina-starter-grande" rel="nofollow ugc">Tina Grande</a>. Installation is as easy as:
<pre><code>git clone https://github.com/tinacms/tina-starter-grande.git

cd tina-starter-grande

yarn install && gatsby develop
</code></pre>
Then copy your exported WordPress Markdown into the <code>content</code> directory or point the wp gatsby-markdown-export command at the content directory.
Want to port your WordPress or HTML theme to Gatsby? Checkout <a href="https://www.gatsbyjs.org/docs/porting-an-html-site-to-gatsby/" rel="nofollow ugc">Porting an HTML Site to Gatsby</a> for tips.
<h3>Command Line Usage</h3>
The command line functionality uses WP-CLI to interact with WordPress. <a href="https://wp-cli.org/#installing" rel="nofollow ugc">WP-CLI is easy to install</a> if you haven’t already.
Once it’s installed, you can export content to a directory like this:
<pre><code>wp gatsby-markdown-export --directory=/example/gatsby-starter/src/content
</code></pre>
All CLI arguments are optional.
 Option 
 Description 
 Default value
 <code>--help</code> 
 get help
 <code>--directory=</code> 
 export output directory 
 random temp directory
 <code>--post_types=</code> 
 post types to export, see: https://developer.wordpress.org/reference/classes/wp_query/#post-type-parameters 
 page,post
 <code>--post_status=</code> 
 post status to export, see: https://developer.wordpress.org/reference/classes/wp_query/#status-parameters 
 any
 <code>--fields_to_markdown=</code> 
 fields to convert to Markdown 
 excerpt
 <code>--excluded_front_matter=</code> 
 fields to exclude from front matter
 <code>--post_date_format=</code> 
 format for post publish date, see: https://www.php.net/manual/en/function.date.php 
 c
 <code>--upload_dir=</code> 
 directory in the export to copy WordPress uploads 
 uploads
 <code>--remap_fields=</code> 
 remap front matter field names, example: find1,replace1;find2,replace2
 <code>--fields_to_array=</code> 
 convert single value front matter fields to arrays
 <code>--include_private_fields=</code> 
 private post meta fields to include (they start with _)
 <code>--skip_copy_uploads</code> 
 flag, skips copying WordPress uploads to the export
 <code>--skip_original_images</code> 
 flag, skips the use of original dimension images
 <code>--skip_enforce_charset</code> 
 flag, skips use of blog_charset for the XML charset
 <code>--create_type_directory</code> 
 flag, creates directories based on post type

WP Gatsby Markdown Exporter

Export WordPress content to Markdown for GatsbyJS.

JAMStackPress vs WP Gatsby Markdown Exporter