Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Q&A in the pricing pages (product and website) #8658

Closed
PazYanoverr opened this issue Jun 16, 2024 · 1 comment · Fixed by #8683
Closed

Update Q&A in the pricing pages (product and website) #8658

PazYanoverr opened this issue Jun 16, 2024 · 1 comment · Fixed by #8683
Assignees

Comments

@PazYanoverr
Copy link
Member

See #8656 (comment) and based on the QA "spec" - https://www.notion.so/amplication/Updated-Q-A-New-Pricing-June-2024-4159568eeb824c89bd893fa733b5f795?pvs=4

  1. The first two questions in the product should contain links to "contact us"

  2. The links in the product (see below example) should be colored purple-
    Image

  3. In the question (product pricing)- "Can you assist with deploying to various cloud providers like AWS?" the "create a custom plugin" should be a link (see the "spec"- https://www.notion.so/amplication/Updated-Q-A-New-Pricing-June-2024-4159568eeb824c89bd893fa733b5f795?pvs=4)

  4. In the question (product pricing) "Does Amplication support advanced security features like 2FA, audit logs, and SSO for organizational security concerns?" - the "Single Sign-On (SSO)" should be a link. See the "spec")

  5. In the question (website) -"Does Amplication support advanced security features like 2FA, audit logs, and SSO for organizational security concerns?" the "Single Sign-On (SSO)" should be a link (- see spec)

@morhag90 morhag90 self-assigned this Jun 17, 2024
@morhag90 morhag90 linked a pull request Jun 17, 2024 that will close this issue
2 tasks
@mulygottlieb
Copy link
Member

Passed QA ✅

Image

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants