Razorpay Integration and CI Fixes: Patch v0.1.1
We're excited to announce version v0.1.1 of the King's Temple Church website. This patch introduces important updates focusing on enhancing our payment systems and improving our continuous integration setup.
Major Enhancements
- Razorpay Payment Gateway Integration #5
- Implemented secure server-side fetching for Razorpay button id, enhancing payment security and simplifying button id
- Github Actions Fixes #8
- Fixed an issue with the Next.js 'app' directory in our Github Actions setup.
- Payment Page Updates #7
- Made various amount and UI fixes on the payment page to improve user experience.
Code Snippets
Due to the sensitive nature of the changes, the specific code snippets aren't included in this public release note for security reasons.
Highlights of Changes
- Razorpay Payment Gateway was integrated into the website to enhance payment security and simplify button id.
- An issue with the Next.js 'app' directory in our Github Actions setup was fixed to improve our continuous integration process.
- Various amount and UI fixes were made on the payment page to provide a smoother user experience.
Summary
This release brings significant improvements to our payment systems and continuous integration processes. It also includes various UI enhancements to provide a better user experience on the payment page. We're excited about the positive impacts these changes will have on our development workflow and user experience of the King's Temple Church website.
Next Steps
Looking ahead, we will continue to refine our development processes, improve our website's functionality, and introduce more enhancements to our payment systems. We're also planning to expand our Github Actions workflows to cover other aspects of our development process, and continue to optimize our code for efficient deployment and runtime performance.
We appreciate the support and contributions from all members of the development team, especially @vamsii777, @prathamesh-dukare, @zeel-codder, @Prachi-Jamdade for their contributions in this release. We're looking forward to the continued progress in our future updates.
