ASPEER-MakeMaker-Markdown-Publish

 view release on metacpan or  search on metacpan

CONTRIBUTING.md  view on Meta::CPAN

# Contributing to ASPEER::MakeMaker::Markdown::Publish

Bug reports and focused contributions are welcome. Search the
[GitHub issues](https://github.com/aspeer/pm-ASPEER-MakeMaker-Markdown-Publish/issues)
before opening a new one, and include a minimal reproduction where possible.

Fork the [GitHub repository](https://github.com/aspeer/pm-ASPEER-MakeMaker-Markdown-Publish),
create a topic branch, keep changes focused, and submit a GitHub pull request.
Run `perl Makefile.PL`, `make test`, and `make disttest` before submitting.

Do not include credentials or private data. Report potential vulnerabilities
privately as described in [SECURITY.md](SECURITY.md).

SECURITY.md  view on Meta::CPAN

Please report security vulnerabilities via GitHub private vulnerability reporting:

https://github.com/aspeer/pm-ASPEER-MakeMaker-Markdown-Publish/security/advisories/new

If you cannot use GitHub, report the issue privately to Andrew Speer
<andrew.speer@isolutions.com.au>. Do not report vulnerabilities through public
issues, pull requests, mailing lists, social media, or other public forums.

Include the affected version, Perl version and operating system when relevant,
reproduction steps or a test case, relevant logs or code, whether exploitation
is known, and whether you want public credit. Do not include credentials or
other sensitive information unless strictly necessary and safe to share.

For triage or CVE coordination, you may also contact the CPAN Security Group at
cpan-security@security.metacpan.org. For a compromised PAUSE account, contact
pause-admin@perl.org.

## Supported Versions

Security fixes are normally made against the latest release on CPAN. Older
releases are not routinely supported unless a backport is practical and

lib/ASPEER/MakeMaker/Markdown/Publish.pm  view on Meta::CPAN

cannot be combined with `config`. MkDocs accepts supplemental YAML; the Node
publishers accept the extension functions documented by their engine modules.

For Workers Static Assets, place `wrangler.jsonc` or `wrangler.json` in the
project root. `publish_cloudflare` discovers those names in that order, so no
Cloudflare publication metadata is needed for the usual layout. Set
`cloudflare => {config => 'deploy/wrangler.docs.jsonc'}` inside `publish` to
select a file elsewhere. Optionally set `wrangler` to the executable path or
`environment` to an authored Wrangler environment in the same `cloudflare`
hash. Wrangler uses its own login or environment for authentication; do not
put credentials in metadata. Deployment does not change Git.

A minimal project-root `wrangler.jsonc` is:

```jsonc
{
    "name": "example-documentation",
    "compatibility_date": "2026-09-29"
}
```

lib/ASPEER/MakeMaker/Markdown/Publish.pm  view on Meta::CPAN

cannot be combined with C<config>. MkDocs accepts supplemental YAML; the Node
publishers accept the extension functions documented by their engine modules.

For Workers Static Assets, place C<wrangler.jsonc> or C<wrangler.json> in the
project root. C<publish_cloudflare> discovers those names in that order, so no
Cloudflare publication metadata is needed for the usual layout. Set
C<<< cloudflare => {config => 'deploy/wrangler.docs.jsonc'} >>> inside C<publish> to
select a file elsewhere. Optionally set C<wrangler> to the executable path or
C<environment> to an authored Wrangler environment in the same C<cloudflare>
hash. Wrangler uses its own login or environment for authentication; do not
put credentials in metadata. Deployment does not change Git.

A minimal project-root C<wrangler.jsonc> is:


 {
     "name": "example-documentation",
     "compatibility_date": "2026-09-29"
 }
The target supplies the generated site using Wrangler's C<--assets> option, so
the file does not need an C<assets.directory> setting. Choose a unique Worker

lib/ASPEER/MakeMaker/Markdown/Publish.pm.md  view on Meta::CPAN

cannot be combined with `config`. MkDocs accepts supplemental YAML; the Node
publishers accept the extension functions documented by their engine modules.

For Workers Static Assets, place `wrangler.jsonc` or `wrangler.json` in the
project root. `publish_cloudflare` discovers those names in that order, so no
Cloudflare publication metadata is needed for the usual layout. Set
`cloudflare => {config => 'deploy/wrangler.docs.jsonc'}` inside `publish` to
select a file elsewhere. Optionally set `wrangler` to the executable path or
`environment` to an authored Wrangler environment in the same `cloudflare`
hash. Wrangler uses its own login or environment for authentication; do not
put credentials in metadata. Deployment does not change Git.

A minimal project-root `wrangler.jsonc` is:

```jsonc
{
    "name": "example-documentation",
    "compatibility_date": "2026-09-29"
}
```