Add a top-level 'get-help' support page to the new NGINXaaS landing#1988
Add a top-level 'get-help' support page to the new NGINXaaS landing#1988tstraley wants to merge 3 commits into
Conversation
✅ Deploy Preview will be available once build job completes!
|
7c77ef6 to
25c6b9c
Compare
25c6b9c to
72b1fe8
Compare
|
I don't think there's any way to get to this page directly w/o backtracking via the breadcrumbs: https://frontdoor-test-docs.nginx.com/previews/docs/1988/nginxaas/
Can this Azure page be updated w/ the include? https://frontdoor-test-docs.nginx.com/previews/docs/1988/nginxaas/azure/get-help/support/. Nit: It shouldn't include images. |
it's possible if you know the URL. I think the idea is to link directly to the page from Azure? |
Why not just surface the include in the Azure docs vs a jump to a topic that has no other siblings?
|
That's correct. We aren't quite ready to surface it as a top-level product yet, since the only one in there is Google. (The existing Azure product is kind of its own animal). There will be more done to prepare some other content that is only accessible by known URLs until we get closer to announcing other things.
No, the Azure support docs are different -- they explicitly intend to start via links in Azure portal and expect some additional information from the user's Azure subscription. |
…ding We want to provide a way for customers to quickly and easly be directed to where to get support / help from for any of the NGINXaaS product offerings without needing to point to various cloud-specific product doc links. For now leaving the specific ones in place as well and only adding.
Re-use for the top-level NGINXaaS get help page, as well as the google cloud support page.
ca23c39 to
a19ba4e
Compare
New product label that will help for tagging generic NGINXaaS content.



We want to provide a way for customers to quickly and easly be directed to where to get support / help from for any of the NGINXaaS product offerings without needing to point to various cloud-specific product doc links.
For now leaving the specific ones in place as well and only adding.
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