-
Notifications
You must be signed in to change notification settings - Fork 5.1k
AI agents page #15097
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AI agents page #15097
Conversation
- Introduced a new navigation item for AI agents in the useNav hook. - Added corresponding translations for AI agents and their descriptions in common.json. - Updated template-usecase.json to include AI agents in the dropdown options. - Enhanced UseCases layout to link to the AI agents page with tracking events.
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dont have a better solution atm with the current setup but I don't like the direction of these very specific components that we can't reuse and that don't share/reuse other existing styles or components.
Was thinking that maybe we could fix this in the md files itself. Where you can handle translations and images. Something like
<Boxes>
<Box>

blabla
</Box>
<Box>

blabla
</Box>
</Boxes>
Unfortunately, this is not supported in the current mdx version (mdx syntax inside jsx) but will be possible after we merge #14968 ! since we are also upgrading the mdx version.
src/components/ProductList.tsx
Outdated
<div>{title}</div> | ||
<div className="mb-0 text-sm opacity-60">{description}</div> | ||
<div className="mb-0 flex flex-col gap-2 text-sm opacity-60"> | ||
{contentItems} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that contentItems
is optional, shouldn't we consider that case and avoid rendering the wrapping div?
the text and button here for some reason looks disabled @corwintines |
Co-authored-by: Jakub <[email protected]>
Co-authored-by: Jakub <[email protected]>
Co-authored-by: Jakub <[email protected]>
Co-authored-by: Jakub <[email protected]>
Co-authored-by: Pablo Pettinari <[email protected]>
https://deploy-preview-15097--ethereumorg.netlify.app/ai-agents