vaakash

<p>Git it Write allows to publish the markdown files present in a GitHub repository to your WordPress site. So with this plugin, whenever the files are added, updated in the repository the WordPress post will be added, updated accordingly.</p>
<p>This plugin is inspired from static site generators like <code>Jekyll</code>, <code>Next.js</code>, <code>Gatsby.js</code> on how content is written is markdown. This is a similar idea for WordPress where markdown files are parsed from GitHub and published as posts.</p>
<p>👓 <strong>Live example:</strong> <a href="https://github.com/vaakash/aakash-web" rel="nofollow ugc">Source github repository</a> (<code>/docs/</code> folder) to <a href="https://www.aakashweb.com/docs/" rel="nofollow ugc">Posts published</a></p>
<p>⚡ <strong>Getting started:</strong> <a href="https://www.aakashweb.com/docs/git-it-write/getting-started/" rel="nofollow ugc">Get started</a> with Git it write. Learn how to write <code>.md</code> files and publish posts on WordPress.</p>
<p>This allows people to collaborate with the post, share edits and suggestions in GitHub which when pulled the WordPress post will be updated automatically.</p>
<p>If a repository has files in the below structure,</p>
<pre><code>docs/
    guide/
        introduction.md
        getting-started.md
help/
    faq.md
</code></pre>
<p>Then below posts will be created like below (if permalinks are configured and the post type supports “hierarchy” i.e creating posts level by level (example: pages))</p>
<pre><code>https://example.com/docs/guide/introduction/
https://example.com/docs/guide/getting-started/
https://example.com/help/faq/
</code></pre>
<h3>🎲 What is the use of this plugin ?</h3>
<ul>
<li>Publish posts using the files in your GitHub repository.</li>
<li>Write your posts in Markdown format.</li>
<li>Write your posts on your desktop application (Notepad++, Sublime Text, Visual studio code).</li>
<li>Collaborate, involve communities on the files in GitHub and publish them on WordPress.</li>
<li>All the advantages of Git and it’s version management system.</li>
</ul>
<h3>🚀 Some use cases</h3>
<ul>
<li>Can be used for documentation posts, FAQs, Wikis etc.</li>
<li>Write blog posts.</li>
<li>Any articles which may need community involvement.</li>
</ul>
<h3>✨ Features</h3>
<ul>
<li>Markdown will be processed and post will be published as HTML.</li>
<li>Images used in the source file will be uploaded to WordPress.</li>
<li>Relative links are supported.</li>
<li>Set post properties like post status, title, order, category, tags etc, in the source file itself.</li>
<li>Webhook support (whenever repository is changed, it updates the plugin to pull the latest changes and publish the posts)</li>
<li>Add multiple repositories.</li>
<li>Publish to any post type.</li>
<li>Posts are published in hierarchial manner if they are under folders. Example: a file <code>dir1/hello.md</code> will be posted as <code>dir1/hello/</code> in WordPress if the post type supports hierarchy.</li>
<li>Support for post metadata like setting tags, categories, custom fields.</li>
</ul>
<h3>ℹ Note</h3>
<ul>
<li>Only Markdown files will be pulled and published right now</li>
<li>Posts won’t be deleted when it’s source file is deleted on GitHub.</li>
<li>It is preferred to have a permalink structure.</li>
<li>It is preferred to select a post type which supports hierarchy.</li>
<li>Images have to present only in <code>_images</code> folder in the repository root. Markdown files have to relatively use them in the file.</li>
</ul>
<h3>🥗 Recommendation</h3>
<p>It is recommended that a permalink structure is enabled in the WordPress site so that, if you have file under <code>docs/reference/my-post.md</code> then a post is published like <code>https://example.com/docs/reference/my-post/</code>. This will be the result when post type has hierarchy support. They will be posted level by level for every folder in the repository. The folder’s post will be taken from the <code>index.md</code> file if exists under that folder.</p>
<h3>🏃‍♂️ Using the plugin</h3>
<ol>
<li>Have a GitHub repository where all the source files (markdown files) are maintained (organized in folders if needed the exact structure)</li>
<li>In the plugin settings page, click add a new repository.</li>
<li>Enter the details of the repository to pull the posts from and under what post type to publish them.</li>
<li>Save the settings</li>
<li>Click “Pull the posts” and then “Pull only” changes. This will publish posts for all the markdown files.</li>
<li>To automatically update posts whenever repository is updated, configure webhook as mentioned in the settings page.</li>
</ol>
<h3>Links</h3>
<ul>
<li><a href="https://www.aakashweb.com/docs/git-it-write/" rel="nofollow ugc">Documentation</a></li>
<li><a href="https://www.aakashweb.com/forum/" rel="nofollow ugc">Support forum/Report bugs</a></li>
<li><a href="https://www.paypal.me/vaakash/" rel="nofollow ugc">Donate</a></li>
<li><a href="https://github.com/vaakash/git-it-write" rel="nofollow ugc">Contribute on GitHub</a></li>
</ul>


Git it Write – Write posts from GitHub

You will like it !

Sometimes commits and pushes don't reflect properly, but that's enough.
This is the way I wanted it.

Great

Publish markdown files present in a GitHub repository as posts to WordPress automatically

Label Blanc

<p>This plugin adds a new and improved “Save” button to the Post Edit screen that, in a single click, saves the current post and immediately takes you to your next action.</p>
<p>(<strong>WordPress 5 info:</strong> see below for particularities for WordPress 5.)</p>
<p>The following actions are available:</p>
<ul>
<li><strong>Save and New</strong>: in a single click, saves the current post and goes to New Post Screen.</li>
<li><strong>Save and Duplicate</strong>: saves the post, duplicates it and goes to this new post’s Edit Screen.</li>
<li><strong>Save and List</strong> (a.k.a. Save and Close): saves the post and goes to the Posts List.</li>
<li><strong>Save and Return</strong>: saves the post and returns you to the page where you were just before (no matter which page).</li>
<li><strong>Save and Next</strong>: saves the post and goes to the next post’s Edit Screen.</li>
<li><strong>Save and Previous</strong>: saves the post and goes to the previous post’s Edit Screen.</li>
<li><strong>Save and View</strong> (same or new window): saves the post and goes to the post’s frontend page. Can show the post in the same window or in a new one.</li>
</ul>
<p>This plugin saves you a lot of time when you have multiple posts, pages or custom posts to create or modify!</p>
<p>Works with pages, posts and custom post types!</p>
<p>Through the plugin’s settings page, you can choose which actions to show and which one to use as the button’s default action.</p>
<p><strong>WordPress 5 info</strong><br />
The plugin technically works with WordPress 5, but it doesn’t work with the new Gutenberg editor, which is the default editor for WordPress 5. You have to disable the Gutenberg editor to use this plugin.</p>
<p><strong>Want to help translate?</strong><br />
This plugin now uses the WordPress Translation Service for translations. <a href="https://translate.wordpress.org/projects/wp-plugins/improved-save-button" rel="nofollow ugc">Please visit the plugin’s page to submit your translation!</a></p>


Improved Save Button

Fantastic! Saves me loads of time.

Still works on WP 5.2.2, also works on custom post types that use /edit layout (e.g. Woocommerce products).

You saved me many hours of just watching the backend reload :D

This is a lifesaver

Improve your productivity with this "2-in-1" save button! It saves the post and immediately takes you to your next action.

Git it Write – Write posts from GitHub vs Improved Save Button