You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Styling Improvements: Change the overall color scheme to make the design more reactive and engaging. Use dynamic colors for better aesthetics and to improve user engagement.
- Form Styling and Layout: In the Price Prediction Section
-- Divide the page into two parts: one for text and one for the price prediction form.
-- Increase the font size to enhance readability.
-- Adjust the form size for a cleaner and consistent layout.
-- Increase the banner size
-- Change the font color and size for better visibility.
-- Mainly using CSS to transform the layout.
-- making predict price hover more dynamic.
Bug Fix: Contact Us Form
Investigate and fix the "Contact Us" form, which is currently not working as intended. Ensure it sends responses correctly and validates input fields.
Use Case
Improved User Interaction and Engagement
Imagine a potential user visits the OpenTekHub Blockchain project to explore its **price prediction feature**. With the current layout, the page may feel cluttered, the form might appear too small, and the colors may not actively engage the user. This could lead to frustration, especially if the **Contact Us form** is not working properly, leaving users with no way to report issues or ask questions.
By implementing the proposed changes:
- Clear separation of content: Users will easily find the information they need and focus on the prediction form without distractions.
- Dynamic colors: Engage users visually, increasing the time spent exploring the site.
- Improved form accessibility: With larger fonts and an optimized layout, users will have a smoother experience when interacting with the form.
- Functional Contact Us form: If users encounter issues, they will be able to contact the support team seamlessly, improving trust and retention.
Benefits
Advantages of Implementing This Feature
1. Better User Engagement:
- Dynamic colors and a nicer design will make the site more fun to explore, keeping users around longer.
2. More Interaction with Features:
- Separating the text and price prediction form will help users focus and interact more easily.
3. Easier to Use and Navigate:
- Bigger fonts and a cleaner layout will make it simpler for users to read and fill out forms.
4. Improved User Support:
- Fixing the "Contact Us" form will make sure users can get in touch easily, building trust.
5. Works Well on Any Device:
- A well-organized layout will make the site look good and function properly on any screen size. Current form is not visible completelyon 14-inch devices.
Priority
High
Record
I agree to follow this project's Code of Conduct
I'm a GSSOC contributor
I want to work on this issue
I'm willing to provide further clarification or assistance if needed.
👋 Hello @pravallika-nunna! Thank you for opening this issue titled "[Feature Request]: Changes to layout of the page and styling, managing navigation bar-contact us."! We're excited to see your contribution and a maintainer will get back to you shortly 😊!
Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible.
Is there an existing issue for this?
Feature Description
- Form Styling and Layout: In the Price Prediction Section
-- Divide the page into two parts: one for text and one for the price prediction form.
-- Increase the font size to enhance readability.
-- Adjust the form size for a cleaner and consistent layout.
-- Increase the banner size
-- Change the font color and size for better visibility.
-- Mainly using CSS to transform the layout.
-- making predict price hover more dynamic.
Investigate and fix the "Contact Us" form, which is currently not working as intended. Ensure it sends responses correctly and validates input fields.
Use Case
Benefits
Advantages of Implementing This Feature
Priority
High
Record
Please assign this issue to me @Harish-2003
The text was updated successfully, but these errors were encountered: