This HTML5 document contains 5 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
n5http://dbkwik.webdatacommons.org/ontology/
n3http://dbkwik.webdatacommons.org/lotrminecraftmod/property/
rdfshttp://www.w3.org/2000/01/rdf-schema#
n7http://dbkwik.webdatacommons.org/resource/Kx9Xcvgn_k-nLvpQRVIIzQ==
n2http://dbkwik.webdatacommons.org/resource/lzhs7HXr5mEtXEiWXtJqEg==
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
xsdhhttp://www.w3.org/2001/XMLSchema#
n4http://dbkwik.webdatacommons.org/resource/BjBA7Nja7Ma2lNrwQadkug==
Subject Item
n2:
rdfs:label
Help/Making Templates
rdfs:comment
If you've read the articles on the page, regarding Wiki code, you know how to add templates to a page. You might ask, however; how would one create such a template in the first place? We have tried to accomplish two things with templates this year. First and foremost, we've tried to make them more portable. Portability means that you can read content easily on any device, whether it's desktop, mobile web, mobile apps, or other second screen experiences. Tools to help with this include Portable Infoboxes and Flags. We've also been trying to make sure admins have more tools to understand and organize their templates better, through better editing interfaces and some of the information presented on the Insights platform.
n3:wikiPageUsesTemplate
n4: n7:
n5:abstract
If you've read the articles on the page, regarding Wiki code, you know how to add templates to a page. You might ask, however; how would one create such a template in the first place? We have tried to accomplish two things with templates this year. First and foremost, we've tried to make them more portable. Portability means that you can read content easily on any device, whether it's desktop, mobile web, mobile apps, or other second screen experiences. Tools to help with this include Portable Infoboxes and Flags. We've also been trying to make sure admins have more tools to understand and organize their templates better, through better editing interfaces and some of the information presented on the Insights platform. Wikia isn't done moving forward with templates yet and we anticipate this work will continue well into the coming year. But in planning our next steps for improvement, we face a unique problem. As I mentioned, templates come in many, many varieties. The sheer volume of options means that it's hard to easily, quickly, and accurately know - whether you're a human reading the code or a program analyzing the wikitext - what the exact purpose and design of a template is. To help tackle this issue for our engineers and our community alike, we've been ramping up a project called Template Types. Its goal is simple: assign a type to every template on every community. Essentially, it involves giving each template a classification such as 'infobox', 'navbox' or 'quote'.