Change directory that doc-en is cloned into

[tiffany-taylor]

The reasoning for this change is so that it's easier to start working with the docs with fresh clones from github. doc-base/configure.php expects an en directory, but if I clone doc-en repo from github, I have a doc-en directory with manual contents in the doc-en folder. This requires further renaming and directory juggling to get the tooling to work together nicely. By cloning into doc-en/en, this leaves a doc-en base directory that can contain en for the doc-en repo, phd and doc-base, then the rest of the tutorial instructions work nicely.

[salathe]

This change is only a small improvement to the instructions: those instructions would be much better off being reviewed and amended as a whole rather than making isolated "improvements" (the SVN to Git changes are a perfect example of what not to do).

@tiffany-taylor - would you be willing to spend some more time on that?

Issues that would remain, to name a but few:

• There is no mention of checking out doc-base!
  • This used to be okay with the old SVN module instructions, which pulled down both doc-base and en from SVN. However, the conversion to the Git command messed this up, and you're now building on top of that.
• The directory layout makes little sense.
  • It is stated that /tmp is the "root directory" or workspace for the instructions, so why not just put phd, en, doc-base, etc. directly under /tmp?
• Directories are referenced in the instructions that won't exist if those instructions are followed
  • doc-base as mentioned above
  • and later /tmp/git/doc-en/mydocs/php-web/ is mentioned, which won't exist.

My suggestions for this page:

• Copy the workspace layout and cloning instructions from https://github.com/php/doc-base
• Review and amend this whole page to actually make it so that one can work the instructions step-by-step and have them "work nicely"

[tiffany-taylor]

I'll step through it tomorrow and give an attempt at rewriting it.