The Cutscript community is the forum on cutscript.dev, where users help each other and where the maintainers hear what matters. It lives at /community, on this site, not on a separate one. Anyone can read it, except the Donors club. To post, you sign in.
What it is for
- Getting help. Ask a question, and mark the reply that solved it.
- Reporting bugs and asking for features. Say what broke, or what job you want Cutscript to do.
- Showing and sharing. Post the videos, graphics and workflows you made, and the tips you found.
- Hearing the news. Releases, roadmap changes, outages and funding updates are in Announcements.
- Talking about a page. The same account lets you comment on blog posts and docs pages.
Join
- Open /community/login, or choose Sign in in the header.
- Choose Continue with GitHub or Continue with Google.
- Check your name and profile address on the page that opens. You can change both later.
There are no passwords. We keep the name, email and picture that GitHub or Google gives us, never show your email, and never post anything to your GitHub or Google account. The site does not join a GitHub account and a Google account that share an email, so keep signing in with the one you started with. The Privacy page lists what the site stores.
Your public profile is at /community/user/ followed by your profile name. Your own settings are at /community/profile: your name, profile address, picture, bio, website, the donations linked to you, and Delete my account. Deleting removes your sign-in, profile, badges and notifications. Your topics and replies stay, shown as "Deleted member".
What you can do
- Start a topic with Start a topic (/community/new). Pick the category that fits. Posts are written in Markdown, and the Preview tab shows what will be published.
- Reply to a topic, and mark a reply Helpful when it helped. You cannot mark your own.
- Mark the answer. In a question category (Help and questions, AI director and graphics, Recording and devices), the person who asked presses Solved this on the reply that fixed it. Solved topics are labelled.
- Comment on the blog and the docs with the same account.
- Edit or delete your own posts.
- Search every topic you may read at /community/search.
- Follow your notifications with the bell in the header. It shows replies to your topics and comments, your replies that were marked as solved, new badges and notes from moderators. The full list is at /community/notifications.
- Report a post or a member. See "Report a problem" below.
Categories
Each category has one purpose, so people can find the right place and the right answer.
| Category | Use it for |
|---|---|
| Announcements | Releases, roadmap changes, outages and funding updates. Read here first. Only the team starts topics here, and signed-in members can reply |
| Help and questions | "How do I..." and "it isn't working". Say your Cutscript and macOS versions, and mark the reply that solved it |
| Bug reports | Something broke and you can make it happen again. Give your version, the steps, what you expected and what happened |
| Feature requests | An idea for the editor. Describe the job you are trying to do, not only the button |
| Show and tell | Videos, graphics, brand kits and workflows made with Cutscript |
| Tutorials and tips | Short guides, shortcuts and workflows from members. The official reference stays in the docs(/docs) |
| AI director and graphics | Prompts, plans, the Design pack, brand kits, AI accounts and what things cost |
| Recording and devices | Screen, window and area capture, microphones and cameras, permissions, cursor and clicks, iPhone and iPad |
| Contributors | Building from source, pull requests, architecture, tests, translations and docs, for people changing the code |
| Donors club | For people who support Cutscript: early looks at what is coming, and a direct line to the people building it. Only donors, and the moderators, can read and post here. Everyone else sees it locked, with a link to donate(/donate) |
Badges
A badge appears beside a member's name on their posts and on their profile.
| Badge | What it means |
|---|---|
| Donor | You gave to Cutscript, any amount, and the donation is linked to your account |
| Monthly donor | You give every month. It stays while the monthly gift is active |
| Top donor | Your donations add up to the Top donor amount or more. The team sets that amount, and it starts at $100 in total, after refunds |
| Contributor | You helped build Cutscript with code, docs or translations. The team gives it |
| Moderator | You help keep the forum friendly and on topic |
| Cutscript team | You build Cutscript |
How donor badges look
Donors get a gold badge, a gold ring with a small diamond on their picture, and a sign under the picture on their profile that reads Donor, Monthly donor or Top donor. A donor also gets the Donors club. The badge shows that you give, never how much. The total on your own profile is for you only.
Link a donation to your account
A donation counts for a badge once it is linked to your account. There are two ways:
- Automatically, when you paid with the same email as your verified GitHub or Google email.
- From your thank-you page. If you paid with another email, open the private thank-you page you were sent to after paying, while signed in, and press Add to my profile.
You can see what is linked in Your support on your profile(/community/profile). A donation that is fully refunded stops counting, and the badge follows. A donation already linked to another member cannot be added to yours.
New accounts
To keep spam out, an account can't post links or pictures in its first 24 hours, and posts less often: two topics a day and ten replies an hour. After that the limits rise to ten topics a day and sixty replies an hour.
House rules
These are the short version. The full text is the Code of conduct.
- Be kind. Disagree with ideas, not people.
- Help us help you. Search first. Post one problem in one topic. Say your Cutscript and macOS versions.
- Use the right category, and give the details that category asks for.
- Keep secrets out. No API keys, passwords or other people's private data. Hide them in screenshots and recordings.
- Share only what you have the right to share. Do not ask for, or give, help taking videos you have no right to use.
- No spam and no unrelated advertising.
- Security problems go to Security, not into a public post.
Confirmed bugs and pull requests live on GitHub. Questions, ideas, show and tell, and early bug reports live in the forum. That keeps one conversation in one place.
Moderators look after the forum. They can hide a post and give a reason, which the author still sees. They can also lock a topic, pin it, move it to another category, and stop a member from posting for a day, a week, a month or for good. The Code of conduct says how they decide.
Report a problem
- A post, reply, comment or member. Press Report on the post, or Report this member on a profile. Pick a reason, add a note if it helps, and send it. You need to be signed in. Reports go to the moderators' queue.
- A security problem. Use Security, not a public post.
- A conduct problem you would rather not raise in public, or one about a moderator: write to our contact page.
Other places
- Questions: read the docs. Start with Troubleshooting, the FAQ and Support.
- Bugs and ideas without an account: email our contact page. See Contributing for what to include.
- News: the changelog(/changelog) and the blog(/blog). The blog has an RSS feed at /blog/rss.xml.
- Help the project: Donate, or hire Kwebby for custom work.