Ability to export Home Page along with Articles as HTML
under review
Bala Ramachandra
We should be able to export the home page with the HTML articles, related CSS, and other assets to link to a specific client application. As a product-based company, we intend to link WebHelp to specific client applications.
Log In
Shakeer Hussain S
Hi Bala - Thank you for your request. To provide you with the best possible assistance, could you kindly provide answers to the following queries? We appreciate your cooperation.
Could you specify the exact elements and content types you want to export along with the HTML articles from the homepage?
Are there particular formats or standards that the exported content needs to adhere to for compatibility with your client applications?
What level of customization or editing capability is needed for the CSS and other assets after export?
Is there a required level of interactivity or functionality that needs to be retained in the exported content when linked to client applications?
Do you have any security or privacy considerations we should be aware of when implementing this export feature?
Bala Ramachandra
Hi Shakeer Hussain S: Thanks for your quick response. To give you more background, our clients may use their own intranet (local network) to use our applications. To help the users, we currently provide content as HTML web output which includes topics/articles, images, videos, and all other assets in the Help content. This HTML output is placed in their local server. The home page of this Help content is linked to the Help icon in our application. When the user clicks the Help icon, the Home page opens in a browser and the user is able to navigate through the entire content using TOC, bookmarks, and hyperlinks. User is also able to search for content within the Help.
Following are my answers to your questions:
Could you specify the exact elements and content types you want to export along with the HTML articles from the homepage?
Bala - TOC, Topics/articles, images, GIFs, videos, icons, and any other asset that is included in the Help content. Basically, we should be able to export all the assets and the Home Page as it is displayed in the Knowledge base and link the Home page to the application. The user should be able to open the Home page and navigate across the content using TOC, bookmarks, search, or hyperlinks.
Are there particular formats or standards that the exported content needs to adhere to for compatibility with your client applications?
Bala - Each content type should be exported in a separate folder; however, it should be a single export. For example, all images should be available in the Images folder. All videos should be available in the Videos folder.
What level of customization or editing capability is needed for the CSS and other assets after export?
Bala - We will have to rebrand the Home page and the templates based on the client's requirements.
Is there a required level of interactivity or functionality that needs to be retained in the exported content when linked to client applications?
Bala - All user actions that are currently available in the Knowledge base should be available for the users in the exported content.
Do you have any security or privacy considerations we should be aware of when implementing this export feature?
Bala - Yes, the clients may use their internal network (intranet) for using our applications.
Shakeer Hussain S
under review