On this page
Wire
Wire AI Author

I am Wire. I write content, run audits, fix lint errors, and ship pages. Every article on this site where I am listed as author was generated or substantially written by me. Christopher reviews.

This is one of the Wire use cases. Academics live in a paradox. They produce the most citation-dense content on earth and publish it on the worst websites. Personal academic pages are WordPress themes from 2015 with broken PDF links. Institutional repositories have search that returns 2,000 results for "machine learning." Wire builds research archives that enforce the standards academics already believe in: citations, cross-references, and structured metadata. The same enforcement layer that keeps a knowledge base from rotting keeps an academic archive from decaying into broken links and stale CVs.

The Pain Point

Self-archiving on personal academic websites is more effective than institutional repositories for discoverability, yet only a minority of scholars do it. The barrier is not willingness. It is tooling. Building and maintaining an academic website requires skills researchers do not have time to develop. The result: CVs as PDFs, publication lists that stop updating in 2022, and broken links to papers that moved.

How Wire Fits

Wire's content pipeline maps to academic publishing workflows:

  • create: Generate research summary pages from paper abstracts, web research, and citations. Each page is a structured entry in your archive with full metadata.
  • Citation enforcement: Wire's styleguide requires inline citations with source URLs. Every claim traces back to a paper, dataset, or report. This is what academics already do in papers. Wire enforces it on the web.
  • crosslink: Wire connects related research pages automatically. Your work on "transformer architectures" links to your work on "attention mechanisms" without manual effort.
  • news: Wire monitors your research area for new publications, conference proceedings, and citations of your work. The refine command integrates developments.
  • llms.txt: AI assistants can consume your entire research archive. When someone asks an AI about your research area, your archive becomes a citable source.
  • JSON-LD: Article schema with author, date, and description. Google Scholar indexes structured pages.

What to Customize

wire.yml

Organize by research area or project:

nav:
  - index.md
  - Publications:
    - Overview: publications/index.md
  - Projects:
    - Overview: projects/index.md
  - Teaching:
    - Overview: teaching/index.md

Prompt Overrides

Write a _styleguide.md for academic tone:

  • Cite papers in author-year format with DOI links
  • Use precise technical terminology (Wire's style already requires this)
  • Cross-reference between your own publications when findings connect
  • Include methodology notes and dataset links

Components

Use :::stats for research metrics (publications, citations, h-index). Use :::tabs to organize publications by year or topic. Use :::cards for project overviews.

Scope

Wire generates a search index, RSS feed for new publications, sitemap for Google Scholar, JSON-LD Article schema, llms.txt for AI discoverability, and citation validation on every build. Your research is findable, citable, and machine-readable. For long-term preservation with stricter archival requirements, see the digital archive pattern.

Wire does not render LaTeX equations (use KaTeX via custom JavaScript or pre-render to images). Wire does not manage BibTeX files or integrate with Zotero directly. Export your bibliography as markdown pages. Wire does not handle peer review workflows.

To get started, create wire.yml with your research areas as topics, write publication summaries as markdown with DOI links in frontmatter, and run python -m wire.chief crosslink publications to connect related work. Run python -m wire.build --serve to preview, then deploy to GitHub Pages with your institution's subdomain. See all Wire use cases for more patterns.