スタイルガイド

Symbol がオープンソースプロジェクトとして成長するにつれ、より多くの開発者がプラットフォームに関する迅速で効率的な教育を提供するためにドキュメンテーションに頼るようになるでしょう。したがって Symbol Developer Documentation デベロッパーセンターの多数の記事に渡って高いレベルの結束が達成されることが不可欠です。次項のスタイルガイドは Symbol テクニカルライティングチームによる、執筆の一貫性と質を向上させるためのガイドラインを提供しています。

入門

ライティングを始める前に理解しておくべきことがあります:

  1. Determine purpose and use

    あなたの記事の目的を定めることは、あなたの執筆プロセスの最初のステップであるべきです。読者が読み終わったときに何を知って欲しいかを明確にすることです。目的を定義することは、各ステップを執筆する上であなたの助けになるでしょう。

  2. Identify the audience and their need

    Keep in mind that the documentation will be mostly read by curious or contributing developers and system integrators, who we should assume to have at least an elementary level of technical knowledge. Determine what information, and how much detail, the readers need to achieve the purpose of your article.

  3. Organize the information

    読者に必要な情報が決まったら、情報を論理的に整理して最良の流れと理解を得ます。

これで書き始める準備が整いました!プロジェクトをダウンロードしてドキュメントを提出する方法を学ぶために page を確認してください。

ツール

Sphinx: Sphinx is the documentation generator we use to facilitate writing documentation. Its features (extensive cross-references, hierarchical structure, automatic indices, etc) and range of languages make it a useful tool for our purposes.

reStructuredText: Sphinx uses reStructuredText as its markup syntax. reStructuredText is a straightforward yet powerful system that is a major strength of using Sphinx. You can refer to the reStructuredText cheat-sheet for the basics.

GitHub: GitHub is the hosting service we use for our documentation. To commit your contributions, you will need to be familiar with the platform. Beginners can start learning by reading this introduction to Git.

Transifex: Transifex is the collaborative localization platform we use to translate our documentation to various languages. Follow our guide to start contributing to the translations.

記述パターン

While it is unreasonable to expect all of the many writers on the technical writing team to have an identical writing style, we can attempt to have a consistent voice that resonates with the readers by maintaining a similar writing pattern. Keep in mind these basic rules as you write.

語調

する

しない

アメリカ英語の使用

Use UK Spelling/grammar: "colo**u**r".

Be friendly, maintaining a professionalism.

Use too much contractions, slang, colloquialism, buzz words, excessive exclamation marks.

Use active voice & present tense by default.

受動的な口語の使用

Address the reader as "you" by default. Use "we" as the default pronoun in your article unless you are referring to a personal recommendation.

Use “you” to describe an action the user has to do.

Write documentation for an international audience, with diversity and inclusivity in mind.

Include culturally or politically controversial ideas or examples.

簡潔に

Use long sentences or filler words in excess ("simply", "really", "just", "please").

基本フォーマット

Maintaining a uniform format is also essential for consistency.

Case

新しい語彙または重要な語彙を定義する。

Private Key is a random 256-integer.

重要な違いを強調する。

If valid, the harvester stores the transaction in a block, and it reaches the confirmed status.

テーブルのヘッダを書く。

This table.

Writing titles.

Basic formatting (first letter capitalized).

Writing numbers

1,000.5. Use the period (full stop) as the decimal separator.

Referencing variable values, functions, file names, mosaic ids, addresses or urls.

Symbol has a rewrite limit of 360 blocks. Once a transaction has more than 360 confirmations, it cannot be reversed.

Warning the reader.

Use notes. Example

Providing helpful hyperlinks throughout your article.

transfer transactions are used to send mosaics between two accounts.

Explaining a difficult concept with many steps.

Break information and actions into bulleted or numbered lists when possible.

コードスニペット

Common practices to include code snippets in a document.

Case

Bash コマンドのドキュメント化

Do not add $> before bash commands: symbol-cli account info.

コードスニペットの使用

Import them from a file using the .. viewsource:: directive. Example

Displaying a subset of the code

Use the comments /* start block 01*/ and /* end block 01 */ to divide code blocks. Example

If you are writing a guide, you might find helpful this guideline.

Terms

頻繁に表記ゆれの傾向がある用語のリスト。

Correct

Incorrect

API

Api, Api

blockchain

block chain

Catapult

catapult, NEM Catapult

CLI

cli, Cli

GitHub, github, Github

id

ID

JavaScript

Javascript, javascript

MongoDB

mongodb, Mongodb

NEM

Nem, nem

Node.js

nodejs, node.js

RxJS

rxjs

SDK

Sdk, Sdk

SHA-256

SHA256, Sha-256

Smart Asset System

Smart asset system

Symbol

symbol, NEM Symbol

TransferTransaction

Transfer Transaction, transfer transaction

TypeScript

typescript, Typescript

Whitepaper

WhitePaper