EDU-122: Blueprints - Hero section - all frameworks

[uttej-vsk]

Description

This PR introduces code for blueprints in the hero section across all frameworks.

Parent Jira: https://builder-io.atlassian.net/browse/EDU-122
React ticket: https://builder-io.atlassian.net/browse/EDU-645
this PR ticket: https://builder-io.atlassian.net/browse/EDU-652

[changeset-bot]

⚠️ No Changeset found

Latest commit: ce5ca10

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11707119	Triggered	Generic High Entropy Secret	e2a69ba	packages/sdks/snippets/react-sdk-next-14-app/app/(blueprints-product-details)/marketing-event/page.tsx	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit ce5ca10.

Command	Status	Duration	Result
nx test @e2e/remix	✅ Succeeded	5m 39s	View ↗
nx test @e2e/sveltekit	✅ Succeeded	5m 12s	View ↗
nx test @e2e/svelte	✅ Succeeded	4m 58s	View ↗
nx test @e2e/vue	✅ Succeeded	4m 48s	View ↗
nx test @e2e/qwik-city	✅ Succeeded	8m 42s	View ↗
nx test @e2e/solid-start	✅ Succeeded	4m 39s	View ↗
nx test @e2e/solid	✅ Succeeded	4m 32s	View ↗
nx test @e2e/react-sdk-next-15-app	✅ Succeeded	6m 11s	View ↗
Additional runs (36)	✅ Succeeded	...	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-05-01 15:48:39 UTC