Skip to content

Optimize 92 Tasks Java pages - #41

Merged
adil-aspose merged 6 commits into
mainfrom
optimize/tasks/java/20260213020612
Aug 5, 2026
Merged

Optimize 92 Tasks Java pages#41
adil-aspose merged 6 commits into
mainfrom
optimize/tasks/java/20260213020612

Conversation

@muqarrab-aspose

Copy link
Copy Markdown
Collaborator

Page Optimization

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

Summary

  • Product Family: Tasks
  • Platform: Java
  • English Pages: 5
  • Total Files (with translations): 92
  • 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/formulas/evaluation-functions/_index.md
    • Changes: - Updated title and meta description to include primary keyword “generate project report”.
  • Changed front‑matter date to 2026‑02‑13.
  • Integrated primary and secondary keywords naturally throughout the content.
  • Added explanatory paragraphs before each code block and a concluding summary.
  • Expanded FAQ with clear Q&A and added trust signals 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
  1. tasks/english/java/formulas/work-with-formulas/_index.md
    • Changes: - Updated title, meta description, and front‑matter date to target primary keyword “calculate days between dates”.
  • Rewrote introduction and added keyword‑rich sections (What is…, Why use…, How to set deadline, How to define extended attribute).
  • Integrated primary and secondary keywords naturally throughout the content (3+ appearances of primary, 1‑2 of each secondary).
  • Added contextual explanations, pro tips, and a clearer step‑by‑step flow while preserving all original code blocks and links.
  • Updated trust signals (Last Updated, Tested With, Author) and refreshed the FAQ formatting.
    • 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
  1. tasks/english/java/formulas/write-read-formulas/_index.md
    • Changes: - Updated title, linktitle, description, and front‑matter date to target primary keyword.
  • Integrated primary keyword “custom field formula example” and secondary keyword “double task cost formula” throughout the content, including a new H2 heading.
  • Re‑written introduction to place primary keyword within the first 100 words.
  • Added a dedicated “Custom Field Formula Example Overview” section for SEO and AI clarity.
  • Refined Quick Answers and FAQ wording while preserving original links.
  • Updated trust‑signal block with the current date and version.
  • Enhanced conversational tone, added context, and clarified why each step matters.
    • 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
  1. tasks/english/java/project-configuration/_index.md
    • Changes: - Updated front‑matter date and refined title/description to include the primary keyword “how to create mpp”.
  • Added a concise definition section and a “Why use” benefits table for better SEO and user value.
  • Integrated secondary keywords (export project to pdf, html, xml, save project to stream) naturally throughout the content.
  • Expanded introductory paragraph to place the primary keyword within the first 100 words and added a “What is ‘how to create mpp’” heading.
  • Added a “Export Project to PDF, HTML, and XML” subsection and best‑practice tips for streaming.
  • Updated trust signals (Last Updated, Tested With, Author) to reflect the current date and latest version.
    • 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
  1. tasks/english/java/project-configuration/configure-gantt-chart/_index.md
    • Changes: - Updated title and meta description to include primary and secondary keywords.
  • Revised front matter date to 2026-02-13.
  • Added primary keyword “how to create new activity” in introduction, new H2 heading, and step description.
  • Integrated secondary keyword “save project as mpp” in step 7 description and conclusion.
  • Expanded introductory and explanatory text for better human engagement and SEO.
  • Added a “How to create new activity?” heading for question‑based SEO.
  • Updated trust signals with current date and version information.
    • 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

  2. English: _index.md

  3. English: _index.md

  4. English: _index.md

  5. English: _index.md

Commit Details

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: 087615f

…x.md - - Updated title and meta description to include primary keyword “generate project report”.

- Changed front‑matter date to 2026‑02‑13.
- Integrated primary and secondary keywords naturally throughout the content.
- Added explanatory paragraphs before each code block and a concluding summary.
- Expanded FAQ with clear Q&A and added trust signals at the bottom.
…md - - Updated title, meta description, and front‑matter date to target primary keyword “calculate days between dates”.

