Documentation is built-in to Phype. Each class file and it's methods are meticulously commented for usage and functionality. When you have a copy of Phype you get all the ideas and information about how it works straight from the developer. But the documentation that you want to see is probably the kind that will be a convincing argument for the using Phype over any of the dozens of available content management systems and frameworks. Read more about that here.
Honestly, Phype is written and marketed by a single developer so there is not a lot of news to be had or talked about. I try to keep things simple and only present news about the important stuff like new releases. To do this I use social media as the main vessel for communicating to the world about Phype development and use. Though there are many options I have chosen to use Twitter.