Publishing Guidelines

Internal reference for authors and assistants working on DeveloperNote.com. Consult this page before creating or publishing a post. These rules record the owner’s preferences; task-specific instructions from the owner take precedence.

Language

Public posts must always be written in English.

Private posts and pages may use different languages depending on their purpose. Internal documentation may be written in Russian when the owner requests it. The owner will specify the intended language or purpose; do not assume that every private entry must be in English.

Editor and code blocks

Structure posts with Gutenberg blocks, including paragraph, heading, and code blocks as appropriate.

Use the installed SyntaxHighlighter plugin’s blocks for commands, source code, and terminal output. Select an explicit, appropriate highlighting language.

Never use Plain Text mode in SyntaxHighlighter blocks, and never leave the language unset so that it defaults to Plain Text. The owner reports that Plain Text mode does not work correctly on this blog. For terminal output, select a suitable supported language, such as Bash for shell sessions.

Read More break

Add a More block after the introduction when appropriate, so listing pages show a useful excerpt before the “Read More” link.

Categories and tags

Choose a relevant existing category and add relevant tags. Reuse existing terms where possible.

For the SSH Git cloning article, the chosen category was Ubuntu and the existing tag was git. This is an example for that article, rather than a default category and tag for every post.

How to use this reference

Keep this page private. It is editorial documentation, rather than a public blog article. When starting future blog work, find this page by its title, “Blog Publishing Guidelines”, and read the current rules through authenticated WordPress access.