Ensure docs are updated for current code.

[lonnieezell]

Need to make sure the docs match up to the current state of code. While I've got a couple of people assigned to this task, feel free to send PR requests for docs if you want!

[jim-parry]

Remaining to do:

• Update session writeup in user guide
• Update contribution guide
• Move reference docs from user guide to API docs ... agreed to leave this for now
• Contrast our style guide vs PSR-1 and PSR-2
• Contrast our loading vs PSR-4
• Document security practices plan <"real" doc is separate issue for pre-alpha 2>
• Document the roadmap or the roadmap process -> JLP
• Document "Running from the CLI"
• Document "Managing Multiple Applications"
• Document "Multiple Environments"
• At least a simple writeup on CI4 "internals", to guide contributions
• Rework the "Upgrading from 3.x to 4.x page" in the installation section

New docs needed:

• Debugging - Kint and the Debug Toolbar
• Content Negotiation
• Headers in Incoming Request
• Security library (CSRF)
• Headers in Response
• Content Security Policy in Response
• Uploaded Files (FileCollection and UploadeFile classes)
• URI library

[lonnieezell]

I added a couple of the pages that need to be written to that list, just so that we can keep it to a single spot.

Over the last week or so, I've been going through each page from the top down trying to ensure it all matches the current stuff, plus has consistent formatting with certain things (like bold for file paths), and writing additional pages that don't yet have content.

Oh - and FYI- we should be 100% compatible with PSR4 autoloading. If not, let me know and I'll tweak, but I'm pretty sure we are.

[jim-parry]

Good to see additions! :)
I suspect we are compatible with PSR-4, but with our own extensions, and I think that merits explanation.

[lonnieezell]

I suspect we are compatible with PSR-4, but with our own extensions, and I think that merits explanation.

Good point. Also, we should probably have something that describes the file-naming scheme. I'm sure that exists in the CI3 docs somewhere but don't think there was ever a single spot that said, "This is how it's done and why".

[lonnieezell]

I've added the Multiple Environments docs, but it wouldn't hurt to revisit this and expand a little bit in the future with a little bit more of a tutorial feel.

[lonnieezell]

What type of information were you thinking of in the "internals" guide?

[jim-parry]

I am pretty sure that everything will need revisiting!

"Internals guide" ... basically what a developer would need to know, beyond the style guide, to create a package/class or extend one

• namespace conventions (do we have specific places we want to put stuff?)
• how such a package would fit in (eg updating Config\AutoloadConfig?)
• unit testing expectations (eg all public or protected methods, not just "how to", which is in tests/readme)
• interface/abstract/concrete class expectations/guideline?

[lonnieezell]

I'll tackle the internals guide, then, unless you wanted to to become more familiar with it.

[jim-parry]

That would be great, thanks :)

I am reviewing the other new pages, and plan to add some caveats & dire warnings to the main readme :-/