Revise PHP How To Guides #279
Labels
documentation
Improvements or additions to documentation
maintainer-cta
An issue that asks Paketo subteam maintainers to take action (not just Content maintainers)
Now that Paketo's docs have been split up into categories: Concepts, Reference, and How To, it's a good time to bring fresh eyes to each type of documentation and help them fulfill their intended purposes.
The guiding ideas for what makes a good How To guide come from Divio.
Some key takeaways about How To guides:
In other words, if someone comes to a How To guide, it's probably because they have experienced a problem they don't know how to solve. Therefore, Paketo's how-to guides shouldn't just enumerate or expose a buildpack's features (e.g. the existence of a certain configuration environment variable). They should each address a user's problem, and (probably) use buildpack features to achieve the desired result. Many buildpack users' problem is, "I have a _______ app and the buildpack isn't building it correctly." So sections like "Build a ________ app" might be useful. (e.g. "Build a React app", "Build a Rails app")
For the sake of consistency, each guide title in Paketo docs should complete the sentence "How do I ..." . For instance, use "Install a Custom CA Certificate" instead of "Installing a Custom CA Certificate" or "Custom CA Certificates"
For some examples/inspiration, see the Paketo Go how to guides, which have been revamped with Divio's guidelines in mind.
Specifically, for this issue, the @paketo-buildpacks/php-maintainers should have a look at the How To documentation for PHP and see how the guides there can be improved.
EDIT
We also want to add a Getting Started guide to https://paketo.io/docs/ that shows a PHP example.
The text was updated successfully, but these errors were encountered: