Optimize 93 Tasks Java pages - #35
Merged
Merged
Conversation
…ex.md - - Updated front‑matter date to 2026‑01‑28 and revised description to include primary keyword. - Optimized title to contain the primary keyword “create calendar exception aspose”. - Added a new H2 heading “How to create calendar exception Aspose with Java” for better SEO and AI readability. - Integrated the primary keyword throughout the introduction, step explanations, and conclusion (total 4 natural occurrences). - Kept all original markdown links, shortcodes, and four code blocks unchanged. - Refined Quick Answers and FAQ sections for clearer AI citation while preserving original content.
…/_index.md - - Updated front‑matter date and enriched meta description with primary and secondary keywords. - Added new H2 headings that include the primary keyword and the secondary phrase “non‑working days schedule.” - Expanded introduction and added a dedicated section on non‑working days scheduling for better context. - Inserted a “How to create project calendar aspose – Define weekdays for calendar exceptions” heading to satisfy H2 primary‑keyword requirement. - Refined wording throughout for a conversational tone and added transitional language. - Updated trust‑signal block with the current date.
…dex.md - - Updated title and H1 to include primary keyword “create mpp project java”. - Revised front‑matter description and added current date field. - Added Quick Answers and AI‑optimized FAQ sections for better AI discoverability. - Integrated primary and secondary keywords naturally throughout headings and body. - Expanded introductions, explanations, and troubleshooting tips while preserving all original code blocks, links, and shortcodes. - Added trust‑signal block with last updated date, tested version, and author.
…-tasks/_index.md - - Integrated primary keyword “project management java” into title, meta description, intro, and H2. - Added Quick Answers section for AI-friendly summarization. - Expanded explanations, added “What is…”, “Why use…”, and “Identify critical tasks” sections. - Included a troubleshooting table and richer contextual content. - Added trust‑signal block with last updated date, tested version, and author.
…butes/_index.md - - Updated title, H1, and front‑matter to include the primary keyword. - Revised description to contain both primary and secondary keywords. - Added a “Quick Answers” section for AI-friendly snippets. - Introduced new explanatory headings, including one that uses the secondary keyword “switch custom field type”. - Expanded introduction, context, and “Common Issues and Solutions” table. - Added trust‑signal block (last updated, tested version, author) at the end. - Kept all original links, code blocks, shortcodes, and images unchanged.
adil-aspose
requested changes
Jun 15, 2026
adil-aspose
left a comment
adil-aspose
left a comment
Contributor
There was a problem hiding this comment.
⚠️ PR Arbiter Review — Score: 57/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 150) | 49 |
| AI evaluation (max 20) | 8 |
| Total | 57/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 | ✅ |
AI Content Evaluation
Summary: Averaged over 5 English Markdown file(s).
| Criterion | Score |
|---|---|
| Technical accuracy (max 25) | 10 |
| Clarity & readability (max 20) | 9 |
| SEO quality (max 20) | 10 |
| Actionability (max 20) | 6 |
| Content uniqueness (max 15) | 6 |
Issues:
- Title contains product-relevant keywords (API name, format, or action verb)
- Repetitive phrasing (e.g., "create project calendar aspose") reduces readability and may confuse readers.
- The step‑by‑step guide is incomplete; essential code for defining weekdays and adding CalendarException objects is omitted.
- Incorrect usage of the Project constructor – it loads an existing file instead of creating a new one.
- Potential confusion between Aspose's Calendar class and java.util.Calendar is not addressed, and no guidance on setting working times for the exception.
- The tutorial is truncated; key steps such as setting percent complete, saving the project, and handling resources are missing.
- The tutorial is truncated; final steps (e.g., saving the project, verifying the exception) are missing.
- Frontmatter values containing colons are quoted to prevent Hugo build failures
- Excessive keyword stuffing leads to repetitive phrasing and reduces readability.
Files Reviewed
Required — must fix to unblock approval
tasks/english/java/task-properties/estimated-milestone-tasks/_index.md
- ❌ Frontmatter values containing colons are quoted to prevent Hugo build failures
Recommended — improve score
tasks/english/java/calendar-exceptions/add-remove/_index.md
⚠️ The tutorial is truncated; final steps (e.g., saving the project, verifying the exception) are missing.⚠️ Potential confusion between Aspose's Calendar class and java.util.Calendar is not addressed, and no guidance on setting working times for the exception.
tasks/english/java/calendar-exceptions/define-weekdays/_index.md⚠️ The step‑by‑step guide is incomplete; essential code for defining weekdays and adding CalendarException objects is omitted.⚠️ Repetitive phrasing (e.g., "create project calendar aspose") reduces readability and may confuse readers.
tasks/english/java/task-properties/change-progress/_index.md⚠️ Incorrect usage of the Project constructor – it loads an existing file instead of creating a new one.⚠️ The tutorial is truncated; key steps such as setting percent complete, saving the project, and handling resources are missing.⚠️ Excessive keyword stuffing leads to repetitive phrasing and reduces readability.
tasks/english/java/task-properties/estimated-milestone-tasks/_index.md⚠️ Title contains product-relevant keywords (API name, format, or action verb)
No issues found
- ✅
tasks/english/java/task-properties/extended-task-attributes/_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.
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 93 files across 5 page(s) and 23 language(s).
Summary
Optimizations Applied
📝 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
4f100c869cReview 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: 4f100c8