[pull] main from tldraw:main#582
Merged
Merged
Conversation
In order to make disabled menu items clearly distinguishable in dark mode, this PR adds `opacity: 0.5` to disabled `.tlui-button` styles. In dark mode, `--tl-color-text-3` (the disabled text color) sits close to `--tl-color-text-1`, so disabled items like "Invert mouse zoom" in the input mode menu looked clickable. Dimming the whole element gives a theme-agnostic visual cue. Maybe something like this? ### Before <img width="276" height="283" alt="CleanShot 2026-05-25 at 12 59 51" src="https://github.com/user-attachments/assets/3e22c52a-4113-4b53-8f5e-d7cf044736ad" /> <img width="337" height="319" alt="CleanShot 2026-05-25 at 12 59 56" src="https://github.com/user-attachments/assets/0aadaa9d-19ee-4fd5-ac6a-899768455f4e" /> ### After <img width="282" height="244" alt="CleanShot 2026-05-25 at 13 04 30" src="https://github.com/user-attachments/assets/c710c4e1-12bc-4506-8ec4-a57d4551b81f" /> <img width="229" height="214" alt="CleanShot 2026-05-25 at 13 04 43" src="https://github.com/user-attachments/assets/0cffbb8c-0cf0-4dcd-b78c-5db4d4c932b2" /> Closes #8162 ### Change type - [x] `bugfix` ### Test plan 1. Open the examples app. 2. Switch to dark mode. 3. Open the main menu → Preferences → Input mode. 4. With "Auto (trackpad)" selected, confirm "Invert mouse zoom" is visibly dimmed and looks clearly disabled. 5. Switch to light mode and confirm the disabled state still reads correctly. ### Release notes - Improve visual contrast of disabled buttons and menu items in dark mode. ### Code changes | Section | LOC change | | --------- | ---------- | | Core code | +1 / -0 | --------- Co-authored-by: Steve Ruiz <steveruizok@gmail.com>
In order to make our contribution policy clear everywhere it's mentioned, this PR rewrites CONTRIBUTING.md to lead with the no-contributions policy and sweeps the rest of the repo for language that invites contributions. Relates to #7695. - `CONTRIBUTING.md` now states up front that we are not accepting contributions and that pull requests are turned off for the repository. It directs people to create an issue to report bugs or discuss proposed changes, and to fork the repo and link to a branch in the issue if a code example would help the discussion. - The docs site's community contributing page says the same. - The root README's contributing section now points to issues instead of inviting contributions. - The shared "Contribution" boilerplate in package, app, and template READMEs no longer invites readers to the contributing guide; it now just links to the issue tracker, matching the pattern already used in `packages/create-tldraw`. - The docs site README's sample section description no longer describes tldraw as an open source project. All changes are README, Markdown, and MDX files only. Note: `apps/docs/content/community/contributing.mdx` is also rewritten in #9091; the wording here matches that PR plus the fork guidance, so whichever merges second will have a trivial conflict. ### Change type - [x] `other` ### Test plan Documentation-only change; no manual testing steps. ### Code changes | Section | LOC change | | ------------- | ---------- | | Core code | +15 / -15 | | Documentation | +12 / -18 | | Apps | +10 / -10 | | Templates | +10 / -10 | Core code and apps rows are README files within those directories; no source code is changed.
In order to stop agents and contributors from hitting a confusing `tldraw/tldraw.css` resolution failure, this PR documents that dev commands must be run from the repo root. The root `yarn dev` runs each package's `predev` step (e.g. `node ./scripts/copy-css-files.mjs` in `packages/tldraw`), which generates the untracked `packages/tldraw/tldraw.css` build artifact. Running a per-workspace command like `yarn workspace examples.tldraw.com dev` skips `predev`, so imports such as `tldraw/tldraw.css` fail to resolve in Vite. The note also reminds that a fresh git worktree starts without `node_modules` and needs `yarn install` first. ### Change type - [x] `docs` ### Test plan - Documentation only; no manual testing required. ### Code changes | Section | LOC change | | ------------- | ---------- | | Documentation | +2 / -0 |
In order to keep the documentation guides accurate and readable, this PR reviews all 104 guide pages under `apps/docs/content` (getting started, learn tldraw, SDK features, starter kits, and community — not the generated reference docs or release notes) against the current SDK source, and updates pages where needed. Pages that were already accurate and clean are untouched. Every API symbol, code example, internal link, and example link on each page was verified against the packages' source and API reports. Changes fall into three groups: ### Accuracy fixes - Removed or replaced stale APIs: `defineMigrations`, the `CollaboratorCursor` component override (now `CollaboratorCursorOverlayUtil`), `@tldraw/tldraw` package references, deprecated `indicator`/`inputs.currentPagePoint`/`isDragging` accessors, and a nonexistent `editor.getDocumentState()`. - Fixed code examples that wouldn't work as written: missing imports and declarations, `editor.canUndo` without parens, a non-reactive preferences read, wrong argument order in a starter-kit example, invalid wrangler TOML, an `updateAssets` pattern that dropped required props. - Corrected behavior claims: license tracking for hobby licenses, `locale` prop precedence, animation speed direction, camera x/y semantics, image-export error handling, embed sandbox/fallback behavior, edge-scrolling insets, handle angle snapping, and others. - Fixed broken or moved example links (persistence had six), a duplicate starter-kit `order` conflict, and a sentence-case/anchor mismatch. ### New content Four SDK feature pages were TODO stubs and are now full guides written from source: **arrow shape**, **eraser**, **grid**, and **pen mode**. They keep `status: draft` — flip to `published` when you're happy with them. ### Clarity and style Sentence-cased headings and labels, direct openings, short paragraphs, trailing-gerund and hollow-filler cleanup, redundant sections removed, and consistent `[Symbol](?)` API-link usage per the repo writing guides. ### Verification - `yarn check-links` passes (no broken links). - `yarn refresh-content` passes against freshly built package API files: all MDX parses and every `[Symbol](?)` API link resolves. (This required rebuilding `packages/*/api/api.json` locally; one bad API link added during review was caught and removed this way.) ### Policy update tldraw has closed external contributions. The contributing page now states that the source is available to read but contributions are not accepted, the translations page no longer invites translation help (and drops the inaccurate "Lokalise for open source" section), and the community section description no longer calls tldraw an open source project. ### Change type - [x] `other` ### Release notes - Update documentation guides for accuracy, clarity, and style; add full guides for the arrow shape, eraser, grid, and pen mode pages.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )