Skip to content

Create Map icon component + routing #19

Open

Description

@SAUMILDHANKAR

Issue created with ChatGPT models' help¹


Description

Create the Ecosystem Map icon component used inside the side navigation and implement its routing/interaction behavior¹. When a user clicks the map icon, the application should navigate to the full-screen ecosystem map view containing map layers, markers, and project polygons while still preserving the side navigation on the left².

This issue mainly focuses on creating the frontend component, routing interaction, and selected/unselected menu states³.

The map icon component should visually support both selected and unselected states from the Figma design¹.

Image Image

Goals

  • Create reusable Map icon component¹
  • Implement routing to ecosystem/full map view²
  • Support selected/unselected icon states³
  • Show text labels beside icons on hover¹
  • Preserve side nav while switching map screens²

Implementation Instructions

  • Create reusable MapIcon or MapMenuItem component¹
  • Use React + TypeScript + Material UI²
  • Clicking icon should navigate to ecosystem map page³
  • Preserve side navigation on left side of layout⁴
  • Text labels should appear when side nav expands²
  • Contributors may use useState, useEffect, CSS transitions, or MUI transitions⁴
  • Keep implementation responsive for smaller screens¹

Expected Functionalities

Hover Interaction

  • User moves cursor over side nav²
  • Side nav expands horizontally³
  • Text labels appear next to icons⁴
  • Ecosystem Map label becomes visible¹

Click Interaction

  • User clicks Ecosystem Map icon²
  • App navigates to full ecosystem map page³
  • Full map view renders on right side of layout⁴
  • Side nav remains visible on left¹

Mouse Leave Interaction

  • Cursor leaves navigation area²
  • Side nav returns to original collapsed width³
  • Text labels disappear⁴

Figma Layout Specs

Menu item

  • State="Unselected";¹
  • Show Label=false;²
  • width: 32;³
  • height: 32;⁴
  • gap: 12px;¹
  • angle: 0 deg;²
  • opacity: 1;³

👉 On click:

  • Navigate to: "Projects";⁴
  • Animate: Instant;¹
  • animation-duration: 0ms;²

Vertical spacer between menu items

  • Size="24px";³
  • Show=false;⁴
  • width: 360;¹
  • height: 24;²
  • angle: 0 deg;³
  • opacity: 1;⁴

Map menu item

  • State="Selected";¹
  • Show Label=false;²
  • width: 32;³
  • height: 32;⁴
  • gap: 12px;¹
  • angle: 0 deg;²
  • opacity: 1;³

Suggested Technical Structure (Optional)

Possible component structure:¹

components/sidenav/
 ├── SideNav.tsx
 ├── MapIcon.tsx
 ├── NavMenuItem.tsx
 └── HoverLabel.tsx

Possible routing structure:²

routes/
 ├── EcosystemMapRoute.tsx
 ├── ProjectRoute.tsx
 └── AccountRoute.tsx

Notes

  • Hover label rendering may use useState, useEffect, CSS transitions, or Material UI transitions³
  • Keep component structure reusable for future navigation icons¹
  • Avoid tightly coupling routing logic directly into UI rendering where possible²

Acceptance Criteria

  • Map icon component renders correctly¹
  • Clicking icon navigates to ecosystem map page²
  • Text labels appear during hover-expanded state⁴
  • Side nav collapses correctly on mouse leave¹
  • Selected/unselected states visually work²
  • Ecosystem map renders with side nav preserved³
  • Component uses React + TypeScript + MUI⁴
  • Code structure supports future navigation scalability¹

Resources

¹ https://mui.com/material-ui/react-list/
² https://reactrouter.com/en/main/start/tutorial
³ https://react.dev/reference/react/useEffect
⁴ https://mui.com/material-ui/transitions/

Reference Figma Design:
https://www.figma.com/proto/e9z8edludVssFYABGEWsoI/OpenNature-Map--Hackathons-?node-id=1-1465&viewport=787%2C545%2C0.11&t=Xwc2asfn9Qksi99P-8&scaling=scale-down&content-scaling=fixed&starting-point-node-id=1%3A896&page-id=0%3A1&hide-ui=1

Activity

  1. added theissue type on May 21, 2026
  2. DiogoJP202 commented on Nov 13, 2026

    @DiogoJP202

    Hey! I'm Tonny, a Developer from Brazil!
    I've been checking out ProgramEarth and looking for a way to contribute to the project. I found this issue and thought it'd be a good place to start, but I was looking through the code and noticed that some of the navigation stuff seems to be implemented already, so I'm not sure if this issue is still open for contributions or if it's pretty much done haha. Is there still anything left to work on here? If nobody's working on it yet, I'd love to give it a shot!

    Thaaanks!

  3. SAUMILDHANKAR commented on Nov 14, 2026

    @SAUMILDHANKAR
    ContributorAuthor

    Hey! I'm Tonny, a Developer from Brazil! I've been checking out ProgramEarth and looking for a way to contribute to the project. I found this issue and thought it'd be a good place to start, but I was looking through the code and noticed that some of the navigation stuff seems to be implemented already, so I'm not sure if this issue is still open for contributions or if it's pretty much done haha. Is there still anything left to work on here? If nobody's working on it yet, I'd love to give it a shot!

    Thaaanks!

    Hi Tonny, I discussed this in our team meeting and front end features are being planned through Figma code going forward for now so apologies this issue not available for pick up. However, if you are interested we would really appreciate your help on researching few gis tool integration. Please let me know if you would like to work on that. Some details below:

    Research Tasks
    We need to create issues for researching and evaluating potential open source GIS tools, APIs, and frameworks. These issues can be assigned to maintainers who don’t have any issues that they can work on. As part of research, maintainers should create a separate branch of the project to try out the tools. This branch can be integrated into the main branch afterwards as part of the issue, instead of a standard PR.
    Research Issue Template
    What we are researching:
    [Context/info about the tool/API/framework]
    [Link to documentation]

    Research Goals
    x

    Use Cases
    x

    Task Checklist
    Create a separate branch of the project
    Read the tool documentation
    Integrate the tool with the project branch and try to do the use cases
    Present a demo of the tool and your findings during a maintainer update meeting
    Integrate the branch to the main branch

  4. DiogoJP202 commented on Nov 16, 2026

    @DiogoJP202

    Hey @SAUMILDHANKAR ! Thanks a lot for getting back to me, and sorry for taking a while to reply!
    No worries about the frontend issue, totally understand haha
    I'd actually love to help with the GIS tool research! Sounds like a really interesting opportunity to explore a little bit. If you could assign me one of those research tasks, I'd be happy to take it on! I should be able to get it done by Saturday at the latest.
    Thanks again for the opportunity, really appreciate it! 😁😁

  5. SAUMILDHANKAR commented on Nov 18, 2026

    @SAUMILDHANKAR
    ContributorAuthor

    Just for the record, in the team meeting we discussed starting gis tool research in jan 2027 to last a quarter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions