Nota is a SaaS company building AI-enabled tools to streamline content creation and distribution. Their assistive AI tools help publishers, marketers and content creators generate headlines, summaries, SEO keywords and more.<\/p>\n\n
Nota is taking the pain points out of the content creation process so you can focus on what really matters: your story.<\/p>\n\n
The Nota plugin is a time-saving tool for editorial, marketing and content teams focused on optimizations\u2014generating headlines, summaries, top quotes, key points, SEO keywords and categories. The plugin utilizes large language models to generate AI responses, returning robust copy results.<\/p>\n\n
Nota runs text through uber-powerful AI and ML tools to break down all that content into workable outputs. No prompts or queries, no AI learning curves, just quick-and-easy text applications. Analyze a post and tailor the outputs for more, less or just different results with the push of a button. If you\u2019re looking for a human touch, you can edit the outputs directly to your liking.<\/p>\n\n
When users choose to use outputs provided by Nota, the plugin will update the appropriate fields on the post. For example, selecting a \"Headline\" will update the post title.<\/p>\n\n
This behaviour can be changed if custom fields are required, by using the @wordpress\/hooks<\/a> functionality.<\/p>\n\n Each field has a corresponding getter and setter function. The filter names follow the pattern: For example, to use a custom field for the title, you would implement the following:<\/p>\n\n Nota supports restricting plugin access to specific users via a WordPress filter.<\/p>\n\n For advanced use cases, you can use the Example: Allow access based on a custom user profile field:<\/strong><\/p>\n\n Example: Allow access based on email domain (e.g., for pilot rollouts):<\/strong><\/p>\n\n Example: Combine default access with additional custom logic:<\/strong><\/p>\n\n Nota provides several filters for customization:<\/p>\n\n Controls whether a user can access Nota tools. See \"Access Control\" section above.<\/p>\n\n Customize which post types display Nota tools:<\/p>\n\n Enable or disable specific Nota tool components:<\/p>\n\n This is a beta tool that requires paid account access. Click here<\/a> to contact Nota about creating your account before proceeding with the steps below.<\/p>\n\nnota.postData.<fieldName>.get<\/code> and nota.postData.<fieldName>.set<\/code>. The following filters are available:<\/p>\n\n\n
nota.postData.title.get<\/code><\/li>\nnota.postData.title.set<\/code><\/li>\nnota.postData.excerpt.get<\/code><\/li>\nnota.postData.excerpt.set<\/code><\/li>\nnota.postData.slug.get<\/code><\/li>\nnota.postData.slug.set<\/code><\/li>\nnota.postData.metaTitle.get<\/code><\/li>\nnota.postData.metaTitle.set<\/code><\/li>\nnota.postData.metaDescription.get<\/code><\/li>\nnota.postData.metaDescription.set<\/code><\/li>\n<\/ul>\n\nconst customTitleMetaKey = 'my-custom-meta-key'\n\nconst getTitle = () => {\n return wp.data.select('core\/editor').getEditedPostAttribute('meta')[customTitleMetaKey]\n}\nwp.hooks.addFilter('nota.postData.title.get', 'custom\/namespace', () => getTitle )\n\nconst setTitle = (nextValue) => {\n wp.data.dispatch('core\/editor').editPost({ meta: { [customTitleMetaKey]: nextValue } })\n}\nwp.hooks.addFilter('nota.postData.title.set', 'custom\/namespace', () => setTitle )\n<\/code><\/pre>\n\nAccess Control<\/h3>\n\n
nota_tools_user_allowed<\/code> filter to implement custom access logic:<\/p>\n\n<?php\n\/**\n * Filter: nota_tools_user_allowed\n * \n * @param bool $allowed Whether the user is currently allowed (default: user can edit_posts).\n * @param WP_User $user The current user object.\n * @param array $context Context about where the check is being made.\n * Keys:\n * - 'area': The feature area being accessed.\n * Values: 'post_tools', 'draft', 'dashboard', 'news'.\n * - 'post_id': The post ID if applicable.\n *\/\nadd_filter( 'nota_tools_user_allowed', 'my_custom_nota_access', 10, 3 );\n<\/code><\/pre>\n\n<?php\nadd_filter( 'nota_tools_user_allowed', function( $allowed, $user, $context ) {\n \/\/ Only allow users with 'nota_access' meta set to 'yes'\n $nota_access = get_user_meta( $user->ID, 'nota_access', true );\n return $nota_access === 'yes';\n}, 10, 3 );\n<\/code><\/pre>\n\n<?php\nadd_filter( 'nota_tools_user_allowed', function( $allowed, $user, $context ) {\n \/\/ Only allow users with @californiapost.com email addresses\n $email = $user->user_email;\n return substr( $email, -strlen( '@californiapost.com' ) ) === '@californiapost.com';\n}, 10, 3 );\n<\/code><\/pre>\n\n<?php\nadd_filter( 'nota_tools_user_allowed', function( $allowed, $user, $context ) {\n \/\/ If already allowed by default, also require specific role\n if ( $allowed ) {\n return in_array( 'editor', $user->roles, true );\n }\n return false;\n}, 10, 3 );\n<\/code><\/pre>\n\nDeveloper Filters<\/h3>\n\n
nota_tools_user_allowed<\/h4>\n\n
nota_tools_supported_post_types<\/h4>\n\n
<?php\nadd_filter( 'nota_tools_supported_post_types', function( $post_types ) {\n \/\/ Add custom 'article' post type\n $post_types[] = 'article';\n return $post_types;\n} );\n<\/code><\/pre>\n\nnota_tools_supported_components<\/h4>\n\n
<?php\nadd_filter( 'nota_tools_supported_components', function( $components ) {\n \/\/ Disable hashtags component\n $components['hashtags'] = false;\n return $components;\n} );\n<\/code><\/pre>\n\n\n\n