PROTOS TOC GENERATOR

Protos TOC Generator compatibility with REEID Translate

Protos TOC Generator compatibility with REEID Translate is being evaluated from available plugin evidence. {"task": "Research factual plugin behavior for compatibility context only. No specific visitor-facing translation surface is currently confirmed.

Visit Protos TOC Generator ↗

AWAITING VERIFICATION

What the available evidence establishes for Protos TOC Generator.

Official plugin information supports the compatibility context documented for this category.

AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.

PLUGIN PROFILE
Protos TOC Generator is documented in the Navigation category with 8 concrete capabilities identified in the current evidence.

EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.

COMPATIBILITY REVIEW

How Protos TOC Generator compatibility is evaluated

01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.

02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.

03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.

04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.

PLUGIN INTELLIGENCE

What the official plugin evidence shows

Plugin capabilities

  • {"task": "Research factual plugin behavior for compatibility context only.
  • Do not extract translation-surface observations.", "plugin_identity": {"name": "Protos TOC Generator", "slug": "protos-toc-generator", "homepage_url": "", "plugin_url": ""}, "official_search_domains": ["wordpress.org", "plugins.svn.wordpress.org"], "rules": ["Return one JSON object only.", "Use only facts supported by supplied plugin evidence or web research from the allowed official domains.", "Use web search only when supplied evidence is insufficient.", "For web research, use only first-party vendor/product documentation and WordPress.org sources within official_search_domains.", "Do not use reviews, blogs, forums, aggregators, search snippets, or third-party documentation as evidence.", "Do not invent plugin behavior, capabilities, settings, or integrations.", "Do not decide REEID compatibility, translation support, approval, or eligibility.", "Follow category_research.rules for what to investigate in this Integration Category.", "Return observations as an empty list.", "Return 4 to 8 concise high-value factual capabilities in features.", "Group related implementation details into broader capability statements.", "Prefer stable product capabilities over minor settings or repeated variations.", "Do not include ratings, installation counts, version requirements, or promotional claims.", "Use unknowns only for materially relevant facts that official evidence does not establish.", "seo_display_name must be the shortest distinctive search-facing product or brand identity that can be copied exactly as one contiguous phrase from plugin_identity.name.
  • Preserve the exact capitalization, spelling, and punctuation used in plugin_identity.name.
  • Never invent, rename, expand, normalize, lowercase, or substitute the plugin brand.
  • Remove generic leading or trailing descriptors when a shorter distinctive product or brand phrase is present, including terms such as Plugin, WordPress Plugin, Page Builder, Website Builder, WooCommerce, Forms, SEO, Addons, Widgets, Templates, Booking, Membership, or similar category/marketing wording.
  • The distinctive brand may appear at the beginning, middle, or end of plugin_identity.name; for example, a title shaped like generic description – Brand should return Brand when Brand is clearly the product identity.
  • When a short distinctive acronym, product token, or branded abbreviation appears after a separator and clearly identifies the plugin, prefer that exact token over the preceding generic description; for example Database Addon for Contact Form 7 – CFDB7 should return CFDB7.
  • Use plugin_identity.slug only as an identity clue, not as output text unless that exact casing and phrase also appears in plugin_identity.name.

Distinctive features
{"task": "Research factual plugin behavior for compatibility context only. Do not extract translation-surface observations.", "plugin_identity": {"name": "Protos TOC Generator", "slug": "protos-toc-generator", "homepage_url": "", "plugin_url": ""}, "official_search_domains": ["wordpress.org", "plugins.svn.wordpress.org"], "rules": ["Return one JSON object only.", "Use only facts supported by supplied plugin evidence or web research from the allowed official domains.", "Use web search only when supplied evidence is insufficient.", "For web research, use only first-party vendor/product documentation and WordPress.org sources within official_search_domains.", "Do not use reviews, blogs, forums, aggregators, search snippets, or third-party documentation as evidence.", "Do not invent plugin behavior, capabilities, settings, or integrations.", "Do not decide REEID compatibility, translation support, approval, or eligibility.", "Follow category_research.rules for what to investigate in this Integration Category.", "Return observations as an empty list.", "Return 4 to 8 concise high-value factual capabilities in features.", "Group related implementation details into broader capability statements.", "Prefer stable product capabilities over minor settings or repeated variations.", "Do not include ratings, installation counts, version requirements, or promotional claims.", "Use unknowns only for materially relevant facts that official evidence does not establish.", "seo_display_name must be the shortest distinctive search-facing product or brand identity that can be copied exactly as one contiguous phrase from plugin_identity.name. Preserve the exact capitalization, spelling, and punctuation used in plugin_identity.name. Never invent, rename, expand, normalize, lowercase, or substitute the plugin brand. Remove generic leading or trailing descriptors when a shorter distinctive product or brand phrase is present, including terms such as Plugin, WordPress Plugin, Page Builder, Website Builder, WooCommerce, Forms, SEO, Addons, Widgets, Templates, Booking, Membership, or similar category/marketing wording. The distinctive brand may appear at the beginning, middle, or end of plugin_identity.name; for example, a title shaped like generic description – Brand should return Brand when Brand is clearly the product identity. When a short distinctive acronym, product token, or branded abbreviation appears after a separator and clearly identifies the plugin, prefer that exact token over the preceding generic description; for example Database Addon for Contact Form 7 – CFDB7 should return CFDB7. Use plugin_identity.slug only as an identity clue, not as output text unless that exact casing and phrase also appears in plugin_identity.name. If no shorter distinctive product or brand phrase can be selected safely, return the full plugin_identity.name.", "seo_keyword_candidates must contain 2 to 4 concise plugin-specific identity phrases based on seo_display_name, plugin_identity.name, and plugin_identity.slug. When the slug corresponds to a brand or product phrase present in the official name, include that phrase as a candidate. Do not return generic category-only phrases and do not assert REEID compatibility, verification, translation support, or other unsupported state claims."], "category_research": {"integration_category": "Navigation", "mode": "compatibility_only", "rules": ["Research factual navigation-plugin behavior relevant to compatibility, including menu construction, navigation rendering, links, and URL handling.", "This Integration Category is compatibility-only.", "Do not research, infer, or emit translation-surface observations.", "Return observations as an empty list.", "Use features and unknowns only for factual compatibility context."], "evidence_focus": {"integration_category": "Navigation", "look_for_literal_terms": []}, "output_schema": {"observations": [{"text": "", "evidence": "", "source_url": ""}], "features": [], "unknowns": [], "seo_display_name": "", "seo_keyword_candidates": []}, "evidence": {"description": "Protos TOC Generator automatically creates a Table of Contents for your posts and pages by scanning for heading tags ( to ). It adds anchor links for smooth navigation within long articles.\n Features:\n– Automatically injects a TOC before the first heading\n– Smooth scrolling to heading sections\n– Supports heading levels h1 to h6\n– SEO-friendly anchor links\n– Easy styling and customization\n– Lightweight and no settings page\n License\n This plugin is licensed under the GPLv2 or later.", "sections": {"installation": "Upload the plugin folder to the /wp-content/plugins/ directory.\n Activate the plugin through the ‘Plugins’ menu in WordPress.\n Visit any post with headings — the TOC appears before the first heading.", "faq": "Can I disable TOC for specific posts?\n Not in this version. Let us know if you need this feature!\nCan I customize where the TOC appears?\n By default, it appears before the first heading. A shortcode version is coming soon.\nWill this work with any theme?\n Yes, it works with all standard themes and heading structures.", "screenshots": "Table of contents automatically inserted before the first heading.\n Smooth scrolling behavior on anchor clicks.1. Admin view for configurations"}, "readme_text": "=== Protos TOC Generator ===\nContributors: Protos Software\nTags: toc, table of contents, seo, navigation, headings\nRequires at least: 5.0\nTested up to: 7.0\nStable tag: 3.0\nRequires PHP: 7.2\nLicense: GPLv2 or later\nLicense URI: https://www.gnu.org/licenses/gpl-2.0.html\n\nAuto-generates a floating or inline table of contents with anchor links based on headings in your post. Improves readability and SEO.\n\n== Description ==\n\n**Protos TOC Generator** automatically creates a Table of Contents for your posts and pages by scanning for heading tags (“ to “). It adds anchor links for smooth navigation within long articles.\n\nFeatures:\n- Automatically injects a TOC before the first heading\n- Smooth scrolling to heading sections\n- Supports heading levels h1 to h6\n- SEO-friendly anchor links\n- Easy styling and customization\n- Lightweight and no settings page\n\n== Installation ==\n\n1. Upload the plugin folder to the `/wp-content/plugins/` directory.\n2. Activate the plugin through the ‘Plugins’ menu in WordPress.\n3. Visit any post with headings — the TOC appears before the first heading.\n\n== Frequently Asked Questions ==\n\n= Can I disable TOC for specific posts? =\nNot in this version. Let us know if you need this feature!\n\n= Can I customize where the TOC appears? =\nBy default, it appears before the first heading. A shortcode version is coming soon.\n\n= Will this work with any theme? =\nYes, it works with all standard themes and heading structures.\n\n== Screenshots ==\n\n1. Table of contents automatically inserted before the first heading.\n2. Smooth scrolling behavior on anchor clicks."}}}

CONTENT BOUNDARY

Protos TOC Generator capabilities and translation scope are documented separately.

The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.

Functional capability alone is not treated as evidence that a value should be translated.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

COMMON QUESTIONS

Protos TOC Generator and REEID Translate FAQ.

What does Protos TOC Generator do according to the available plugin evidence?

Protos TOC Generator has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.

Is a REEID translation surface currently confirmed for Protos TOC Generator?

No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.

What would establish translation scope for Protos TOC Generator?

The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.

RELATED GUIDES

Continue through the compatibility library.

INTEGRATION EVIDENCE

Evaluate Protos TOC Generator in a multilingual WordPress workflow.

REEID documents Protos TOC Generator functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.

Translation scope will be published when concrete visitor-facing content is established by evidence.

Shopping Cart
Scroll to Top