Content Publication

Overview

Content publishing is a core feature that allows you to control where when and to whom content is displayed.
You can publish different content types (Routes, Posts, Announcements, Collections, and Pins) either at the application level or at the object level, depending on your needs.

Types of Content Publishing

1. Application-Level Publishing
   • Publish, unpublish, or republish a specific Route, Post, Collection, Announcement or Pin within a single application.
   • Best for content that is tied to one app only.
2. Object-Level Publishing
   • Publish a specific Route, Post, Collection, Announcement, or Pin across multiple applications.
   • Best for reusable content that should appear in more than one app.

Accessing Content Management

1. Open the side menu and click Guidance.
2. Go to the Applications tab.
3. The Applications screen appears with a list of available apps.
4. Select the desired application.
5. Open the 3-dots menu and click Manage Content.
6. The screen will display tabs for:
   • Routes
   • Posts
   • Announcements
   • Collections
   • Pins

Each tab has three columns: Assign, Unassignand Publish.

Publishing Content

Content can be published in two ways:

1. Drag and Drop
2. From Context Menu

Drag and Drop

1. Select the desired tile.
2. Drag and drop it into the Published column.
3. A Publish dialog will appear.
4. Enter the required publish details.
5. The content will then move to the Published column.

Using the Options Menu

1. Select the desired tile.
2. Click the 3-dots menu and choose Publish.
3. A Publish dialog will appear.
4. Enter the required details and click Publish.
5. The content will then move to the Published column.

Managing Published Content

By simple drag and drop or by context menu , user can perform following options as well.

• Unpublish: The content will be removed from guest users but remain available to logged-in users within the assigned application. It will move back to the Assigned column.
• Unassign: The content will be removed from the application entirely and will no longer be visible to any users. It will move to the Unassigned column.
• Edit: Allows the user to update or modify existing content.
• Republish: After editing, the content can be republished with updated details. In case of edit, new details will be visible to public users only if content is republished.

Details of Publish Dialog

When publishing, users will see the following options in the dialog:

• Restrict Display → Show content only under specific conditions on applications.
• Pinned → Keep content fixed at the top.
• Date Range → Define start and end dates for visibility.
• Hide in Avatar → Prevent content from appearing in the Avatar for guest users.
• Target Audience → Choose which user groups can access the content.
• Language Edit → Add translations or language-specific edits.
• Retention → Define how long the content stays available.

Versioning

• Latest Version → Changes saved but not published.
• Published Version → The last version visible to users.

With Save and Publish, the latest version becomes the published version immediately.

Object Level based Content Publishing (Mass Publishing)

The Publishing Assistant allows you to publish multiple items at once (up to 25).

Steps:

1. Go to the Guidance tab from the main menu.
2. Open Applications and select an app.
3. Open Manage Content.
4. Select a content tab (e.g., Routes).
5. Click the Publishing Assistant icon.
6. A dialog appears showing available content.
7. Select up to 25 items.
8. Click Publish → all selected content will be published to the chosen application.

Restrict Display

When publishing content (such as Routes, Posts, Announcements, Collection and Pins), you can define specific URL patterns where the content should appear. This helps ensure content is shown only on relevant pages.

Functionality

• Users can add new patterns using a plus (+) button.
• Activate or Deactivate patterns.
• Delete unwanted patterns.

Pattern Rules & Flexibility:

• Users can add up to 5 URL patterns for each piece of content.
• Supports wildcards (*) for greater flexibility.
• Users can match patterns in any part of the URL including:
  • Pathname
  • Query parameters

Examples of Supported Patterns:

EXAMPLE

Let's take an example of a Route Restrict display while publishing.

When publishing a route in AppNavi, you can restrict its display by adding a specific URL pattern. This ensures that the route is only visible on designated pages of application and hidden elsewhere.

1. Add a Pattern While Publishing

• During the publishing process, define a specific URL pattern for the route.
  example define pattern : /reference/react
• This pattern determines where the route will be displayed.

2. Check on the Avatar Side
   On the avatar interface, the route appears only when the user is on a page matching the defined pattern.
3. Restricted on Other Links
   For example, if you navigate to a /community or /reference page or any other URL that does not match the pattern, the route will not be displayed there on avatar.

URL-Based Display Rules for Content Visibility

This section explains how the "Restrict Display On" setting affects the visibility of content (e.g., Routes, Posts, or Announcements) based on URL configurations and their activation status.

1. Restrict Display ON → No URL Configured
   • Result: Content is displayed on all pages.
   • Explanation: Since no URL pattern is defined, the restriction has no effect and the content is shown everywhere.
2. Restrict Display ON → One URL Configured (Inactive)
   • Result: Content is displayed on all pages as URL is inactive.
   • Explanation: An inactive URL is ignored. As there are no active URLs, the restriction is effectively bypassed.
3. Restrict Display ON → Two URLs Configured (One Active, One Inactive)
   • Result: Content is displayed only on the active URL.
   • Explanation: The restriction applies only to active URL patterns. The inactive one is ignored.
4. Restrict Display OFF → URLs Configured (Active or Inactive)
   • Result: Content is displayed on all pages.
   • Explanation: The "Restrict Display" toggle is off, so the system does not consider any URL patterns regardless of their status.

Retention

The retention feature helps users to delete un-necessary data that has been made for any application over a period of time such as routes, pins, posts, collection and announcements. This feature can be found in the edit page of any content on the portal. Each content has a retention tab on its right and user can add the retention.

The users can create any type of content and add a retention period to the content. The standard retention period are as follows:

• Routes: 3 Years
• Posts: 1 Year
• Announcements: 180 Days
• Collections: 3 Years
• Pins: 1 Year

The users can also change the retention period of any content by selecting the standard retention's from the drop down. Once the user saves the retention, from the current day till its retention time the content will exist on the assigned application and then get deleted and move to the recycle bin only if it is assigned or unassigned in that period of time. The content will not be deleted if it is still published even if the retention period has been met.