[Sample] Fake Masquerade Solution (Product)

This is a sample page used to provide guidelines on how product pages should be documented. The purple note panels describe the content elements on the page.

Product pages must be located in the Product Database section.

The title of a product page should be composed of the short company name followed by the product name and suffixed with “ (Product)”.

The table below is contained in a page properties macro. The table must be structured with 2 columns, one header column containing property names and one standard column containing property values. The page properties macro makes it possible to build dynamic lists on other wiki pages in table format. For more information on this macro, please refer to the official documentation.

Vendor	[Sample] Fake (Vendor) A link to the corresponding Open-Measure vendor wiki page.
Product Name	Fake Masquerading Solution The full name of the product.
Version	`1.0` A version number for the page. Confluence keeps track of all page versions but the idea of this version number maintained manually is to inform readers of page version changes. The minor version number should be incremented whenever minor changes are applied to the page. The major version number should be incremented whenever significant changes are applied to the page.
Product Page	https://www.open-measure.org/wiki The URL of the official home page of the product.
Description	This is a short description of the product. https://www.open-measure.org/wiki, accessed 30 mar 2020 A short description of the product. Usually an excerpt of the vendor’s product web page, providing source URL and access date.
Feature / characteristic 1 Then, list the product features and characteristics row by row	✔✘ Add a green check if the characteristic or feature is implemented in the product and a red cross if it isn’t. Please note that we are working on a more sophisticated scale, you may preview it here Feature Support Scale and try to use it already. But it requires that standardized definitions for product features and characteristics be produced first, thus we may leave this for future enhancement at this current point in time.
Feature / characteristic 2	…
Feature / characteristic 3	…
…	…

For page labels, we use lower-case words with dashes. Add at least the product-record label that makes it possible to easily retrieve the list of all product pages. Add also a label with the company name and another one for the product name. Finally, add any number of complementary labels that may prove useful to retrieve that product, but do not exaggerate as too many labels is counter-productive for research purposes.