- Rewrote introduction and added keyword‑rich sections (What is…, Why use…, How to set deadline, How to define extended attribute).
- Integrated primary and secondary keywords naturally throughout the content (3+ appearances of primary, 1‑2 of each secondary).
- Added contextual explanations, pro tips, and a clearer step‑by‑step flow while preserving all original code blocks and links.
- Updated trust signals (Last Updated, Tested With, Author) and refreshed the FAQ formatting.
….md - - Updated title, linktitle, description, and front‑matter date to target primary keyword.

- Integrated primary keyword “custom field formula example” and secondary keyword “double task cost formula” throughout the content, including a new H2 heading.
- Re‑written introduction to place primary keyword within the first 100 words.
- Added a dedicated “Custom Field Formula Example Overview” section for SEO and AI clarity.
- Refined Quick Answers and FAQ wording while preserving original links.
- Updated trust‑signal block with the current date and version.
- Enhanced conversational tone, added context, and clarified why each step matters.
… Updated front‑matter date and refined title/description to include the primary keyword “how to create mpp”.

- Added a concise definition section and a “Why use” benefits table for better SEO and user value.
- Integrated secondary keywords (export project to pdf, html, xml, save project to stream) naturally throughout the content.
- Expanded introductory paragraph to place the primary keyword within the first 100 words and added a “What is ‘how to create mpp’” heading.
- Added a “Export Project to PDF, HTML, and XML” subsection and best‑practice tips for streaming.
- Updated trust signals (Last Updated, Tested With, Author) to reflect the current date and latest version.
…tt-chart/_index.md - - Updated title and meta description to include primary and secondary keywords.

- Revised front matter date to 2026-02-13.
- Added primary keyword “how to create new activity” in introduction, new H2 heading, and step description.
- Integrated secondary keyword “save project as mpp” in step 7 description and conclusion.
- Expanded introductory and explanatory text for better human engagement and SEO.
- Added a “How to create new activity?” heading for question‑based SEO.
- Updated trust signals with current date and version information.

@adil-aspose adil-aspose left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ 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 150) 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 ⚠️

AI Content Evaluation

Summary: Averaged over 5 English Markdown file(s).

Criterion Score
Technical accuracy (max 25) 8
Clarity & readability (max 20) 7
SEO quality (max 20) 6
Actionability (max 20) 5
Content uniqueness (max 15) 5

Issues:

  • The article ends abruptly (truncated text) and the title/SEO keywords are somewhat mismatched, reducing search relevance.
  • The step‑by‑step section omits the full code for defining the formula, assigning it to a task, and saving the project, which may hinder a beginner from completing the example.
  • Title contains product-relevant keywords (API name, format, or action verb)
  • Internal links use Hugo shortcode format ({{< relref >}}) or relative paths
  • Frontmatter values containing colons are quoted to prevent Hugo build failures
  • The tutorial does not actually show how to use evaluation functions or generate a report, leaving the core topic unaddressed.
  • Tutorial content includes at least one fenced code block
  • Some helper methods (e.g., CreateTestProjectWithCustomField) are referenced but not shown or explained in the excerpt.

Files Reviewed

Required — must fix to unblock approval

tasks/english/java/formulas/write-read-formulas/_index.md

  • ❌ Frontmatter values containing colons are quoted to prevent Hugo build failures

Recommended — improve score

tasks/english/java/formulas/evaluation-functions/_index.md

  • ⚠️ The tutorial does not actually show how to use evaluation functions or generate a report, leaving the core topic unaddressed.
  • ⚠️ The article ends abruptly (truncated text) and the title/SEO keywords are somewhat mismatched, reducing search relevance.
    tasks/english/java/formulas/work-with-formulas/_index.md
  • ⚠️ Title contains product-relevant keywords (API name, format, or action verb)
  • ⚠️ The step‑by‑step section omits the full code for defining the formula, assigning it to a task, and saving the project, which may hinder a beginner from completing the example.
  • ⚠️ Some helper methods (e.g., CreateTestProjectWithCustomField) are referenced but not shown or explained in the excerpt.
    tasks/english/java/project-configuration/_index.md
  • ⚠️ Tutorial content includes at least one fenced code block
  • ⚠️ Internal links use Hugo shortcode format ({{< relref >}}) or relative paths

