Optimize 115 Email Java pages - #65
Merged
Merged
Conversation
…Updated front matter with current date and keyword list. - Integrated primary keyword “extract email attachments java” into title, description, first paragraph, and multiple headings. - Added definition anchor and direct‑answer paragraph for the primary concept. - Expanded sections with step‑by‑step explanations, quantified benefits, and troubleshooting tips. - Refined FAQ answers for clarity and added authoritative framing. - Updated trust‑signal block with new date and version information.
…k-template-management-aspose-email-java/_index.md - - Updated front‑matter date and added a focused keywords list. - Added definition anchors for `MailMessage` and `MapiMessage`. - Inserted two new question‑format H2 sections with direct‑answer paragraphs. - Replaced vague statements with quantified claims (e.g., 50+ formats, 2 GB limit, 1,000 conversions/minute). - Enhanced trust signals block and enriched introductory and conclusion text for better SEO and AI extractability.
…vcf-mhtml-aspose-email-java/_index.md - - Updated front matter with current date and expanded keyword list. - Added primary keyword “how to convert vcf” in title, description, and multiple body locations. - Inserted Quick Answers section for immediate AI extraction. - Created question‑format H2 headings with 40‑70 word direct answers. - Added definition anchors for `MailMessage`, `MapiMessage`, and `MhtSaveOptions`. - Replaced vague statements with quantified claims (e.g., “supports 150+ formats”). - Enhanced human‑focused explanations, use‑case context, and performance tips. - Added trust signals block with last updated date, tested version, and author.
…nversion-eml-to-mht-aspose-email-java/_index.md - - Updated title and meta description to include primary and secondary keywords. - Added Quick Answers and expanded FAQ sections for AEO compliance. - Inserted definition anchors for `MailMessage` and `MhtSaveOptions`. - Provided a direct‑answer paragraph for the core “convert eml to mht” question. - Added quantified claims, performance tips, and trust‑signal block. - Integrated the secondary keyword “aspose email maven dependency” naturally.
…- - Updated title and front‑matter to embed primary keyword and added date/keywords. - Added introductory paragraph with primary keyword and definition anchor. - Inserted quantified claim about format support and file size handling. - Created Quick Answers, direct‑answer question headings, and FAQ sections for AEO/GEO. - Added trust‑signal block with last‑updated date, tested version, and author. - Preserved all original 25 markdown links, shortcodes, and ensured zero code blocks remain unchanged.
adil-aspose
requested changes
Aug 13, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
❌ PR Arbiter Review — Score: 49/100
This PR has significant quality issues that must be resolved. Please review the checklist failures and AI feedback carefully.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ❌ Not met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 0 |
| Total | 49/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 0 |
| Clarity & readability (max 20) | 0 |
| SEO quality (max 20) | 0 |
| Actionability (max 20) | 0 |
| Content uniqueness (max 15) | 0 |
Issues:
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- AI evaluation could not be completed.
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Tutorial content includes at least one fenced code block
- Links use descriptive text, not vague phrases like 'click here' or 'here'
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ AI evaluation could not be completed.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ AI evaluation could not be completed.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 13, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 6 |
| SEO quality (max 20) | 6 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Some headings and sentences do not fully follow the Google Developer Documentation style (e.g., mixed case headings, occasional passive voice).
- Headings and phrasing do not fully follow Google Developer Documentation style (e.g., sentence‑case headings, consistent second‑person voice).
- Tutorial content includes at least one fenced code block
- The article is largely a high‑level overview and reads like a marketing blurb rather than a tutorial.
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Key terms such as OFT, MSG, and Aspose.Email classes are not introduced or explained before use.
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Steps are high‑level and miss code snippets, imports, and error handling.
- No code snippets or API usage details; developers cannot reproduce the conversion without additional information.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Steps are high‑level and miss code snippets, imports, and error handling.⚠️ Some headings and sentences do not fully follow the Google Developer Documentation style (e.g., mixed case headings, occasional passive voice).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ No code snippets or API usage details; developers cannot reproduce the conversion without additional information.⚠️ Headings and phrasing do not fully follow Google Developer Documentation style (e.g., sentence‑case headings, consistent second‑person voice).⚠️ Key terms such as OFT, MSG, and Aspose.Email classes are not introduced or explained before use.⚠️ The article is largely a high‑level overview and reads like a marketing blurb rather than a tutorial.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 13, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 55/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 6 |
| Total | 55/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 8 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 4 |
Issues:
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Tutorial content includes at least one fenced code block
- Missing concrete code snippets and full walkthrough for MSG, EML, and PST scenarios.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Missing practical code snippets and detailed instructions; the tutorial cannot be followed end‑to‑end.
- Headings and prose are not fully compliant with the Google Developer Documentation style (sentence‑case, consistent second‑person voice).
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Headings and phrasing do not consistently follow sentence‑case and second‑person style required by the style guide.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Missing concrete code snippets and full walkthrough for MSG, EML, and PST scenarios.⚠️ Headings and prose are not fully compliant with the Google Developer Documentation style (sentence‑case, consistent second‑person voice).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing practical code snippets and detailed instructions; the tutorial cannot be followed end‑to‑end.⚠️ Headings and phrasing do not consistently follow sentence‑case and second‑person style required by the style guide.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 14, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 55/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 6 |
| Total | 55/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 6 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 4 |
Issues:
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Missing detailed implementation steps and code snippets; developers cannot reproduce the conversion without additional information.
- Headings use title case instead of sentence case and some phrasing could be more concise per the Google style guide.
- Tutorial content includes at least one fenced code block
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Headings are not consistently sentence‑case and some sections are truncated, reducing completeness.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Steps are high‑level only; missing concrete code snippets, error handling, and resource‑cleanup guidance.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Steps are high‑level only; missing concrete code snippets, error handling, and resource‑cleanup guidance.⚠️ Headings use title case instead of sentence case and some phrasing could be more concise per the Google style guide.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing detailed implementation steps and code snippets; developers cannot reproduce the conversion without additional information.⚠️ Headings are not consistently sentence‑case and some sections are truncated, reducing completeness.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 14, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 53/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 4 |
| Total | 53/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 6 |
| Actionability (max 20) | 3 |
| Content uniqueness (max 15) | 3 |
Issues:
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Headings and phrasing do not consistently follow the Google Developer Documentation style (sentence case, second‑person, active voice).
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Actionable guidance is too brief; developers may not be able to implement the solution without additional details.
- Headings and sentences do not fully follow the Google Developer Documentation style (e.g., mixed voice, missing sentence‑case headings).
- The main content is truncated; essential code snippets, error handling, and explanations are missing.
- Missing code snippets, Maven dependency details, and explicit instructions needed for developers to implement the conversion.
- Tutorial content includes at least one fenced code block
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ The main content is truncated; essential code snippets, error handling, and explanations are missing.⚠️ Headings and sentences do not fully follow the Google Developer Documentation style (e.g., mixed voice, missing sentence‑case headings).⚠️ Actionable guidance is too brief; developers may not be able to implement the solution without additional details.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing code snippets, Maven dependency details, and explicit instructions needed for developers to implement the conversion.⚠️ Headings and phrasing do not consistently follow the Google Developer Documentation style (sentence case, second‑person, active voice).
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 14, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 55/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 6 |
| Total | 55/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 8 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Steps are high‑level and miss concrete code snippets, imports, and error handling, reducing practical usability.
- Headings and tone do not fully comply with the style guide (sentence‑case headings, consistent second‑person voice).
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Content is largely high‑level overview with little original insight beyond standard product marketing.
- Missing practical code samples and detailed instructions; developers cannot follow the tutorial to complete the task.
- Tutorial content includes at least one fenced code block
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Headings and some sentences do not follow the Google Developer Documentation style (e.g., title‑case headings, occasional passive voice).
- Links use descriptive text, not vague phrases like 'click here' or 'here'
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Steps are high‑level and miss concrete code snippets, imports, and error handling, reducing practical usability.⚠️ Headings and some sentences do not follow the Google Developer Documentation style (e.g., title‑case headings, occasional passive voice).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing practical code samples and detailed instructions; developers cannot follow the tutorial to complete the task.⚠️ Headings and tone do not fully comply with the style guide (sentence‑case headings, consistent second‑person voice).⚠️ Content is largely high‑level overview with little original insight beyond standard product marketing.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 14, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 53/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 4 |
| Total | 53/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 3 |
| Content uniqueness (max 15) | 3 |
Issues:
- Insufficient depth makes the content feel like a thin rewrite of product marketing copy.
- The body is truncated and missing concrete code snippets, import statements, and error‑handling guidance.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Writing does not fully adhere to the Google Developer Documentation style (e.g., mixed voice, missing sentence‑case headings, and insufficient explanation of terms).
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Missing code snippets, Maven dependency details, and complete step‑by‑step instructions.
- Tutorial content includes at least one fenced code block
- Headings and title are not in sentence case, and the article repeats the keyword phrase excessively.
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ The body is truncated and missing concrete code snippets, import statements, and error‑handling guidance.⚠️ Writing does not fully adhere to the Google Developer Documentation style (e.g., mixed voice, missing sentence‑case headings, and insufficient explanation of terms).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing code snippets, Maven dependency details, and complete step‑by‑step instructions.⚠️ Headings and title are not in sentence case, and the article repeats the keyword phrase excessively.⚠️ Insufficient depth makes the content feel like a thin rewrite of product marketing copy.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 14, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 6 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 4 |
Issues:
- Tutorial content includes at least one fenced code block
- Missing essential code snippets, Maven dependency block, and step‑by‑step instructions, making the tutorial non‑actionable.
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Insufficient code examples and missing import statements; steps are too high‑level.
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- The body appears truncated and does not provide a complete, step‑by‑step walkthrough.
- Headings are not consistently sentence‑case and some sentences use passive voice, deviating from the Google Developer Documentation style guide.
- Links use descriptive text, not vague phrases like 'click here' or 'here'
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Insufficient code examples and missing import statements; steps are too high‑level.⚠️ The body appears truncated and does not provide a complete, step‑by‑step walkthrough.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing essential code snippets, Maven dependency block, and step‑by‑step instructions, making the tutorial non‑actionable.⚠️ Headings are not consistently sentence‑case and some sentences use passive voice, deviating from the Google Developer Documentation style guide.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 14, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 55/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 6 |
| Total | 55/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 8 |
| Clarity & readability (max 20) | 6 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 4 |
Issues:
- Inconsistent heading capitalization and occasional passive voice; some jargon (e.g., “MSG”, “OFT”) is not defined on first use.
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Steps are high‑level and miss concrete Java code snippets, imports, and error handling.
- Missing practical code snippets and a complete walkthrough; the HowTo steps are high‑level use cases rather than actionable instructions.
- Tutorial content includes at least one fenced code block
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Writing is not fully in second‑person active voice; some sentences could be more direct and concise.
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- The article is largely a re‑phrasing of marketing copy, offering limited original insight beyond the API documentation.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Steps are high‑level and miss concrete Java code snippets, imports, and error handling.⚠️ Writing is not fully in second‑person active voice; some sentences could be more direct and concise.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing practical code snippets and a complete walkthrough; the HowTo steps are high‑level use cases rather than actionable instructions.⚠️ Inconsistent heading capitalization and occasional passive voice; some jargon (e.g., “MSG”, “OFT”) is not defined on first use.⚠️ The article is largely a re‑phrasing of marketing copy, offering limited original insight beyond the API documentation.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 15, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 6 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 6 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Missing concrete code snippets, import statements, and error‑handling guidance, which reduces practical usefulness.
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Headings and title are not in sentence case, and some marketing language reduces clarity; style does not fully adhere to Google Developer Documentation guidelines.
- The tutorial body is truncated; it does not cover MSG, EML, or inline attachment handling as promised.
- Inconsistent writing style: headings are not sentence‑case, occasional passive voice, and some jargon (e.g., “hub”) is unexplained.
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Missing detailed, step‑by‑step code snippets and configuration instructions; the tutorial is incomplete.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Tutorial content includes at least one fenced code block
- Links use descriptive text, not vague phrases like 'click here' or 'here'
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Missing concrete code snippets, import statements, and error‑handling guidance, which reduces practical usefulness.⚠️ Inconsistent writing style: headings are not sentence‑case, occasional passive voice, and some jargon (e.g., “hub”) is unexplained.⚠️ The tutorial body is truncated; it does not cover MSG, EML, or inline attachment handling as promised.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing detailed, step‑by‑step code snippets and configuration instructions; the tutorial is incomplete.⚠️ Headings and title are not in sentence case, and some marketing language reduces clarity; style does not fully adhere to Google Developer Documentation guidelines.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 15, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 4 |
Issues:
- Tutorial content includes at least one fenced code block
- Missing essential code snippets, Maven dependency details, and full workflow steps, making it hard for developers to implement.
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Missing concrete code snippets, imports, and error‑handling guidance; steps are too high‑level.
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- The introductory prose could be tighter and adhere more consistently to the Google Developer Documentation style (sentence‑case headings, second‑person voice throughout).
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Headings and phrasing do not consistently follow the Google Developer Documentation style (sentence‑case, second‑person, active voice).
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Missing concrete code snippets, imports, and error‑handling guidance; steps are too high‑level.⚠️ The introductory prose could be tighter and adhere more consistently to the Google Developer Documentation style (sentence‑case headings, second‑person voice throughout).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing essential code snippets, Maven dependency details, and full workflow steps, making it hard for developers to implement.⚠️ Headings and phrasing do not consistently follow the Google Developer Documentation style (sentence‑case, second‑person, active voice).
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 15, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Missing core tutorial content – no code snippets, Maven configuration, or step‑by‑step instructions.
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Key concepts (e.g., OFT, MSG, Aspose.Email classes) are not defined or illustrated, reducing technical depth.
- Headings and style do not fully comply with the Google Developer Documentation Style Guide (e.g., not sentence‑case, inconsistent use of bold).
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Tutorial content includes at least one fenced code block
- Headings are not sentence‑case and the writing occasionally drifts into marketing language rather than developer‑focused guidance.
- Missing concrete code snippets, imports, and error‑handling guidance, reducing practical usefulness.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Missing concrete code snippets, imports, and error‑handling guidance, reducing practical usefulness.⚠️ Headings and style do not fully comply with the Google Developer Documentation Style Guide (e.g., not sentence‑case, inconsistent use of bold).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing core tutorial content – no code snippets, Maven configuration, or step‑by‑step instructions.⚠️ Headings are not sentence‑case and the writing occasionally drifts into marketing language rather than developer‑focused guidance.⚠️ Key concepts (e.g., OFT, MSG, Aspose.Email classes) are not defined or illustrated, reducing technical depth.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 15, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 6 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 4 |
Issues:
- Missing concrete code examples and full end‑to‑end snippets for MSG, EML, and PST extraction.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Action steps are described only as use‑case scenarios rather than concrete, reproducible instructions
- Missing code samples, Maven dependency snippet, and full walkthrough – the tutorial is incomplete
- Headings are not sentence‑case and some phrasing deviates from the recommended second‑person, active‑voice style
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Steps are too high‑level; developers may be unsure about required imports, error handling, and resource cleanup.
- Tutorial content includes at least one fenced code block
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Missing concrete code examples and full end‑to‑end snippets for MSG, EML, and PST extraction.⚠️ Steps are too high‑level; developers may be unsure about required imports, error handling, and resource cleanup.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing code samples, Maven dependency snippet, and full walkthrough – the tutorial is incomplete⚠️ Headings are not sentence‑case and some phrasing deviates from the recommended second‑person, active‑voice style⚠️ Action steps are described only as use‑case scenarios rather than concrete, reproducible instructions
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 15, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 6 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Missing concrete code samples (imports, try‑with‑resources, error handling) that are essential for developers to follow.
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Actionable steps are vague; readers cannot follow a reproducible workflow.
- Steps are high‑level and omit handling of MSG/EML files, inline attachments, and stream management details.
- Missing code snippets and detailed API usage; technical details are insufficient.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Tutorial content includes at least one fenced code block
- Headings are not consistently sentence‑case and the article stops abruptly without full tutorial content.
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Missing concrete code samples (imports, try‑with‑resources, error handling) that are essential for developers to follow.⚠️ Steps are high‑level and omit handling of MSG/EML files, inline attachments, and stream management details.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing code snippets and detailed API usage; technical details are insufficient.⚠️ Headings are not consistently sentence‑case and the article stops abruptly without full tutorial content.⚠️ Actionable steps are vague; readers cannot follow a reproducible workflow.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 15, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 6 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 4 |
Issues:
- Missing code snippets, Maven dependency block, and step‑by‑step instructions, making the tutorial non‑actionable.
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- The tutorial content is truncated and does not provide full step‑by‑step code snippets or import statements.
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Inconsistent heading style and occasional deviation from the Google Developer Documentation style guide (e.g., not always using second‑person, active voice, or sentence‑case headings).
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Tutorial content includes at least one fenced code block
- Headings and some sentences do not fully follow the Google Developer Documentation style (e.g., mixed case headings, occasional passive voice).
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ The tutorial content is truncated and does not provide full step‑by‑step code snippets or import statements.⚠️ Headings and some sentences do not fully follow the Google Developer Documentation style (e.g., mixed case headings, occasional passive voice).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing code snippets, Maven dependency block, and step‑by‑step instructions, making the tutorial non‑actionable.⚠️ Inconsistent heading style and occasional deviation from the Google Developer Documentation style guide (e.g., not always using second‑person, active voice, or sentence‑case headings).
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 16, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 6 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 6 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Tutorial content includes at least one fenced code block
- Content only covers PST; MSG and EML extraction are mentioned but not demonstrated.
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Headings are not sentence‑case and some style guidelines (second‑person, active voice) are inconsistently applied.
- Headings are not consistently sentence‑case and some sections use passive voice or vague phrasing, reducing readability.
- Missing core tutorial content such as Maven dependency snippet, code sample for loading an OFT, populating fields, and saving as MSG.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Missing concrete code snippets, import statements, and error‑handling details, reducing practical usefulness.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Missing concrete code snippets, import statements, and error‑handling details, reducing practical usefulness.⚠️ Content only covers PST; MSG and EML extraction are mentioned but not demonstrated.⚠️ Headings are not sentence‑case and some style guidelines (second‑person, active voice) are inconsistently applied.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing core tutorial content such as Maven dependency snippet, code sample for loading an OFT, populating fields, and saving as MSG.⚠️ Headings are not consistently sentence‑case and some sections use passive voice or vague phrasing, reducing readability.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 16, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 6 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Missing code snippets and complete walkthrough; readers cannot reproduce the conversion without additional information.
- Formatting and style need improvement: headings are not sentence‑case, some sentences lack second‑person voice, and there is insufficient explanation of terms such as "inline attachment".
- The “Why use Aspose.Email…” section is truncated, leaving the article incomplete.
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Headings are not consistently sentence‑case and the writing sometimes drifts from second‑person active voice.
- Tutorial content includes at least one fenced code block
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- The tutorial is incomplete – key sections (e.g., code snippets, handling MSG/EML, error handling) are missing or truncated.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ The tutorial is incomplete – key sections (e.g., code snippets, handling MSG/EML, error handling) are missing or truncated.⚠️ Formatting and style need improvement: headings are not sentence‑case, some sentences lack second‑person voice, and there is insufficient explanation of terms such as "inline attachment".
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing code snippets and complete walkthrough; readers cannot reproduce the conversion without additional information.⚠️ Headings are not consistently sentence‑case and the writing sometimes drifts from second‑person active voice.⚠️ The “Why use Aspose.Email…” section is truncated, leaving the article incomplete.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 16, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 8 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Missing detailed implementation steps and code snippets; the How‑To section lists only high‑level scenarios.
- Actionable guidance is too high‑level, making it hard for a developer to follow the tutorial end‑to‑end.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Headings are not sentence‑case and some language is not fully second‑person active voice, which reduces readability per Google Docs style.
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- The tutorial content is truncated; essential code snippets, setup steps, and full explanations are missing.
- Tutorial content includes at least one fenced code block
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ The tutorial content is truncated; essential code snippets, setup steps, and full explanations are missing.⚠️ Actionable guidance is too high‑level, making it hard for a developer to follow the tutorial end‑to‑end.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing detailed implementation steps and code snippets; the How‑To section lists only high‑level scenarios.⚠️ Headings are not sentence‑case and some language is not fully second‑person active voice, which reduces readability per Google Docs style.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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.
Collaborator
Author
|
🚨 Human review required The automated fixer has attempted to resolve arbiter feedback 18 time(s) but the PR still does not pass all required checks. Failing checks (last known):
What to do:
Automated fixes are paused for this PR until the label is removed. |
adil-aspose
requested changes
Aug 16, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 6 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 6 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Content is largely high‑level marketing language, offering little unique insight beyond generic product description
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Headings and phrasing do not fully follow Google Developer Documentation style (sentence case, second‑person voice)
- Headings and prose do not fully follow the Google Developer Documentation Style Guide (e.g., sentence‑case headings, consistent second‑person voice).
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Tutorial content includes at least one fenced code block
- Missing concrete code snippets, imports, and error‑handling guidance, reducing practical usefulness.
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- No code snippets or API usage details; developers cannot reproduce the conversion
- Content is largely a re‑phrasing of existing documentation, offering limited unique insight.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Missing concrete code snippets, imports, and error‑handling guidance, reducing practical usefulness.⚠️ Headings and prose do not fully follow the Google Developer Documentation Style Guide (e.g., sentence‑case headings, consistent second‑person voice).⚠️ Content is largely a re‑phrasing of existing documentation, offering limited unique insight.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ No code snippets or API usage details; developers cannot reproduce the conversion⚠️ Headings and phrasing do not fully follow Google Developer Documentation style (sentence case, second‑person voice)⚠️ Content is largely high‑level marketing language, offering little unique insight beyond generic product description
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 16, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 55/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 6 |
| Total | 55/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 6 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 4 |
Issues:
- Tutorial content includes at least one fenced code block
- Some stylistic inconsistencies with the Google Developer Documentation style (e.g., mixed voice, occasional hedging).
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Headings and phrasing do not fully follow the Google Developer Documentation style (e.g., title case, more second‑person active voice).
- Missing concrete code examples and import statements; steps are too high‑level to be immediately actionable.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Missing concrete code snippets, Maven dependency block, and full walkthrough needed for developers to implement the conversion.
- Links use descriptive text, not vague phrases like 'click here' or 'here'
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Missing concrete code examples and import statements; steps are too high‑level to be immediately actionable.⚠️ Some stylistic inconsistencies with the Google Developer Documentation style (e.g., mixed voice, occasional hedging).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing concrete code snippets, Maven dependency block, and full walkthrough needed for developers to implement the conversion.⚠️ Headings and phrasing do not fully follow the Google Developer Documentation style (e.g., title case, more second‑person active voice).
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 16, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 6 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- The tutorial body is truncated and missing concrete code examples, import statements, and error‑handling guidance, reducing its practical usefulness.
- The article is truncated and does not cover the full tutorial flow, reducing its usefulness.
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Headings are not in sentence case and some phrasing does not follow the Google Developer Documentation style (e.g., use of bolded phrases instead of clear imperative instructions).
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Writing does not fully follow the Google Developer Documentation style (e.g., headings are not sentence‑case, some passive constructions, and missing descriptive link text).
- Tutorial content includes at least one fenced code block
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Missing practical code snippets and detailed walkthrough; steps are high‑level and not reproducible.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ The tutorial body is truncated and missing concrete code examples, import statements, and error‑handling guidance, reducing its practical usefulness.⚠️ Writing does not fully follow the Google Developer Documentation style (e.g., headings are not sentence‑case, some passive constructions, and missing descriptive link text).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing practical code snippets and detailed walkthrough; steps are high‑level and not reproducible.⚠️ Headings are not in sentence case and some phrasing does not follow the Google Developer Documentation style (e.g., use of bolded phrases instead of clear imperative instructions).⚠️ The article is truncated and does not cover the full tutorial flow, reducing its usefulness.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 17, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 6 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- The main content is incomplete/truncated; missing code snippets, import statements, and error‑handling guidance.
- Missing code snippets and detailed procedural steps; developers cannot reproduce the task.
- Headings and prose do not fully adhere to the Google Developer Documentation style (sentence‑case, second‑person voice, clear link text).
- The HowTo schema lists use‑case scenarios instead of concrete actionable steps.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Tutorial content includes at least one fenced code block
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Headings are not in sentence case and the article repeats the phrase “convert oft to msg” excessively, reducing readability.
- Actionable details such as handling MSG/EML files, dealing with inline attachments, and stream management are only mentioned in FAQs, not integrated into the tutorial flow.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ The main content is incomplete/truncated; missing code snippets, import statements, and error‑handling guidance.⚠️ Headings and prose do not fully adhere to the Google Developer Documentation style (sentence‑case, second‑person voice, clear link text).⚠️ Actionable details such as handling MSG/EML files, dealing with inline attachments, and stream management are only mentioned in FAQs, not integrated into the tutorial flow.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing code snippets and detailed procedural steps; developers cannot reproduce the task.⚠️ Headings are not in sentence case and the article repeats the phrase “convert oft to msg” excessively, reducing readability.⚠️ The HowTo schema lists use‑case scenarios instead of concrete actionable steps.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 17, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Tutorial content includes at least one fenced code block
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Steps are high‑level and not fully actionable; developers may need additional context such as import statements, exception handling, and stream management.
- The tutorial body is truncated and missing concrete code snippets for MSG, EML, and PST handling.
- Headings are not in sentence case and some sections use passive voice or vague language, deviating from the Google Developer Documentation style.
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- Missing code snippets and detailed implementation steps, making it hard to follow.
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ The tutorial body is truncated and missing concrete code snippets for MSG, EML, and PST handling.⚠️ Steps are high‑level and not fully actionable; developers may need additional context such as import statements, exception handling, and stream management.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing code snippets and detailed implementation steps, making it hard to follow.⚠️ Headings are not in sentence case and some sections use passive voice or vague language, deviating from the Google Developer Documentation style.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 17, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 160) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 | Frontmatter contains a 'url' or 'linktitle' field | Recommended | ✅ |
| 12 | English content body has ≥ 200 words | Recommended | ✅ |
| 13 | Content has at least one H2 heading (##) below any H1 | Recommended | ✅ |
| 14 | Title contains product-relevant keywords (API name, format, or action verb) | Recommended | ✅ |
| 15 | Description contains product-relevant keywords | Recommended | ✅ |
| 16 | Tutorial content includes at least one fenced code block | Recommended | |
| 17 | Internal links use Hugo shortcode format ({{< relref >}}) or relative paths | Recommended | |
| 18 | Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide | Recommended | |
| 19 | Links use descriptive text, not vague phrases like 'click here' or 'here' | Recommended |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 7 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 4 |
Issues:
- Inconsistent heading capitalization and occasional redundant phrasing; does not fully adhere to Google Developer Documentation style guidelines.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Steps are high‑level and lack concrete Java code snippets, import statements, and error handling.
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Tutorial content includes at least one fenced code block
- Writing does not fully adhere to the Google Developer Documentation style (e.g., mixed heading case, occasional passive voice, missing first‑use definitions for terms like "PST").
- Missing code examples and detailed API usage; developers cannot follow the tutorial to implement the conversion.
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Steps are high‑level and lack concrete Java code snippets, import statements, and error handling.⚠️ Writing does not fully adhere to the Google Developer Documentation style (e.g., mixed heading case, occasional passive voice, missing first‑use definitions for terms like "PST").
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing code examples and detailed API usage; developers cannot follow the tutorial to implement the conversion.⚠️ Inconsistent heading capitalization and occasional redundant phrasing; does not fully adhere to Google Developer Documentation style guidelines.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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
requested changes
Aug 17, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 55/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 49 |
| AI evaluation (max 20) | 6 |
| Total | 55/100 |
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 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 8 |
| Clarity & readability (max 20) | 6 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Tutorial content includes at least one fenced code block
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Links use descriptive text, not vague phrases like 'click here' or 'here'
- The article is truncated and ends abruptly, leaving sections like "Why use Aspose.Email…" incomplete.
- The main tutorial body is truncated, leaving the reader without full context or complete instructions.
- Headings and prose do not fully follow Google Developer Documentation style (sentence‑case headings, consistent second‑person voice, and clear definitions of acronyms).
- All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Missing concrete code snippets and error‑handling guidance, reducing practical usability.
- Missing practical code snippets and a complete walkthrough; developers cannot reproduce the task as presented.
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Missing concrete code snippets and error‑handling guidance, reducing practical usability.⚠️ The main tutorial body is truncated, leaving the reader without full context or complete instructions.
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide⚠️ Links use descriptive text, not vague phrases like 'click here' or 'here'⚠️ Missing practical code snippets and a complete walkthrough; developers cannot reproduce the task as presented.⚠️ Headings and prose do not fully follow Google Developer Documentation style (sentence‑case headings, consistent second‑person voice, and clear definitions of acronyms).⚠️ The article is truncated and ends abruptly, leaving sections like "Why use Aspose.Email…" incomplete.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
email/english/java/email-message-operations/_index.md⚠️ Tutorial content includes at least one fenced code block⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
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.
…are closed before end of file (no content leaks outside main-wrap-class), Tutorial content includes at least one fenced code block (+3 more)
Collaborator
Author
|
🔧 Automated fix applied — 5 file(s) updated The following arbiter checks were targeted:
An immediate Arbiter re-review has been triggered. |
adil-aspose
requested changes
Aug 17, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 54/100
This PR needs some improvements before it can be merged. Please address the issues listed below and push an update.
| Threshold | Score |
|---|---|
| Auto-approve (≥ 80) | ❌ Not met |
| Request changes (≥ 50) | ✅ Met |
⚠️ Required check failed in one or more files — static score capped at 49 regardless of other passing files. Resolve all ❌ required checks below to lift the cap.
Score Breakdown
| Component | Points |
|---|---|
| Static checklist (max 170) | 49 |
| AI evaluation (max 20) | 5 |
| Total | 54/100 |
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 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 6 |
| Clarity & readability (max 20) | 5 |
| SEO quality (max 20) | 7 |
| Actionability (max 20) | 4 |
| Content uniqueness (max 15) | 3 |
Issues:
- Technical details about the Aspose.Email API (e.g., classes, methods, Maven coordinates) are absent
- Missing code samples and detailed implementation steps, making it hard for developers to follow
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Headings and title are not in sentence case; some phrasing is repetitive and not fully aligned with the Google Developer Documentation style guide
- Headings and prose do not fully follow the Google Developer Documentation style (e.g., sentence‑case headings, consistent second‑person voice).
- The tutorial body is truncated; essential step‑by‑step code snippets and explanations are missing.
- The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures)
Files Reviewed
Required — must fix to unblock approval
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md
- ❌ The relref shortcode is self-closing and must not be used with inner text or a closing tag (causes Hugo build failures)
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ The tutorial body is truncated; essential step‑by‑step code snippets and explanations are missing.⚠️ Headings and prose do not fully follow the Google Developer Documentation style (e.g., sentence‑case headings, consistent second‑person voice).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Missing code samples and detailed implementation steps, making it hard for developers to follow⚠️ Headings and title are not in sentence case; some phrasing is repetitive and not fully aligned with the Google Developer Documentation style guide⚠️ Technical details about the Aspose.Email API (e.g., classes, methods, Maven coordinates) are absent
No issues found
- ✅
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md - ✅
email/english/java/email-message-operations/_index.md
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.
… be used with inner text or a closing tag (causes Hugo build failures), Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
Collaborator
Author
|
🔧 Automated fix applied — 4 file(s) updated The following arbiter checks were targeted:
An immediate Arbiter re-review has been triggered. |
adil-aspose
approved these changes
Aug 17, 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) | 170 |
| AI evaluation (max 20) | 12 |
| Total | 100/100 (capped from 182) |
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 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 16 |
| Clarity & readability (max 20) | 13 |
| SEO quality (max 20) | 16 |
| Actionability (max 20) | 9 |
| Content uniqueness (max 15) | 8 |
Issues:
- Technical steps are incorrect – they describe loading an MSG stream instead of processing a VCF file, which misleads developers.
- The content feels like a thin wrapper around marketing copy rather than a substantive tutorial.
- Writing does not fully follow the Google Developer Documentation style (e.g., mixed voice, missing sentence‑case headings, and some jargon not defined).
- Headings and title are not in sentence case, and some phrasing is repetitive or vague.
- Missing code examples and detailed implementation steps, making it hard for developers to follow.
- Headings are not in sentence case and some sentences contain unnecessary filler, deviating from the Google Docs style guide.
- Insufficient code snippets and step‑by‑step details; developers may struggle to implement the guide.
- Writing does not fully adhere to the Google Developer Documentation style (sentence‑case headings, consistent second‑person voice, and missing explanations for acronyms).
- Some sentences are overly long, and a few minor grammatical issues reduce readability.
- Content is incomplete – key sections (full code sample, Maven dependency, licensing snippet) are missing or truncated.
- The tutorial is truncated and lacks detailed, runnable code snippets and a clear step‑by‑step workflow.
- The content is incomplete and missing essential code snippets, import statements, and error‑handling guidance.
Files Reviewed
Recommended — improve score
email/english/java/attachments-handling/_index.md
⚠️ Insufficient code snippets and step‑by‑step details; developers may struggle to implement the guide.⚠️ Writing does not fully follow the Google Developer Documentation style (e.g., mixed voice, missing sentence‑case headings, and some jargon not defined).
email/english/java/calendar-appointments/master-outlook-template-management-aspose-email-java/_index.md⚠️ Missing code examples and detailed implementation steps, making it hard for developers to follow.⚠️ Headings and title are not in sentence case, and some phrasing is repetitive or vague.⚠️ The content feels like a thin wrapper around marketing copy rather than a substantive tutorial.
email/english/java/email-conversion-rendering/convert-vcf-mhtml-aspose-email-java/_index.md⚠️ Technical steps are incorrect – they describe loading an MSG stream instead of processing a VCF file, which misleads developers.⚠️ The content is incomplete and missing essential code snippets, import statements, and error‑handling guidance.⚠️ Writing does not fully adhere to the Google Developer Documentation style (sentence‑case headings, consistent second‑person voice, and missing explanations for acronyms).
email/english/java/email-conversion-rendering/email-conversion-eml-to-mht-aspose-email-java/_index.md⚠️ Content is incomplete – key sections (full code sample, Maven dependency, licensing snippet) are missing or truncated.⚠️ Headings are not in sentence case and some sentences contain unnecessary filler, deviating from the Google Docs style guide.
email/english/java/email-message-operations/_index.md⚠️ The tutorial is truncated and lacks detailed, runnable code snippets and a clear step‑by‑step workflow.⚠️ Some sentences are overly long, and a few minor grammatical issues reduce 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.
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 115 files across 5 page(s) and 23 language(s).
Summary
Optimizations Applied
MailMessageandMapiMessage.MailMessage,MapiMessage, andMhtSaveOptions.MailMessageandMhtSaveOptions.📝 Files to Review
Please review the English files (translations are auto-generated):
English: _index.md
English: _index.md
English: _index.md
English: _index.md
English: _index.md
Commit Details
6f99ecd4d4Review 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: 6f99ecd