81:
108:
90:
63:
51:
137:
40:
44:
331:
133:
351:
320:
306:
289:
257:
243:
229:
208:
191:
149:
23:
17:
80:
297:- Although is it possible to get the headers on the same line, or at least the same indentation? It looks unfinished with them indented differently.
132:, but two were converted into aircraft carriers and served in World War II. The format is a little unusual, but I've based it on that used in
311:
I wish that it was possible to center them both the same as I agree that it would look better, but I don't believe that it can be done.--
278:
171:
66:
166:
should be linked separately in the links to the lead articles. Besides, those articles are linked in the first sentence of both
274:
167:
54:
107:
89:
316:
239:
145:
129:
24:
Knowledge (XXG):Featured topic candidates/Lexington-class battlecruiser & aircraft carrier/archive1
93:
111:
312:
302:
235:
141:
343:
253:
225:
183:
220:
having two headers. Pick which one is more notable and have the other one as a sub-article.
163:
282:
204:
298:
286:
159:
336:
249:
221:
176:
174:. The topic will remain on nomination until after some discussion is initiated.--
200:
128:-class battlecruisers laid down after World War I; four fell victim to the
234:
This is the exact same header style used for the
Courageous-class topic.--
199:. I've gone ahead and fixed the templates in the box.
328:
Closed with a consensus to promote to
Featured Topic.
34:
Lexington-class battlecruiser & aircraft carrier
158:As in the other topic you linked, I do not believe
18:Knowledge (XXG):Featured and good topic candidates
334:, the topic is passed with two lead articles.--
8:
330:And going along with the precedent set by
269:with two headers, or no objection to "
7:
62:
50:
124:This featured topic covers the six
31:
285:, which it almost certainly is.
172:Lexington-class aircraft carrier
106:
88:
79:
61:
49:
332:Courageous-class battlecruisers
134:Courageous-class battlecruisers
1:
168:Lexington-class battlecruiser
150:13:16, 1 September 2013 (UTC)
352:22:03, 27 October 2013 (UTC)
321:00:19, 21 October 2013 (UTC)
307:19:45, 19 October 2013 (UTC)
290:08:21, 15 October 2013 (UTC)
258:10:19, 12 October 2013 (UTC)
244:18:30, 11 October 2013 (UTC)
230:15:15, 11 October 2013 (UTC)
209:12:23, 5 October 2013 (UTC)
192:21:58, 2 October 2013 (UTC)
368:
136:. That nom had a lengthy
281:" if that's not overly
140:before its promotion.--
130:Washington Naval Treaty
70:-class aircraft carrier
248:Which I also opposed.
58:-class battlecruiser
22:(Redirected from
359:
350:
347:
340:
279:aircraft carrier
190:
187:
180:
164:aircraft carrier
156:Delegate Comment
110:
92:
83:
65:
64:
53:
52:
27:
367:
366:
362:
361:
360:
358:
357:
356:
345:
338:
335:
185:
178:
175:
122:
121:
120:
102:
84:
76:
75:
72:
47:
36:
29:
28:
21:
20:
12:
11:
5:
365:
363:
355:
354:
325:
324:
323:
292:
264:
263:
262:
261:
260:
211:
194:
119:
118:
103:
101:
100:
85:
78:
77:
73:
60:
48:
39:
38:
37:
35:
32:
30:
15:
14:
13:
10:
9:
6:
4:
3:
2:
364:
353:
349:
348:
342:
341:
333:
329:
326:
322:
318:
314:
313:Sturmvogel 66
310:
309:
308:
304:
300:
296:
293:
291:
288:
284:
280:
276:
275:battlecruiser
272:
268:
265:
259:
255:
251:
247:
246:
245:
241:
237:
236:Sturmvogel 66
233:
232:
231:
227:
223:
219:
215:
212:
210:
206:
202:
198:
195:
193:
189:
188:
182:
181:
173:
169:
165:
161:
160:battlecruiser
157:
154:
153:
152:
151:
147:
143:
142:Sturmvogel 66
139:
135:
131:
127:
117:
115:
109:
105:
104:
99:
97:
91:
87:
86:
82:
71:
69:
59:
57:
46:
42:
33:
25:
19:
344:
337:
327:
294:
270:
266:
217:
213:
196:
184:
177:
155:
125:
123:
113:
95:
67:
55:
138:discussion
74:4 articles
271:Lexington
201:Parsecboy
126:Lexington
96:Lexington
68:Lexington
56:Lexington
299:Miyagawa
114:Saratoga
295:Support
273:-class
267:Support
250:Nergaal
222:Nergaal
216:topic,
214:Support
197:Support
45:discuss
218:oppose
116:(CV-3)
98:(CV-2)
16:<
317:talk
303:talk
283:eggy
277:and
254:talk
240:talk
226:talk
205:talk
170:and
162:and
146:talk
112:USS
94:USS
41:edit
319:)
305:)
287:Ed
256:)
242:)
228:)
207:)
148:)
43:|
346:八
339:十
315:(
301:(
252:(
238:(
224:(
203:(
186:八
179:十
144:(
26:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
