Optimize 92 Tasks Net pages - #52
Merged
Merged
Conversation
….md - - Updated title, linktitle, and description to include primary and secondary keywords. - Added `date` field in front matter (2026-03-16). - Rewrote introduction to feature “remove ole objects” early and added Quick Answers section. - Added question‑based headings and expanded explanations for each scenario. - Integrated secondary keywords “how to manage ole”, “how to clear ole”, and “load project file” naturally. - Inserted troubleshooting table, Pro tip, and a comprehensive FAQ section. - Added trust‑signal block with last updated date, tested version, and author.
…ck/_index.md - - Updated title and H1 to include exact primary keyword “implement page saving callback”. - Added `date` field in front matter and refined meta description for SEO. - Inserted a **Quick Answers** section for AI-friendly snippets. - Added explanatory sections (“What is…”, “Why export project as PNG…”, “Common Pitfalls & Troubleshooting”) to enrich content. - Integrated secondary keyword “export project as png” in headings and body. - Re‑structured FAQ into a concise “Frequently Asked Questions” block. - Added trust signals (last updated, tested version, author) at the end of the article.
…ted title and meta description to include primary keyword “set calculation mode”. - Added primary keyword in the first paragraph and a dedicated H2 heading. - Integrated secondary keywords (“manage project assignments”, “manage resource availability”, “style gantt chart bars”) naturally in headings and body text. - Inserted a Quick Answers section for AI-friendly summarization. - Added a comprehensive FAQ section covering common queries. - Included trust signals (last updated, tested version, author) at the bottom.
…tion/_index.md - - Updated title and meta description to include primary keyword “combine multiple conditions”. - Added `date` field with today’s date. - Inserted Quick Answers and Common Issues tables for AI-friendly summarization. - Expanded introduction, added “What is…”, “Why use…”, and “Common Issues” sections. - Integrated all primary and secondary keywords naturally throughout the tutorial. - Added trust‑signal block (last updated, tested version, author).
Contributor
|
This PR is 100 commits behind This notice is posted once; it won't repeat as the gap grows further. |
adil-aspose
requested changes
Aug 21, 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 170) | 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 | 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 4 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:
- Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
- Title contains product-relevant keywords (API name, format, or action verb)
- 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)
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
- Tutorial content includes at least one fenced code block
Files Reviewed
Required — must fix to unblock approval
tasks/english/net/advanced-concepts/ole-objects/_index.md
- ❌ All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
tasks/english/net/advanced-features/_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
tasks/english/net/advanced-concepts/ole-objects/_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'
tasks/english/net/advanced-concepts/page-saving-callback/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ 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'
tasks/english/net/advanced-features/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ 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
tasks/english/net/advanced-features/advanced-and-operation/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ 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'
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), Title contains product-relevant keywords (API name, format, or action verb) (+4 more)
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 21, 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) | 166 |
| AI evaluation (max 20) | 15 |
| Total | 100/100 (capped from 181) |
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 4 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 20 |
| Clarity & readability (max 20) | 15 |
| SEO quality (max 20) | 17 |
| Actionability (max 20) | 13 |
| Content uniqueness (max 15) | 11 |
Issues:
- The custom callback class definition is incomplete, preventing developers from copying a working example.
- Steps are minimal; they do not cover loading an existing project or handling typical edge cases.
- Headings are not in sentence case and there are unused using directives, reducing readability.
- Some wording is awkward (e.g., "how to filter tasks" in a sentence) and the article ends abruptly, reducing readability and completeness.
- Missing final steps for actually removing OLE objects and saving the project file.
- Missing qualified call to
TaskUtils.Filterand incomplete final code for displaying results, making the tutorial hard to run as‑is. - Title contains product-relevant keywords (API name, format, or action verb)
- Occasional awkward phrasing (e.g., "implement page saving callback") and minor deviations from the Google style guide.
- Article is truncated, missing substantial content after the "Working" section.
- Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
Files Reviewed
Recommended — improve score
tasks/english/net/advanced-concepts/ole-objects/_index.md
⚠️ Missing final steps for actually removing OLE objects and saving the project file.⚠️ Headings are not in sentence case and there are unused using directives, reducing readability.
tasks/english/net/advanced-concepts/page-saving-callback/_index.md⚠️ The custom callback class definition is incomplete, preventing developers from copying a working example.⚠️ Occasional awkward phrasing (e.g., "implement page saving callback") and minor deviations from the Google style guide.
tasks/english/net/advanced-features/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths⚠️ Article is truncated, missing substantial content after the "Working" section.⚠️ Steps are minimal; they do not cover loading an existing project or handling typical edge cases.
tasks/english/net/advanced-features/advanced-and-operation/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)⚠️ Missing qualified call toTaskUtils.Filterand incomplete final code for displaying results, making the tutorial hard to run as‑is.⚠️ Some wording is awkward (e.g., "how to filter tasks" in a sentence) and the article ends abruptly, reducing readability and completeness.
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 92 files across 4 page(s) and 23 language(s).
Summary
Optimizations Applied
datefield in front matter (2026-03-16).datefield in front matter and refined meta description for SEO.datefield with today’s date.📝 Files to Review
Please review the English files (translations are auto-generated):
English: _index.md
English: _index.md
English: _index.md
English: _index.md
Commit Details
532aabb52eReview 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: 532aabb