[Feature Request] :"Try It Here" button leads to a cluttered landing page, not an interactive demo

[Mimansha19-tech]

Required prerequisites

• I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
• Consider asking first in a Discussion.

Motivation

The "Try It Here" button for the Eigent product on the main camel-ai.org homepage creates a misleading user expectation. It implies an immediate interactive experience, but instead redirects to another dense, content-heavy landing page (eigent.ai). This creates friction and does not fulfill the button's promise, potentially causing user drop-off.

camel.1.1.mp4

Solution

Ideal Solution (Better UX): Change the button's link to point directly to an actionable part of the eigent.ai page. The best target would be an anchor link to the download buttons (#download) or a dedicated, simple "Get Started" section. This aligns the button's text with its actual function.

Alternatives

Simple Solution (Quick Fix): Change the button's text to manage user expectations more accurately. Instead of "Try It Here," it could say:

    "Learn More About Eigent"
    "Explore Eigent"
    "Visit Eigent.ai"

This is less ideal but would immediately fix the misleading call-to-action.

Additional context

Fixing this small but critical detail in the user journey is essential for converting interest from the open-source project into active users of the Eigent product. A clear, low-friction path from discovery to trial is key for adoption.

[Wendong-Fan]

thanks @Mimansha19-tech for creating this issue! could @Douglasymlai help checking this?

[Mimansha19-tech]

@Wendong-Fan Ohk sure , if you don't mind could I ask why you assigned my issue to someone else????

[Wendong-Fan]

Hi @Mimansha19-tech, I've assigned this to @Douglasymlai as he is the primary person responsible for our website's UI and front-end. It's our standard practice to route issues to the team member with the most relevant expertise to ensure it gets addressed effectively

We really appreciate your detailed report! If you were interested in working on this yourself, please feel free to submit a pull request. We would be more than happy to review it

[Douglasymlai]

Hi @Mimansha19-tech. Thanks for bringing up this issue! I’ve already added it to be fixed this week. Since our website is currently built using a no-code platform, we’re unable to invite external contributors at this stage. However, we’re planning to rebuild the next version of the CAMEL website with Next.js. Once that’s underway, we’ll open more issues for community members to contribute. I’ll make sure to notify you with more details when that begins.