| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
Support *.spin pointers in addition to *.rpod pointers for external POD
files. The command-line flags used in *.rpod pointers are replaced by
the title and options key of the *.spin file. *.rpod files are
deprecated and support will be removed in a future version of DocKnot.
Add spin_thread_output method to App::DocKnot::Spin::Thread, intended
to convert thread to HTML as part of a conversion pipeline of a
non-thread input file, while still using sitemap information and
generating the page footer. DocKnot now depends on Path::Tiny.
|
|
|
|
|
|
| |
Fix unintended localization of dates in RSS output, which are supposed
to be RFC 2822 dates and therefore always use English month and day of
week names. Thanks to Slaven Rezić for testing.
|
|
|
|
|
|
|
| |
We're dropping support for \id, so require a version of Pod::Thread
that does not generate that command.
Add versions to the cpanfile for CI.
|
|
|
|
|
|
| |
Update the overall package description to reflect that it's now
primarily a static web site generator. Add Changes for the 5.00
release.
|
|
|
|
|
|
|
| |
Add a spin-rss command to run App::DocKnot::Spin::RSS on a single
file outside of recursive processing, and rename spin-file to
spin-thread, setting up a convention for handling other types of
conversion.
|
|
|
|
|
|
|
|
|
|
|
| |
Rename spin-rss to App::DocKnot::Spin::RSS, add an API, and update
the documentation accordingly. Call App::DocKnot::Spin::Thread
instead of running spin. Add a basic test for RSS and thread
generation from .rss files. Call the new module instead of
spin-rss from App::DocKnot::Spin.
This has a few horrible hacks to deal with the working directory
of thread spinning that will need a better solution later.
|
|
|
|
|
|
|
| |
Move the thread processing into its own module separate from the
machinery to drive the recursive site generation. Update the
documentation, remove duplicate documentation, and move the thread
language documentation into App::DocKnot::Spin::Thread.
|
|
|
|
|
|
|
|
|
| |
Start the grand refactor of App::DocKnot::Spin. Refactor the core
parsing code and move handling of macro definitions, string
definitions and \\ into command handlers. Tag commands with
whether they care about format arguments and remove a bunch of
useless arguments to commands that take arguments but not a format
string.
|
|
|
|
|
|
| |
Rather than construct a command line for pod2thread, call
Pod::Thread directly. Add the required version numbers for
dependency modules to the documentation.
|
|
|
|
|
|
| |
Mention the App::DocKnot::Spin dependencies in Build.PL and the
overall documentation. Make the Git::Repository dependency
unconditional rather than working around its absence.
|
|
|
|
| |
Use Test::CPAN::Changes to check the format of the Changes file.
|
| |
|
|
|
|
|
| |
Pod::Usage comes with Perl core, so follow the normal convention
of not calling out that dependency explicitly.
|
| |
|
|
|
|
| |
This comes after IO::Compress::Xz.
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the load_appdata_json helper function from App::DocKnot. This
is no longer used now that all DocKnot data is in YAML.
Properly depend on and import Pod::Usage so that docknot --help works.
Correct the REQUIREMENTS sections of the module documentation to
reflect new dependencies and the removal of a JSON dependency from
most of DocKnot.
|
|
|
|
|
|
|
| |
Add App::DocKnot::Update to the API files, fix a bit more wording
to reflect the new single metadata file layout, and add a note to
the description that DocKnot generates distribution tarballs as
well.
|
|
|
|
|
| |
Drop the current version number from the title of README.md. This is
not a common practice and doesn't seem to add much value.
|
|
|
|
|
|
|
|
|
|
| |
Drop support for the support.cpan metadata key, since the CPAN RT
instance is going away. For packages with support.cpan set, if
vcs.github was set and support.github was not, set support.github to
match vcs.github during a docknot update.
Change DocKnot to point to the GitHub issue tracker and make the
same change to the affected test data.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the metadata format to a single YAML file, with a slightly
different internal representation, whose default location is
docs/docknot.yaml. The new docknot update command (or the
App::DocKnot::Update module) will convert from the old JSON format.
The new metadata format is checked against a schema when read.
DocKnot now depends on YAML::XS and Kwalify.
Word wrap numeric lists and, in Markdown output, quoted paragraphs.
Previously these preserved the original spacing from the input text
snippets.
Require paragraphs be indented by at least six spaces, not five, to be
treated as verbatim paragraphs and left unwrapped. (Markdown
paragraphs can still use four spaces because they are wrapped in
markup lines.)
|
| |
|
|
|
|
|
|
| |
Ensure that style/critic tests pass with Perl::Critic::Freenode
installed. This fixes build issues when testing with the
perl-tester Docker image, which pre-installs that set of rules.
|
|
|
|
|
| |
Replace List::MoreUtils with List::SomeUtils and List::Util, as
recommended by Perl::Critic::Freenode.
|
|
|
|
| |
Recommended by Perl::Critic::Freenode.
|
| |
|
|
|
|
| |
Switch entirely to GitHub Actions workflows for CI.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the vcs.travis metadata key to vcs.status.travis. This will
require changes to all templates and package metadata.json files that
use this key.
Add support for generating a build status badge from a GitHub Actions
workflow. To do this, set vcs.status.workflow to the name of the
workflow that should be referenced for the badge.
Also specify DocKnot's dependencies with a cpanfile. This makes it
easier to install its dependencies with some tools, such as cpm.
|
| |
|
|
|
|
|
|
|
|
| |
docknot dist now uses IO::Uncompress::Gunzip and IO::Compress::Xz to
generate a missing xz tarball rather than running external gzip and xz
programs, which avoids test failures when those programs aren't
available or don't support the expected options. Thanks to Slaven
Rezić for the testing and report. (#131406)
|
| |
|
|
|
|
|
| |
For CPAN packages pushed to GitHub, add a license badge to the
Markdown README file.
|
| |
|
|
|
|
|
|
| |
If the native distribution generation commands create only a
gzip-compressed tarball, generate an xz-compressed tarball from the
gzip-compressed tarball during docknot dist.
|
| |
|
| |
|
|
|
|
|
| |
Use Capture::Tiny and File::Copy::Recursive to make the docknot
dist test a bit simpler and easier to maintain.
|
|
|
|
|
| |
Add new docknot dist command and App::DocKnot::Dist module, which runs
appropriate commands to create a distribution tarball.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Separate the TESTING section from BUILD AND INSTALLATION for Perl
modules in both README and README.md, and move the Lancaster
instructions to that section. Add instructions for how to run a
single test with Perl build systems. Test dependencies for Perl
modules should now move into docs/metadata/test/suffix, the same as
for packages with an Autoconf build system.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Move the description of Lancaster Consensus environment variables into
the testing section of README and README.md instead of the
requirements section, since they're more about running the tests and
less about package requirements in general.
|
|
|
|
|
|
| |
Add a Status.io badge for the CPAN version to README.md and a link to
metacpan.org in the thread output if the distribution.cpan key is set
in metadata.json.
|
|
|
|
|
|
|
| |
Use the new postfix dereference syntax and update all of the Perl
version requirements accordingly. Requires some tweaking to the
Perl::Critic configuration due to a false positive with the new
syntax.
|
|
|
|
|
|
| |
Add the Travis-CI badge to README.md and a link to Travis-CI to the
thread development links if the vcs.travis key is set in
metadata.json.
|
| |
|
| |
|
|
|
|
|
|
| |
Add a paragraph to the license section of README and README.md saying
that SPDX license identifiers are in use and providing a pointer to
the SPDX license list.
|
| |
|