{
    "href": "/post/2016/12/29/pds-skeleton-standard-now-in-beta/",
    "relId": "2016/12/29/pds-skeleton-standard-now-in-beta",
    "title": "PDS \"skeleton\" Standard Now In Beta",
    "author": "pmjones",
    "markup": "html",
    "tags": [
        {
            "href": "/tag/php/",
            "relId": "php",
            "title": "PHP",
            "author": null,
            "created": null,
            "updated": [],
            "markup": "markdown"
        },
        {
            "href": "/tag/programming/",
            "relId": "programming",
            "title": "Programming",
            "author": null,
            "created": null,
            "updated": [],
            "markup": "markdown"
        },
        {
            "href": "/tag/standards/",
            "relId": "standards",
            "title": "Standards",
            "author": null,
            "created": null,
            "updated": [],
            "markup": "markdown"
        }
    ],
    "created": "2016-12-29 15:39:29 UTC",
    "updated": [
        "2016-12-29 15:39:29 UTC"
    ],
    "html": "<p>I am proud to announce the immediate availability of <a href=\"https://github.com/php-pds/skeleton/tree/1.0.0-beta1\"><code>pds/skeleton</code></a> 1.0.0-beta1 for inclusion in your PHP package.</p>\n<p>The <code>pds/skeleton</code> standard defines specific names for specific kinds of root-level directories in PHP packages. If you use all the directory and file names in the standard, your package will look something like this:</p>\n<pre><code>bin/            # executable files\nconfig/         # configuration files\ndocs/           # documentation\npublic/         # web server files\nresources/      # other resource files\nsrc/            # PHP source code\ntests/          # tests\nCHANGELOG       # change notes\nCONTRIBUTING    # contribution guidelines\nLICENSE         # licensing and copyright\nREADME          # read-me-first file\n</code></pre>\n<p>Believe it or not, roughly <a href=\"https://github.com/php-pds/skeleton_research#addendum\">78 thousand packages on Packagist</a>, from tens of thousands of vendors, already appear compliant with <code>pds/skeleton</code>.</p>\n<p>To formally indicate that your package attempts to comply to <code>pds/skeleton</code>, add it to your package manifest as a development requirement. For example, if you use Composer, you can do something like the following:</p>\n<pre><code>\"require-dev\": {\n    \"pds/skeleton\": \"~1.0\"\n}\n</code></pre>\n<p>(Alternatively, mention in your README that the package attempts to comply with <code>pds/skeleton</code>.)</p>\n<p>This standard will remain in beta for at least two weeks, to give ample time for additional public review. If you find errors or omissions, please be sure to <a href=\"https://github.com/php-pds/skeleton/issues\">open an issue</a> on it.</p>\n<hr>\n<p>As a side note, <a href=\"http://getproducer.org\">Producer</a> will end up supporting <code>pds/skeleton</code> and validating against it by default. This will mean a BC break for Producer, so look for a 3.x version soon!</p>\n"
}