No issues found

  • tasks/english/java/project-configuration/configure-gantt-chart/_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.

…o prevent Hugo build failures, Title contains product-relevant keywords (API name, format, or action verb) (+2 more)
@muqarrab-aspose

Copy link
Copy Markdown
Collaborator Author

🔧 Automated fix applied — 5 file(s) updated

The following arbiter checks were targeted:

  • Frontmatter values containing colons are quoted to prevent Hugo build failures
  • 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

Re-review by the PR Arbiter is pending on the next scheduled run.

@adil-aspose adil-aspose left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ 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 160) 152
AI evaluation (max 20) 13
Total 100/100 (capped from 165)

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) 16
Clarity & readability (max 20) 13
SEO quality (max 20) 17
Actionability (max 20) 10
Content uniqueness (max 15) 9

Issues:

  • Missing explanation of how to retrieve or display the calculated values, and no sample output.
  • Links use descriptive text, not vague phrases like 'click here' or 'here'
  • The code example is truncated and contains a typo (Task task = pr...), making it impossible to copy‑paste.
  • Headings are not in sentence case and some terms (e.g., MPP) are not defined on first use.
  • Headings are not consistently sentence‑case and some terminology (e.g., “extended attribute”) could be explained more thoroughly.
  • Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
  • Important steps such as saving the project, handling exceptions, and customizing table fields are omitted.
  • Missing actual implementation details (code snippets, API calls, save/export steps).
  • Headings are not in sentence case and some language is overly promotional, deviating from the Google Developer Documentation style.
  • Title contains product-relevant keywords (API name, format, or action verb)
  • The guide stops abruptly after the first two steps; essential code for the formula and project saving is absent.
  • The tutorial is truncated and never shows how to set or evaluate a formula using functions like Sin().
  • The code sample is truncated, leaving out crucial steps such as assigning the formula and saving the project.
  • Typographical error ('perserving') and occasional wording that could be more concise.

Files Reviewed

Recommended — improve score

tasks/english/java/formulas/evaluation-functions/_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
  • ⚠️ The tutorial is truncated and never shows how to set or evaluate a formula using functions like Sin().
  • ⚠️ Missing explanation of how to retrieve or display the calculated values, and no sample output.
    tasks/english/java/formulas/work-with-formulas/_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'
  • ⚠️ The guide stops abruptly after the first two steps; essential code for the formula and project saving is absent.
  • ⚠️ Headings are not consistently sentence‑case and some terminology (e.g., “extended attribute”) could be explained more thoroughly.
    tasks/english/java/formulas/write-read-formulas/_index.md
  • ⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
  • ⚠️ The code sample is truncated, leaving out crucial steps such as assigning the formula and saving the project.
  • ⚠️ Typographical error ('perserving') and occasional wording that could be more concise.
    tasks/english/java/project-configuration/_index.md
  • ⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
  • ⚠️ Missing actual implementation details (code snippets, API calls, save/export steps).
  • ⚠️ Headings are not in sentence case and some language is overly promotional, deviating from the Google Developer Documentation style.
    tasks/english/java/project-configuration/configure-gantt-chart/_index.md
  • ⚠️ Headings (##, ###) use sentence case, not Title Case, per Google Developer Documentation Style Guide
  • ⚠️ The code example is truncated and contains a typo (Task task = pr...), making it impossible to copy‑paste.
  • ⚠️ Important steps such as saving the project, handling exceptions, and customizing table fields are omitted.
  • ⚠️ Headings are not in sentence case and some terms (e.g., MPP) are not defined on first use.

This review was generated automatically by the Tutorials PR Arbiter. Static checks evaluate frontmatter, structure, and content completeness. The AI evaluation assesses overall quality and SEO effectiveness.

@adil-aspose
adil-aspose merged commit 3d91792 into main Aug 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants