well if you work a lot with Django than you have the same stuff like that aswell: > https://docs.djangoproject.com/en/1.10/howto/initial-data/ https://docs.dja

well if you work a lot with Django than you have the same stuff like that aswell: > https://docs.djangoproject.com/en/1.10/howto/initial-data/ https://docs.djangoproject.com/en/1.10/howto/initial-data/ > https://docs.djangoproject.com/en/1.10/topics/serialization/#xml https://docs.djangoproject.com/en/1.10/topics/serialization/... of course you can't just use it directly in Python. Documentation is about reading, 90% of the stuff is just reading. And there is clearly everything said about the snippet above the snippet: "In the code samples below, we’ll use the following JSON:". Since you already visited the last page, you should've probably already understood how to parse the Json. I see a lot of issue's on a daily basis and I even give some examples if needed, even if a discussion should take place on a mailing list, however I think before ANY issue should be made, people should carefully read and check if there is even an issue. But Playframework's documentation is already really good. There are some cases which aren't described so good, but they aren't even well described in Django I guess, what I mean is testing, a lot of this topic is not easy and you probably learn on your way of getting a better developer to get better in it. I started to contribute to Play! In the middle/start of the year and a lot of people are just helpful (and busy). And I've seen plenty of one character spelling mistakes merged. If something is not strictly understandable we even give a advice to discuss it on the mailing list.