Optimize 70 Tasks Java pages

[muqarrab-aspose]

Page Optimization

This PR contains optimized and refreshed content for 70 files across 4 page(s) and 23 language(s).

Summary

• Product Family: Tasks
• Platform: Java
• English Pages: 4
• Total Files (with translations): 70
• Languages: 23 (arabic, chinese, czech, dutch, english, french, german, greek, hindi, hongkong, hungarian, indonesian, italian, japanese, korean, polish, portuguese, russian, spanish, swedish, thai, turkish, vietnamese)
• Interactive Pages: 0

Optimizations Applied

1. tasks/english/java/task-properties/handle-priorities/_index.md
   • Changes: - Updated title, H1, and meta description to include primary keyword “how to use asp”.

• Added date field in front matter with today’s date.
• Inserted a “Quick Answers” section for AI-friendly summarization.
• Added a new H2 heading that contains the primary keyword and secondary keyword.
• Expanded introduction, benefits, and FAQ with conversational language and additional Q&A.
• Included trust‑signal block (last updated, tested version, author) at the bottom.
  • Languages: english, russian, chinese, arabic, french, german, italian, spanish, swedish, turkish, portuguese, korean, polish, indonesian, japanese, vietnamese, dutch, hungarian, thai, greek, czech, hongkong, hindi
  • Type: text

2. tasks/english/java/task-properties/handle-variances/_index.md
   • Changes: - Updated title and meta description to include primary keyword “set project start date”.

• Added “date” field in front matter with today’s date.
• Rewrote introduction to feature primary keyword early and added context.
• Inserted a “Quick Answers” section for AI-friendly summarization.
• Added explanatory H2 sections (“What is set project start date?”, “Why set project start date and manage variances?”) and a “Common Issues & Tips” block.
• Integrated secondary keywords “set task duration” and “manage project variances” naturally throughout the tutorial.
• Included trust‑signal block with last updated date, tested version, and author.
  • Languages: english, russian, chinese, arabic, french, german, italian, spanish, swedish, turkish, portuguese, korean, polish, indonesian, japanese, vietnamese, dutch, hungarian, thai, greek, czech, hongkong, hindi
  • Type: text

3. tasks/english/java/task-properties/manage-durations/_index.md
   • Changes: - Updated title, description, and added date field with primary keyword.

• Integrated primary keyword “add task to project” throughout content and headings.
• Added Quick Answers section for AI-friendly summaries.
• Inserted question‑based headings using secondary keywords “how to set duration” and “how to convert duration”.
• Expanded introduction, added common pitfalls, tips, and extra FAQ entries.
• Included trust‑signal block with last updated date, tested version, and author.
  • Languages: english, russian, chinese, arabic, french, german, italian, spanish, swedish, turkish, portuguese, korean, polish, indonesian, japanese, vietnamese, dutch, hungarian, thai, greek, czech, hongkong, hindi
  • Type: text

4. tasks/english/java/task-properties/manage-task-cost/_index.md
   • Changes: - Integrated primary keyword “calculate project cost variance” throughout title, meta, headings, and body (4×).

• Added Quick Answers and expanded FAQ sections for AI-friendly snippets.
• Enriched introduction with context, use‑cases, and conversational tone.
• Added “What is …” and “Why use …” sections plus a troubleshooting table.
• Updated front‑matter with current date and refined description to include secondary keywords.
  • Languages: english, russian, chinese, arabic, french, german, italian, spanish, swedish, turkish, portuguese, korean, polish, indonesian, japanese, vietnamese, dutch, hungarian, thai, greek, czech, hongkong, hindi
  • Type: text

📝 Files to Review

Please review the English files (translations are auto-generated):

1. English: _index.md

   • Russian: _index.md
   • Chinese: _index.md
   • Arabic: _index.md
   • French: _index.md
   • German: _index.md
   • Italian: _index.md
   • Spanish: _index.md
   • Swedish: _index.md
   • Turkish: _index.md
   • Portuguese: _index.md
   • Korean: _index.md
   • Polish: _index.md
   • Indonesian: _index.md
   • Japanese: _index.md
   • Vietnamese: _index.md
   • Dutch: _index.md
   • Hungarian: _index.md
   • Thai: _index.md
   • Greek: _index.md
   • Czech: _index.md
   • Hongkong: _index.md
   • Hindi: _index.md

2. English: _index.md

   • Russian: _index.md
   • Chinese: _index.md
   • Arabic: _index.md
   • French: _index.md
   • German: _index.md
   • Italian: _index.md
   • Spanish: _index.md
   • Swedish: _index.md
   • Turkish: _index.md
   • Portuguese: _index.md
   • Korean: _index.md
   • Polish: _index.md
   • Indonesian: _index.md
   • Japanese: _index.md
   • Vietnamese: _index.md
   • Dutch: _index.md
   • Hungarian: _index.md
   • Thai: _index.md
   • Greek: _index.md
   • Czech: _index.md
   • Hongkong: _index.md
   • Hindi: _index.md

3. English: _index.md

   • Russian: _index.md
   • Chinese: _index.md
   • Arabic: _index.md
   • French: _index.md
   • German: _index.md
   • Italian: _index.md
   • Spanish: _index.md
   • Swedish: _index.md
   • Turkish: _index.md
   • Portuguese: _index.md
   • Korean: _index.md
   • Polish: _index.md
   • Indonesian: _index.md
   • Japanese: _index.md
   • Vietnamese: _index.md
   • Dutch: _index.md
   • Hungarian: _index.md
   • Thai: _index.md
   • Greek: _index.md
   • Czech: _index.md
   • Hongkong: _index.md
   • Hindi: _index.md

