Migrate the Monkey365 documentation site from Material for MkDocs to Zensical

Abierto
  • ¿Algo no está bien?
#184 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Área
documentation

Línea de trabajo

Start with the current Monkey365 documentation site and the linked Zensical reference, then inspect the repository's existing documentation configuration and navigation. Done means the site runs on Zensical, its structure is redesigned, and the proposed architecture, collector, rule, ruleset, and contributor topics are documented with build and link validation.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

documentation enhancement epic priority-medium

Summary

Migrate the Monkey365 documentation site from Material for MkDocs to Zensical and use the migration as an opportunity to redesign and significantly expand the project documentation.

Material for MkDocs is now in maintenance mode, with development focused on Zensical. Although critical fixes and security updates will continue for a limited period, no new features are expected to be added to Material for MkDocs.

Motivation

The current documentation provides a good introduction to installing, configuring, and running Monkey365. However, many of the project's most powerful capabilities and internal concepts are not documented yet.

Migrating the documentation platform would be a good opportunity to:

  • Redesign the documentation structure and navigation.
  • Improve the contributor and authoring experience.
  • Document Monkey365's architecture and internal workflows.
  • Make advanced customisation and extension points easier to understand.
  • Help users and contributors realise the full potential of Monkey365.

Proposed documentation areas

The redesigned documentation could include dedicated sections for the following topics.

Architecture and core internals
  • High-level architecture.
  • Execution lifecycle.
  • Module and component responsibilities.
  • Authentication and connection management.
  • Internal data flow.
  • Error handling, logging, retries, and throttling.
  • Report generation pipeline.
Collectors
  • Collector lifecycle.
  • Collector structure and conventions.
  • Supported data sources.
  • How collectors are discovered and executed.
  • Creating a custom collector.
  • Collector configuration.
  • Collector output contracts.
Collector helpers
  • Available helper functions.
  • Authentication and API request helpers.
  • Pagination and retry helpers.
  • Logging helpers.
  • Error-handling conventions.
  • Performance considerations.
  • Examples of using helpers in custom collectors.
Data normalisation and aggregation
  • Normalised object structure.
  • Provider-specific transformations.
  • Type and property conventions.
  • How normalised and aggregated data is consumed by rules and reports.
Declarative rules
  • Rule schema and supported properties.
  • Rule metadata.
  • Query and condition syntax.
  • Evidence generation.
  • Severity and classification.
  • Creating and validating a custom rule.
  • Complete rule examples.
Rule evaluation
  • Rule discovery and loading.
  • Evaluation lifecycle.
  • How collected data is selected.
  • Query execution.
  • Pass and fail error states.
  • Evidence construction.
  • Debugging rule evaluation.
Rulesets
  • Ruleset structure.
  • Rule selection and grouping.
  • Creating organisation-specific rulesets.
  • Versioning and maintaining rulesets.
  • Sharing reusable rulesets.
Contributor documentation
  • Documentation development environment.
  • Documentation style guide.
  • Contribution workflow.
  • Adding new pages and navigation entries.
  • Link, formatting, and build validation.

References

Lenguaje dominante
PowerShell
Estrellas
1.4k
Forks
144
Merge medio
1 d 21 h
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de silverhack/monkey365

Todos los issues de silverhack/monkey365

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.