Easy-to-manage touch screens
무료 오픈소스 터치스크린으로 USB 설정 가이드, 드래그‑드롭 편집기, 로컬 제어를 제공하며 Home Assistant용으로 제작되었습니다
Assassin's Creed 컬렉션을 탐색·추적합니다 600개 이상 공식 컬렉터블 이미지·필터·관리
Browse and track your Assassin's Creed collection. 600+ officially licensed collectibles with images, filters, and collection tracking.
라이프스타일HTML · JavaScriptGitHub @ThePrivateGeek온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기ACDb - Assassin's Creed Collector's Database is a fan-made collection tracker for official Assassin's Creed collectibles. Browse, search, and track your collection — all in your browser.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗A fan-made collection tracker for official Assassin's Creed collectibles. Browse, search, and track your collection right in your browser, or sign in with Google to see it on any device. Share your progress and compete on the leaderboard.
Live site: acdb.theprivategeek.com
collects), and an edition you own part of drops out while its missing parts show on their own. The four newest items wear a NEW sticker, and every card and item window shows the item's permanent id (#14) on its game lineseries field (e.g. Assassin's Creed: Assassins) that groups single issues with the trade paperbacks that collect them, and can span types (the Last Descendants novels and the Locus comic share one series). The Series dropdown only appears when the current selection contains series items, and the series line in an item's card is a one-click filter to the whole runread field holds the book's path inside that collection, unencoded as the archive names it (e.g. 07. AC Templars/AC Templars 2016 (3)), and readUrl in js/utils.js builds the link; a full https:// URL is used as-is for books hosted elsewhere. An optional readLang (e.g. "fr") marks a scan in a different language and adds a tag such as "(Fr)" to the button. collected editions only get one when the archive holds a scan of the collection itself, not just its single issuescollects list of the items they reprint, so marking a trade paperback read also marks its issues read (never the other way round, and unmarking it changes nothing) Which types count is READABLE_TYPES in js/utils.js#reading) lists curated orders with a Chronological / Release toggle, read switches, an "Up next" shortcut and an "Only missing" switch that hides the books you have in any edition (a book you own only in a collected edition says "Owned in "). Complete Lore covers every canon novel, comic and manga in story order (120 entries, grouped under era headings that fold; all start open, with Collapse all / Expand all); a game filter narrows it to the stories tied to one game (#reading/complete/valhalla) or to the original stories not tied to any game. By Series (#reading/series) lists every series in the orders with your read progress (series under way first, under "Continue reading"); each series opens as its own page (#reading/series/uprising) under a "By Series › Uprising" breadcrumb, with a header card (first cover, types, era range, progress, "Up next" and a link to the whole series in the collection), its books placed as in Complete Lore, and links to the series before and after it. Series pages are derived from the orders and the items' series field, so they need no data of their own. Complete Lore places the games among the books as unnumbered rows (a "Show games" switch hides them), and a DLC set in another period than its game (Freedom Cry, Jack the Ripper, Wrath of the Druids) gets a row of its own; a game row opens the game's dialog over the list (see Games). There are also the Oliver Bowden Novels (also the Bowden series' page) and Non-canon Stories. Books in an order show their position and the next book in their item card. Orders live in js/reading-orders.js: each entry is an item id, the start year and in-universe setting of its main story, and its earliest release date; the list order is the chronological order. Placement rules: a unit sits where its main historical story happens, story arcs stay together in issue order, anthologies split by era, and collected editions that only reprint issues are left out#games) lists every released Assassin's Creed game with its DLCs (expansions, story missions, game modes and Discovery Tours; cosmetic packs, multiplayer map and character packs and seasonal events are left out). Release order is a grid of box-art cards; Story order is a timeline under era headings, where a DLC set in another period than its game gets a row of its own. Search (it ignores accents, so "ragnarok" finds Dawn of Ragnarök) and kind chips (main games, spin-offs, handheld, mobile, browser, VR) narrow the list; the tab opens on the main games, with All one chip away. A card opens the game's dialog (#games/assassins-creed-valhalla): box art, developer, setting, release date, platforms, re-releases such as The Ezio Collection, a short spoiler-free description, links to its stories in Complete Lore and its items in the collection, and its DLCs grouped by type. The dialog keeps keyboard focus inside it and gives it back on close, and Back closes it. Games aren't catalog items: they live in js/games.js, with their cover art in images/games/; the old #reading/games links still workFilters and Collection Insights: three games picked on the timeline, with completion by game and category, condition breakdown and reading progress.
Item card: details, your collection fields and, for books, the reading order position and the Read switch.
Reading Order: Complete Lore in story order, with a filter by game, era sections and Up next.
A series page: opened from By Series, with its header card, read progress and links to the series around it.
On a phone: the collection with filters folded away, Complete Lore, a series page and an item card.
Your collection is stored in your browser's LocalStorage. Unless you sign in or share, nothing is sent to any server. You can back up your data anytime with Back up to file in the account menu (top right), and restore it with Restore from file. Filters are remembered between visits.
Every entry in js/database.js carries a permanent numeric id, and collections, exports, and shared profiles are keyed by it, so item names can be corrected without affecting anyone's data. Item links are made from the name, so when an item is renamed, add its old slug to js/slug-aliases.js: old links then still open the item (the address switches to the new slug), and the share page builder keeps a page at the old s/ address. New entries take the next unused number (the dev tool fills it in); an id is never changed or reused, even if its item is removed. Collections saved before ids existed are migrated once on load; entries whose name no longer matches an item are dropped. The old name-keyed copy stays in LocalStorage as a backup until January 2027, when it is deleted automatically.
Just open the site, browse the database, and click any item to track it in your collection.
Signing in is optional. Sign in in the header (or the banner that appears once you own something) takes you to Google, which asks you to pick an account and sends you back. From then on:
How it works: sign-in uses Google's OAuth 2.0 authorization code flow with PKCE as a plain redirect, so no Google script loads until you click Sign in. The Worker exchanges the code with Google, asks only for your email address and account ID, and gives the browser its own session token. See privacy.html for what is stored.
You can optionally publish your collection for the community:
Sharing is entirely optional. Your local collection works independently — sharing just creates a public snapshot of your owned items.
worker/README.md)The site has one design language, written down in DESIGN.md, the design book: what each colour means, the type scale, spacing, the shared components with markup to copy, page widths, wording and the accessibility rules. The values themselves are the design tokens at the top of css/style.css. Read the book before adding or changing any UI. CLAUDE.md holds the working notes that Claude Code sessions load automatically (project rules, data conventions, tools).
DESIGN.md — the design book: rules every page and feature follows
CLAUDE.md — working notes loaded by Claude Code sessions
js/
database.js — item database (640+ entries, each with a permanent numeric id)
images.js — image path mappings
slug-aliases.js — old item slugs of renamed items, mapped to their ids
reading-orders.js — curated reading orders (chronological list + release dates)
games.js — the games and their DLCs (Games tab, game rows in Complete Lore)
utils.js — shared utilities (toast, escapeHTML, slugify, release dates,
focus trap, share links, etc.)
modal.js — item modal, gallery, lightbox
stats.js — stats dashboard, completion celebration
collection.js — export/import
sync.js — cloud sync: merge rules, push/pull
auth.js — Google sign-in, account menu, sign-in banner
sharing.js — sharing, profile view, leaderboard
reading.js — reading order view and the item modal's reading order line
games-view.js — Games tab: release grid, story timeline, game dialog
devtool.js — admin code generator
app.js — filters, rendering, routing, events, init
css/
style.css — design tokens and shared components first, then per-view styles
s/
<slug>.html — static share pages with per-item Open Graph tags, plus one
per old slug in js/slug-aliases.js
(generated by tools/build-share-pages.py; re-run after adding items)
privacy.html — privacy policy
worker/
acdb-worker.js — Cloudflare Worker API
migrations/ — D1 schema (applied in the D1 console)
README.md — deploy runbook
tools/
validate-catalog.py — checks database.js, images.js, reading-orders.js and
games.js (ids, names, fields, games, categories, images,
read links, share pages, slug aliases, reading order entries,
game data)
test-sync-merge.mjs — tests for the sync merge rules (node tools/test-sync-merge.mjs)
.githooks/
pre-commit — runs validate-catalog.py before every commit
A pre-commit hook runs tools/validate-catalog.py and blocks the commit if the catalog has errors, such as a missing or duplicate id, a duplicate name, an unknown game or category, or an image file that doesn't exist. Warnings, like a missing share page, are printed but don't block. Enable the hook once per clone:
git config core.hooksPath .githooks
Run the check by hand with python3 tools/validate-catalog.py, and skip the hook in an emergency with git commit --no-verify.
The version is shown in the footer (index.html); releases from 3.0 on are tagged in git (v3.0).
This is a fan-made collection tracker, not affiliated with or endorsed by Ubisoft. Assassin's Creed and all related names, logos, and trademarks are property of Ubisoft Entertainment. Product images are the property of their respective manufacturers and retailers (e.g. PureArts, Ravenforge). They are used for identification and reference only; no copyright or affiliation is claimed. Contact [email protected] to request removal of any image. No personal data is collected unless you sign in; see the privacy policy. Shared profiles are public and stored on Cloudflare.
Missing an item? Suggest it with the issue form, or email [email protected]. The site links to both from the footer, and from the empty state whenever a search finds nothing.
Found a bug or have a suggestion? Open an issue.