Refine Project Management documentation (structure, clarity, subpages) - #183
Open
hkostadinov28 wants to merge 31 commits into
Open
Refine Project Management documentation (structure, clarity, subpages)#183hkostadinov28 wants to merge 31 commits into
hkostadinov28 wants to merge 31 commits into
Conversation
Introduces a dedicated Cases subpage under Project Management, explaining how tasks are executed, tracked, and managed in ERP.net, including context, communication, hierarchy, backlog, and Kanban flow.
Image Update in project-management.md
Adds a new Project Management subpage explaining how Areas, Project Groups, and Milestones help structure projects as they grow in scope and complexity. The article focuses on: - Organizing projects into logical areas and phases - Managing programs of related projects through Project Groups - Using milestones to create orientation and rhythm without adding overhead Includes navigation links to the main Project Management page and related subpages.
Introduction revised
Introduces a new Project Management subpage explaining how Project Types, Case Categories, and WIP limits help manage flow, capacity, and focus across different types of work.
Adds a Project Management subpage explaining Assignment Rules and User States. Covers automated task distribution, shared status semantics, and process stability at scale.
…k-management/project-management/project-management.md
… features/work-management/project-management/areas-project-groups-milestones.md
…project-management/cases.md
…o features/work-management/project-management/types-case-categories-wip-limits.md
…atures/work-management/project-management/assignment-rules-user-states.md
Link Project Management section with subpages via dedicated toc.yml and index.md
Image Cases was uploaded
Reworked the remaining sections to reduce generic SaaS language and make benefits more concrete and verifiable. Improved narrative flow and readability while keeping the original ideas and messages. Reduced reliance on bullet-heavy formatting by converting many lists into prose. Added a compact “Why ERP.net” section focused on platform specifics: explainability, enforceable rules/constraints, traceability, consistent models, and predictable processes. Kept existing internal links and the “Try now” call-to-action intact.
Rewrote the “Cases” sub-article for Project Management in @@name to align with info.erp.net style and structure. Reduced generic SaaS phrasing by grounding claims in concrete, checkable mechanisms (ownership, state, history, context, time markers). Consolidated overlapping sections to remove repetition while preserving all key ideas and messages. Kept all section headings unchanged and ensured markdown line-break rules are followed (sentence-per-line, explicit paragraph breaks). Added a compact “Why ERP.net” section highlighting platform specifics: explainability, enforceable rules/states, traceability, and consistent concepts across @@name
…o.erp.net Rewrote the sub-article to align with info.erp.net style while preserving the original structure and section headings. Reduced generic SaaS phrasing by grounding claims in concrete, checkable mechanisms (type-driven context, category-based work classification, explicit WIP boundaries). Clarified the relationship between Project Types, Project Groups, and Case Categories with tighter, more practical explanations. Improved narrative flow and readability using sentence-per-line Markdown formatting and clean paragraph breaks. Added a compact “Why ERP.net” section emphasizing platform specifics: explicit models, enforceable rules, traceability, and predictable processes in @@name.
Rewrote the sub-article with the same section headings, reducing generic SaaS phrasing and grounding claims in concrete, checkable mechanisms in @@name. Clarified the conceptual distinction between System States (lifecycle phases) and User States (business sub-stages), and explained how they work together. Expanded the “Assignment Rules” section with high-level evaluation logic (trigger on create/attribute change) and deterministic conflict resolution (priority + ordering). Added two micro-scenarios: one illustrating rule-based routing/handovers, and one illustrating how User States make waiting reasons explicit and reportable. Improved readability with sentence-per-line Markdown formatting and clean paragraph breaks.
lines added
lines refinement
Rewrote the sub-article with the same section headings, using sentence-per-line Markdown formatting and clean paragraph breaks. Reduced generic SaaS phrasing by grounding claims in concrete concepts: Project Groups (program-level view), Project Areas (in-project structure), and Milestones (reference points for progress). Added two micro-scenarios to make the concepts practical and verifiable (Project Groups; Areas + Milestones). Clarified the role of program-level financial visibility under Project Groups without overpromising. Included a single screenshot placement recommendation (Project Areas section) to support the core “structure inside the project” message.
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
1 participant
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.
Summary
This PR updates the Project Management documentation under
features/work-management/project-management/.The goal is to improve clarity, structure, and real-world readability,
while keeping the content aligned with how Project Management works in ERP.net.
What’s included
index.md)Scope
This PR affects only documentation under:
features/work-management/project-management/No functional or technical changes outside this section.
Notes for reviewers