AI Scribe – Content Writer, OpenAI GPT
AI Scribe is an AI-driven content generator for WordPress that leverages the OpenAI API to produce high-quality, original content. It uses the same technology behind ChatGPT to create customized written content aligned with your objectives and requirements. The premium version of the tool can generate text as well as images. With this tool, you can easily create compelling and engaging content for your website, blog, or other digital platforms. Whether you are a blogger, marketer, or business owner, this content generator can help you save time and effort while creating high-quality content that resonates with your target audience. Built with React JS, AI Scribe features sleek controls and instant-loading template pages. Watch the demo videos below to know more. Template Dashboard Demo Generate a Post/Page in the Blocks Editor Upon activating the plugin, please navigate to the settings panel located at AI Scribe -> Settings in WP Admin and input the Open AI secret key. Be sure to also provide all necessary default values for fields temperature and language model before saving the changes. Generate content using the provided templates either in the AI Scribe app within WP Admin or directly in the blocks editor for a page or post. The AI Scribe app is also accessible in the sidebar of the post or page editor in WordPress. AI Scribe offers over 13 templates for content generation. To generate high-quality content, each template requires you to provide relevant information, such as the topic, target audience, and key points or takeaways. The plugin comes with more than 10 templates for content generation. Each template requires you provide relevant information like topic, target audience, key points or takeaways to generate quality content. Remember, the output quality is directly related to the quality of the input. This plugin is designed to help you offer the right input that optimizes AI’s potential. Each of the 13+ AI Scribe templates includes clear, comprehensive instructions on the information needed to be submitted to the AI for generating unique, high-quality content. Once you provide the additional information like language, max words, writing style and tone, hit the Generate button to create or rephrase content. The premium version of the plugin can do much more – * 20+ templates for content generation. The free version supports only 13 templates. * You can generate AI images with Generate Images template. You can choose the image style as well as the size. The image generated can be saved to media library and inserted into the posts editor. * Article Wizard Template lets you create articles step by step from title to outline to article. * Additional premium templates include Rewrite Content, Shorten Content, Listicle Ideas, AIDA Framework, Before After Bridge, Social Media Post with more planned in coming days. The Article Wizard Demo (Premium) Generating and Adding AI Images to a Post (Premium) Main Features 1. AI Scribe is a fast-loading, highly intuitive React JS app that allows you to harness AI for text generation, based on your chosen prompt, keywords, writing style, tone, and language. 2. The user interface features elegant controls and instant-loading template pages thanks to React JS. You’ll enjoy working with AI Scribe. 3. The 20+ templates are designed to help you create high-quality content. Each template includes detailed instructions on the input AI requires to generate content. AI Scribe guides you through the process step by step to ensure the AI understands your specific needs. We even provide a way to insert example instructions for most templates to help you get started quickly. It’s not just another gimmicky app that promises unrealistic results. 4. Choose between two apps: one as the AI Scribe page in WP Admin, and another as a sidebar app in the blocks editor for Posts and Pages. Using the sidebar AI Scribe app in the editor, you can insert the generated content into the blocks editor with just one click. 5. The 20+ templates cater to a wide range of needs. Generate blog posts, create content for your pages, rephrase/rewrite/expand/shorten/summarize sentences, or produce sales copy and marketing content for web pages or social media. 6. Customize the instructions sent to AI to obtain content tailored to your specific requirements. Most AI tools lack such granular control, but our tool strikes a balance by offering essential controls without overwhelming you. Template pages are thoughtfully designed to include only the crucial options needed for the AI to deliver outstanding results. 7. Ability to save the AI instructions (prompt) and reset the same to default. The plugin now lets you save the changes you make to the prompt of a template to suit your needs. You can reset to the default prompt any time in the future with a single click of a button. 8. AI Scribe makes creating quality content easier and more affordable than ever. If you’ve used content generation tools like Jasper/Jarvis, Copy AI, or Writesonic, you’ll find AI Scribe just as effective while saving you hundreds of dollars annually. With more templates and features planned, this tool will only improve over time. Upcoming Premium Features Ability to save and reset prompt for a template–Done An uber blog post template that generates a blog post step by step from title to sections to post paragraphs within a single window–Done Ability to create templates of one’s own and save the same. Ability to generate images and insert the same into the post/page editor–Done Elementor support. The sidebar app will be available for Elementor editor as well. Classic editor support. The sidebar app will be available for Classic editor as well. Many more including any templates or features users request for …. Support We provide support to the free version of the plugin in the dedicated support forum.
Top keywords
- ai27×2.80%
- content24×2.49%
- ai scribe14×1.45%
- scribe14×1.45%
- templates13×1.35%
- template12×1.24%
- editor11×1.14%
- generate11×1.14%
- post9×0.93%
- pages6×0.62%
- premium6×0.62%
- provide6×0.62%
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor
The most configurable way to leave the block editor behind. Activate it and everything block related is gone: the block editor, Global Styles, patterns, block widgets, the Site Editor and the block CSS and JavaScript that every page loads. From there you decide the scope: everywhere, or only for the post types, roles, templates and entries you choose. What this plugin removes: Core Gutenberg Features Gutenberg Block Editor (completely disabled) Full Site Editing (FSE) Global Styles and inline CSS Block-based Widget Editor (reverts to Classic Widgets) Block Patterns and Pattern Directory Theme.json support and processing Block Directory integration Site Editor functionality Performance Optimizations The block library CSS and JavaScript that every page loads The Global Styles inline CSS, which dequeuing the handle never reaches The block assets of any other plugin that registers blocks, on pages where no block appears The block editor assets in the admin, wherever the Classic Editor is the one opening WooCommerce Integration The block based product editor, which follows the same rules as any other post type The WooCommerce block styles and scripts, removed along with the rest of the block assets Nothing else: leave blocks on for products and the block product editor keeps working Admin Experience Removes the welcome panel that promotes the block editor Removes the Patterns submenu from the Appearance menu (WP 6.5+) Removes the Fonts submenu from the Appearance menu (WP 7.0+) Blocks access to Site Editor pages Shows activation success notice Warns you when a block theme is active Adds settings and support links to plugin actions A default that asks nothing, and a settings page for everything else – Activating the plugin disables the block editor and every block feature across the site, which is what most people install it for. The rest of this page is about wanting less than that. Full control when you need it – The settings page lives under Settings > No Gutenberg?, built around one master switch. Leave it on and the whole site keeps the complete disable. Turn it off and you decide where the block editor goes away: by post type, by user role, by page template or by individual entry. The site wide pieces (classic widgets, block patterns, frontend block assets, theme.json and the Site Editor) are then yours to keep or remove one by one. Every checkbox means the same thing, so no setting ever undoes another one. Switch editors entry by entry, where it makes sense – Editor switching is chosen per post type, right next to the rule that disables the block editor. Enable it for pages, for instance, and every page gets “Edit (Classic)” and “Edit (Blocks)” links in the list plus a switch inside both editors, while your posts stay untouched. Each entry remembers the editor chosen for it, and that choice beats the rules in both directions: one landing page can stay on the Classic Editor while the rest keep blocks, or the other way around. It tells you what it is doing – The settings screen opens with a status panel for your particular site: how many block patterns are being blocked, how much weight is off every page, whether your theme is a block theme, and how much of your published content is really built with blocks. That last number is the one that should decide whether you strip the block styles from the frontend or not, and no other plugin tells you. Built for agencies and managed sites – The whole configuration can be fixed from wp-config.php, and the settings screen locked as read only or hidden altogether, so a site you deliver keeps the setup you left behind. A whole network configured in one file – This is where the plugin stands alone. Every single setting it has, and not just which editor opens, can be written in wp-config.php, the same file every site of a multisite network reads. A network of a hundred sites is set up once, all of them with the same rules, all of them with the same block CSS gone, and none of them able to drift away from it. The plugin can also be network activated and left alone, because settings are stored per site, so a network can equally let each site decide for itself. Same mechanism as the locking above, and this is how it is written. One configuration for a whole network, or for a site you deliver Everything the settings screen does can also be written in wp-config.php, where nobody changes it by accident, and what you write there wins over whatever is stored in the database. It is the same file for every site of a multisite network, so it is also how you set up a network without repeating the configuration site by site. Add the lines you need above the comment that says “That’s all, stop editing! Happy publishing.” To disable Gutenberg everywhere and leave no settings screen for anyone to touch, which is the usual setup both for a network and for a site you hand over to a client: define( 'NO_GUTENBERG_OPTIONS', array( 'complete' => true ) ); define( 'NO_GUTENBERG_HIDE_SETTINGS', true ); Drop that second line and the settings page is still there, showing the configuration the site is really running, but read only. And if all you want is to lock the screen, leaving the configuration as each site has it stored: define( 'NO_GUTENBERG_LOCK_SETTINGS', true ); NO_GUTENBERG_OPTIONS takes any of the settings on the screen, so a selective setup is written the same way: define( 'NO_GUTENBERG_OPTIONS', array( 'complete' => false, 'disable_post_types' => array( 'post', 'page' ), 'disable_roles' => array( 'editor', 'author' ), 'frontend_css' => false, ) ); The keys are the settings on the screen. complete, widgets, patterns, frontend_css, theme_json, site_editor and fse_notices take true or false, while disable_post_types, disable_roles, disable_templates and switch_post_types take an array of slugs, and disable_ids an array of entry IDs. Any key you leave out keeps the value stored on the site. Note that defining NO_GUTENBERG_OPTIONS already turns the whole screen read only, so NO_GUTENBERG_LOCK_SETTINGS is not needed on top of it. It fits sites that: – Work better in the Classic Editor and want it back – Run classic themes and plugins that were never built around blocks – Are paying for block CSS and JavaScript on pages with no blocks in them – Need the Classic Editor for everyone except a few post types, roles or people – Are a multisite network that wants the same editing experience on every site Support Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need. Need help or have suggestions? Official website WordPress support forum YouTube channel Documentation and tutorials Love the plugin? Please leave us a 5-star review and help spread the word! About AyudaWP We are specialists in WordPress security, SEO, and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.