[1;34mNAME[0m
        Test Program for App::POD::Manual

[1;34mAUTHOR[0m
        Patrick Spek

[1;34mVERSION[0m
        0.0.1

[1;34mLICENSE[0m
        GNU Affero GPL v3

[1;34mA test program for App::POD::Manual[0m

        Now we're reaching the real POD document that I care about. Let's add in
        some test cases as well here.

  [1;34mText styles[0m

        • This text is [1mbold[0m

        • This text is [3mitalic[0m

        • This text is [4munderlined[0m

        • This text is [1mcode[0m

        • This text is a link[1] to my blog

        • This text is normal 

        • I'm running ouf of ideas [2]

  [1;34mLists[0m

          • Starting off at level 2

                • Progressing to leel 5

        • Back to level 1

          • On to level 2

            • On to level 3

              • On to level 4

                      • But what about an item with content that goes
                        well beyond the 80 characters?

                          • Which can easily occur in a block item, for
                            instance. It should wrap around and bring the
                            next lines on a similar level of indentation.

                            The question is, does it?

    [1;34mDefinition lists[0m

        [36mpod[0m
          Plain Ol' Documentation

        [36mfoo[0m
          Not the same as bar

  [1;34mCode blocks[0m

        Now on to some code blocks. These are generally used to show code
        samples.

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃[1mThis is a code block. It is indented by 4 spaces to indicate this.[0m┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

        Code samples are important to easily show a user how to interact with the
        program they're using. Nobody wants to read through pages of a manual
        when they just want to know how to use it for their particular use case.

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃Named code block                                                                                     ┃
            ┠─────────────────────────────────────────────────────────────────────────────────────────────────────┨
            ┃[1mThis is a code block by name. It is covered by a begin and end block. It has no limit to line length.[0m┃
            ┃[1mSpaces  in  the  code  are    preserved    .[0m                                                         ┃
            ┃                                                                                                     ┃
            ┃[1mSimilar for newlines, actually.[0m                                                                      ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃[1mCode on a single line should also work as expected.[0m               ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

        And that concludes the test for code blocks!

  [1;34mIO blocks[0m

        There are blocks to denote program input and output, called IO blocks.
        They also have in-line variants:

        • This is [33mkeyboard input[0m

        • This is [35mterminal output[0m

        The bigger blocks deserve a test as well, I think:

    [1;34mShort-hand input and output[0m

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃[33mA simple input line[0m                                               ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃[35mA simple output line[0m                                              ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

    [1;34mBig input and output blocks[0m

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃[33mA larger block of input.[0m                                          ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

            ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
            ┃[35mA larger block of output.[0m                                         ┃
            ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

  [1;34mUnicode[0m

        And of course, let's throw in some Unicode stuff. I stole these examples
        from the documentation site, but I don't think that's a bad source of
        input for testing purposes.

        Perl 6 makes considerable use of the «[0m and »[0m characters.

        Perl 6 makes considerable use of the laquo[0m and raquo[0m characters.

        Perl 6 makes considerable use of the «[0m and »[0m characters.

        Perl 6 makes considerable use of the «[0m and »[0m characters.

        Perl 6 makes considerable use of the «[0m and »[0m characters.

        Perl 6 makes considerable use of the «[0m and »[0m characters.

[1;34mFootnotes and references[0m

        1:  [34;4mhttps://www.tyil.work[0m
        2:  Search the Internet for more!
