Call the same grow-light product a “lamp,” a “bulb,” and a “complete lighting system,” and readers may not know what comes in the box. A content style guide settles those choices. It gives writers shared rules for equipment terms, units, claims, tone, and formatting without making every post sound alike.
For a small grow-equipment publication, a few working pages with examples from real posts are more useful than a long manual nobody checks. Start with choices that affect a grower’s understanding or safety. Capitalization can wait.
Define the reader and the limits of advice
Say who each post is for: a home grower choosing a shelf fixture, a farm worker checking greenhouse equipment, or an operator planning a larger installation. The level of detail will change, but selection advice still needs context. Crop, growing area, available daylight, mounting height, climate, and electrical supply can all affect a recommendation. Ask writers to name the conditions that matter before suggesting equipment.
Draw a clear line between explaining a product and designing an installation. A post can explain why humidity matters when choosing a fixture enclosure; a product label alone does not establish that the fixture is suitable for every damp location. Leave electrical installation, structural mounting, and other hazardous work to qualified specialists working under applicable regulations and approved procedures. Keep this rule in the guide so it does not disappear when contributors change.
Agree on equipment terms before polishing prose
Build a short glossary from terms that cause confusion in drafts, product listings, and reader inquiries. For each entry, give the preferred term, its meaning, and any acceptable alternative. Preserve distinctions that could change a purchase decision:
- Fixture or luminaire: the assembled lighting unit. Do not call an integrated LED fixture a “bulb.”
- Lamp: a replaceable light source, where that distinction applies. Say whether a ballast or fixture is sold separately.
- Driver and ballast: name the component used by the equipment in question; the terms are not interchangeable.
- Grow tent, cabinet, and grow room: name the space described rather than calling every enclosure a “grow room.”
Allow product names to appear as the manufacturer prints them, but use the glossary in the explanation. If a supplier calls an integrated fixture a “lamp,” use the official name once, then make clear what the product contains. Search terms should not obscure what a buyer receives.

Standardize measurements and comparisons
Specify how writers present area, power, light measurements, and time. A guide might call for watts when stating electrical input, a consistent choice of square metres or square feet for coverage, and a named measurement plane when discussing light at canopy level. If readers work in different regions, choose a primary unit and add conversions where they help.
Do not let wattage stand in for evidence that one fixture suits a crop better than another. Measured area, mounting position, light distribution, operating conditions, and the manufacturer’s test method all affect the meaning of a specification. Spell out photosynthetic photon flux or photosynthetic photon flux density on first use, and distinguish total fixture output from light received at a surface. If test conditions are missing, say so rather than treating the figures as directly comparable.
This is a rule for expressing claims, not a demand to compare products in every post. An explanation of one feature may need only a measurement and its context. A buying guide may need more detail about test conditions; the method in comparing grow lights for a specific growing space fits that task.
Set a voice that matches the evidence
“Use a friendly tone” gives an editor little to work with. Show writers sentences that make a useful claim without overselling it. “Check whether the fixture’s rated environment matches the greenhouse location” tells readers what to check; “This fixture is perfect for every greenhouse” does not. Likewise, “The manufacturer reports this value under these conditions” identifies the source of a performance figure.
Tell writers how to handle uncertainty. Separate manufacturer specifications, independent measurements, and rules of thumb. Daylight, crop stage, irrigation, temperature, and fixture placement can affect a grower’s results, but mention only the variables relevant to the claim. Do not scatter “may” through a draft instead of checking the evidence. When the evidence supports a firm statement, use one.
Set rules for promotional language even if the publication does not sell products. “Best,” “guaranteed,” and “maintenance-free” need support that a short product description may not provide. Describe the feature and its practical effect instead: “The replaceable driver can simplify service where spare parts are available” says more than “built for worry-free operation.”
Make formatting rules serve the task
Choose a few patterns for information that recurs. A fixture description could name the intended space, say what is included, and then give the specifications relevant to installation or use. A greenhouse controls post could separate sensor placement, control settings, and conditions that need specialist review. Readers get a familiar structure without every subject being forced into the same template.
Make the formatting rules easy to check during an edit:
- Expand technical abbreviations at first mention unless they are common units.
- Put the relevant condition beside a number that depends on mounting height, tested area, or operating setting.
- Use bullets for separate checks and numbered steps when order matters.
- Label product specifications as reported figures if the publication has not verified them.
- Use a table when aligned columns make several options easier to compare.
Not every equipment post needs a table. When one does, specify consistent column names and a way to mark unavailable data; an empty cell can be mistaken for zero. A separate treatment of making grow-light comparison tables useful can inform the rule without turning the style guide into a table-design manual.

Put the guide into an editing workflow
Keep one current version in the team’s shared workspace, where contributors can reach it while editing. Put the owner, revision date, and a brief change record at the top. Link to approved examples within the workspace, labeling each by the rule it illustrates rather than treating an entire older post as a flawless model.
Try the first version on three different drafts: one about a home grow tent, one about a greenhouse fixture, and one about environmental controls. Have an editor mark where the guide settles a choice and where it leaves a question. If writers keep disagreeing about “coverage,” add a definition and an example that qualifies the manufacturer’s stated area. Revise rules that make sentences awkward without improving accuracy.
Keep fixed standards separate from editorial judgment. Units, component names, and the treatment of unverified figures should remain consistent. Sentence length and background detail can change with the reader’s task. If an exception makes sense, note it beside the relevant rule rather than quietly creating a second convention.
On the next equipment draft, finish with three checks: match component names to the glossary, attach conditions to performance figures, and flag installation statements for qualified review where needed. Put any unresolved wording in the guide’s change record before publication.
