User:Steelpillow/test1

Engine infobox refactor
Merge all usages into Infobox engine.

Split off other data to spec templates. Maybe offer the specs as nested templates?

Already uses the politically correct header(n), label(n) and data(n).

Add image_size, alt, type parameters.
 * Infobox engine:

Discussion/consensus needed: Should image_border and/or long_caption also be added, for compatibility with Aircraft begin?

Engine infoboxes merge (draft)

 * What is needed is a TfD or two to clean out the messes, before going ahead with this TfM

The idea is to merge all these into a single template. Infobox engine is the obvious page title, so merging the others into it looks the way to go.

However several of these templates, including the destination one, include technical details which appear to go against the spirit of WP:INFOBOXPURPOSE, if not the letter. But that tech stuff should not be deleted or ignored, it needs to be moved to a better home. This should be done before the templates are merged. Templated in-article sections on the engine specification are used for aero engines, including pistonspecs, jetspecs, rocketspecs and electricspecs, so these might point a way forward, although the adopted solutions are not within scope of this RfM.

The purpose of this RfM is to reach a consensus on whether the merge is, in itself, to be proceeded with or not.

To summarise the infoboxes in scope (if there are more, I cannot find them):
 * Infobox engine. This is the natural destination, but currently almost entirely comprises technical information on piston engine types.
 * Infobox aircraft engine. Conforms well to WP:INFOBOXPURPOSE, but lacks header information which has to be supplied by Infobox aircraft begin.
 * Infobox aircraft begin. Comprises header information used for all aircraft-related infoboxes. However its use with other aircraft infoboxes has been deprecated and Infobox aircraft engine is the only one for which consensus to use it is still extant.
 * Infobox historic engine. Used for individual museum pieces, especially steam engines. Includes a modest amount of technical information which would need to be moved out. Also includes a module parameter intended to embed sub-templates, but it is not clear to me whether this is ever actually invoked.
 * Infobox rocket engine. Primarily intended for space rockets. Includes more technical parameters even than rocketspecs, so that anomaly needs to be ironed out.
 * Infobox Automobile engine. Redirects to Infobox engine, so needs no change. But the pages which transclude it will.

Step 1: Merge "begin" template into aero engines
Before getting started, wait for the clone/merge into Infobox aircraft to see how it deals with deprecated fields, e.g.:
 * image_border
 * size

Merge across non-deprecated fields from Infobox aircraft begin, which are missing in Infobox aircraft engine. These include the following, together with any of the above which may be kept:
 * name
 * image
 * image_size
 * alt
 * caption
 * long caption

Step 2: Add new fields to Infobox engine

 * 1) Engage at Template talk:Infobox engine to confirm merge in principle, and agree the fields to be merged.
 * 2) Add fields to Infobox engine and test.
 * 3) Go live.