Disable Gutenberg vs Git it Write – Write posts from GitHub

This plugin disables the new Gutenberg Editor (aka Block Editor) and replaces it with the Classic Editor. You can disable Gutenberg completely, or selectively disable for posts, pages, roles, post types, and theme templates. Plus you can hide the Gutenberg nag, menu item, and more! ♠ The all-in-one, COMPLETE solution for handling Gutenberg ♠ Hide ALL traces of Gutenberg and replace with Classic Editor ♠ Restores original Edit Post screen (TinyMCE, meta boxes, etc.) The Disable Gutenberg plugin restores the classic (original) WordPress editor and the “Edit Post” screen. So you can continue using plugins and theme functions that extend the Classic Editor. Supports awesome features like Meta Boxes, Quicktags, Custom Fields, and everything else the Classic Editor can do. Easy to Use Just activate and done! The default plugin settings are configured to hide all traces of the Gutenberg Block Editor, and fully restore the original Classic Editor. Further options for customizing when/where Gutenberg is enabled are available in the plugin settings. ♠ Disable Block Widgets and restore Classic Widgets 🙂 Options Disable Gutenberg completely (all post types) Disable Gutenberg for any post type Disable Gutenberg for any user role Disable Gutenberg for any theme template Disable Gutenberg for any post/page IDs Disable Gutenberg admin notice (nag) Option to restore Classic Widgets Option to hide the plugin menu item Option to hide the Gutenberg plugin menu item (settings link) Adds “Classic Editor” link to each post on the Posts screen Adds item to the WP sidebar menu: “Add New (Classic)” Option to enable Custom Fields Meta Box for ACF Choose which editor to use for each post Whitelist any post title, slug, or ID Option to enable/disable frontend Gutenberg stylesheet ♠ Works same as Classic Editor plugin, but can do a LOT more! ♠ Lightweight and super fast, built with WP APIs 🙂 Fully configurable, enable or disable Gutenberg and restore the Classic Editor wherever is necessary. Automatically replaces Gutenberg with the Classic Editor. Features Super simple Clean, secure code Built with the WordPress API Lightweight, fast and flexible Regularly updated and “future proof” Works great with other WordPress plugins Plugin options configurable via settings screen Focused on flexibility, performance, and security One-click restore plugin default options Translation ready ♠ Works great with Google AMP and the WordPress AMP plugin Disable Gutenberg is developed and maintained by Jeff Starr, 15-year WordPress developer and book author. Super light & fast plugin, super easy on server resources! Why? Gutenberg is a useful editor but sometimes you want to disable it for specific posts, pages, user roles, post types, and/or theme templates. This plugin enables you to disable Gutenberg and replace it with the Classic Editor wherever you want. For example, lots of WordPress users already enjoy robust page-building functionality via one of the many great plugins like Composer or Elementor. So many options, no need to feel “locked in” to using Gutenberg! If you like Disable Gutenberg, please give it a 5-star rating, thank you! Privacy This plugin does not collect or store any user data. It does not set any cookies, and it does not connect to any third-party locations. Thus, this plugin does not affect user privacy in any way. Support development I develop and maintain this free plugin with love for the WordPress community. To show support, you can make a donation or purchase one of my books: The Tao of WordPress Digging into WordPress .htaccess made easy WordPress Themes In Depth Wizard’s SQL Recipes for WordPress And/or purchase one of my premium WordPress plugins: BBQ Pro – Blazing fast WordPress firewall Blackhole Pro – Automatically block bad bots Banhammer Pro – Monitor traffic and ban the bad guys GA Google Analytics Pro – Connect WordPress to Google Analytics Head Meta Pro – Ultimate Meta Tags for WordPress REST Pro Tools – Awesome tools for managing the WP REST API Simple Ajax Chat Pro – Unlimited chat rooms USP Pro – Unlimited front-end forms Links, tweets and likes also appreciated. Thanks! 🙂

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