MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Selling_the_Benefits_of_Project_Management",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "142": {
                "pageid": 142,
                "ns": 0,
                "title": "Report backs afternoon",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "REPORT BACKS\n\n'''Organization project management:'''\n\n*End user education, it is important to work with the different personalities in tech projects\n* Communicating, picture is worth a thousand words.\n* Emerging projects last minute, you have to be a buzzkill and bring people back to reality.\n* PM is not a series of switches but a series of dials that require adjustments\n\n'''Overthrowing the client:'''\n\n* Identified things about the consultant client relationship, focused on whether is about the money.  \n* The necessity to establish trust, that you're providing value for the money, exchange of knowledge for money is fair\n* There is no relationship between the money and the technology provider. \n* It is about relationships not about technology, relationship between client and contractor you will build more than the road if the clients are happy.\n\n'''Basecamp:''' Moved to Overthrowing\n\n'''Wikis:'''\n* You can use wikis to get a sense of who's contributing in a team in ways that you wouldn't if you were using regular tools\n* Wikis are the ultimate example of technology being more horizontal.\n* Wikis as great documentation and KM tool, simple straightforward sketch for how to do wiki project management\n* Slit between wikis that are file based and database based, things to look at.\n\n'''Software development:'''\n* When you decide to develop your own software, a consortium based model can provide mentorship and possibly some funding.\n* Markets that are not addressed because they are specific"
                    }
                ]
            },
            "143": {
                "pageid": 143,
                "ns": 0,
                "title": "Report backs from sessions morning 2",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "REPORT BACKS\n\n'''Collaboration tools session'''\n* Synchronous events, multitasking is a problem\n* Less is more, don`t have too many tools\n* Joomla! debugging session as example, different tools in combination\n\n'''Database design:'''\n* From scratch vs. off the shelf, differences\n* Hybrid model\n* Think of the information before you go to the technology\n* Documentation is extremely important, wiki, tracker\n\n'''Website cost:'''\n* Getting a sample invoice from a vendor\n* Be very aggressive and specific details\n* Use standard off the shelf items, custom has unforeseen costs\n* Large range of cost"
                    }
                ]
            }
        }
    }
}