Skip to content
ddakit

Get the base and install

The goal of this step is simple: get blog-studio onto your computer and install the Python packages the publish script uses. Usually done within 10 minutes.

1) Get the base

Section titled “1) Get the base”

If you have a license and Template access, use “Use this template” on GitHub to make your own repository, then clone it. Otherwise, get it directly with git clone.

Terminal window
cd ~/projects
git clone https://github.com/ddakit/blog-studio.git my-blog
cd my-blog

If the ~/projects folder doesn’t exist, run mkdir -p ~/projects first. You can rename my-blog to whatever you like.

Normal screen: a line starting with “Cloning into ‘my-blog’…” shows, and after a moment the prompt returns.

Stuck screen:

  • “command not found: git” → git isn’t installed. Go back to the git item in prerequisites.
  • “Permission denied” or an auth request → if it’s a private repository, you need to be logged into GitHub. Using your own repository URL made via Template is cleaner.

2) Step into the folder you got

Section titled “2) Step into the folder you got”
Terminal window
cd my-blog
ls

If you see names like AI_AUTOMATION.md, CLAUDE.md, scripts/, and .claude/, you got it right.

3) Install the publish-script dependencies

Section titled “3) Install the publish-script dependencies”

Install the Python packages the Blogger publish script uses.

Terminal window
pip install -r scripts/requirements.txt

Or use pip3 if pip points at Python 2 in your environment.

Normal screen: the packages download and a line like “Successfully installed …” shows at the end.

Stuck screen:

  • “command not found: pip” → retry with pip3 install -r scripts/requirements.txt. If that still fails, check that python3-pip was installed in the Python item of prerequisites.
  • On a permission error, install into the user area with pip install --user -r scripts/requirements.txt.

4) first-run handles git history separation

Section titled “4) first-run handles git history separation”

When you get the base with git clone, the base’s commit history comes along. It’s cleaner to cut the history before your own work commits pile on top, but that spot is something the next step’s /start detects automatically and asks about once. No need to do it by hand now.

Next

Section titled “Next”

Once you’ve got it and installed it, go to first-run. You verify the environment with /start and capture the blog identity.