rebrand: rename Bitext Align to Word Aligner in public-facing content

dani-polani · claude · dani-polani · commit 7a1688bccffa · 2026-06-23T02:31:57.000+03:00
SITE_NAME, DISPLAY_NAME, and all user-visible descriptions updated. Removed "also referred to as Bitext Align" copy from the About page. Kept "bitext alignment" as a natural linguistic term in the SEO intro for long-tail search coverage. Technical identifiers (localStorage keys, JSON format names, package name) unchanged.

Also adds Obsidian task workflow files (.agents/tools/obsidian-tasks.md, PROJECT.md) and AGENTS.md/CLAUDE.md.

Co-Authored-By: Claude Sonnet 4.6 &lt;noreply@anthropic.com&gt;
diff --git a/.agents/tools/obsidian-tasks.md b/.agents/tools/obsidian-tasks.md
@@ -0,0 +1,184 @@
+# Obsidian Tasks (TaskNotes plugin)
+
+Tasks are stored as individual `.md` files — one file per task. A project page does not
+contain tasks directly; it renders them via `![[tasks-default.base#ThisProject]]` (dynamic
+query by the Bases plugin).
+
+## Reusing this file in another repo
+
+This file is project-agnostic — copy it verbatim into any repo's `.agents/tools/`.
+
+- **`<PROJECT>`** — the only per-project value. It is defined once in that repo's `PROJECT.md`.
+  It is the project page filename (`PROJECTS/<PROJECT>.md`) and the wikilink used in a task's
+  `projects:` field (`"[[<PROJECT>]]"`). Substitute it wherever `<PROJECT>` appears below.
+- **Machine configuration** (vault paths, see section below) is constant across all projects on
+  this machine. Change it only when moving to a different machine or vault.
+
+---
+
+## Machine configuration
+
+| Location | Path |
+|---|---|
+| Vault root | `/home/titkovd/bliss-vault/Bliss` |
+| Active tasks | `/home/titkovd/bliss-vault/Bliss/META/planning/Tasks/` |
+| Archived tasks | `/home/titkovd/bliss-vault/Bliss/META/planning/Archive/` |
+| Project pages | `/home/titkovd/bliss-vault/Bliss/PROJECTS/` |
+| Plugin config | `/home/titkovd/bliss-vault/Bliss/.obsidian/plugins/tasknotes/data.json` |
+
+---
+
+## Frontmatter schema
+
+```yaml
+---
+title: Task title
+status: planned
+priority: normal
+contexts:
+  - agentic             # always set when agent creates or modifies a task
+projects:
+  - "[[<PROJECT>]]"     # wikilink matching the project page filename
+agent-identity: claude-sonnet-4-6  # fill with actual agent/model id
+dateCreated: 2026-01-01T00:00:00.000+03:00
+dateModified: 2026-01-01T00:00:00.000+03:00
+tags:
+  - task
+scheduled: 2026-01-01  # optional
+due: 2026-01-01        # optional
+timeEstimate: 60       # minutes, optional
+blockedBy:             # list of wikilinks, optional
+timeEntries:           # filled during work, see Time tracking section
+  - startTime: 2026-01-01T10:00:00.000Z
+    description: Brief description of what was done
+    endTime: 2026-01-01T11:30:00.000Z
+---
+```
+
+Tasks are identified by the `task` tag. Every task file must have it.
+
+---
+
+## Field values
+
+These values come from the plugin config and apply across all projects.
+
+### Status
+
+| Value | Label | Active? |
+|---|---|---|
+| `backlog` | Backlog | Yes |
+| `planned` | Planned | Yes (default for new tasks) |
+| `ongoing` | Ongoing | Yes |
+| `onhold` | On Hold | Yes |
+| `review` | Review | Yes |
+| `done` | Done | No |
+| `closed` | Closed | No (auto-archives) |
+
+### Priority
+
+| Value | Label |
+|---|---|
+| `low` | Low |
+| `normal` | Normal (default) |
+| `high` | High |
+
+### Contexts
+
+Free-form — no predefined values in plugin config. Always include `agentic` when the agent
+creates or modifies a task.
+
+---
+
+## Agent behavior
+
+When creating a task:
+- Set `contexts: [agentic]`
+- Set `agent-identity` to the current model/agent identifier
+- Set `projects` to `"[[<PROJECT>]]"`
+- `status` defaults to `planned`, `priority` defaults to `normal`
+
+When updating a task, update `dateModified` to the current timestamp.
+
+When work on a task is complete:
+- Set `status: review` (not `done` — the user reviews and closes)
+- Add a brief summary to the task body: what was done and anything the user should know
+  (e.g. decisions made, caveats, follow-ups)
+- Add a Changelog entry on the project page (see Changelog section)
+
+---
+
+## Time tracking
+
+When working on a task, record the session by appending to `timeEntries` in the frontmatter.
+
+**Format:**
+```yaml
+timeEntries:
+  - startTime: 2026-06-20T10:00:00.000Z
+    description: Brief description of what was done in this session
+    endTime: 2026-06-20T11:30:00.000Z
+```
+
+**Rules:**
+- Times are in UTC (suffix `Z`)
+- Note the start time before beginning work, note the end time when done
+- `description` should describe what was accomplished in this specific session (not repeat the task title)
+- Add a new entry per work session; never edit past entries
+- If `timeEstimate` is set on the task, use it as a rough target
+
+---
+
+## Changelog
+
+Each project page (`/home/titkovd/bliss-vault/Bliss/PROJECTS/<PROJECT>.md`) has a `## Changelog` section. Update it
+when completing meaningful work.
+
+**Format** — group by date, most recent first, one line per entry or group:
+
+```markdown
+## Changelog
+
+### 2026-06-20
+- Added top/bottom padding controls for cards
+- Various UI improvements: mini-preview on mobile, export flow
+
+### 2026-06-10
+- Initial card generation feature
+```
+
+**Rules:**
+- Write entries when marking a task as `review`
+- One line per change; group small related changes into a single line (e.g. several UI tweaks → "Various UI adjustments: X, Y, Z")
+- Focus on user-visible outcomes, not implementation details
+- **Compact periodically:** if a date has many granular entries, merge them. Older history should read as milestones, not a commit log
+- Significant features and decisions stay separate; minor fixes and polish get grouped
+
+---
+
+## Common queries
+
+Find all tasks for this project:
+```bash
+grep -rl '"[[<PROJECT>]]"' /home/titkovd/bliss-vault/Bliss/META/planning/Tasks/
+```
+
+Find tasks by status:
+```bash
+grep -rl 'status: planned' /home/titkovd/bliss-vault/Bliss/META/planning/Tasks/
+```
+
+Combine both:
+```bash
+grep -l 'status: planned' $(grep -rl '"[[<PROJECT>]]"' /home/titkovd/bliss-vault/Bliss/META/planning/Tasks/)
+```
+
+---
+
+## Refreshing this document
+
+If statuses, priorities, or paths change, re-read the plugin config:
+```
+/home/titkovd/bliss-vault/Bliss/.obsidian/plugins/tasknotes/data.json
+```
+Key fields: `customStatuses[].value`, `customPriorities[].value`, `tasksFolder`, `archiveFolder`.
diff --git a/AGENTS.md b/AGENTS.md
@@ -0,0 +1,59 @@
+## Purpose
+
+This file defines stable, project-agnostic instructions for AI agents working in this repository. Keep this file short and universal. Do not add project-specific documentation, plans, temporary notes, or implementation details here.
+
+## Project knowledge
+
+Treat `AGENTS.md` as read-only operating guidance. Do not edit it or use it as project memory.
+
+## Tasks 
+
+When you need to search or find project tasks, issues, tickets, etc., address to @PROJECT.md file for specific instructions. Respect the task management system described there. 
+
+## Architecture
+
+- Use the simplest architecture that keeps the code easy to understand, test, and change.
+- Separate responsibilities when they have different reasons to change.
+- Avoid adding layers, patterns, or abstractions before they solve a real problem in the codebase.
+- Keep business/domain logic away from framework, UI, transport, storage, and infrastructure details when practical.
+
+## Comments
+
+- Code should be self-explanatory.
+- Use clear, descriptive variable and function names.
+- Structure code so its intent is obvious.
+- Use comments only when they add useful context that is not obvious from the code.
+- Keep comments concise and to the point.
+- Comments in code files should always be in English.
+- If code needs a long comment to be understood, refactor it first.
+
+## Error handling
+
+- Errors should be visible. Avoid silent and hidden errors.
+- Errors should be specific. Avoid wrapping lots of logic in a single try-catch block (or other error handling mechanism).
+- Avoid fallback code unless it is an explicit requirement of the task. Fail fast to prevent hiding broken functionality.
+- Do not handle multiple input formats unless it is required by the task. For example, if some variable should be "https://example.com" (with domain) don't handle "example.com" as well, unless it is explicitly required by the task. Handle unexpected input as an error, unless the task required to support multiple formats.
+
+## Code structure
+
+- Keep code reasonably modular, but avoid unnecessary abstraction.
+- Prefer small functions and components that are easy to reuse and test independently.
+- If a file becomes too large or mixes unrelated responsibilities, split it into focused files.
+
+## Makefile
+
+- Use Makefile for project-wide commands. Keep it simple and focused on the most common tasks. It should have commands that are useful for local development and are intended to be used frequently. 
+- Add .PHONY targets for commands that are not file-based directly above the target.
+- Don't create "help" target or other non-functional targets.
+- If Makefile commands need some configuration, use environment variables. Connect .env file to Makefile.
+
+## Environment variables
+
+- Use .env.example file as a template for .env file. Keep it updated. If some variables are not needed or deprecated, remove them from the example file. Obviously, don't store actual secrets in .env.example file.
+
+## Refactoring
+
+- Keep changes focused on the task.
+- Small, safe refactorings are allowed when they directly support the current change, reduce duplication, or make the fix simpler.
+- Do not perform broad, unrelated refactoring without explicit user approval.
+- If you notice larger structural problems, mention them in the final response as optional follow-ups instead of interrupting the task.
diff --git a/CLAUDE.md b/CLAUDE.md
@@ -0,0 +1 @@
+@AGENTS.md
diff --git a/PROJECT.md b/PROJECT.md
@@ -0,0 +1,26 @@
+Project-specific details
+
+## Tasks
+
+Task management: Obsidian (TaskNotes plugin).
+Workflow, schema, field values, time tracking, changelog rules, and queries:
+`.agents/tools/obsidian-tasks.md`.
+
+**Project name:** `Word Aligner`
+
+This is the only project-specific value. It is the `[[Word Aligner]]` wikilink in a task's `projects:`
+field and the `PROJECTS/Word Aligner.md` project page. It substitutes for `<PROJECT>` in
+`.agents/tools/obsidian-tasks.md`.
+
+### Task workflow
+
+When asked to work with tasks, issues, tickets, etc., follow `.agents/tools/obsidian-tasks.md`,
+with these project-level rules on top:
+
+- Look at `planned` and `ongoing` tasks first; if both are empty, check `backlog`.
+- Unless asked directly, only work tasks whose context is `agentic` or empty.
+- After work: set status to `review` (not `done`), summarize in the task body, and add a
+  Changelog entry on the project page.
+- Feel free to refine a task's title/description for precision (keep titles concise).
+- If asked to do something without a task, consider creating one in the relevant project and
+  following this flow.
diff --git a/README.md b/README.md
@@ -2,7 +2,7 @@
 
 **[aligner.tinygods.dev](https://aligner.tinygods.dev)**
 
-Aligner (also called *Bitext Align*) is a free web tool that shows **which word matches which** across stacked lines of text. Type or paste a sentence and its translation, click a word and then its match on the line above or below, and curved connectors draw the alignment between them. Add extra rows for **glosses** or **IPA**, then **export** the diagram or **share** it with a link.
+Word Aligner is a free web tool that shows **which word matches which** across stacked lines of text. Type or paste a sentence and its translation, click a word and then its match on the line above or below, and curved connectors draw the alignment between them. Add extra rows for **glosses** or **IPA**, then **export** the diagram or **share** it with a link.
 
 No accounts, no machine translation — you stay in control of every link. Great for lessons, social posts, grammar notes, and conlang documentation.
 
diff --git a/bitext/README.md b/bitext/README.md
@@ -1,4 +1,4 @@
-# Bitext Align
+# Word Aligner
 
 Single-page **word-by-word translation visualizer** — manual bilingual alignment, optional interlinear gloss, exports (PNG / SVG / PDF / HTML), and shareable `?data=` URLs.
 
diff --git a/bitext/src/lib/components/seo/SeoIntro.svelte b/bitext/src/lib/components/seo/SeoIntro.svelte
@@ -6,7 +6,7 @@
 		What this tool does
 	</h2>
 	<p>
-		<strong class="font-medium text-gray-900 dark:text-white">Aligner</strong> (also labeled Bitext Align)
+		<strong class="font-medium text-gray-900 dark:text-white">Word Aligner</strong>
 		is a free word-by-word translation visualizer: it shows which words in one line correspond to which
 		words on the next. Type or paste text in the <strong class="font-medium text-gray-900 dark:text-white"
 			>line editor</strong
@@ -15,6 +15,6 @@
 		<strong class="font-medium text-gray-900 dark:text-white">preview</strong>, click a word, then click
 		a match on the <strong class="font-medium text-gray-900 dark:text-white">line directly above or below</strong>;
 		only those adjacent rows link, so reorder lines with the arrows if something is out of reach.
-		Linguists call this a word alignment; most people just want to see which words match.
+		Linguists call this a word alignment or bitext alignment; most people just want to see which words match.
 	</p>
 </section>
diff --git a/bitext/src/lib/seo/metadata.ts b/bitext/src/lib/seo/metadata.ts
@@ -1,4 +1,4 @@
-export const SITE_NAME = 'Bitext Align';
+export const SITE_NAME = 'Word Aligner';
 
 /**
  * Title and description favor colloquial, user-first phrasing while keeping the formal category
@@ -8,4 +8,4 @@ export const SITE_NAME = 'Bitext Align';
  */
 export const DEFAULT_TITLE = 'Word-by-word translation visualizer — see which words match';
 export const DEFAULT_DESCRIPTION =
-	'Aligner (Bitext Align): free word-by-word translation visualizer. Stack multiple lines, link adjacent rows in the preview, optional gloss/IPA lines, exports (PNG, SVG, PDF, HTML), and shareable URLs. For learners, teachers, linguists, and conlang posts.';
+	'Word Aligner: free word-by-word translation visualizer. Stack multiple lines, link adjacent rows in the preview, optional gloss/IPA lines, exports (PNG, SVG, PDF, HTML), and shareable URLs. For learners, teachers, linguists, and conlang posts.';
diff --git a/bitext/src/routes/about/+page.svelte b/bitext/src/routes/about/+page.svelte
@@ -10,9 +10,9 @@
 	import { settingsStore } from '$lib/state/settings.svelte.js';
 
 	const TITLE = 'About';
-	const DISPLAY_NAME = 'Aligner';
+	const DISPLAY_NAME = 'Word Aligner';
 	const DESCRIPTION =
-		'Aligner (Bitext Align): multi-line word alignment, interlinear glosses and IPA, RTL scripts, word-splitting rules, per-line typography, exports (PNG, SVG, PDF, HTML), and shareable URLs — for learners, teachers, and linguists.';
+		'Word Aligner: multi-line word alignment, interlinear glosses and IPA, RTL scripts, word-splitting rules, per-line typography, exports (PNG, SVG, PDF, HTML), and shareable URLs — for learners, teachers, and linguists.';
 
 	const canonical = $derived(page.url.origin + page.url.pathname);
 	const ogImage = $derived(`${page.url.origin}/api/og`);
@@ -228,11 +228,8 @@
 	<p class="mt-4 text-lg text-gray-600 dark:text-gray-400">
 		<strong class="font-semibold text-gray-800 dark:text-gray-200">{DISPLAY_NAME}</strong> is a free,
 		browser-based tool for drawing word-to-word and morpheme-to-morpheme links between stacked lines of
-		text — for bilingual glosses, interlinear annotations, classroom handouts, and social posts. The same
-		project is also referred to as <strong class="font-semibold text-gray-800 dark:text-gray-200"
-			>Bitext Align</strong
-		>
-		in URLs and branding. Everything runs in your browser; your sentences are not stored on our servers
+		text — for bilingual glosses, interlinear annotations, classroom handouts, and social posts.
+		Everything runs in your browser; your sentences are not stored on our servers
 		unless you choose to share them.
 	</p>
 
diff --git a/bitext/src/routes/privacy/+page.svelte b/bitext/src/routes/privacy/+page.svelte
@@ -6,7 +6,7 @@
 
 	const TITLE = 'Privacy policy';
 	const DESCRIPTION =
-		'How Bitext Align handles your data: no accounts, no server-side storage of your sentences, and what third-party tools (Google Analytics, Tally) we load.';
+		'How Word Aligner handles your data: no accounts, no server-side storage of your sentences, and what third-party tools (Google Analytics, Tally) we load.';
 
 	const canonical = $derived(page.url.origin + page.url.pathname);
 	/** Last meaningful content review of this policy. Bump when wording changes. */

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# Bitext Align`
	`1`	`+# Word Aligner`
`2`	`2`
`3`	`3`	Single-page word-by-word translation visualizer — manual bilingual alignment, optional interlinear gloss, exports (PNG / SVG / PDF / HTML), and shareable `?data=` URLs.
`4`	`4`