docs: add Spanish translation for README quickstart#52
Open
OMEE-Y wants to merge 3 commits into
Open
Conversation
|
@OMEE-Y is attempting to deploy a commit to the Dodo Payments Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
Author
|
Closes #22 |
Replaced old content with updated information about Dualmark, including installation instructions, quick start guides, and marketing team benefits.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Spanish translation of the repository's Quickstart guide by creating a dedicated
README.es.mdfile at the root level. This helps accessibility for Spanish-speaking marketing engineers looking to implement Dualmark infrastructure.Changes
README.es.mdin the root directory containing the fully translated Quickstart documentation for Astro, Next.js, and Cloudflare Workers adapters.Type
AEO_SPEC_VERSION)Verification
bun run buildpassesbun run testpassesbun run typecheckpassesdualmark verifyagainst the example end-to-end/spec/: ranbun run --filter dualmark-docs sync-specand committed the mirrorChangeset
bun run changeset) for any package with a user-visible change