diff --git a/TODO.md b/TODO.md index 2ab4d10..c157f26 100644 --- a/TODO.md +++ b/TODO.md @@ -10,7 +10,21 @@ Last updated: 2026-09-10. ## Now -- [ ] Approve the copy: review the drafted company-voice text page by page. +- [ ] Add some copy somewhere, something like: +``` + Have something that needs making? + A website that's embarrassing you? + A product that needs explaining? + An idea that doesn't fit neatly into a service category? + Tell us what you're trying to do. We'll figure out what needs to be made. +``` + and +``` + I've figured out how to use AI to dramatically accelerate the design/development process without turning the result into generic AI slop. +``` + and something about the workflow: Old workflow → AI-assisted workflow → finished result + + and something like "Got a weird project? Give it to us." ## Assets @@ -25,10 +39,13 @@ Last updated: 2026-09-10. ## Polish (ideas, not yet agreed) +- [ ] Consider a graphics or video section + - [ ] find and add IKEHU video - [ ] Urban Moto case-study hero is low resolution (450px native at its widest); find or shoot a better crop. - [ ] Consider moving `writtenearplugs.jpg` from the Urban Moto grid into the Print gallery. +- [ ] redesign the site as a sales funnel rather than as a design piece ## Done diff --git a/memory-bank/activeContext.md b/memory-bank/activeContext.md index 2fb44a2..43cca7a 100644 --- a/memory-bank/activeContext.md +++ b/memory-bank/activeContext.md @@ -1,14 +1,13 @@ # Active Context - 2RE03 Portfolio Site > Current focus, recent changes, next steps, and active decisions. -> Last updated: 2026-09-10. +> Last updated: 2026-09-22. ## Working Agreements (read first) -- **Never `git commit` or `git push` without explicit approval.** Do the work, - verify it, then STOP and ask. Approval covers that one action only; every future - commit and push needs its own yes. -- Until approval, leave finished work in the working tree as uncommitted changes, - and say plainly what is sitting there waiting. +- **Do not edit files outside the project folder.** + Every write (create, edit, move, delete) stays under the workspace root. Reading files elsewhere is allowed. If a task looks like it needs a write outside that folder, STOP and ask the user first, naming the path and the reason. +- **Never `git commit` or `git push` without explicit approval.** Do the work, verify it, then STOP and ask. Approval covers that one action only; every future commit and push needs its own yes. +- Until approval, leave finished work in the working tree as uncommitted changes, and say plainly what is sitting there waiting. ## Current Work Focus **Build phase.** A working static site on a locally vendored Bootstrap 5.3.3, @@ -17,6 +16,12 @@ with custom CSS/JS and a live Web3Forms contact page. It now includes a Next is user review of copy/design and the deployment decision. ## Recent Changes +- **2026-09-22** - User set a **code and writing style requirement**: **soft wrap**. Do not hard-wrap lines to fit a column limit (there is no ~80-char limit) in code or in memory-bank writing; let the editor soft wrap long lines and break lines only at structural boundaries. Existing hard-wrapped files are left alone, with no reformat pass. +- **2026-09-22** - User set a second **working agreement**: **do not edit files + outside the project folder** (`/home/torrey/Documents/Sites/2RE03`). Recorded + here (Working Agreements at the top, plus the decisions log), in + `projectbrief.md` (Ways of Working), `techContext.md` (Tool Usage Patterns), and + `progress.md`. No production files changed. - **2026-09-10** - Created the standard memory bank (`memory-bank/`): the six core files plus `reference-materials.md` (replacing an earlier single-file draft). @@ -148,6 +153,8 @@ Next is user review of copy/design and the deployment decision. | 19 | Keep `memory-bank/` and `.clinerules/` tracked in the repo | ✅ Done | | 20 | `TODO.md` at the repo root is the backlog; the memory bank points at it | ✅ Done | | 21 | **No `git commit` or `git push` without explicit user approval** | ✅ Active rule | +| 22 | **No editing files outside the project folder** (`/home/torrey/Documents/Sites/2RE03`); reads elsewhere are fine, writes are not, so ask first if a task seems to need one | ✅ Active rule | +| 23 | **Soft wrap: no hard wrapping at a column limit**, in code and in memory-bank writing; a break marks a structural boundary, not a width boundary. Going forward only, with no reformat pass over existing files | ✅ Active convention | ### Open Questions (remaining) 1. **Real assets:** any real favicon, Open Graph/social image, or logo to add? @@ -167,6 +174,7 @@ Next is user review of copy/design and the deployment decision. (see `projectbrief.md` → Ways of Working). - Private asset provenance (never credit the CEO on the site). - Keep all site copy in the tone defined in `productContext.md`. +- **Soft wrap, no hard wrapping:** do not insert line breaks to satisfy a column limit. Keep each logical unit (statement, tag, CSS rule, list item, paragraph) on one line; a break marks a structural boundary, never a width boundary. Applies to code (HTML/CSS/JS) and to memory-bank writing. Existing hard-wrapped files stay as they are. Details in `techContext.md` -> Code Style. ## Learnings & Insights - The reference build used hand-coded HTML + Bootstrap 5 with a small custom diff --git a/memory-bank/progress.md b/memory-bank/progress.md index 22fb84c..11335ff 100644 --- a/memory-bank/progress.md +++ b/memory-bank/progress.md @@ -1,7 +1,7 @@ # Progress - 2RE03 Portfolio Site > What works, what's left, current status, known issues, and decision evolution. -> Last updated: 2026-09-10. +> Last updated: 2026-09-22. ## What Works - Memory bank initialized in the standard multi-file form. @@ -194,3 +194,9 @@ copy/design review and the optional polish tracked in `TODO.md`. - **2026-09-10** - User set a **working agreement**: no `git commit` or `git push` without explicit approval. Recorded in `activeContext.md` (Working Agreements at the top, plus the decisions log) and `techContext.md` (Tool Usage Patterns). +- **2026-09-22** - User set a second **working agreement**: **do not edit files + outside the project folder** (`/home/torrey/Documents/Sites/2RE03`). Recorded in + `activeContext.md` (Working Agreements at the top, Recent Changes, and the + decisions log), `projectbrief.md` (Ways of Working rule 8), `techContext.md` (Tool + Usage Patterns), and here. No production files changed. +- **2026-09-22** - User set a **code and writing style requirement**: **soft wrap**. No hard wrapping to a column limit in code or in memory-bank writing; lines break only at structural boundaries. Applied going forward only, with no reformat pass over existing files (explicit user instruction). Recorded in `activeContext.md` (Recent Changes, Important Patterns & Preferences, decisions log), `projectbrief.md` (Ways of Working rule 9), and `techContext.md` (new Code Style section). diff --git a/memory-bank/projectbrief.md b/memory-bank/projectbrief.md index d853118..bff4c0a 100644 --- a/memory-bank/projectbrief.md +++ b/memory-bank/projectbrief.md @@ -1,7 +1,7 @@ # Project Brief - 2RE03 Portfolio Site > Foundation document. Shapes all other memory-bank files and is the source of -> truth for scope. Last updated: 2026-09-10. +> truth for scope. Last updated: 2026-09-22. ## Overview Build a portfolio website for the design company **2RE03**. The primary focus is @@ -58,6 +58,13 @@ the company does, with a distinct personality. assets resolve, check responsive behavior) before reporting done. 7. **Prefer plain, dependency-light, static output** unless a decision says otherwise. +8. **Stay inside the project folder.** Do not create, edit, move, or delete files + outside `/home/torrey/Documents/Sites/2RE03` (the workspace root). Reading files + elsewhere is fine. If a task seems to need a write outside it, stop and ask the + user first. This also means do not move repo files to paths outside the repo, and + do not delete or write to the external asset backup at + `/home/torrey/2RE03-unused-assets-backup/`, without asking. +9. **Soft wrap, do not hard wrap.** Do not break lines just to stay under a column limit, in code or in the memory bank: let the editor soft wrap long lines and break only where the structure calls for it. This is a going-forward rule; do not reformat existing files to apply it. ## Source Material All source material lives in the temporary `refrence/` folder. See diff --git a/memory-bank/techContext.md b/memory-bank/techContext.md index 8321d35..fcdf312 100644 --- a/memory-bank/techContext.md +++ b/memory-bank/techContext.md @@ -1,7 +1,7 @@ # Tech Context - 2RE03 Portfolio Site > Technologies, development setup, constraints, dependencies, and tool usage. -> Last updated: 2026-09-10. +> Last updated: 2026-09-22. ## Current State A working static-site scaffold exists at the repo root: @@ -86,7 +86,17 @@ No build step and no package manager - it is plain static HTML/CSS/JS. - Output should be lightweight and static unless a decision says otherwise. - Work data should have a single source of truth. +## Code Style +- **Soft wrap, do not hard wrap.** There is no column limit (~80 chars or otherwise). Do not insert line breaks to keep a line short: keep each logical unit (a JS statement, an HTML tag, a CSS rule, a list item, a sentence or paragraph) on one line and let the editor soft wrap it. A line break should mark a structural boundary, never a width boundary. +- **Applies to** HTML, CSS, JS, and Markdown writing, including the memory bank and `TODO.md`. +- **Going-forward rule only (set 2026-09-22).** The existing files are hard-wrapped at roughly 80 chars and stay that way. Do not run a reformat pass over them unless the user asks for one. + ## Tool Usage Patterns +- **Never edit files outside the project folder.** All writes (create, edit, move, + delete) stay under `/home/torrey/Documents/Sites/2RE03`. Reading files elsewhere + is allowed; writing is not. If a task seems to need an outside write, stop and + ask first, naming the path and the reason. This includes the external asset + backup at `/home/torrey/2RE03-unused-assets-backup/`. - **Never `git commit` or `git push` without explicit approval from the user.** Make the edits, verify them, then stop and report; leave the work uncommitted until told otherwise. Approval is per action, not standing.