Repository navigation
Optimize 72 Email Java pages - #93
Merged
Merged
Conversation
…email-java-exchange-appointments-management/_index.md - - Updated title and H1 to include primary keyword in sentence case. - Added front‑matter fields (lastmod, tags, og_title, og_description, og_image_alt) with primary & secondary keywords. - Inserted Quick Answers, definition anchors, quantified claims, and a FAQ section for AEO/GEO compliance. - Added direct‑answer paragraph after each question‑style H2 and definition sentence before first use of `IEWSClient`. - Included trust‑signal block with last updated date, tested version, and author. - Rewrote introductory and concluding paragraphs for better engagement while preserving all original placeholders and shortcodes.
…email-java-exchange-messages-listing/_index.md - - Updated front matter with current date, OG fields, keywords, and tags. - Rewrote title and headings to embed the primary keyword naturally. - Added Quick Answers, definition anchors, direct answer paragraphs, and FAQ sections for AEO/GEO compliance. - Integrated quantified claims and authoritative framing throughout. - Preserved all original markdown links, placeholders, and Hugo shortcodes exactly as required.
…email-java-exchange-server-connection/_index.md - - Updated title, meta description, and front‑matter to embed primary keyword “aspose email java”. - Added Open Graph fields, tags, and lastmod date for social sharing and freshness. - Inserted Quick Answers and expanded FAQ sections for AEO compliance. - Created question‑based H2 with direct answer paragraph and definition anchors for GEO. - Replaced vague statements with quantified claims and authoritative framing. - Enriched introductions, practical use‑cases, and performance tips while preserving all original links, placeholders, and shortcodes.
adil-aspose
approved these changes
Oct 3, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 10 |
| Total | 100/100 (capped from 173) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 12 |
| Clarity & readability (max 20) | 9 |
| SEO quality (max 20) | 14 |
| Actionability (max 20) | 7 |
| Content uniqueness (max 15) | 8 |
Issues:
- Technical explanations are sparse; API methods, required imports, and error‑handling guidance are absent.
- Title contains product-relevant keywords (API name, format, or action verb)
- Steps are not enumerated or described; developers cannot reproduce the task without the missing implementation details.
- Headings and prose do not fully adhere to the Google Developer Documentation style (e.g., missing sentence‑case headings, second‑person voice).
- Actionable steps are missing, preventing developers from reproducing the task.
- Steps are too abstract; developers cannot copy‑paste a working example.
- Description contains product-relevant keywords
- Content is incomplete – the main tutorial body is truncated and missing essential code snippets and configuration details.
- Content is truncated – essential sections such as environment setup, code examples for creating, updating, listing, and deleting appointments are missing.
- The tutorial body is truncated; no Maven dependency snippet, connection code, or folder‑listing logic is present.
- Writing does not fully follow the Google Developer Documentation style (sentence‑case headings, consistent second‑person voice, and clear link text).
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Content is truncated – essential sections such as environment setup, code examples for creating, updating, listing, and deleting appointments are missing.⚠️ Steps are not enumerated or described; developers cannot reproduce the task without the missing implementation details.⚠️ Technical explanations are sparse; API methods, required imports, and error‑handling guidance are absent.
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ The tutorial body is truncated; no Maven dependency snippet, connection code, or folder‑listing logic is present.⚠️ Headings and prose do not fully adhere to the Google Developer Documentation style (e.g., missing sentence‑case headings, second‑person voice).⚠️ Actionable steps are missing, preventing developers from reproducing the task.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Content is incomplete – the main tutorial body is truncated and missing essential code snippets and configuration details.⚠️ Writing does not fully follow the Google Developer Documentation style (sentence‑case headings, consistent second‑person voice, and clear link text).⚠️ Steps are too abstract; developers cannot copy‑paste a working example.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 3, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 10 |
| Total | 100/100 (capped from 173) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 14 |
| Clarity & readability (max 20) | 9 |
| SEO quality (max 20) | 16 |
| Actionability (max 20) | 7 |
| Content uniqueness (max 15) | 8 |
Issues:
- Headings and narrative do not fully follow Google Developer Documentation style (e.g., missing sentence‑case headings, inconsistent second‑person voice)
- The tutorial content is truncated; essential code snippets and configuration details are missing.
- The main body of the tutorial is incomplete – no code samples, no step‑by‑step instructions, and the introduction is cut off.
- Core tutorial body is truncated – missing setup steps, code snippets, and detailed guidance
- Title contains product-relevant keywords (API name, format, or action verb)
- Key concepts (e.g., Maven dependency, licensing, SSL handling) are mentioned only in metadata, not explained in the article.
- Steps are vague and do not provide complete, runnable examples.
- Inconsistent naming (IESWClient vs IEWSClient) and minor grammatical issues.
- Headings are not consistently sentence‑case and some sentences contain hedging language.
- Description contains product-relevant keywords
- Insufficient explanation of key concepts (e.g., no definition of Aspose.Email classes, no discussion of authentication options beyond a brief mention)
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Core tutorial body is truncated – missing setup steps, code snippets, and detailed guidance⚠️ Headings and narrative do not fully follow Google Developer Documentation style (e.g., missing sentence‑case headings, inconsistent second‑person voice)⚠️ Insufficient explanation of key concepts (e.g., no definition of Aspose.Email classes, no discussion of authentication options beyond a brief mention)
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ The main body of the tutorial is incomplete – no code samples, no step‑by‑step instructions, and the introduction is cut off.⚠️ Headings are not consistently sentence‑case and some sentences contain hedging language.⚠️ Key concepts (e.g., Maven dependency, licensing, SSL handling) are mentioned only in metadata, not explained in the article.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The tutorial content is truncated; essential code snippets and configuration details are missing.⚠️ Inconsistent naming (IESWClient vs IEWSClient) and minor grammatical issues.⚠️ Steps are vague and do not provide complete, runnable examples.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 3, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 10 |
| Total | 100/100 (capped from 173) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 13 |
| Clarity & readability (max 20) | 9 |
| SEO quality (max 20) | 15 |
| Actionability (max 20) | 7 |
| Content uniqueness (max 15) | 6 |
Issues:
- Headings and sentences do not consistently follow the Google Developer Documentation style (e.g., mixed case, missing second‑person voice).
- Writing does not consistently follow the Google Developer Documentation style (e.g., headings are not sentence‑case, second‑person voice is missing).
- Technical details are vague; no API usage, method signatures, or error‑handling guidance is shown.
- Actionable guidance is insufficient – developers cannot reproduce the solution without the missing implementation details.
- Description contains product-relevant keywords
- Stylistic issues: headings are not consistently sentence‑case, and some sentences contain hedging language.
- The body of the tutorial is truncated; no code samples, configuration steps, or detailed explanations are present.
- Title contains product-relevant keywords (API name, format, or action verb)
- Core tutorial content is missing or incomplete; no code snippets, import statements, or full example workflow.
- Steps are vague (e.g., “Use the static
EWSClient.getEWSClientfactory method”) without showing parameters, handling of credentials, or verification of connection. - The main content is truncated; essential sections such as environment setup, code snippets, and step‑by‑step instructions are missing.
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The main content is truncated; essential sections such as environment setup, code snippets, and step‑by‑step instructions are missing.⚠️ Technical details are vague; no API usage, method signatures, or error‑handling guidance is shown.⚠️ Headings and sentences do not consistently follow the Google Developer Documentation style (e.g., mixed case, missing second‑person voice).
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ The body of the tutorial is truncated; no code samples, configuration steps, or detailed explanations are present.⚠️ Writing does not consistently follow the Google Developer Documentation style (e.g., headings are not sentence‑case, second‑person voice is missing).⚠️ Actionable guidance is insufficient – developers cannot reproduce the solution without the missing implementation details.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Core tutorial content is missing or incomplete; no code snippets, import statements, or full example workflow.⚠️ Steps are vague (e.g., “Use the staticEWSClient.getEWSClientfactory method”) without showing parameters, handling of credentials, or verification of connection.⚠️ Stylistic issues: headings are not consistently sentence‑case, and some sentences contain hedging language.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 3, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 11 |
| Total | 100/100 (capped from 174) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 14 |
| Clarity & readability (max 20) | 9 |
| SEO quality (max 20) | 15 |
| Actionability (max 20) | 8 |
| Content uniqueness (max 15) | 8 |
Issues:
- Title contains product-relevant keywords (API name, format, or action verb)
- Description contains product-relevant keywords
- Insufficient explanation of required prerequisites (e.g., Maven dependency, licensing, authentication).
- Insufficient explanation of API classes and methods; readers cannot reliably implement the solution.
- Writing contains awkward phrasing (e.g., “manage exchange appointments java”) and occasional passive voice.
- Steps are truncated, missing code snippets, import statements, and error‑handling guidance.
- Technical details are incomplete and contain typos (e.g., "IESWClient" vs "IEWSClient").
- The core tutorial content is truncated; missing environment setup, code examples, and detailed steps.
- Headings are not consistently sentence‑cased and the prose contains truncations and vague statements.
- Headings are not consistently sentence‑case and some sections are cut off, reducing readability.
- Main body is incomplete – missing code examples, configuration details, and full step‑by‑step guidance.
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The core tutorial content is truncated; missing environment setup, code examples, and detailed steps.⚠️ Writing contains awkward phrasing (e.g., “manage exchange appointments java”) and occasional passive voice.⚠️ Insufficient explanation of API classes and methods; readers cannot reliably implement the solution.
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ Main body is incomplete – missing code examples, configuration details, and full step‑by‑step guidance.⚠️ Headings are not consistently sentence‑cased and the prose contains truncations and vague statements.⚠️ Insufficient explanation of required prerequisites (e.g., Maven dependency, licensing, authentication).
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Technical details are incomplete and contain typos (e.g., "IESWClient" vs "IEWSClient").⚠️ Steps are truncated, missing code snippets, import statements, and error‑handling guidance.⚠️ Headings are not consistently sentence‑case and some sections are cut off, reducing readability.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 3, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 10 |
| Total | 100/100 (capped from 173) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 12 |
| Clarity & readability (max 20) | 9 |
| SEO quality (max 20) | 15 |
| Actionability (max 20) | 7 |
| Content uniqueness (max 15) | 6 |
Issues:
- Lacks clear, actionable steps; developers cannot accomplish the task as presented.
- Description contains product-relevant keywords
- Typographical errors (e.g., "IESWClient" vs. "IEWSClient") and inconsistent naming can confuse readers.
- Lacks clear, actionable guidance – no full example of creating the EWSClient, handling authentication, or disposing resources.
- The article appears truncated, making it impossible to assess completeness or correctness of the implementation.
- Core tutorial body is incomplete – no code samples, configuration steps, or explanation of the Aspose.Email API.
- Missing core content: no code snippets, no step‑by‑step instructions, and no discussion of required configuration (e.g., authentication, service URL).
- Headings and prose do not follow the Google Developer Documentation style (sentence‑case, second‑person, active voice).
- Headings are not in sentence case and some phrasing does not follow the Google Developer Documentation style (e.g., use of passive voice, hedging language).
- The tutorial content is incomplete; key sections such as code snippets, full step‑by‑step instructions, and sample output are missing.
- Title contains product-relevant keywords (API name, format, or action verb)
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Missing core content: no code snippets, no step‑by‑step instructions, and no discussion of required configuration (e.g., authentication, service URL).⚠️ Headings are not in sentence case and some phrasing does not follow the Google Developer Documentation style (e.g., use of passive voice, hedging language).⚠️ The article appears truncated, making it impossible to assess completeness or correctness of the implementation.
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ Core tutorial body is incomplete – no code samples, configuration steps, or explanation of the Aspose.Email API.⚠️ Headings and prose do not follow the Google Developer Documentation style (sentence‑case, second‑person, active voice).⚠️ Lacks clear, actionable steps; developers cannot accomplish the task as presented.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The tutorial content is incomplete; key sections such as code snippets, full step‑by‑step instructions, and sample output are missing.⚠️ Typographical errors (e.g., "IESWClient" vs. "IEWSClient") and inconsistent naming can confuse readers.⚠️ Lacks clear, actionable guidance – no full example of creating the EWSClient, handling authentication, or disposing resources.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 3, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 10 |
| Total | 100/100 (capped from 173) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 15 |
| Clarity & readability (max 20) | 11 |
| SEO quality (max 20) | 16 |
| Actionability (max 20) | 7 |
| Content uniqueness (max 15) | 7 |
Issues:
- Headings and title use lower‑case terms (e.g., "exchange") instead of sentence case, and some phrasing is vague
- Description contains product-relevant keywords
- The article is incomplete – the introduction and code snippets are truncated, leaving critical implementation details missing.
- Headings and prose do not follow the Google Developer Documentation style (sentence‑case, second‑person, active voice).
- Lack of explicit setup instructions (Maven dependency, authentication configuration) reduces actionable value
- Body of the tutorial is truncated – missing code snippets, detailed steps, and complete explanations
- Step descriptions are vague and some sentences are cut off (e.g., the second HowTo step ends abruptly).
- Content body is truncated; no code snippets, Maven dependency details, or configuration steps are present.
- Stylistic issues: headings are not consistently sentence‑case, and some jargon (e.g., "IEWSClient") is not introduced before use.
- Title contains product-relevant keywords (API name, format, or action verb)
- Missing explanations of key concepts (e.g., what a public folder is, how to obtain credentials, handling SSL).
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Body of the tutorial is truncated – missing code snippets, detailed steps, and complete explanations⚠️ Headings and title use lower‑case terms (e.g., "exchange") instead of sentence case, and some phrasing is vague⚠️ Lack of explicit setup instructions (Maven dependency, authentication configuration) reduces actionable value
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ Content body is truncated; no code snippets, Maven dependency details, or configuration steps are present.⚠️ Headings and prose do not follow the Google Developer Documentation style (sentence‑case, second‑person, active voice).⚠️ Missing explanations of key concepts (e.g., what a public folder is, how to obtain credentials, handling SSL).
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The article is incomplete – the introduction and code snippets are truncated, leaving critical implementation details missing.⚠️ Step descriptions are vague and some sentences are cut off (e.g., the second HowTo step ends abruptly).⚠️ Stylistic issues: headings are not consistently sentence‑case, and some jargon (e.g., "IEWSClient") is not introduced before use.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 4, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 10 |
| Total | 100/100 (capped from 173) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 12 |
| Clarity & readability (max 20) | 9 |
| SEO quality (max 20) | 15 |
| Actionability (max 20) | 8 |
| Content uniqueness (max 15) | 7 |
Issues:
- Headings and prose do not fully follow the Google Developer Documentation style (e.g., missing sentence‑case, second‑person voice).
- The tutorial lacks concrete code snippets, full configuration details, and error‑handling guidance, making it hard for developers to follow.
- Lacks actionable steps, code snippets, and explanations of API classes/methods, reducing technical accuracy and usability.
- Core tutorial body (introduction, code samples, step‑by‑step instructions) is incomplete or missing.
- Title contains product-relevant keywords (API name, format, or action verb)
- The main content is truncated; essential sections such as environment setup, code samples, and detailed procedures are missing.
- Key typographical errors (e.g., "IESWClient" instead of "IEWSClient") and truncated sentences reduce technical credibility.
- Insufficient technical detail to verify API usage; no Maven dependency snippet or sample code shown.
- Headings and phrasing (e.g., "manage exchange appointments java") are awkward and do not follow sentence‑case or second‑person style guidelines.
- The introductory paragraph is cut off, and several steps are incomplete, leaving gaps in the workflow.
- Description contains product-relevant keywords
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The main content is truncated; essential sections such as environment setup, code samples, and detailed procedures are missing.⚠️ Headings and phrasing (e.g., "manage exchange appointments java") are awkward and do not follow sentence‑case or second‑person style guidelines.⚠️ Lacks actionable steps, code snippets, and explanations of API classes/methods, reducing technical accuracy and usability.
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ Core tutorial body (introduction, code samples, step‑by‑step instructions) is incomplete or missing.⚠️ Insufficient technical detail to verify API usage; no Maven dependency snippet or sample code shown.⚠️ Headings and prose do not fully follow the Google Developer Documentation style (e.g., missing sentence‑case, second‑person voice).
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Key typographical errors (e.g., "IESWClient" instead of "IEWSClient") and truncated sentences reduce technical credibility.⚠️ The tutorial lacks concrete code snippets, full configuration details, and error‑handling guidance, making it hard for developers to follow.⚠️ The introductory paragraph is cut off, and several steps are incomplete, leaving gaps in the workflow.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 4, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 10 |
| Total | 100/100 (capped from 173) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 15 |
| Clarity & readability (max 20) | 11 |
| SEO quality (max 20) | 14 |
| Actionability (max 20) | 7 |
| Content uniqueness (max 15) | 8 |
Issues:
- Main body is incomplete; essential sections such as code snippets, configuration steps, and explanation of API calls are missing.
- Writing does not fully follow the Google Developer Documentation style (mixed tense, some hedging, headings not consistently sentence‑case).
- The main content is truncated; essential code snippets, configuration steps, and full explanations are missing.
- Description contains product-relevant keywords
- Actionable guidance is insufficient – no clear, ordered steps, sample projects, or troubleshooting tips.
- Actionability is low – without full examples or a clear workflow, readers cannot accomplish the task.
- The main tutorial body is truncated; no code snippets, imports, or full example are shown.
- Writing does not fully adhere to the Google Developer Documentation style (headings are not consistently sentence‑case, some passive voice, and missing explanatory context for acronyms).
- Title contains product-relevant keywords (API name, format, or action verb)
- Clarity suffers because headings and sentences are cut off, and there is no consistent second‑person, active‑voice style throughout.
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The main content is truncated; essential code snippets, configuration steps, and full explanations are missing.⚠️ Writing does not fully adhere to the Google Developer Documentation style (headings are not consistently sentence‑case, some passive voice, and missing explanatory context for acronyms).⚠️ Actionable guidance is insufficient – no clear, ordered steps, sample projects, or troubleshooting tips.
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ Main body is incomplete; essential sections such as code snippets, configuration steps, and explanation of API calls are missing.⚠️ Clarity suffers because headings and sentences are cut off, and there is no consistent second‑person, active‑voice style throughout.⚠️ Actionability is low – without full examples or a clear workflow, readers cannot accomplish the task.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The main tutorial body is truncated; no code snippets, imports, or full example are shown.⚠️ Writing does not fully follow the Google Developer Documentation style (mixed tense, some hedging, headings not consistently sentence‑case).
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 4, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 10 |
| Total | 100/100 (capped from 173) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 12 |
| Clarity & readability (max 20) | 9 |
| SEO quality (max 20) | 15 |
| Actionability (max 20) | 6 |
| Content uniqueness (max 15) | 6 |
Issues:
- Key concepts such as authentication, appointment creation, updating, listing, and deletion are not demonstrated, reducing actionability and technical depth.
- Some headings and bullet points are incomplete, and the article does not follow the full Google Developer Documentation style (e.g., missing sentence‑case headings, descriptive link text).
- Description contains product-relevant keywords
- Title contains product-relevant keywords (API name, format, or action verb)
- Headings and prose do not fully adhere to the Google Developer Documentation style (missing sentence‑case, second‑person voice, and clear actionable steps).
- Steps are not detailed enough for a developer to reproduce the connection without external references.
- The main body of the tutorial is truncated; there are no code samples, step‑by‑step instructions, or complete explanations of the Aspose.Email API.
- The tutorial content is truncated; no code snippets, configuration steps, or example output are present.
- The content is truncated; essential code snippets, import statements, and error‑handling guidance are missing.
- Insufficient explanation of required prerequisites (e.g., Maven dependency details, licensing, SSL handling) within the body.
- Typographical error "IESWClient" instead of "IEWSClient" and incomplete sentences reduce technical credibility.
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The main body of the tutorial is truncated; there are no code samples, step‑by‑step instructions, or complete explanations of the Aspose.Email API.⚠️ Key concepts such as authentication, appointment creation, updating, listing, and deletion are not demonstrated, reducing actionability and technical depth.⚠️ Some headings and bullet points are incomplete, and the article does not follow the full Google Developer Documentation style (e.g., missing sentence‑case headings, descriptive link text).
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ The tutorial content is truncated; no code snippets, configuration steps, or example output are present.⚠️ Headings and prose do not fully adhere to the Google Developer Documentation style (missing sentence‑case, second‑person voice, and clear actionable steps).⚠️ Insufficient explanation of required prerequisites (e.g., Maven dependency details, licensing, SSL handling) within the body.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The content is truncated; essential code snippets, import statements, and error‑handling guidance are missing.⚠️ Typographical error "IESWClient" instead of "IEWSClient" and incomplete sentences reduce technical credibility.⚠️ Steps are not detailed enough for a developer to reproduce the connection without external references.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 4, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 9 |
| Total | 100/100 (capped from 172) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 13 |
| Clarity & readability (max 20) | 9 |
| SEO quality (max 20) | 14 |
| Actionability (max 20) | 6 |
| Content uniqueness (max 15) | 6 |
Issues:
- Description contains product-relevant keywords
- Headings are not consistently sentence‑cased and the prose does not fully follow the Google Developer Documentation style (second‑person, active voice, no hedging).
- Headings and sentences do not consistently follow the Google Developer Documentation style (e.g., missing sentence‑case headings, occasional passive voice).
- The body of the tutorial is incomplete – key sections such as environment setup, code samples for creating, updating, listing, and deleting appointments are missing.
- The tutorial body is truncated; no code snippets, import statements, or full example are provided.
- Missing explanations of required Maven/Gradle dependencies, SSL/TLS settings, and handling of common connection errors.
- Missing explanations of required classes, authentication setup, and error handling, making the guide non‑actionable.
- Insufficient technical detail makes it impossible for a developer to follow the guide without additional resources.
- The tutorial content is truncated – no code examples, configuration details, or complete step list are present.
- Title contains product-relevant keywords (API name, format, or action verb)
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The body of the tutorial is incomplete – key sections such as environment setup, code samples for creating, updating, listing, and deleting appointments are missing.⚠️ Insufficient technical detail makes it impossible for a developer to follow the guide without additional resources.⚠️ Headings and sentences do not consistently follow the Google Developer Documentation style (e.g., missing sentence‑case headings, occasional passive voice).
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ The tutorial content is truncated – no code examples, configuration details, or complete step list are present.⚠️ Headings are not consistently sentence‑cased and the prose does not fully follow the Google Developer Documentation style (second‑person, active voice, no hedging).⚠️ Missing explanations of required classes, authentication setup, and error handling, making the guide non‑actionable.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The tutorial body is truncated; no code snippets, import statements, or full example are provided.⚠️ Missing explanations of required Maven/Gradle dependencies, SSL/TLS settings, and handling of common connection errors.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 4, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 11 |
| Total | 100/100 (capped from 174) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 12 |
| Clarity & readability (max 20) | 9 |
| SEO quality (max 20) | 15 |
| Actionability (max 20) | 8 |
| Content uniqueness (max 15) | 7 |
Issues:
- Title contains product-relevant keywords (API name, format, or action verb)
- The content is truncated; essential code snippets, import statements, and full usage examples are missing.
- The main body of the tutorial is truncated; code examples and step‑by‑step instructions are absent.
- Description contains product-relevant keywords
- The tutorial body is incomplete – essential code samples, configuration steps, and explanations are missing.
- Technical accuracy cannot be confirmed without concrete code samples.
- Typographical errors (e.g., "IESWClient" instead of "IEWSClient") and incomplete sentences reduce technical credibility.
- Clarity suffers due to incomplete sentences and missing headings; the article does not fully adhere to the Google Developer Documentation style guide.
- Writing does not consistently use second‑person voice, active tense, or sentence‑case headings as required by style guidelines.
- The writing does not fully follow the Google Developer Documentation style – headings are not consistently sentence‑case, and some sentences use passive voice or hedging.
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The main body of the tutorial is truncated; code examples and step‑by‑step instructions are absent.⚠️ Clarity suffers due to incomplete sentences and missing headings; the article does not fully adhere to the Google Developer Documentation style guide.⚠️ Technical accuracy cannot be confirmed without concrete code samples.
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ The tutorial body is incomplete – essential code samples, configuration steps, and explanations are missing.⚠️ Writing does not consistently use second‑person voice, active tense, or sentence‑case headings as required by style guidelines.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The content is truncated; essential code snippets, import statements, and full usage examples are missing.⚠️ Typographical errors (e.g., "IESWClient" instead of "IEWSClient") and incomplete sentences reduce technical credibility.⚠️ The writing does not fully follow the Google Developer Documentation style – headings are not consistently sentence‑case, and some sentences use passive voice or hedging.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 4, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 10 |
| Total | 100/100 (capped from 173) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 13 |
| Clarity & readability (max 20) | 10 |
| SEO quality (max 20) | 15 |
| Actionability (max 20) | 7 |
| Content uniqueness (max 15) | 7 |
Issues:
- The tutorial content is truncated; no code snippets, configuration details, or execution steps are provided.
- The main content is truncated; essential sections such as environment setup, code examples for creating, updating, listing, and deleting appointments are missing.
- Steps are incomplete and end abruptly, missing essential code snippets, imports, and error‑handling guidance.
- The main body is truncated; headings and narrative do not fully explain configuration, connection verification, or usage scenarios.
- Writing does not consistently follow the Google Developer Documentation style (second‑person, active voice, sentence‑case headings).
- Technical details (e.g., authentication, timezone handling, recurrence) are not demonstrated with real code, reducing technical accuracy and usability.
- Key concepts such as authentication, SSL handling, and pagination are only hinted at in the FAQ, not demonstrated in the main guide.
- Description contains product-relevant keywords
- How‑to steps in the schema are generic marketing statements rather than actionable instructions.
- Title contains product-relevant keywords (API name, format, or action verb)
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The main content is truncated; essential sections such as environment setup, code examples for creating, updating, listing, and deleting appointments are missing.⚠️ How‑to steps in the schema are generic marketing statements rather than actionable instructions.⚠️ Technical details (e.g., authentication, timezone handling, recurrence) are not demonstrated with real code, reducing technical accuracy and usability.
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ The tutorial content is truncated; no code snippets, configuration details, or execution steps are provided.⚠️ Writing does not consistently follow the Google Developer Documentation style (second‑person, active voice, sentence‑case headings).⚠️ Key concepts such as authentication, SSL handling, and pagination are only hinted at in the FAQ, not demonstrated in the main guide.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Steps are incomplete and end abruptly, missing essential code snippets, imports, and error‑handling guidance.⚠️ The main body is truncated; headings and narrative do not fully explain configuration, connection verification, or usage scenarios.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 5, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 10 |
| Total | 100/100 (capped from 173) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 13 |
| Clarity & readability (max 20) | 10 |
| SEO quality (max 20) | 15 |
| Actionability (max 20) | 8 |
| Content uniqueness (max 15) | 9 |
Issues:
- The main body of the tutorial is truncated; no Maven dependency snippet, no code example, and no detailed steps are provided.
- Writing does not fully follow the Google Developer Documentation style (headings are not consistently sentence‑case, some passive voice, and missing descriptive link text).
- Clarity suffers because the introduction is cut off and headings are not consistently sentence‑case; some sentences use passive voice and vague wording.
- Technical details are sparse; the article does not demonstrate how to create, update, list, or delete appointments.
- Clarity suffers because readers cannot follow concrete steps; headings and sections are incomplete.
- Description contains product-relevant keywords
- Core tutorial content is missing – no code examples, configuration steps, or complete workflow.
- Title contains product-relevant keywords (API name, format, or action verb)
- The core tutorial content is missing or incomplete – no code snippets, no full step‑by‑step instructions, and no explanation of required imports or Maven dependencies.
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Core tutorial content is missing – no code examples, configuration steps, or complete workflow.⚠️ Technical details are sparse; the article does not demonstrate how to create, update, list, or delete appointments.⚠️ Clarity suffers because readers cannot follow concrete steps; headings and sections are incomplete.
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ The main body of the tutorial is truncated; no Maven dependency snippet, no code example, and no detailed steps are provided.⚠️ Clarity suffers because the introduction is cut off and headings are not consistently sentence‑case; some sentences use passive voice and vague wording.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The core tutorial content is missing or incomplete – no code snippets, no full step‑by‑step instructions, and no explanation of required imports or Maven dependencies.⚠️ Writing does not fully follow the Google Developer Documentation style (headings are not consistently sentence‑case, some passive voice, and missing descriptive link text).
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
adil-aspose
approved these changes
Oct 5, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
✅ PR Arbiter Review — Score: 100/100
This PR meets quality standards and is approved for merge.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ✅ Met |
| Request changes (≥ 50) | ✅ Met |
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 163 |
| AI evaluation (max 20) | 11 |
| Total | 100/100 (capped from 174) |
Checklist Results
| # | Check | Type | Result |
|---|---|---|---|
| 1 | Every Markdown file has a YAML frontmatter block (--- ... ---) | Required | ✅ |
| 2 | Frontmatter contains a non-empty 'title' field | Required | ✅ |
| 3 | Frontmatter contains a non-empty 'description' field (≥ 50 chars) | Required | ✅ |
| 4 | Content contains no placeholder text (TODO, FIXME, [PLACEHOLDER], Lorem ipsum) | Required | ✅ |
| 5 | Body content after frontmatter is not empty (≥ 100 chars) | Required | ✅ |
| 6 | All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class) | Required | ✅ |
| 7 | No LLM reasoning or draft text appears before the first Hugo shortcode tag | Required | ✅ |
| 8 | Headings (##, ###) are translated into the file's target language, not left in English | Required | ✅ |
| 9 | Frontmatter values containing colons are quoted to prevent Hugo build failures | Required | ✅ |
| 10 | No markdown links with missing protocol scheme (e.g. ://example.com) that cause Hugo build failures | Required | ✅ |
| 11 | The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures) | Required | ✅ |
| 12 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 13 | English content body has ≥ 200 words | Recommended | ✅ |
| 14 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 15 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | |
| 16 | Description contains product-relevant keywords | Recommended | |
| 17 | Tutorial content includes at least one fenced code block | Recommended | ✅ |
| 18 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | ✅ |
| 19 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | ✅ |
| 20 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended | ✅ |
AI Content Evaluation
Summary: Averaged over 3 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 14 |
| Clarity & readability (max 20) | 11 |
| SEO quality (max 20) | 15 |
| Actionability (max 20) | 8 |
| Content uniqueness (max 15) | 8 |
Issues:
- Some headings and sentences do not fully adhere to the Google Developer Documentation style (e.g., missing second‑person voice, occasional passive constructions).
- The main content is truncated; essential code snippets, configuration steps, and usage details are missing, making it hard to follow.
- The main tutorial body is truncated; essential code snippets and configuration details are missing.
- Headings use lower‑case “exchange” and some sentences are vague, violating the Google Docs style guide.
- The tutorial body is truncated; no complete code sample or detailed steps are visible.
- Steps are vague and lack error‑handling, environment‑setup, and sample output guidance.
- Description contains product-relevant keywords
- Writing does not consistently follow the Google Developer Documentation style (headings, second‑person voice, active tense).
- Title contains product-relevant keywords (API name, format, or action verb)
Files Reviewed
Recommended — improve score
email/english/java/exchange-server-integration/aspose-email-java-exchange-appointments-management/_index.md
⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The main content is truncated; essential code snippets, configuration steps, and usage details are missing, making it hard to follow.⚠️ Some headings and sentences do not fully adhere to the Google Developer Documentation style (e.g., missing second‑person voice, occasional passive constructions).
email/english/java/exchange-server-integration/aspose-email-java-exchange-messages-listing/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Description contains product-relevant keywords⚠️ The tutorial body is truncated; no complete code sample or detailed steps are visible.⚠️ Headings use lower‑case “exchange” and some sentences are vague, violating the Google Docs style guide.
email/english/java/exchange-server-integration/aspose-email-java-exchange-server-connection/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ The main tutorial body is truncated; essential code snippets and configuration details are missing.⚠️ Writing does not consistently follow the Google Developer Documentation style (headings, second‑person voice, active tense).⚠️ Steps are vague and lack error‑handling, environment‑setup, and sample output guidance.
This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Page Optimization
This PR contains optimized and refreshed content for 72 files across 3 page(s) and 23 language(s).
Summary
Optimizations Applied
IEWSClient.📝 Files to Review
Please review the English files (translations are auto-generated):
English: _index.md
English: _index.md
English: _index.md
Commit Details
b08c70f108Review Checklist
🤖 Autonomous Optimization
This pull request was automatically generated by the Hugo Website Content Optimizer.
All content has been optimized using AI-powered analysis including:
Optimization run: b08c70f