Latest revision as of 04:53, 22 March 2026

Community

Community describes how contributors can use this wiki as a shared technical record for PlexyDesk.

Contribution paths

improve architecture, component, and API reference pages when behaviour becomes clearer
add diagrams, screenshots, and short demo media that document actual runtime behaviour
correct source-oriented pages when code structure or exposed interfaces change
use article talk pages to discuss wording, missing details, or technical accuracy

Media contributions

Gallery is the public index for screenshots and short demo captures
Desktop Submissions explains how to prepare, upload, and list desktop screenshots
Special:Upload is the upload entry point for image and video files

Useful pages

Documentation for the main documentation map
Special:RecentChanges for a live view of current edits
Special:AllPages for the full page index
News for milestone summaries and documentation updates

Content conventions

Pages should use technical language, avoid marketing claims, and stay close to what the codebase and runtime actually support. Captions, summaries, and page text should explain behaviour precisely enough to be useful to both contributors and readers.

@@ Line 1: / Line 1: @@
 = Community =
-'''Community''' describes how people can use this wiki as a shared editorial and technical record for PlexyDesk.
+'''Community''' describes how contributors can use this wiki as a shared technical record for PlexyDesk.
-== Ways to contribute ==
+== Contribution paths ==
-* improve explanatory pages when architecture or behaviour becomes clearer
+* improve architecture, component, and API reference pages when behaviour becomes clearer
-* upload screenshots, diagrams, icons, and short videos that help explain the desktop
+* add diagrams, screenshots, and short demo media that document actual runtime behaviour
-* use article talk pages to discuss wording, structure, and missing references
+* correct source-oriented pages when code structure or exposed interfaces change
-* keep source-backed technical pages aligned with the code and the generated API reference
+* use article talk pages to discuss wording, missing details, or technical accuracy
-== Useful places around the site ==
+== Media contributions ==
-* [[Special:Upload]] for images and video
+* [[Gallery]] is the public index for screenshots and short demo captures
-* [[Special:RecentChanges]] for a live view of ongoing edits
+* [[Desktop Submissions]] explains how to prepare, upload, and list desktop screenshots
+* [[Special:Upload]] is the upload entry point for image and video files
+== Useful pages ==
+* [[Documentation]] for the main documentation map
+* [[Special:RecentChanges]] for a live view of current edits
 * [[Special:AllPages]] for the full page index
-* [[Documentation]] for the main reading map
+* [[News]] for milestone summaries and documentation updates
-* [[News]] for the current project chronicle
-== Editorial direction ==
+== Content conventions ==
-This wiki is meant to feel like a serious technical publication. Pages should explain the system clearly, avoid inflated claims, and stay close to what the source tree and runtime actually support. The goal is a record that is readable to newcomers and still useful to engineers.
+Pages should use technical language, avoid marketing claims, and stay close to what the codebase and runtime actually support. Captions, summaries, and page text should explain behaviour precisely enough to be useful to both contributors and readers.

Community: Difference between revisions