Is it possible to create redirects in WebHelp Responsive?
Post here questions and problems related to editing and publishing DITA content.
-
- Posts: 20
- Joined: Sat Jun 24, 2023 7:35 pm
Is it possible to create redirects in WebHelp Responsive?
My team decided to change the name of one of our products and the URLs in our documentation (i.e. the topic names) reflected the old name of the product. I will have to change the topic filenames and, hence, the resulting URLs in WebHelp Responsive, but I don't want to leave the search engines and the users hanging in case they bookmarked an old name.
Is there any way to create new topics with old names that would be converted during publishing to WebHelp Responsive into HTML redirects? Such as <meta http-equiv="refresh" content="0; url=http://example.com/" />? And then, how to add these topics to the map so that they're not actually displayed anywhere, but still converted into HTML when the map is processed?
To make sure it's understood correctly, if I have a topic called old_product_name.dita, I will rename that file into new_product_name.dita, and I would like to create an old_product_name.dita file that will not have any content, that will not be in the table of content (menu in WebHelp Responsive) or in any other way visible or linked from the current site, but would be converted into HTML with a redirect to new_product_name.html.
Is there any way to create new topics with old names that would be converted during publishing to WebHelp Responsive into HTML redirects? Such as <meta http-equiv="refresh" content="0; url=http://example.com/" />? And then, how to add these topics to the map so that they're not actually displayed anywhere, but still converted into HTML when the map is processed?
To make sure it's understood correctly, if I have a topic called old_product_name.dita, I will rename that file into new_product_name.dita, and I would like to create an old_product_name.dita file that will not have any content, that will not be in the table of content (menu in WebHelp Responsive) or in any other way visible or linked from the current site, but would be converted into HTML with a redirect to new_product_name.html.
Return to “DITA (Editing and Publishing DITA Content)”
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service