Skip to content

Docs(Plugins): Migrate existing plugin content to separate files #426

@JesseStutler

Description

@JesseStutler

Goal

Decompose the monolithic content/en/docs/plugins.md file into individual, self-contained documentation files for each plugin.

Context

The single plugins.md file has become large and difficult to maintain. Migrating each plugin's documentation to a separate file will improve organization and make future updates easier. But we should done #425 first

Acceptance Criteria

  • The content/en/docs/plugins.md file is removed.
  • A new directory, content/en/docs/plugins/, is created.
  • For each plugin originally in plugins.md (e.g., Gang, Binpack, Priority), a corresponding Markdown file is created in the new directory (e.g., content/en/docs/plugins/gang.md).
  • The content for each plugin is accurately migrated from the original file to its new file.
  • Content that is outdated or inconsistent with the current scheduler implementation is updated for accuracy( e.g., Predicate and NodeOrder's description is not correct in current doc)

Metadata

Metadata

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/documentationCategorizes issue or PR as related to documentation.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions