🔥firejune.io /📘Notes/
📖Content Authoring Manual
AboutContact
📖

Content Authoring Manual

English reference for writing and maintaining firejune.io content in Notion.
Required marks steps needed for the page to display as intended. Recommended marks conventions for clear, consistent writing.

1. Choose the page structure

Content
Structure
A translated Writing post
Two database pages, one with Language = en, one with Language = ko.
A bilingual general page, such as About or Contact
Korean blocks, a standalone [EN] marker, then English blocks.
A single-language reference page
One page without a language divider.
Keep the Notion page title in the title property. For Writing posts, use Name; use Description for the short summary shown outside the article.

2. Headings

Use real heading blocks

Required for the outline: use Notion Heading blocks. A bold paragraph only looks like a heading; it does not become an outline entry.
Use the page title for the article title, then organize the body with Notion headings:
Notion editor
Recommended use
Page title
Article or page title
Heading 1
Main section
Heading 2
Subsection
Heading 3
Detail within a subsection
Recommended: start a new article's main sections with Notion Heading 1, then nest Heading 2 and Heading 3 by meaning. Do not choose a heading level just to make text larger or smaller. Do not repeat the page title as the first body heading.
Existing pages use both Heading 1/2 structures and Heading 2-only bodies. Preserve a coherent existing hierarchy when making a small edit.

Write headings that work in the outline

  • Name the subject or action clearly. A reader should understand the article's structure by scanning its headings.
  • Use consistent capitalization within the page. Sentence case is a useful default for new English section headings.
  • Keep heading text in the page's language. Leave product names, API names, and code identifiers unchanged.
  • Avoid empty headings or headings used only as visual spacers.
Keep essential section headings in the main page flow and check the outline on the site. Do not add unnecessary headings just to make an outline appear.

3. Korean and English

Writing posts: separate pages

Required:
  1. Create one page per language in the same collection.
  1. Set the Language select explicitly to en or ko.
  1. Set both versions to the exact same Published start-date value, including the time if one is set.
  1. Check the language switch on the site before treating the pair as complete.
The two versions may have different titles. Keep them in the same collection, use the appropriate language setting, and give them matching publication dates.
If several posts share a publication date, double-check that the language switch opens the right article. Keep the real publication date; ask for help if the counterpart is incorrect.
Localize the title and Description as well as the body. Keep factual dates, numbers, source links, and code examples aligned across versions.
Set the language explicitly rather than relying on a default. Check both language views after adding or updating a translation.

General pages: the [EN] divider

Use this structure in the Notion editor:
Korean content

[EN]

English content
Required: put [EN] once, in its own block in the main page flow. Use that exact spelling. Do not put it inside a sentence, column, or nested list.
Keep each language's prose together. On pages with shared databases or a footer, check that these appear correctly in both language views. Do not mix this divider structure with the separate-page convention for translated Writing posts.

Writing and translation conventions

Use these conventions when drafting or translating.
  • Write natural prose in each language. Preserve meaning and certainty rather than copying sentence order.
  • Keep a consistent voice within an article. Existing Korean pages do not establish one mandatory speech level for the entire site.
  • Preserve names, technical identifiers, command syntax, paths, and quoted source text unless an explanation requires a translation.
  • Translate image captions and meaningful alt descriptions too. A translated body with captions left in the other language is unfinished.
  • When a source-language correction changes a fact, update its counterpart. Do not silently add a stronger claim to one version.
  • Use the matching language version for internal article links when one exists.

4. Light and dark images

Tag the target theme in Alt text

Required: put #light or #dark in the image's actual Alt text field. The tag describes the website theme in which that asset should appear.
  • #light: image for light mode, often a dark-colored logo.
  • #dark: image for dark mode, often a white or light-colored logo.
  • #white is not a supported tag. “White” describes the artwork, not the theme name.
Keep a meaningful description alongside the tag:
Steam logo #light
Steam logo #dark
The Korean form Steam 로고 #light follows the same convention. A prefix such as #light Steam logo also works. Use lowercase tags consistently and exactly one tag per image. Keep the tag separated from ordinary words.

Keep the two image blocks adjacent

  1. Add the light-mode and dark-mode versions as two consecutive image blocks under the same parent.
  1. Give one image #light and the other #dark.
  1. Do not insert a paragraph, blank block, divider, or other block between them.
  1. Keep both assets at matching dimensions and composition so switching themes does not move the content.
Use light first, dark second in new content. Keep the same size and alignment for both. On the website, the pair should appear as one image that changes with the theme.

Captions, links, and missing partners

  • Put one shared caption on the first image. Write it so that it makes sense in both themes.
  • If the images have hyperlinks, use matching destinations on both and test the link in each theme.
  • Supply a meaningful alt description on both images.
  • An untagged image appears in both themes. Use one image when it works well in both.
  • Include both versions when an image needs to appear in both themes. A tagged image on its own is visible only in its designated theme.
  • Check that both uploaded images load and remain readable.

5. Before publishing

The title and summary match the page's language.
Section labels are real Notion headings with a coherent hierarchy.
The website outline contains the expected headings.
Both translated versions have explicit language values and the same Published start date.
The language switch opens the intended counterpart in both directions.
Titles, descriptions, captions, alt descriptions, facts, and links are localized or intentionally shared.
Each theme-specific image has exactly one theme tag in Alt text.
Image pairs are adjacent under the same parent and appear only once on the website.
Both light and dark mode show the correct asset with readable contrast.
The collection page's Public setting is correct.

Reference

Examples