You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Get seamless release notes on one page.
Describe the solution you'd like
There's a couple ways to handle this, one is to use the existing JavaScript to generate one long page, the other is to use Hugo's GetJSON function to create a static page. I prefer the Hugo solution since Swiftype could index the content and make it searchable, also the content wouldn't reload every time the user navigates to a page.
The Hugo solution would take longer to implement and the site would have to be rebuilt every time there's a new release, otherwise the new release notes content wouldn't get added to the site. That's probably already happening through the existing Expeditor config when we get content updates for each product release. I'd have to investigate this a bit.
One big problem with making a single page of release notes is that all the headings are set for multiple pages. Every heading would have to be bumped down automatically so the version number heading can be an H2 heading.
Describe alternatives you've considered
We leave things as they are.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Get seamless release notes on one page.
Describe the solution you'd like
There's a couple ways to handle this, one is to use the existing JavaScript to generate one long page, the other is to use Hugo's GetJSON function to create a static page. I prefer the Hugo solution since Swiftype could index the content and make it searchable, also the content wouldn't reload every time the user navigates to a page.
The Hugo solution would take longer to implement and the site would have to be rebuilt every time there's a new release, otherwise the new release notes content wouldn't get added to the site. That's probably already happening through the existing Expeditor config when we get content updates for each product release. I'd have to investigate this a bit.
One big problem with making a single page of release notes is that all the headings are set for multiple pages. Every heading would have to be bumped down automatically so the version number heading can be an H2 heading.
Describe alternatives you've considered
We leave things as they are.
The text was updated successfully, but these errors were encountered: