iamkanhaiyakumar / ai-content-generator

MIT License
7 stars 33 forks source link

[Feat] Pricing Section Design #68

Closed dev129 closed 1 month ago

dev129 commented 1 month ago

Description

Title: Design AI Content Generator Pricing Section Hi @iamkanhaiyakumar @GauravKesh

Description:
We need to create a visually appealing and user-friendly pricing section for our AI Content Generator tool. This section should clearly present different pricing tiers, highlight the features included in each, and guide users towards selecting the best plan for their needs.

Requirements:

  1. Layout and Design:

    • Design a clean, modern, and responsive layout for the pricing section.
    • Include visually distinct cards or sections for each pricing tier (e.g., Basic, Pro, Enterprise).
  2. Content and Features List:

    • Clearly outline the features and limitations for each plan (e.g., word count limits, access to premium templates, support availability).
    • Include prominent CTAs like “Choose Plan” or “Get Started” for each tier.
  3. Highlighting Features and Benefits:

    • Use icons or checkmarks to highlight key features.
    • Emphasize benefits unique to each plan (e.g., priority support for Enterprise users).
  4. Support for User Queries:

    • Add an FAQ or "Need Help?" section below the pricing tiers with a phone and email support option.
  5. Styling:

    • Follow our existing branding guidelines (colors, fonts, etc.).
    • Ensure the design is visually balanced with ample spacing and readable font sizes.

Acceptance Criteria:


Additional Context:
This issue aligns with the goal of making our pricing clearer and more accessible to new and returning users.

Screenshots

No response

Checklist

dev129 commented 1 month ago

Hi @GauravKesh @iamkanhaiyakumar , this is the design image

dev129 commented 1 month ago

Hi @iamkanhaiyakumar @GauravKesh , please check and review my PR.

dev129 commented 1 month ago

Hey @GauravKesh , some more things first of all the package-lock.json the clerk js must be installed in package.json or be told in documentation , I don't know about it but thought to address this issue at the earliest.