Mikey Lombardi (He/Him)

As a Puppet Content Template user, developer, and maintainer, I want to be able to refer to a document which explains the difference between project templates and item templates and...

As a Puppet Content Template developer, I want to be able to refer to a walkthrough for designing and implementing a complex template so I can understand in practice how...

As a Puppet Content Template developer, I would like to be able to reference a walkthrough which explains how to create my own template with minimal complexity and cognitive load...

As a user, I would like to be able to automatically open my narrative/concept docs in my browser instead of my terminal.

It is already possible to install a package from locally available archive, remotely available archive (ie download then install), or git URI. As a user, I would like to be...

Once the version command is fully generic, it can be reused in other projects/apps, as `build` has been in PRM. ## Acceptance Criteria - [ ] Add a `VersionCommand` struct...

As with `build`, the `explain` command can be fully genericized for reuse without re-implementation in other projects such as PRM. ## Acceptance Criteria - [ ] Convert the `var` declaration...

The `ConfigProcessorI` interface requires a valid interface to have two functions: `CheckConfig()` and `ProcessConfig()`. On inspection, `ProcessConfig()` is an install-only function which uses data returned from the currently private `readConfig()`...

The install command is extremely similar in `pct` and `prm` - the primary differences are in language about the _type_ of package being installed. If `install` is fully genericized, it...

The functionality in PCT which enables a user to turn a template into a package should be genericized for reuse in PRM's tool building functionality.