4. English: _index.md

   • Russian: _index.md
   • Chinese: _index.md
   • Arabic: _index.md
   • French: _index.md
   • German: _index.md
   • Italian: _index.md
   • Spanish: _index.md
   • Swedish: _index.md
   • Turkish: _index.md
   • Portuguese: _index.md
   • Korean: _index.md
   • Polish: _index.md
   • Indonesian: _index.md
   • Japanese: _index.md
   • Vietnamese: _index.md
   • Dutch: _index.md
   • Hungarian: _index.md
   • Thai: _index.md
   • Greek: _index.md
   • Czech: _index.md
   • Hongkong: _index.md
   • Hindi: _index.md

Commit Details

• Source Repository: https://github.com/aspose-tasks/Aspose-Task-Reference-Tutorials
• Base Commit: fed978bcd9
• Total Files Changed: 92

Review Checklist

• Content accuracy and quality in English files
• SEO keywords are naturally integrated
• Code examples functionality (if applicable)
• Translation consistency across languages
• Interactive examples work correctly (if applicable)
• No broken links or outdated references

---

🤖 Autonomous Optimization

This pull request was automatically generated by the Hugo Website Content Optimizer.
All content has been optimized using AI-powered analysis including:

• Google autocomplete keyword research
• SEO optimization with primary/secondary keywords
• Content humanization and engagement improvements
• GEO optimization for AI search engines
• Automatic translation to configured languages

Optimization run: fed978b

[adil-aspose]

❌ 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:

• Title contains product-relevant keywords (API name, format, or action verb)
• Frontmatter values containing colons are quoted to prevent Hugo build failures
• 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'
• 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

tasks/english/java/task-properties/handle-priorities/_index.md

• ❌ Frontmatter values containing colons are quoted to prevent Hugo build failures
  tasks/english/java/task-properties/handle-variances/_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/java/task-properties/handle-priorities/_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/java/task-properties/handle-variances/_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/java/task-properties/manage-durations/_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/java/task-properties/manage-task-cost/_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.

[muqarrab-aspose]

🔧 Automated fix applied — 4 file(s) updated

The following arbiter checks were targeted:

• All Hugo shortcode tags opened after frontmatter are closed before end of file (no content leaks outside main-wrap-class)
• Frontmatter values containing colons are quoted to prevent Hugo build failures
• 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'

An immediate Arbiter re-review has been triggered.

[adil-aspose]

✅ 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)	168
AI evaluation (max 20)	14
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 4 English Markdown file(s).

Criterion	Score
Technical accuracy (max 25)	17
Clarity & readability (max 20)	14
SEO quality (max 20)	16
Actionability (max 20)	13
Content uniqueness (max 15)	10

Issues:

• Some API elements (e.g., BaselineType, Prj, Tsk) are not explained for newcomers.
• Article is truncated, leaving the tutorial unfinished.
• Some headings are not properly capitalized and the description contains inaccurate terminology.
• Headings are not consistently sentence‑case and some phrasing uses hedging language that deviates from style guidelines.
• Does not demonstrate how to set or save task priorities, which the title promises.
• Code examples contain incorrect API usage (e.g., default duration assumptions, misuse of Duration.subtract).
• The tutorial stops before showing how to verify or export the variance results.
• Cost variance definition is imprecise; it should be clarified as Fixed Cost minus Actual Cost (or Earned Value) rather than “planned vs remaining”.
• The tutorial is truncated – key steps such as calculating the variance, saving the project, and displaying results are missing, reducing actionability.
• Title contains product-relevant keywords (API name, format, or action verb)
• Repeated use of the undefined term “how to use ASP” creates confusion.

Files Reviewed

Recommended — improve score

tasks/english/java/task-properties/handle-priorities/_index.md

• ⚠️ Repeated use of the undefined term “how to use ASP” creates confusion.
• ⚠️ Does not demonstrate how to set or save task priorities, which the title promises.
• ⚠️ Some headings are not properly capitalized and the description contains inaccurate terminology.
  tasks/english/java/task-properties/handle-variances/_index.md
• ⚠️ Title contains product-relevant keywords (API name, format, or action verb)
• ⚠️ Some API elements (e.g., BaselineType, Prj, Tsk) are not explained for newcomers.
• ⚠️ The tutorial stops before showing how to verify or export the variance results.
  tasks/english/java/task-properties/manage-durations/_index.md
• ⚠️ Code examples contain incorrect API usage (e.g., default duration assumptions, misuse of Duration.subtract).
• ⚠️ Article is truncated, leaving the tutorial unfinished.
  tasks/english/java/task-properties/manage-task-cost/_index.md
• ⚠️ Title contains product-relevant keywords (API name, format, or action verb)
• ⚠️ Cost variance definition is imprecise; it should be clarified as Fixed Cost minus Actual Cost (or Earned Value) rather than “planned vs remaining”.
• ⚠️ Headings are not consistently sentence‑case and some phrasing uses hedging language that deviates from style guidelines.
• ⚠️ The tutorial is truncated – key steps such as calculating the variance, saving the project, and displaying results are missing, reducing actionability.

---

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.