Publishing NEs, Tiles and Fields

Top  Previous  Next

Published not publishedWhen you publish an NE or map, you control the information that becomes public. This means that, when you publish work in progress to other members of your team, you can pick exactly what you want to publish, and what you don't want to publish, without creating a "new" set of documentation. Simply unpublish any association, field or tile that you don't want to publish. Unpublished information works and appears within the desktop environment: the difference only arises when the NE or map is published to the web.

 

All information objects in the DNE (fields, association NEs, or tiles) can be either published or not published. A published object is automatically included when a linked map, NE or tile is published or exported, whereas an unpublished object can either be included or excluded from the publication of a map, NE or tile. By deciding to not publish an object you can maintain control over information that is of a sensitive nature.

 

In any NE, you can choose to not publish one or any combination of association NEs, tiles and fields. This means that you have complete control over what information you make public and what information you keep private. Unpublished objects are fully functional within the confines of your own DNE, but they are tagged such that reference to them can be removed easily when exporting or publishing any NE in your DNE.

 

Whether or not an object is published is easy to track. By default, everything is published, but if an object is not published, the unpublished object turns blue. In the example NE, the blue fields, associated NEs and tiles are unpublished; the others are all published.