Website Edit Handbook
This handbook explains how to edit Keigan websites when the usual maintainer is away.
It is written for complete beginners. Follow the steps in order the first time. After that, use the End-to-end checklist for each change.
Language
Use the English | 日本語 control in the top nav to switch languages. The full handbook is available in Japanese at /ja/.
Which sites does this cover?
| Site | Local folder (typical) | Bitbucket repo | What you edit |
|---|---|---|---|
| KeiganALI website | projects/keiganali-website | KeiganALI_Homepage | Markdown pages + microCMS news |
| KeiganALI Support Center | projects/keiganali_support_center | keiganali_support_center | Markdown docs pages |
| KeiganHAUVIL | projects/KeiganHAUVIL | hauvil_website | HTML / CSS / JS (Vite project) |
The safe workflow (always)
1. Get / update the project from Bitbucket
2. Create a new branch (contingency — easy to undo)
3. Edit content (yourself or with Cursor)
4. Preview with npm run dev (or the site-specific dev command)
5. Build with npm run build (or the site-specific build command)
6. Commit and push your branch
7. Upload the build output with FileZilla
→ staging first, then production after checkingFirst time? Follow this order
- What you will need — shopping list
- Install tools — Cursor, Node, Git, FileZilla
- Password vault — SharePoint download + Cursor setup
- Clone the repositories — Bitbucket +
.envshells - Then day-to-day editing and publish pages as needed
Passwords
Never store real passwords in this handbook.
Website passwords (SFTP, microCMS, .env keys) come from the Website password vault on SharePoint — 株式会社Keigan\Sales - ドキュメント\73Web・SNS\KeiganWEB管理 — not from Bitbucket.
Bitbucket is only for downloading and saving code. Sign in with your work email or Slack. If you cannot see the Keigan repos, ask to be invited to the workspace. Bitbucket login is separate from the password vault.