added header - #71
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request enhances the landing page and navigation experience by adding an FAQ section and improving the navbar layout and behavior. The FAQ section provides answers to common questions, while the navbar now includes smooth scrolling and better organization of navigation links, with improved responsiveness for different screen sizes.
Landing Page Enhancements:
LandingPage.jsxwith common questions and answers about TORQ, including how documentation is retrieved, manual uploads, supported languages, and data security.LandingPage.module.css, including a responsive grid layout and card hover effects.Navbar Improvements:
Navbar.jsxto smoothly scroll to the top of the page when already on the homepage, instead of reloading.Pipeline,Features,How it works) to the navbar and grouped them for better structure.Navbar.module.css, positioning them centrally and hiding them on screens narrower than 900px for improved mobile responsiveness. [1] [2]