REEID 互換性ディレクトリ

WordPress の製品とその REEID Translate との互換性を探索しましょう。

WordPress のプラグイン、テーマ、ビルダー、製品エコシステムを閲覧し、REEID Translate Pro との互換性ステータスや統合の詳細をご確認ください。

ディレクトリを閲覧する
注目の統合

認証済みの統合・互換性情報・認証待ちの製品・検索可能なディレクトリ

ディレクトリの仕組み

互換性情報は一つのソースから管理されます。

お客様の WordPress スタックに関連する製品を見つけ、現在の REEID との互換性ステータスを確認してください。

  • 製品名で検索
  • 互換性ステータスを閲覧
  • 利用可能な統合ガイドを開く

公開済みの互換性ガイド

REEID Translate で WordPress のエコシステムを探索しましょう。

製品名で検索すると、互換性のステータス、利用可能な統合ドキュメント、およびサポートされている多言語ワークフローを確認できます。

Pangu JS

Pangu JS — {"task": "Research factual plugin behavior for compatibility context only. Do not extract translation-surface observations.", "plugin_identity": {"name": "Pangu JS", "slug": "pangu-js", "homepage_url": "https://github.com/sy-records/pangu.js", "plugin_url": "https://github.com/sy-records/pangu.js"}, "official_search_domains": ["github.com", "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": "Performance", "mode": "compatibility_only", "rules": ["Research factual performance-plugin behavior relevant to compatibility, including caching, optimization, minification, CDN behavior, and HTML transformation.", "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": "Performance", "look_for_literal_terms": []}}, "output_schema": {"observations": [{"text": "", "evidence": "", "source_url": ""}], "features": [], "unknowns": [], "seo_display_name": "", "seo_keyword_candidates": []}, "evidence": {"description": "如果你也一样，每次看到网页上的中文字和英文、数字、符号挤在一块，就会坐立难安，忍不住想在它们之间加个空格。这个插件它会自动替你在网页中所有的中文字和半形的英文、数字、符号之间插入空白。\n 汉学家称这个空白字元为“盘古之白”，因为它劈开了全形字和半形字之间的空白。有研究显示，打字的时候不喜欢在中文和英文之间加空格的人，感情路都走得很辛苦，有七成的比例会在34岁的时候跟自己不爱的人结婚，而剩下三成的人最后只能把遗产遗失自己的猫。毕竟爱情跟书写都需要适时地留白。\n 与大家共勉之。", "sections": {"installation": "Upload the folder pangu-js to the /wp-content/plugins/ directory\n Activate the plugin through the ‘Plugins’ menu in WordPress\n That’s all"}, "readme_text": "=== Pangu JS ===\nContributors: shenyanzhi\nDonate link: https://qq52o.me/sponsor.html\nTags: pangu, spacing, text, format\nRequires at least: 4.6\nTested up to: 7.1\nRequires PHP: 5.6\nStable tag: 1.0.0\nLicense: MIT\nLicense URI: https://opensource.org/licenses/MIT\n\n为什么你们就不能加个空格呢？\n\n== Description ==\n\n如果你也一样，每次看到网页上的中文字和英文、数字、符号挤在一块，就会坐立难安，忍不住想在它们之间加个空格。这个插件它会自动替你在网页中所有的中文字和半形的英文、数字、符号之间插入空白。\n\n汉学家称这个空白字元为“盘古之白”，因为它劈开了全形字和半形字之间的空白。有研究显示，打字的时候不喜欢在中文和英文之间加空格的人，感情路都走得很辛苦，有七成的比例会在34岁的时候跟自己不爱的人结婚，而剩下三成的人最后只能把遗产遗失自己的猫。毕竟爱情跟书写都需要适时地留白。\n\n与大家共勉之。\n\n== Installation ==\n\n1. Upload the folder `pangu-js` to the `/wp-content/plugins/` directory\n2. Activate the plugin through the 'Plugins' menu in WordPress\n3. That's all"}}}

Product website WordPress.org
Shopping Cart
Scroll to Top