Leave what you know for the next KAMITSUBAKI fan.

Read the relevant paragraph in an artist, song, album, project or event article. Describe your proposed change in one sentence.

A typo, an official link or a sourced date is a good first contribution. A complete rewrite or a synchronized lyric timeline can wait. Replacing “recently released” with a confirmed release date needs the actual announcement; a punctuation fix does not need an unrelated citation.

If you have no article in mind, browse the song directory. You can also report a specific problem through Issues at the bottom of this page.

1. Select Edit source on an article. This guide will show its file path above.
2. Choose Open visual editor to load supported article types. If there is an existing draft, back it up before agreeing to replace it.
3. Alternatively, choose Edit existing article in the editor, search by title or path, then Load original.
4. Check the title, content and language: zh.md, ja.md and en.md mean Simplified Chinese, Japanese and English.

If loading fails, retry or get the complete Raw file from GitHub. Import source accepts pasted source or a .md file up to 1 MB. Include the information between both --- lines.

Guides, announcements and homepage copy are outside the editor’s five supported collections. Use the GitHub link for those files.

Click a paragraph and type. Body headings start at level 2; the page title has its own field.

Your goal	Control
Bold, italic or a link	Select text and use the top or floating toolbar
Highlight, ruby or a spoiler	Use the corresponding toolbar item and fill any requested details
Heading, list, image or table	Press / in an empty paragraph, or choose Insert content
Adjust a block	Select it and open its Properties
Reorder content	Use the block’s move up/down controls or drag handle
Find text or a chapter	Use Find in document or Outline
Change title, date or other details	Article details in the left Properties panel

Try adding a source: select the words “official announcement”, choose Add link, enter the real URL and apply it. Check the result in Preview.

A Preserved source block contains complex markup. Keep it unless you need to edit that section. Use Source and the syntax reference for a narrow change; fix any YAML parsing error before returning to Visual. Do not delete unknown details to dismiss an error.

Use official work pages, announcements, published interviews or publications for dates, credits and event details. Link the specific page supporting the nearby sentence, not just a homepage.

Keep opinions attributed: “I love this song” does not support “critically acclaimed.” Search snippets, AI answers and fan speculation are not substitutes for sources.

• Check names and dates against the source.
• Check image sources and permission, and preserve existing license fields. An image URL in the editor does not upload an image file.
• Preserve the original, translator credits and attribution for quotes, translations and lyrics.
• Leave uncertain facts out and explain missing evidence in the PR.

AI may help clarify writing, organize sources you supply or explain an error. You still need to verify each claim; do not ask it to invent credits, interpretations or lyric timings.

1. Read Preview from beginning to end. Check headings, links, captions, tables and disclosures. On smaller screens, use the bottom Preview control.
2. Open Before you export and complete required fields. Field validation cannot determine factual accuracy.
3. Check the autosave status. A draft saved in this browser is not synced to other devices; download important work.
4. Choose Export Markdown → Copy complete Markdown or Download .md. The export includes the article details at the top.
5. With a valid path, the same menu provides Open file location on GitHub. Paste the complete file into the correct editor, preserving its metadata.

Review Preview / Changes or the diff on GitHub. GitHub may not render this site’s ruby, media or lyric syntax; use the site preview for those and let the build checks verify the final file.

You can download an unfinished draft and return later. Do not invent required information just to clear a warning.

New to GitHub? Create an account and verify your email when you are ready to submit. A free account is sufficient for public contributions; you can practice in the editor first.

1. Without write access, GitHub guides you to a Fork, a copy under your account.
2. Paste and inspect the change, then choose Commit changes… / Propose changes. Write a short description of the actual edit. A Commit is a saved change, not the PR itself.
3. Continue to Compare & pull request / Create pull request. The base repository should be LinkTh1rsty/kamitsubaki-wiki-site, using the development branch currently designated by the maintainers; the comparison comes from your edited branch.
4. Add a clear title and describe changes, sources and checks with the template below. Create the PR. A numbered Pull Request page confirms it has been submitted.

Checks run automatically. Wait while they run; open the error details if they fail. Passing checks still leaves human review. If a reviewer requests changes, edit the same branch in your Fork and Commit again; the existing PR updates automatically.

Merge adds the change to the main branch; the live site still needs a successful deployment. PRs and commits retain contribution history, while on-site contributor information may update later.

Button wording may change. See GitHub’s web editing guide and PRs from a Fork.