Board Thread:New Features/@comment-24739709-20150518230347/@comment-2240397-20150522172710

Again thanks for lot of ideas and constructive criticism!

We know that it's possible to hack current infoboxes to look good on mobile. That's great and thank you for doing it! It helps us a lot. However, what we are trying to accomplish here is much more than just mobile view. We would like your infoboxes to look great not only on desktop and mobile web, but also in apps. We want to make infobox data available through API so you could build better bots or even your own application using this data. Finally, we could use this data to have better search, enhance SEO, build more accurate recommendations and build infobox editing tools.

This stage is just the first step toward possibilities that are opened by data and view separation. And to make all of these features great we want to hear your feedback as early as possible. That is why, this project is for volunteers only and so far, so minimal in its features. However it's growing with your help!

We finally have the first version of documentation: Help:PortableInfoboxes. Thank you Ducksoup for adding it to the blog post.

Fewfre: Great idea with the NavBoxes. Would like to help us build/test new NavBox markup?

Rigel Kent: Thanks for the markup suggestions! I'll pass it to our engineering team for consideration.

SuperSajuuk: We know that the the current version of the infoboxes is very minimal, only few building blocks are available. However, you hit something with Narutopedia. One of the great benefits of this new markup is clear separation of data from the view which gives us access to near semantic data. We hope to use it as a platform for more features in near future.

SpyTec: Yes, the LUA modules can be invoked from within the new markup. We have also tested the size of the new markup and, thanks to auto-hiding empty rows, they need less markup to render.

Thanks to feedback we have learned about the need for appending and prepending data and we are working on solving this use case. Please share with us if you some ideas or suggestions on how such markup should look like.