aphid 0.1.3

aphid 0.1.3 is about getting started faster. Instead of creating directories and files by hand, a single command now scaffolds a complete site or adds a new content file with the right frontmatter already in place.

Site scaffolding

Two new commands set up a fresh aphid site from scratch:

aphid new my-blog     # create my-blog/ with everything inside
aphid init            # scaffold in the current directory
aphid init path/to    # scaffold in a specific directory

Both generate a minimal but buildable site: aphid.toml with a title derived from the directory name, a .gitignore for /dist, a starter blog post, a “Getting Started” wiki page, an about page, a home page, and an empty static/ directory. The site is built immediately after scaffolding, so dist/ is ready to serve:

aphid new my-blog
cd my-blog
aphid serve

aphid new fails if the target directory already exists; aphid init fails if the directory already contains an aphid.toml. Both are intentional guard rails — no silent overwrites.

Content creation

Once a site exists, three commands create new content files with valid frontmatter:

aphid blog new "My First Post"
aphid wiki new "Architecture Overview"
aphid page new "Contact"

Each derives the filename slug from the title ("My First Post" → my-first-post). Blog posts are prefixed with today’s date and get the full blog frontmatter (title, slug, author, created, description, tags). Wiki and standalone pages get lighter frontmatter matching their respective types. All three commands check for an existing aphid.toml via the --config flag and write into the configured source_dir.

If a file with the same slug already exists the command fails rather than overwriting — rename or delete the existing file first.

Upgrading

cargo install aphid --locked --force
aphid --version

There are no breaking changes from 0.1.2. The new commands are purely additive — existing sites and workflows are unaffected.