Implement New Landing Page Layout from Figma Design#355
Conversation
…ctions Signed-off-by: Ntege Daniel <danientege785@gmail.com>
…ctions Signed-off-by: Ntege Daniel <danientege785@gmail.com>
…ctions Signed-off-by: Ntege Daniel <danientege785@gmail.com>
…ctions Signed-off-by: Ntege Daniel <danientege785@gmail.com>
…ctions Signed-off-by: Ntege Daniel <danientege785@gmail.com>
Signed-off-by: Ntege Daniel <danientege785@gmail.com>
✅ Deploy Preview for open-elements ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: Ntege Daniel <danientege785@gmail.com>
There was a problem hiding this comment.
Pull request overview
This PR implements the new Figma landing page by replacing the previous multi-section home composition with a single LandingPage component, updating navbar/footer styling to match the new layout, and expanding EN/DE localization to support the new content structure.
Changes:
- Replace the home route’s legacy section stack with a unified
LandingPagecomponent. - Redesign the footer structure (including mobile accordions) and adjust navbar visuals for the new landing layout.
- Add/expand
homeLandingand footer translation keys inlocales/en.jsonandlocales/de.json.
Reviewed changes
Copilot reviewed 12 out of 15 changed files in this pull request and generated 9 comments.
Show a summary per file
| File | Description |
|---|---|
| src/app/[locale]/page.tsx | Switches the home route to render the new unified landing page component. |
| src/components/home/LandingPage.tsx | Adds the new landing page layout and content structure driven by homeLanding translations. |
| src/components/Navbar.tsx | Updates navbar styling and mobile header controls to fit the new design. |
| src/components/Footer.tsx | Rebuilds footer into new column layout with mobile collapsible sections and new translation keys. |
| locales/en.json | Adds homeLanding content and new footer keys for the redesigned footer. |
| locales/de.json | Adds homeLanding content and new footer keys for the redesigned footer. |
| src/components/home/HeroSection.tsx | Removes legacy home hero section (superseded by LandingPage). |
| src/components/home/OpenKnowledgeSection.tsx | Removes legacy section (superseded by LandingPage). |
| src/components/home/OpenEventsSection.tsx | Removes legacy section (superseded by LandingPage). |
| src/components/home/OpenSourceSection.tsx | Removes legacy section (superseded by LandingPage). |
| src/components/home/OpenDoorsSection.tsx | Removes legacy section (superseded by LandingPage). |
| src/components/home/OpenOfficeSection.tsx | Removes legacy section (superseded by LandingPage). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| <button | ||
| className="cursor-pointer" | ||
| onClick={() => setIsOpen(!isOpen)}> |
| <button | ||
| className="flex items-center justify-between lg:pointer-events-none" | ||
| onClick={() => toggleSection('nav')}> | ||
| <h3 className="text-xs font-bold uppercase leading-[26px] tracking-[1.2px] text-white"> | ||
| {t('footerNavigation')} | ||
| </h3> | ||
| <ChevronDown | ||
| className={`lg:hidden transition-transform ${openSection === 'nav' ? 'rotate-180' : ''}`} | ||
| /> | ||
| </button> | ||
| <div | ||
| className={`flex-col gap-4 ${openSection === 'nav' ? 'flex' : 'hidden'} lg:flex`}> | ||
| {mainMenu.map((item, index) => { |
| <button | ||
| className="flex items-center justify-between lg:pointer-events-none" | ||
| onClick={() => toggleSection('company')}> | ||
| <h3 className="text-xs font-bold uppercase leading-[26px] tracking-[1.2px] text-white"> | ||
| {t('footerCompany')} | ||
| </h3> | ||
| <ChevronDown | ||
| className={`lg:hidden transition-transform ${openSection === 'company' ? 'rotate-180' : ''}`} | ||
| /> | ||
| </button> | ||
| <div | ||
| className={`flex-col gap-4 ${openSection === 'company' ? 'flex' : 'hidden'} lg:flex`}> |
| <span className="text-base leading-[26px] text-[#C5DEF3]"> | ||
| {t('footerCopyright')} | ||
| </span> |
| "footerCompany": "Company", | ||
| "footerContact": "Contact", | ||
| "footerEmail": "info@open-elements.com", | ||
| "footerLocation": "Deutschland / Europe", |
| "footerCompany": "Unternehmen", | ||
| "footerContact": "Kontakt", | ||
| "footerEmail": "info@open-elements.com", | ||
| "footerLocation": "Deutschland / Europe", |
| "linux": { | ||
| "category": "Self-sovereign identity", | ||
| "logoAlt": "The Linux Foundation logo", | ||
| "body": "In our modern labs, we develop." | ||
| }, |
| "linux": { | ||
| "category": "Self-Sovereign Identity", | ||
| "logoAlt": "The Linux Foundation Logo", | ||
| "body": "In unseren hochmodernen Laboren entwickeln." | ||
| }, |
Jexsie
left a comment
There was a problem hiding this comment.
Thank you @danielmarv. The UI looks good to me. I just have a few suggestions.
- Have different section as components under the home.
- Have the dynamic content as a separate component
- Separate reusable components like buttons, Icons, that are not specific for the Landing page
- There is an issue with the layout of the hero-image
/illustrations/home-bg-2.svgon ultra wide screens. It has been there already, not related to these changes
…, and values Signed-off-by: Ntege Daniel <danientege785@gmail.com>
|
Final text for the page will be provided later the week |
Signed-off-by: Ntege Daniel <danientege785@gmail.com>
Signed-off-by: Ntege Daniel <danientege785@gmail.com>







Description
This pull request introduces a new, comprehensive landing page for the home route and significantly expands both the German and English localization files to support the new content and footer structure.
Landing Page Redesign:
HeroSection,OpenKnowledgeSection, etc.) insrc/app/[locale]/page.tsxwith a singleLandingPagecomponent, streamlining the home page rendering and paving the way for a unified, richer landing experience. (src/app/[locale]/page.tsxL1-R4)Localization Enhancements:
homeLandingin bothlocales/de.jsonandlocales/en.json, providing all text, labels, and content needed for the new landing page, including hero section, business areas, metrics, distinguishing features, values, and contact sections. [1] [2]Brief description of changes made in this PR.
Type of Change
Related Issue(s)
Closes #354
Changes Made
How to Test
Checklist