OttoKit Pricing Template #335
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jaieds
requested changes
Jun 27, 2025
There was a problem hiding this comment.
Great work so far! 👏
Please check the Template Development Guideline and update the PR as per the document.
Also, please check the feedback points given below:
- In tablet view, we need to add margin/padding on the x-axis. Screenshot: https://d.pr/i/lizOAQ
- Can we use the color class name from the Force-UI, instead of arbitrary class names?
- Add Figma mockup link in the PR description (if available).
Thanks for your efforts! 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added a new pricing-ottokit Storybook template using Force-UI components. The template features a responsive pricing page with three plans, a tab switcher for Annual/Lifetime pricing, and clear visual distinction for the recommended plan. All UI elements use Force-UI components and follow accessibility and design best practices.
Demo Video
https://d.pr/v/kZYQy3
Types of changes
New feature (non-breaking change which adds functionality)
How has this been tested?
Viewed and interacted with the template in Storybook across device sizes.
Checklist:
[ yes ] My code is tested
[ yes ] I've created the npm build.
[ yes ] I've created the story book build.