DocsInstall
Templates and downloads
How full-stack projects and downloadable templates reach you: releases, links, checksums, demos and AI prompts.
Updated This page as Markdown
Full-stack projects reach you as downloads, and so do landing pages and components written in plain HTML, CSS and JS, and mobile components (React Native code for Expo apps). Everything here happens on the product's page, signed in.
What it solves
The problem. A template from a download link leaves you guessing: whether the file is the one that was published, which version you have, and when a fix is out.
What you get. Versioned releases with notes, a file for each platform with its SHA-256 checksum, scanned for malware before it's published, behind short-lived links of your own that resume.
How it grows. Older versions stay downloadable, What's new says which version you have, and you hear of each new one; a release whose notes say "fixes #12" closes that bug for everyone who reported it.
Releases
A product that ships as files has releases: a version (such as 1.2.0), notes on what changed, and its files, each for
a platform: any, Windows, macOS, Linux, Android, iOS or the web.
- The product page lists every published release, newest first. Older versions stay downloadable.
- Each file shows its size and its SHA-256 checksum, so you can check what you downloaded is exactly what was published.
- Release files are scanned for malware when they're uploaded; a file found infected is never published.
- What's new on the product page shows every release with its notes. Once you have the product it says which version you have ("You have v1.2 · v1.3 is out"), and you hear about each new one on the site and by e-mail: see Reviews, bugs and updates.
Downloading
Press Download beside a file. The site makes you a link of your own, and your browser starts the download.
- A link works for 10 minutes and can resume a broken download. Once it expires, press Download again for a new one.
- Components, landing pages and mobile components also download as a ZIP of their code (Download source on their
page), with a README on putting it into your project. A mobile component's has a
package.jsontoo, naming its packages at the versions UpFork checked: Install mobile components.
Who can download:
| Product | Who |
|---|---|
| Free | Any member |
| Paid | Its buyers, even after it goes off sale: find it in your purchases |
Checking a download
On macOS or Linux:
shasum -a 256 <file>On Windows, in PowerShell:
Get-FileHash <file> -Algorithm SHA256The result should be the checksum on the product page (Windows writes it in capitals; that doesn't matter).
Demos
Many products have a live demo. The preview on the product page is for everyone. Members can also open the demo in a tab of its own, to try it full size; so can anyone for a free product, without an account.
AI prompts
A component's or landing page's AI prompt hands its whole code to your AI assistant (Claude, ChatGPT, Cursor and the like), with instructions for putting it into your project. Copy it from the product's page.
- It's for members. A paid product's prompt is for its buyers, since it holds the whole code.