@mrjn
This is really nice.
It would be really awesome to see more from this series to entice newbies, such as myself, to use Dgraph more. I know the structured blog/video can take quite some time to plan and create, and so a live coding video series would be really helpful. And @francesc would do a great job with them. 
Best practices in the design and structuring of the data.
Should it be a node, type, edge, or facet? Are there rules/questions that can be used as guides?
Naming predicates - just name, or author_name, tag_name, status_name - does it matter?
What is important to plan for the long term so that the data is not a mess?
More advanced tutorials
A similar product suggestion example
A geo/map related example
Something you really can’t do with a relational database
Basic multi-host production setup with TLS for dummies for those unfamiliar with backend, Docker, etc. I.e. how can an individual or small team more focused on the front-end setup Dgraph for production for a small project.
How would you set a dev/stage/prod setup?
How do you start with one instance and then add another two?
How to manage Draph/Go updates while it is running?
What to monitor periodically?
How do you export data from the container to your host, reload it, and verify for integrity?