For your convenience in contributing to the CircuitLab community, many fields accept a flavor of markup which allows you to contribute rich content including links, images, and more. This applies on the forums, as well as in circuit descriptions and comments.

The supported markup includes a subset of BBCode as well as Markdown.

Here are some examples:

Paragraphs

Use two enters (one completely blank line) to denote a new paragraph.

If you don't, your sentences will run together. Like this, with only one "enter" pressed between these two sentences.

Use two enters (one completely blank line) to denote a new paragraph.

If you don't, your sentences will run together.
Like this, with only one "enter" pressed between these two sentences.


Bold and italics

This must be important or surely you'd miss it.

Markdown-style syntax is also supported for your convenience.

This must be [b]important[/b] or [i]surely[/i] you'd miss it.

Markdown-style syntax is **also** supported for *your* convenience.


Links can be specified explicitly or implicitly. For example:

Learn electronics with educational electronics kits. Also see the videos at http://www.nerdkits.com/videos/

[url=http://www.nerdkits.com/]Learn electronics[/url] with educational
electronics kits.  Also see the videos at http://www.nerdkits.com/videos/

are also supported.


Equations

Nicely-formatted mathematical equations can be specified using LaTeX-style formats.

Inline equations can be specified by surrounding them with a single dollar sign, like this one: $V_x (t) - V_y (t) = 5 \times cos( 60 \pi t )$.

Inline equations can be specified by surrounding them with a single
dollar sign, like this one: $V_x (t) - V_y (t) = 5 \times cos( 60 \pi t )$.


Standalone equations can be specified by surrounding them with a double dollar sign, like this one:

$$I_A = \frac{V_{R_1}}{470 \Omega}$$

$$I_A = \frac{V_{R_1}}{470 \Omega}$$


For more examples of supported equation formatting, see this tutorial.

You can link to a CircuitLab circuit using this simple notation, like this:

[circuitlab]7f3wae[/circuitlab]


This gets a screenshot and links directly to open the CircuitLab Editor in a new tab:

Usernames prefixed with the "@" character (at sign) become links to that CircuitLab user, as is common in contemporary usage of that character. For example:

That's a beautiful circuit, @mrobbins! or

@mrobbins, are you concerned about reverse leakage through diode D1?

That's a beautiful circuit, @mrobbins!  [i]or[/i]

@mrobbins, are you concerned about reverse leakage through diode D1?


Subscript and superscript

Since we're often talking about equations, which can have subscripts or exponents, we need a way to include these in our formatting. Try the sup (superscript) or sub (subscript) BBCode-style tags:

VR1 = 5.321 * 10-3 volts

ID = IS * e VD / (N*Vth)

V[sub]R1[/sub] = 5.321 * 10[sup]-3[/sup] volts

I[sub]D[/sub] = I[sub]S[/sub] * e [sup] V[sub]D[/sub] / (N*V[sub]th[/sub]) [/sup]


Images

Images can be included like this:

[img]http://www.nerdkits.com/videos/robotic_xylophone/coil_closeup_t.jpg[/img]


and images can be used for links like this:

[url=http://www.nerdkits.com/videos/robotic_xylophone/][img]http://www.nerdkits.com/videos/robotic_xylophone/coil_closeup_t.jpg[/img][/url]


If you include images in your post, please keep the CircuitLab Terms of Service in mind. Be sure that the images you include are both appropriate and you have appropriate permission to include them in your comment or post.

Code Blocks

If you want to include symbols without having them be interpreted as markup, consider using inline code backticks like this: 5*V(in)*I(R1.nA).

If you want to include symbols without having them be interpreted as markup, consider using inline code backticks like this: 5*V(in)*I(R1.nA).


The backticks protect the contents from being interpreted as, for example, bold or italics.

Furthermore, if you want a multi-line section of unformatted text, simply add four spaces to the beginning of every line:

Regular text #1 with special symbols and a second line which gets collapsed into the first

Code-formatted text, *with special symbols*
and a second line which stays separate


Regular text #2

And the markup that generated the three previous paragraphs:

Regular text #1 *with special symbols*
and a second line which gets collapsed into the first

Code-formatted text, *with special symbols*
and a second line which stays separate

Regular text #2