Overview This issue tracks the process and progress for migrating PSModule module repositories to use the new Zensical-based Process-PSModule framework. This is a coordinated rollout that runs in parallel with implementation issue #336 .
The goal is to transition all 59 module repositories from the legacy MkDocs/Material build to the new Zensical framework in a staged, low-risk manner.
Related Issues Rollout Strategy Wave 1: Foundational/Core Modules (Early Adopters) Well-maintained core modules; good validation canaries
Process:
Wave 2: Utility & Infrastructure Modules Network, system, and general utilities
Process:
Wave 3: AI/Cloud/API Modules Integrations with external services and AI platforms
Process:
Wave 4: Domain-Specific & Specialized Modules Niche domains, reference implementations, fonts
Process:
Prerequisites for Rollout Before rollout begins:
Progress Tracking Wave 1 Progress (12 modules) Module PR Status Notes Base64 - Not Started Json - Not Started Yaml - Not Started Toml - Not Started Guid - Not Started Retry - Not Started Object - Not Started Hashtable - Not Started Path - Not Started TimeSpan - Not Started Uri - Not Started DateTime - Not Started
Wave 2 Progress (22 modules) Module PR Status Notes Net - Not Started IPv4 - Not Started IPv6 - Not Started Dns - Not Started Tls - Not Started GZip - Not Started MemoryMappedFile - Not Started Sodium - Not Started Jwt - Not Started GraphQL - Not Started Markdown - Not Started PowerShellDataFile - Not Started PSCredential - Not Started PSCustomObject - Not Started PSSemVer - Not Started CasingStyle - Not Started DynamicParams - Not Started Ast - Not Started Hcl - Not Started Lua - Not Started PowerShellGallery - Not Started Utilities - Not Started
Wave 3 Progress (15 modules) Module PR Status Notes OpenAI - Not Started Claude - Not Started Anthropic - Not Started DeepSeek - Not Started Gemini - Not Started GitHub - Not Started Discord - Not Started Twitch - Not Started LinkedIn - Not Started Bluesky - Not Started Confluence - Not Started AzureDevOps - Not Started CurseForge - Not Started Domeneshop - Not Started PublicIP - Not Started
Wave 4 Progress (10 modules) Module PR Status Notes Admin - Not Started Context - Not Started Context7 - Not Started DistTestModule - Not Started ElvUI - Not Started Fonts - Not Started GoogleFonts - Not Started NerdFonts - Not Started Telemetry - Not Started WoW - Not Started
Communication & Documentation Success Criteria Notes Module repositories can adopt the new framework on their own schedule; backward compatibility is maintained via Zensical's native mkdocs.yml support If any repo cannot migrate due to unsupported plugins, create a follow-up issue and track the blocker Rollout can pause between waves if issues are discovered; resumption is coordinated in comments below Next Steps Implementation issue Implement: Migrate Process-PSModule Framework to Zensical (Minor Bump) #336 completes framework migration Open PRs for Wave 1 modules (coordinate with team) Validate Wave 1 builds successfully Proceed to Wave 2 Proceed to Wave 3 Proceed to Wave 4 with extra scrutiny Close this issue when all modules are migrated (or document exceptions)
Overview
This issue tracks the process and progress for migrating PSModule module repositories to use the new Zensical-based Process-PSModule framework. This is a coordinated rollout that runs in parallel with implementation issue #336.
The goal is to transition all 59 module repositories from the legacy MkDocs/Material build to the new Zensical framework in a staged, low-risk manner.
Related Issues
Rollout Strategy
Wave 1: Foundational/Core Modules (Early Adopters)
Well-maintained core modules; good validation canaries
Process:
Wave 2: Utility & Infrastructure Modules
Network, system, and general utilities
Process:
Wave 3: AI/Cloud/API Modules
Integrations with external services and AI platforms
Process:
Wave 4: Domain-Specific & Specialized Modules
Niche domains, reference implementations, fonts
Process:
Prerequisites for Rollout
Before rollout begins:
Progress Tracking
Wave 1 Progress (12 modules)
Wave 2 Progress (22 modules)
Wave 3 Progress (15 modules)
Wave 4 Progress (10 modules)
Communication & Documentation
Success Criteria
Notes
Next Steps