// Tutorial //

How To Format DigitalOcean Articles For Publication

Published on May 23, 2014
Default avatar
By Sharon Campbell
Developer and author at DigitalOcean.
How To Format DigitalOcean Articles For Publication

Thank you for your interest in writing for DigitalOcean! Our style and formatting guides have moved; we apologize for the inconvenience.

Here’s a link to the latest version of the style guide. The short links do.co/style and do.co/formatting will also always point to the correct page. Happy writing!

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in our Questions & Answers section, find tutorials and tools that will help you grow as a developer and scale your project or business, and subscribe to topics of interest.

Sign up
About the authors
Default avatar
Developer and author at DigitalOcean.

Still looking for an answer?

Was this helpful?

Hey, could you please share stencils you are used in your diagrams as well?

Is there any preview tool for write up before submitting a tutorial ??

I plan to write one, but since never used the DO write up formatting, hence wanted to preview the sample before submitting !!

So is there anyway to preview the write to see how it looks ??

Your documentation has such a great look and feel. The writing and UX meld perfectly. Can you share what tools you are using to generate the Markdown into this lovely page?

@vanting: Unfortunately, Markdown support hasn’t reached the comments and answers just yet. It should hopefully be coming very soon though! In the mean time, you can use pre tags. I’ll go use my super powers to fix up the formatting on your answer.

What about emphasis for commands? I’m not sure if I should use word or word on a paragraph when referring a command of a file system path within a paragraph.

My current convention is to use word for commands and word for words that may need emphasis.

I’ve gone ahead and updated this article. That’s for catching that. :)

The “Command and Output” section is not clear. The “command” block is empty and the paragrafph after is incomplete.