A fast Kanban board, built for speed, not busywork. Sign in with Google and your boards live only in your own Drive — Taskboards has no database of its own.
| Multiple boards | Create as many boards as you need. Tabs auto-paginate when they overflow. Double-click a tab to rename it, drag it to reorder (hover ‹ › to reach another page), and right-click it (long-press on touch) to pick its colour. |
| 4-zone Kanban | Archive → To Do → In Progress → Done. Drag cards between columns or reorder within a column. |
| Edit or delete a card | Double-click a card (long-press on touch) or right-click it: it turns red and shows ✎ (edit — the same form as a new card) and ✕ (delete) on its right. Click elsewhere to cancel. |
| Owner & due date | Each card tracks an assignee and optional due date. Overdue = red, due ≤ 3 days = orange. |
| Notes | Click 🗒️ in the card form to add a short note. Cards with a note show 🗒️ at the bottom right — click it to read the note. Notes stay private: shared links leave them out. |
| Owner filter | Quick-filter chips above the board — tap an owner to see only their cards. |
| Google sign-in required | A full-screen gate blocks the board until you sign in with Google. There is no local/offline account-free mode. |
| Google Drive sync | Every board saves to your personal Drive (private app folder) — nothing is stored on any Taskboards server. Works across devices. |
| Share one board | Click the 🔒 before a board’s name to publish a read-only link. Only that board is shared, protected by a passphrase; 🚀 means it is public, and one click revokes it. |
| Backup | Export / import all boards as a .json file from the user menu. |
| Stays signed in | With the optional session server, a Google refresh token (encrypted, in an httpOnly cookie) renews your sign-in quietly — no hourly re-login. |
| Installable | Install banner appears automatically on Chrome/Edge (desktop + Android) and with step-by-step instructions on iOS Safari. |
| Dark / light theme | Toggle between themes. Preference saved locally. |
| Confetti | Cards moved to Done get a small celebration. 🎉 |
Here's how a small team might use Taskboards for a sprint:
1. Create a board called "Sprint 4"
2. Add cards to TO DO:
- "Design login screen" → owner: Ana → due: 10 Apr
- "Write API tests" → owner: Bruno → due: 12 Apr
- "Fix checkout bug" → owner: Carla → due: 9 Apr ← turns red when overdue
3. Ana starts working → drag "Design login screen" to IN PROGRESS
4. Carla finishes → drag "Fix checkout bug" to DONE 🎉
5. Sprint ends → drag leftover cards to ARCHIVE to park them
Open next sprint's board — archive is always one click away to reactivate ideas
6. Use owner filter chips to see only Bruno's cards across any board
| Shortcut | Action |
|---|---|
Ctrl + Enter |
Open new card modal |
Escape |
Close modal / cancel edit |
| Double-click card | Inline edit title |
| Double-tap card (mobile) | Inline edit title |
| Drag card | Move between columns or reorder within column |
- Vanilla JS + HTML + CSS — no framework, no build step
- Service Worker — offline caching, background sync
- Google Identity Services (GSI) — one-tap sign-in
- Google Drive API — per-user private app folder storage
- Railway — deployment platform
- Primer design system — GitHub's open-source token system for colours and typography
- Go to console.cloud.google.com → create a project
- APIs & Services → Library → enable Google Drive API
- APIs & Services → Credentials → Create Credentials → OAuth 2.0 Client ID
- Type: Web application
- Authorized JavaScript origins:
https://your-app.railway.app http://localhost:3000
- Copy the Client ID
- Open
public/config.jsand paste it:GOOGLE_CLIENT_ID: '123456789.apps.googleusercontent.com' - Commit and push → Railway redeploys → done ✓
The Client ID is not a secret — it identifies the app, not any user. Each user authenticates with their own Google account and data stays in their own Drive.
Each board has a lock in its tab: 🔒 private (default) or 🚀 public. Click it to open the share dialog.
- Share link publishes just that board as one encrypted file in the owner’s Google Drive (visible to anyone with the link, but unreadable without the passphrase). A passphrase like
7KQM-X2PD-9WFH-ZT4Cis generated and shown in the dialog together with the link; Copy share details copies both. - Viewers open
view.html?b=…, type the passphrase and see the latest version, read-only, refreshed every ~30 s. They don’t need a Google account. Decryption happens in their browser; the passphrase never leaves it. - Only the owner edits. Every change is re-published automatically within seconds.
- Revoke public access deletes the shared copy, so the link stops working immediately and the board is private again. Deleting a shared board (or replacing everything via Import) revokes it too.
Set it up (one time)
- Google Cloud Console → Credentials → Create credentials → API key. Restrict it: Application restrictions → HTTP referrers
https://taskboards.monco.io/*; API restrictions → Google Drive API. Paste it inconfig.js:DRIVE_API_KEY: AIza…(it is public by design). Until it is set, the app says sharing isn’t enabled and nothing is published. - Google Auth Platform → Data access → Add or remove scopes: add
.../auth/drive.file(non-sensitive — no Google review). The app creates files only for boards the user chooses to share. - Redeploy the session server (it now also requests
drive.file). Existing users are asked for the extra permission the first time they share.
The passphrase is stored in the owner’s own private Drive copy so it can be shown again. Anyone who has both the link and the passphrase can read the board — revoke to cut them off.
A board owner can invite people by email to edit it (editor) or only look (viewer). There is still no Taskboards database: a team board is one extra file in the owner's Drive, shared with the invited addresses through normal Drive permissions.
- Owner: click the lock/rocket on a board's tab → Make team board → invite by email (or remove people). The invitee gets Google's share email plus a link
app.html?team=<fileId>. - Invitee: opens the link, signs in, clicks Open board and picks the single file in Google's file picker. That pick is what lets the
drive.filescope reach it — no broader Drive access is ever requested. The board then shows up as a normal tab (with a team icon). - Sync: each member polls every ~30 s (and ~1.5 s after an edit). Cards are merged one by one — newest
updatedAtwins, deletions are tombstones — so two people editing different cards never overwrite each other. Viewers never write. If access is revoked or the file is deleted, the board stays as a private copy. - Not encrypted: unlike public links, the team file is readable by anyone it is shared with (and by Google). The privacy policy says so.
Turn it on
- Google Cloud Console → APIs & Services → Library → enable Google Picker API; allow it on
DRIVE_API_KEYtoo if the key is API-restricted. - In
public/config.jssetTEAMS_ENABLED: true(by default it is on only forlocalhost). - The Picker's
appIdis the Cloud project number, taken from the Client ID prefix — nothing to configure.
Not included yet: seats, billing and per-team admin; the Teams plan on the landing page still says "Coming soon".
The roadmap of each product is edited in the separate Roadmaps app (its own repository, hosted on Railway). Taskboards only shows it:
- Landing page: embeds the public Taskboards roadmap with the Roadmaps widget (
<div data-roadmap="<id>">plushttps://roadmaps.monco.io/embed.js). The widget follows the page's light/dark theme and is isolated from its CSS. roadmap.html: redirects to the roadmap's public page on Roadmaps (https://roadmaps.monco.io/r/<id>), so old links keep working.- To change the roadmap, sign in to Roadmaps and edit it there: every change shows up here without a deploy.
Google’s browser-only sign-in only gives 1-hour tokens, so without this the app re-asks Google about once an hour (and some browsers block that pop-up). auth.js fixes it with Google’s authorization code flow: it keeps a refresh token in an encrypted, httpOnly cookie in the user’s own browser and swaps it for a fresh access token whenever the app needs one.
- It stores nothing — no database, no token list. Board data still goes browser → the user’s Drive.
- If it’s not configured (
AUTH_APIempty inconfig.js), the app falls back to the browser-only sign-in.
Set it up (one time)
-
Use the Railway service that already deploys this repo (see below) — it serves
/auth/*by itself, no second service needed. Give it a custom domain on the same site as the app — e.g.auth.monco.iofortaskboards.monco.io: Railway → Settings → Networking → Custom Domain, then add the CNAME it shows at your DNS. (Its default*.up.railway.appaddress is a different site, so cookies set there would be third-party and get blocked.) Same site is what keeps the cookie first-party, so browsers don’t block it. -
Google Cloud Console → Credentials → your OAuth client: add the authorized redirect URI
https://auth.monco.io/auth/callback, and copy the Client secret. -
Set these environment variables in Railway → Variables (see
.env.example):Variable Value GOOGLE_CLIENT_IDthe same Client ID as in config.jsGOOGLE_CLIENT_SECRETthe client secret from step 2 (keep it secret) COOKIE_SECRETa long random string, e.g. openssl rand -hex 32(encrypts the cookie)AUTH_BASE_URLhttps://auth.monco.ioAPP_ORIGINhttps://taskboards.monco.io(comma-separate more origins) -
In
config.jsset the URL, only for the real domain so other hosts (like the*.up.railway.appcopy) keep using the browser-only sign-in:AUTH_API: location.hostname.endsWith('monco.io') ? 'https://auth.monco.io' : '',
then push.
-
In the OAuth consent screen, publishing status must be In production (in Testing, Google expires refresh tokens after 7 days).
Prefer one host for everything? Point
taskboards.monco.ioitself at the Railway service (instead of GitHub Pages) and setAUTH_BASE_URLandAPP_ORIGINto that same URL — then no second domain is needed.
Railway keeps the service running (unless you turn on App Sleeping), so there is no cold start. On a host that sleeps when idle, the first sign-in after a quiet spell can take ~30 s.
- Fork or push this repo to GitHub
- railway.app → New Project → Deploy from GitHub repo
- Variables: none needed for the app itself — the Client ID lives in
public/config.js. Without the variables listed above,/auth/statusanswers{"enabled":false}and the app uses the browser-only sign-in - Railway auto-deploys on every push to
main
npm install
npm start
# open http://localhost:3000Google SSO requires the page to be served over HTTP/HTTPS (not
file://).npm starton localhost works fine.
taskboards/
├── public/
│ ├── index.html # Product / landing page — sign in or continue without an account
│ ├── app.html # App shell + all modals (the actual board)
│ ├── app.js # All logic: boards, cards, drag, sync, PWA install
│ ├── style.css # Primer-based design system, light + dark themes
│ ├── sw.js # Service worker — cache versioning, offline support
│ ├── manifest.json # PWA manifest — icons, display mode, theme colour
│ ├── share-core.js # Passphrase + AES-GCM encryption for shared boards
│ ├── roadmap.html # Redirect to the roadmap page on Roadmaps
│ ├── view.html/.js/.css # Read-only viewer for a shared board
│ └── config.js # Google Client ID (not secret, safe to commit)
├── auth.js # Optional session server: refresh-token cookie, /auth/*
├── .env.example # Session-server settings
└── server.js # Express: static files + /auth
Vibe coded by David Marques · Product Manager & occasional vibe coder from Lisbon 🇵🇹
If this saves you time or sparks something, consider buying me a coffee:
MIT — do whatever you like with it.