Manage each article as one row and separate drafting, review, approval, and publishing. Covers importing a local CSV, dropdowns, filter views, sharing permissions, and version history, and sets up a flow for manually updating site files after approval.
This translation was generated by AI. Check the code, units, and numbers against the original. Native-speaker review has not yet been completed for each language. 한국어
Who this is forWriters and reviewers who run a small tutorial site or team knowledge docs together
With only a list of topics, it is hard to know which draft is under review and what is blocking publication. This example links article ID, audience, deliverable, writer, reviewer, status, evidence, privacy check, approval date, published URL, and release version in one row. The article ID stays the same even if the title changes, and is used as the key for finding records again.
| Column group | What to record |
|---|---|
| Article ID · title · audience · deliverable | What problem is solved, for whom, and what they get |
| Writer · reviewer · review due date | Roles and dates to check |
| Status · next action | The current stage and what the next person does |
| Evidence · privacy check | Official sources or a description of the synthetic example, and the check result |
| Approval date · published URL · release version | When it was approved and the result that was actually published |
Use only one of these statuses: idea, drafting, in review, changes requested, approved, published, on hold. “Approved” is the team's record that review is finished, and “published” is the record that it was applied to the site and the result was checked. This distinction is an operating rule we set, not an approval system built into Sheets.
Google's official help describes file import and cell dropdowns as separate features. A CSV carries only values, so you must add these settings after importing. Do not describe the file as already set up with automatic syncing or connections.
A reviewer may want to see rows with status in review first, and a writer may want to see their own changes-requested rows first. In desktop Sheets, use Data > Create filter view, choose the status and owner criteria, and save views such as “Awaiting review” and “My changes.” A regular filter can also be visible to other users of a shared file, so use filter views to organize individual work.
The file owner should consider keeping general access restricted and adding specific people. Writers can be editors, reviewers who only leave feedback can be commenters, and stakeholders who only read can be viewers. Commenters cannot change the status in a cell directly, so decide that the editor who receives the review feedback records the status and approval date. The administrator grants permissions according to actual work needs.
Users with edit permission can check previous states and who made changes in version history, and name versions at important points. This helps find the state just before approval, but it is not the same as the version history of the site files. Restoring an earlier version can undo other edits, so check the impact before doing it. Downloading a CSV does not carry over sharing permissions or version history.
No automatic behavior such as “changing the status to approved in Sheets updates the site” has been implemented. This tracking sheet is a record in which people link who approved which draft and which release it went into.
| Sample | Status · check | Action needed now |
|---|---|---|
| EX-001 | Idea / not checked | Write the synthetic example draft |
| EX-002 | Drafting / not checked | Fill in the handover items |
| EX-003 | In review / needs changes | Re-review after removing internal paths |
| EX-004 | Approved / done | Apply to JSON, verify, and deploy; published URL still blank |
EX-004 also has no published URL or release version, so it is not counted as published. Conversely, adding a link alone does not let you skip review. Before publishing, a person checks that the approval date, evidence, and privacy check result are all present. The CSV contains no formulas or automation that enforce these judgments.
content-register.csv is a local template with 14 columns and 4 rows of synthetic data. README.txt, column-guide.txt, and workflow-checklist.txt contain the settings to apply after importing and the status rules. The local file's UTF-8 encoding, row and column counts, duplicate article IDs, allowed statuses, and the samples' blank published URLs were checked. The actual Google Sheets import and the dropdown, permission, and version history operations were not tested.
No accounts or Google Drive files were created or connected, and the site checkout was not modified. In organization accounts, sharing scope may be limited by admin policy. The official help pages were checked on September 19, 2026, and menu labels may differ depending on display language and product updates.
Local @oai/artifact-tool and Python CSV/JSON checks; official sources checked 2026-09-19
Includes code, input data, and instructions. Extract the ZIP and read README.txt first.
Download example ZIPExample code, filenames, and input keys remain unchanged. Refer to the commands and checking steps in the translated article as well.
The explanations and examples were written for this site. See the official sources below for the related behavior and concepts.