Skip to content
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

Update README.md as per SEO recommendation #251

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

vijay-dialedin
Copy link
Contributor

Enhance Elastic Path Composable Frontend Documentation and Setup Process

This update enhances the documentation and setup process for the Elastic Path Composable Frontend, a Next.js Commerce starter kit provided by Elastic Path. The changes aim to improve the onboarding experience by clearly documenting the steps involved in generating and deploying a Next.js storefront with Elastic Path.

Enhance Elastic Path Composable Frontend Documentation and Setup Process
Copy link

changeset-bot bot commented Nov 11, 2024

⚠️ No Changeset found

Latest commit: 65e09da

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

Copy link

vercel bot commented Nov 11, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
composable-frontend-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 18, 2024 6:59am

Copy link

vercel bot commented Nov 11, 2024

@vijay-dialedin is attempting to deploy a commit to the EP Frontend Team Team on Vercel.

A member of the Team first needs to authorize it.

Removed the misleading line next.js commerce and updated the content
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant