How does it relate to PHP Manual's "Hacker's guide"?

[Sobak]

Hi guys,

I encountered phpinternalsbook.com over a year ago, for a first time, and it's really great to see it moving towards PHP 7 changes. Kudos!

But what I wonder about is the question stated in the title. We do have PHP at the Core: A Hacker's Guide section in the PHP Manual which, I suppose, is not even close when it comes to accuracy and detailing. The problem is that we already have multiple places to describe PHP internals, and none of them is complete.

• phpinternalsbook.com
• http://php.net/manual/en/internals2.php
• PHP.net wiki

The most correct (or even idealistic?) approach for me would be to place such information where it belongs - in the PHP Manual. On the other hand, my experience tells me that current way of handling it (with GitHub, RST and separate domain) is what gives it a proper traction. Despite being part of docs team I'm fully aware that DocBook is not as friendly, our workflow and relying on SVN is even less and even small detail like having fancy domain name and design is helping to promote such resource.

What I would only like to avoid is having even bigger fragmentation. What do you think about just dropping internals2 from the manual and linking one of it's ToC sections here? When you'll consider this somehow ready, of course?

[jpauli]

I prefer contributing and adding content to this repo.
After that, people do what they want with links, etc...

We could link PHP manual here, and PHP manual could link us as well.
I don't care how and why, what I care about is content.

[SammyK]

I'm +1 for adding a link on http://php.net/manual/en/internals2.php that points to phpinternalsbook.com. It's so much harder to update the official manual that it will no doubt discourage contributions.

[Sobak]

Ok. I'll handle it on the PHP.net side (including changes to PhD if manual's ToC would came up to be unflexible), but let's wait for some stabilization first.