Local articles have 2 types

• Collaboratively edited main articles for items only in Wikidocumentaries will be displayed similarly to Wikipedia articles for items that exist in Wikidata and Wikipedia.
• POV articles are treated as primary sources and should not be edited by others than the original writer. They can be quoted and remixed. They fall into two categories (specifically in the UI), but that needs to be reconsidered if it is necessary.
  • Testimonials, memoirs
  • Writings, texts, articles

Local articles are written in the Wikidocumentaries wiki. Translations of an article exist as separate entities in the main namespace (TBD).

• The main article, when it exists in Wikidocumentaries instead of Wikipedia, and its translations, are directly linked to the topic item. Topic items are created when a topic cannot be created in Wikidata.
• POV article will need its own item that connects the translations together and links to related topics.

The users should be able to use translation tools to create translations of an article. Can Content Translate be adapted for this purpose?

For users to be able to easily write articles, they should be able to use Visual Editor.

Creating links in the local articles is different from creating links in Wikipedia articles. These articles must link to Q-items to be able to link to all topics in all languages.

In the Vue interface, the local main article is placed in the Article section. The POV articles are placed in their own section(s). There are two options to categorise:

• Testimonial and memoirs of different data types are placed in a common section and factual writings, articles etc are placed in another. The problem lies with the mixed specifications of different data types to manage the section.
• User-contributed content is categorised based on the data type. Video is displayed in a video section, texts are displayed in another. This is easier to manage, and the content type can be made visible in another way.

Currently, tables, galleries, images etc. are stripped from the Wikipedia article. We should gradually build them back while allowing these content types to be used in the local articles as well. Some ideas for a wiki article > Vue transformations.

• Article layout can be made more enjoyable. The article text body can be made enjoyably narrow.
• The images can be made expandable or full-screen.
• Tables can be brought back with neat styling
• Listeria lists can be turned into different kinds of Vue components, for example galleries based on the underlying SPARQL query.
• A "Link harvester" interface could be built for articles. With its help, statements could be added to Wikidata. The subject is the page topic and the object is the link target. The user is asked to find the corrects predicate. When saving, the Wikipedia article would be stated as the source, if no other source is declared.
• A "Source harvester" interface could be built for articles. It would read and display a citation tag's content and allow editing the data. It would then try to find the source in Wikidata and write it if it does not exist. It would additionally write the association between the topic and the source to Wikidocumentaries including the details of the reference (page, retrieval date, quotation etc.) This data could also be added to Wikidata.
• Video could be made full-screen in the Vue layout.

This means that creating articles in Wikidocumentaries would focus on making MediaWiki articles.

Another article-like data type can be a story, which is made of components. There has been thinking made around this in WMF and this should be developed in accordance. In Wikidocumentaries, this can evolve into different flexible data stories: map stories, time-based minimovies and scrollable articles.