@weierophinney I think in many components we do have invalid Plugin Manager configuration - see:

https://github.com/zendframework/zend-text/blob/master/src/Table/DecoratorManager.php#L42-L44

and test I have added in this PR.

I believe these aliases should be added into $aliases property.

In the current state these "aliases" are not usable.

I have a Laravel Zero based project which using an ASCII logo feature depends on this library, and it turns out it breaks on PHP 7.4.

We get the error: Invalid characters passed for attempted conversion, these have been ignored at https://github.com/zendframework/zend-text/blob/master/src/Figlet/Figlet.php#L1091

Will take a look later in the exact issue and try fixing, for now I just stopped using this feature which was cosmetic only, so I figured would throw this in here in case someone else finds this.

Depends on: https://github.com/zendframework/zend-servicemanager/pull/91 https://github.com/zendframework/zend-servicemanager/pull/92 https://github.com/zendframework/zend-servicemanager/pull/93 (for test)

We need to test against 7.2, and fix any errors observed.

Additionally, we can:

• Remove support for HHVM
• Add support for PHP 7.1
• Remove support for PHP 5.5.

With version 2 package has been renamed from satooshi/php-coveralls to php-coveralls/php-coveralls, and the script has been renamed from coveralls to php-coveralls

• Checked all headers (Fixes #4)
• Checked all code blocks (Fixes #5)
• Checked all blockquotes (Fixes #8)
• Checked for tables (none) (Fixes #7)
• Checked for content, and for figlet representation (Fixes #6)
• Updated to use mkdocs
  • added HTML landing page to swap in
• Adds build automation tooling to travis configuration

I've also updated the patch to ensure that all PHP targets have builds against both v2 and v3 of zend-servicemanager; previously, PHP 5.5 and 5.6 were testing against v2, and PHP 7 and HHVM were testing against v3.

Check the document for bad blockquoutes

TLDR; Check blockquotes are formatted correctly using > and check headings in blockquotes are using ###

Blockquotes are donated by a single greater than character and then a space. Make sure all the blockquotes in every doc file are correctly formatted. Headings in blockquotes should use ### and not bold.

Any paragraph spacing in blockquotes should be marked using a single greater than, then a space.

Check the tables in a document

TLDR; All tables should be in the format of GHFM using | and - as horizontal and vertical separators respectively

Check all tables are in the correct format. Please don't use leading and trailing | - more information on github flavoured markdown tables can be found here.

Check docs for other problems

TLDR; Cast your eye over the documetation for any problems not covered in the other issues

Things slip through the net, so check the documentation for other problems that have been missed. Common other problems include

• Bullet lists (should be single * then space at the start of line)
• Inline code - should be marked by three backticks at start and finish
• bookdown.json file is correctly formated and has the right escaping
• Links between documentation using RST have been stripped
• Any other RST has been removed correctly
• Anything and everything not covered

If you end up fixing the same problem over and over, please ping Gary Hockin - we may be able to add bespoke issue for that problem, or fix in automated capacity

Check code blocks are correct

TLDR; Check in all files that codeblocks are correct, in PSR-2 format and have PHP syntax highlighting applied.

Code blocks should be in the following format...

```php
 'ZEND-FRAMEWORK');

// No required options
$rendererOptions = array();
$renderer = Barcode::factory(
    'code39', 'image', $barcodeOptions, $rendererOptions
);

```

Note the three backticks then php in the opening fence, and the closing fence is just three backticks. It's common for the opening backticks to have no code type, or something like source.

Code should also have been automatically formatted into PSR-2 format, but sometimes these slip through the net.

Check headers are correct

TLDR; Headers should use the #, ## etc to format different levels of headers, and not be underlines using ===== or ``-----`, or be psuedo header using bold

Check all headers on the documentation - headers should use the hash style of declaration rather then be underlined with equals or dashes. The more hashes, the more of a subheading. Eg:

• # is equal to <h1>
• ## is equal to <h2>
• ### is equal to <h3>
• #### is equal to <h4>
• ##### is equal to <h5>

Headings should be appropriate for their level in the documentation.

Psuedo headers using bold tags ** should be replaced with appropriate level of heading tag.