24:
245:
Sometimes, images can contribute to whitespace. But the size of images can be controlled, so if an image is causing there to be a lot of whitespace, it may be worth reducing the size of the image, even just a little, in order to fill more of that space with text (depending on display width). Beware,
236:
or similar horizontal template at the bottom, and the amount of text on the page takes up far less space than the template to the left. Even without a horizontal template, there may still be a lot of whitespace to the left of the template between the final line of text and the category box at the
76:
listing the headings is automatically generated. When this occurs, the table of contents box will appear on the left side of the page between the lead section and the first heading. There will be no text to the right of the table of contents, though an image or a vertical template, such as an
327:
Avoid "fixing" white space issues which are peculiar to your combination of screen, window, and font sizes, your choice of browser, your image settings, and so on. Check with other settings or systems, or ask other editors to check them for you.
81:, will appear in the space to the right if formatting causes it to require that space. Still, no text will appear in the space in between; it'll be white (as you notice, there is some white space between the TOC box and the image above).
214:
In an automatically generated table of contents, there will be one listing per line. But in a self-produced table of contents, multiple listings can be condensed into one line, as much as space allows, using the line break (<br /:
58:
Whitespace is not always desirable. It can give the page an untidy appearance and make the article look incomplete. But it cannot always be avoided, and there are times when it may actually come in handy when added in small amounts.
216:) text to mark the end of a line. The drawback to this is that you will have to manually add, remove, or modify headings as they are edited on the page. Still, it'll reduce the amount of whitespace on the page.
52:
is blank space that appears on the published version of a
Knowledge page in any namespace. It is not occupied by any characters, templates, multimedia, or anything else. In other words, it appears
315:
Sometimes, a minor fix will help eliminate or reduce whitespace. This may involve adding or removing one blank line from some part of the page, re-ordering templates, or the use of a
249:
On a short page, a single image may be to blame for whitespace. If the height of the image is greater than that of the text, there will be some whitespace at the bottom.
331:
Avoid "fixes" which break the appearance of the page on mobile devices. Again, if you do not have a suitable device on which to check, other editors can advise you.
275:
Many infoboxes take an image, so if an image is placed there, it'll add more height that may benefit from balancing with text and other left-justified content.
27:
The
Knowledge article shown here is a stub. It has a minimal amount of text along with an infobox and a navbox. The remainder of the page is blank.
16:
This page is about the appearance of blank space on an article. For the Manual of Style section on using line breaks in an article, see
312:
Sometimes, when you have undesirable whitespace, the best way to solve the problem is to expand the article (with suitable content).
100:
at the top of the page will produce a table of contents to the left or right that does share its lines with some text. The
252:
On a longer page divided by multiple headings, it may be desirable to provide a small amount of whitespace by using the
340:
260:
family of templates so the image does not protrude into the next paragraph or section. Using several blank lines,
319:
for multiple images. If an embedded list creates white space, using two or more columns may solve the problem.
272:
will not work correctly for all display widths, and surplus blank lines are removed by a number of processes.
355:
104:
__NOTOC__ will cause the table of contents to be altogether absent, which for some pages may be necessary.
302:
The beginning of a paragraph ... ... the end of a paragraph. <!-- but doing it this way is fine --: -->
307:
303:
The beginning of a paragraph ... ... the end of a paragraph.<!-- and so is doing it like this --: -->
290:
can contribute to whitespace. Format the comment to avoid this, by ensuring either that the initial
278:
67:
84:
There are various ways to modify the appearing of the table of contents. Entering the templates
8:
40:
95:
32:
316:
229:
87:
78:
301:... the end of a paragraph. <!-- Don't use hidden comments in this manner --: -->
283:
233:
101:
62:
219:
267:
255:
225:
17:
349:
73:
240:
224:
Whitespace cannot easily be avoided when a page with little text, often a
107:
It is also possible to produce your own table of contents as follows:
246:
though, of making one image significantly narrower than all others.
232:
or similar vertical template that is quite tall along with a
23:
294:
touches the text immediately beforehand, or that the final
334:
322:
347:
298:touches the text immediately afterwards:
22:
348:
72:On pages with multiple headings, a
13:
14:
367:
341:Category:Inline spacing templates
304:The beginning of a paragraph ...
308:Addressing the whitespace issue
1:
7:
10:
372:
30:
15:
286:in the wikicode added by
111:
288:<!-- Comment --: -->
28:
26:
63:Causes of whitespace
356:Knowledge page help
279:Invisible comments
29:
147:{{MediaWiki:Toc}}
74:table of contents
68:Table of contents
363:
297:
293:
289:
271:
263:
259:
209:
205:
202:
199:
196:
193:
190:
187:
184:
181:
178:
175:
172:
169:
166:
163:
160:
157:
154:
151:
148:
145:
142:
139:
136:
133:
130:
127:
124:
121:
118:
115:
99:
91:
43:
371:
370:
366:
365:
364:
362:
361:
360:
346:
345:
337:
325:
310:
305:
295:
291:
287:
281:
265:
261:
253:
243:
222:
211:
210:
207:
203:
200:
197:
194:
191:
188:
185:
182:
179:
176:
173:
170:
167:
164:
161:
158:
155:
152:
149:
146:
143:
140:
137:
134:
131:
128:
125:
122:
119:
116:
113:
93:
85:
70:
65:
47:
46:
39:
35:
21:
12:
11:
5:
369:
359:
358:
344:
343:
336:
333:
324:
321:
309:
306:
300:
280:
277:
242:
239:
228:, contains an
221:
218:
212:
112:
110:
108:
69:
66:
64:
61:
45:
44:
36:
31:
18:MOS:LINEBREAKS
9:
6:
4:
3:
2:
368:
357:
354:
353:
351:
342:
339:
338:
332:
329:
320:
318:
313:
299:
285:
276:
273:
269:
262:<br /: -->
257:
250:
247:
238:
235:
231:
227:
217:
109:
105:
103:
97:
89:
82:
80:
75:
60:
56:
55:
51:
42:
38:
37:
34:
25:
19:
330:
326:
314:
311:
282:
274:
251:
248:
244:
223:
213:
106:
83:
71:
57:
53:
49:
48:
206:__NOTOC__
141:"Contents"
102:magic word
50:Whitespace
220:Templates
96:TOC right
350:Category
335:See also
284:Comments
264:tags or
237:bottom.
88:TOC left
41:WP:WHITE
33:Shortcut
323:Caveats
317:gallery
230:infobox
135:summary
79:infobox
241:Images
234:navbox
54:white.
296:: -->
268:Break
256:Clear
132:"toc"
126:class
123:"toc"
292:<
226:stub
215:-->
92:or
352::
270:}}
266:{{
258:}}
254:{{
208:|}
201:}}
195:{{
189:}}
183:{{
174:}}
168:{{
162:}}
156:{{
153:|]
150:|-
117:id
114:{|
98:}}
94:{{
90:}}
86:{{
204:]
198:·
192:]
186:·
180:]
177:]
171:·
165:]
159:·
144:!
138:=
129:=
120:=
20:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
