Wikivoyage:Section headers

Wherever possible, section headers should be identical to the ones in the article skeleton. Don't add a "Restaurants" header to an article; make it "Eat" instead. Don't add "Introduction", but "Understand". The more consistent the sections of articles in Wikivoyage are, the easier it is for readers to find what they're looking for.


Wiki markup has a specific format for section headers. Section headers should start with two equal signs. If there are sub-sections of the sections, their headers start with three equal signs, and sub-sub-sections get four equal signs, etc.

For example,

==Section 1==

===Section 1.1===

===Section 1.2===

====Section 1.2.1====

Section headers should be separated from text in the preceding section by a blank line, as follows:

...and that's all you need to know.

The people of Frosnobish speak Frosnobian.


Section headers should follow the same rules of capitalization as article titles: capitalize the first word in the title, and any proper names. Everything else should be lower case.

Combining sections

When appropriate, two sections may be combined into one, such as See and do, or Eat and drink. The section name should still follow our standard conventions (e.g. "See and do" is acceptable, "Sights and sounds" is not). The word "and" should be what joins the two section names.

Combining sections should only be done when it makes sense to do so; for instance, in Walt Disney World/Magic Kingdom, the line between attractions and activities is a difficult distinction for this destination, hence the combination of the See and Do sections made sense for this article.

Dividing sections

For any but the smallest towns, Eat, Drink and Sleep are usually divided in a few subsections: by type, price, location or some other suitable criterion. This can be done also for sections that don't have any subsections listed in the template, and by criteria not listed there. See the relevant sections in Wikivoyage:Article skeleton templates/Sections and Wikivoyage:Listings#Avoid long lists.

Which section to use

See Where you can stick it.

See also