Repository navigation
Add standalone Premove landing page - #152
Merged
Merged
Conversation
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
1 participant
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
Copy the standalone Premove landing page from
premove-ai/premoveinto this public repository without changing the page or the Mintlify docs.Why
The landing page can live here temporarily while the main Premove repository remains private. The site is isolated under
website/, andvercel.jsonpublishes only that directory.Changes
premove-ai/premovePR Polish Premove docs landing and ITN navigation #109.docs.json,index.mdx, and the existing docs routes unchanged.Validation
git archivefrompremove-ai/premovecommit44ffe22.uv run --locked python scripts/agent/check.py focused --pytest tests/test_docs_routes.pypassed.git diff --check, JavaScript syntax, and JSON syntax checks passed.Deployment note
Vercel's current documentation says Hobby projects cannot connect to repositories owned by GitHub organizations, including public repositories. This move does not by itself remove that Git integration restriction.