that's the whole premise. thoughts go in, thoughts compound, quality is increased (maybe).
a github pages site where I put words. sometimes the words are good. no guarantees.
- open site
- read
- (optional) think
thoughts are mine. the html is vibes-licensed.
The browser editor is Pages CMS, configured by .pages.yml. Once these site changes are pushed to GitHub, use the Edit site footer link (or /edit/).
One-time setup:
- Sign in to Pages CMS with GitHub.
- Install its GitHub App for corpaci/corpaci.github.io only.
- Open the repository's main branch. The editor loads
.pages.ymlautomatically. - Choose a section, add or edit an entry, and save.
Readings and art have title, creator, link, and formatted notes fields. Art also supports image uploads and credits. Publications have citation fields. Posts have title, topics, visibility controls, and a Markdown editor that preserves existing HTML, equations, footnotes, and theme layers. The homepage, section introductions, footer line, and About are editable too. Section introductions use the same text on the homepage and section pages.
Persistence: saves and image uploads are committed to GitHub, shared across devices, and recoverable through GitHub's file history. A save is separate from deployment: the public site changes after GitHub Pages successfully builds the saved commit. If it doesn't update, check the repository's Pages settings and deployment status.
Drafts: new readings, art entries, and posts start with publication switched off. Turn on “Show on the site” for readings/art, or “Publish on the site” for posts when ready. This excludes them from the website, but does not make their files private in this public repository. Hidden published posts remain accessible through their direct URLs.
When returning to local editing, pull browser changes before editing the same files. Keep settings.content.merge: true in .pages.yml so unconfigured front matter is preserved. Keep an existing post's permalink unchanged.
_data/readings.ymland_data/art.yml: ordered lists; empty until you add your own entries._data/publications.yml: published research._posts/: open thoughts and questions; new filenames include the date automatically._data/home.yml: homepage, section introductions, and footer wording.about.md: About page.assets/uploads/: uploaded images.
Preview with bundle exec jekyll serve, or build with bundle exec jekyll build.
Editor reference: Pages CMS quick start and configuration.
Personal claims, reading selections, art selections, questions, and future plans come from Luiza. Editing assistance should preserve that voice and leave missing content empty rather than inventing it. New writing has no automatic AI attribution.
The five existing posts remain visible with the requested Claude attribution. Each note can be changed in the editor as its post is rewritten. The note appears on the post, in the feed, and in the machine-readable summary; the writings list links directly to it. The citation under published research remains separate from these exploratory posts.
Readings and art are deliberately empty. Their descriptions use Luiza's wording from the brief. The generated “questions I keep coming back to” list has been removed; actual questions can be added as posts by Luiza.
Older pages in research/ and projects/, and text in _drafts/, retain their existing content. Their first-person descriptions and plans still need Luiza's editorial review; the attribution request only established authorship for the five posts. No new claims about those pages' authorship have been inferred.
- GitHub Pages builds
main; push reviewed changes there to publish updates. - Connect Pages CMS to the repository through Luiza's GitHub login.
- Add Luiza's reading and art selections when ready.
- Rewrite the attributed posts and review older research/project pages in Luiza's own voice.
The site build and content rendering can be checked locally. Browser saves require the GitHub connection and deployment before they can be verified end to end.