This article provides guidelines and requirements for contributing to the wiki by adding new articles or editing existing ones. Please refer to the Intelligence Office Policy for broad guidelines on Bravo Fleet canon and its creation.

1. Purpose of the Bravo Fleet Wiki

The Bravo Fleet Wiki exists to support collaborative storytelling by providing a shared, in‑character reference for materials such as assets (ships and stations), locations, organisations, and events that appear in Bravo Fleet writing.

Bravo Fleet maintains a cohesive canon; the Intelligence Office decides on our version of 2403, and that is the standard to which all stories in the Fleet must adhere. This includes the timeline of recent events, the nature of modern governments, and Starfleet activities and engagement. Records of such information are maintained on the BFMS and on this wiki by the Science Office.

As such, our wiki content should:

Support current and future storytelling;
Be usable by members beyond the original contributor;
Remain compatible with established Bravo Fleet canon;
Be written from an in‑universe perspective.

The wiki is not intended to be an exhaustive recreation of Star Trek canon, nor a repository for personal logs or out‑of‑character commentary.

The wiki is collaboratively developed by members and maintained and developed by the Science Office in consultation with the Intelligence Office.

2. Canon and Ownership

2.1 Fleet Canon and Member Canon

The Bravo Fleet Wiki contains two categories of content:

Fleet Canon content, which has been approved by the Intelligence Office and applies across Bravo Fleet. These pages are marked with a canon icon.
Member Canon, which may include individual ships, stations, and certain locations. This content is optional for other members to reference unless it is later elevated to fleet canon.

2.2. Fleet Canon Contributions

Members should not substantially alter Fleet Canon articles without approval. Suggestions for improvement or expansion should be directed to the Intelligence Office. Please remember that we are not trying to replicate Memory Alpha. Fleet Canon articles are for everyone.

Members are encouraged to focus on their storytelling and contribute it to our Wiki. Though we appreciate everyone’s ideas and thoughts on matters to add to Fleet Canon, remember that when we are dealing with Fleet Canon, this is on a large scale for everyone and will affect all our members. If you have a question about Fleet Canon, please reach out to the Intelligence and/or Science Offices.

Ultimately, we encourage members to tell their own stories within the world that has been set out, rather than get caught up in the smaller details of worldbuilding.

3. Article Creation and Development

3.1 Logistics Created Articles

Certain article types, most notably ships and stations, are created by the Logistics Office when an asset is approved through Prestige. These pages include essential infobox data, categorisation, and basic structure.

Members are expected to develop these articles, not recreate them. Core infobox information and administrative sections should not be removed or significantly altered without approval.

For more information, please see

Logistics Office Policy
Science Guide: Ship & Station Article Development Guide

3.2 Member Created Articles

Members may create articles for locations, minor organisations, or other story‑relevant subjects, provided they do not conflict with existing canon and follow this guidance.

Please consider the following categories, and their caveats, for member-created articles:

Locations: Planets, regions, starbases, systems, etc. Please specify where this location is situated, and add it to the category of the relevant Quadrant.
People: These should be NPCs such as Starfleet staff, heads of government, and notable civilian figures. These should not be player characters or a fiction’s main characters - ie, characters that are already listed on BFMS. Please link to those BFMS articles instead, using the following code example: [[bfms_char:13085|Teylas Ramar]]
Governments: Political groups, such as the Klingon Empire. Distinct from species, though in cases of limited but key information, descriptions of a species can be contained in a sub-section of the government page. Non-government factions (such as the Fenris Rangers) can also be added.
Species: Where relevant, information on a species’ biology and psychology can often be included on the relevant government page. Please do not unnecessarily add articles when a link to Memory Alpha would suffice.
Ships: Every ship which exists in the Bravo Fleet registry is entitled to an article. This will be created by the Logistics Office and can be developed by members. Articles for other ships require ratification by the Intelligence and Science Offices.

While there may be other kinds of pages, please think hard or consult the Science Office before creating a page which does not fit within these guidelines.

4. Writing Style and Perspective

All wiki articles should be written:

From an In‑Character, In‑universe perspective (the default assumption is that an article is written from the perspective of what Starfleet knows*).
Using a neutral, reference‑style tone.
In the present tense, where appropriate.
So members are given essential information, allowing them to use it within their own contributions.

* This is especially useful when there is intentional ambiguity around a topic, like the Gorn Hegemony, which is being developed by Strange New Worlds, where framing ideas as theories helps clarify. However, this guidance is for writers, not an in-universe text.

What should not appear in articles:

References to TV episodes;
References to BF missions;
Backstage/behind the scenes material by name or from a production perspective;
Out‑of‑character commentary;
Contributor notes.

Examples: In-Universe Framing

References to established Star Trek events or Bravo Fleet missions are permitted where relevant, but they must always be framed in-universe. Articles should describe events as historical occurrences within the setting, rather than referring to episode titles, production details, mission names, or campaign branding. Wiki content should read as if written by someone living in the Star Trek universe, not from a viewer or participant perspective.

Acceptable

“The station was occupied by Cardassian forces during the Dominion War.”
“The vessel sustained significant damage during the Vaadwaur incursions.”
“Following a series of classified Starfleet operations in the sector, the region was placed under increased patrol.”

Not Acceptable

“As seen in Deep Space Nine, Season 6, Episode 5…”
“During the ‘Shore Leave 2402’ Bravo Fleet campaign…”
“This event took place in the Nightfall Bravo Fleet Fleet Action.”

We are not interested in vast articles giving minute detail on every nuance of a culture, useful or otherwise. Think of this as a sourcebook for a role-playing game, rather than one of Tolkien’s appendices. The Science Office recognises this is a highly subjective distinction and is happy to provide guidance.

When real-world or established Star Trek canon exists, it is often preferable to link externally (e.g., to Memory Alpha and Wikipedia) rather than reproduce information unnecessarily.

Use of Footnotes

Footnotes may be used to provide optional context or source information without breaking the in-universe framing of an article.

They are most appropriate for:

Linking missions on BFMS.
Linking to other external reference material (i.e. Memory Alpha or Wikipedia).

All essential information must appear in the main article text, written fully in-universe. Footnotes should just be links. They should not contain author commentary, speculative justification, or replace proper article content.

5. Structure and Use of Headers

Articles should be clearly structured using logical section headers. Consistent use of headers improves readability and makes articles easier to review.

Some article types, such as specifications, governments, ships and stations, may have recommended or required headers defined in more detailed development guides. Where such guides exist, members should follow them.

Do not remove required headers placed by the Intelligence, Logistics, or Science Offices.

5.1 In Play Sections

Many articles include an ‘In Play’ section. This section provides guidance on how to portray the subject in storytelling. An In Play section should be brief, around a half-dozen points at most. In Play section provides a chance for simple Out-of-Character explanations.

In Play sections, should:

Describe general behaviour, reputation, or constraints.
Help members portray the subject consistently.
Avoid recounting specific story events.

In Play Sections are the essential ‘Do’s’ and ‘Don’t’s’, the Cardinal Rules. They should not be used as narrative summaries or future predictions. However, this is also the place to summarise or explain ideas ‘Out of Character’ if ideas or guidance could not be effectively conveyed in the main article - see, again, the Gorn Hegemony article.

6. Images and Media

Images used on the wiki must:

Be appropriately licensed or original.
Be categorised correctly (see below for more details).
Be relevant to the article content.

Members should avoid excessive image use. Images should support the article rather than overwhelm it.

6.1 Categorising Images

As part of file uploading to the wiki, categorisation should be done either at the time of upload or immediately after. This is so that images of a similar content type (plaques, patches, etc.) can be grouped together and allow other users in the future to search for an image they may wish to use that is already uploaded, instead of loading a new image.

Image sub-categories can be found under Category:Images.

To categorise an image, simply add the category to the bottom of the image summary when uploading, or edit the image after uploading and include the summary there. ie

''This is an image of the Starbase Kickass

[[Category:Images-Starbases]]''

If a sub-category doesn't exist that you feel needs to exist, please contact the Science Office before creating a new sub-category.

Please restrict all images to the JPG, PNG, or GIF formats. WebP image formats do not work on the Bravo Fleet Wiki. Please keep all images below 12 MB as well.

7. Generative AI Content

All content on the wiki must adhere to the Creative Integrity Policy when using generative AI (meaning both text-generation LLMs, such as ChatGPT, and AI image generation software, such as Midjourney).

All AI-generated images on the website must be credited as such on the image description, specifying which generator was used.

AI-generated text is forbidden on the Bravo Fleet Wiki. The purpose of this wiki is to provide information that members find useful in developing and understanding the Bravo Fleet setting. The use of AI-generated text undermines the wiki’s purpose of being relevant and concise. Even edited, AI-generated text runs the risk of contravening Trek and fleet canon, and prioritising content production and quantity over quality and pertinence. Simply put, if an author does not feel the text is worth writing themselves, why should a wiki reader find it useful?

Members may use LLMs such as ChatGPT to help develop ideas for articles. They must, however, be the authors of the content itself. See the Generative AI in your Writing guide for support in how to use LLMs in your creative writing, in line with the Creative Integrity Policy.

Failure to comply with this may result in the removal of content.

8. Common Do’s and Don’ts

Do:

Write with future reuse in mind. You may include something that inspires another member to write their own piece.
Keep content relevant and expandable.
Use internal links to other wiki pages where appropriate. If you are not sure if a page exists, then search for it. You never know! However, only use one internal link to the same article. E.g. Once you’ve put a link to the Federation, don’t link every other time after that point that the Federation is referenced.
Update articles following major story developments. This avoids it becoming a big task if you decide to update your wiki.
Look at other articles in similar categories to see how they have been written and get a feel for what to include. You may even discover how the Wiki coding works!

Don’t:

Include irrelevant details or overly detailed descriptions that distract from the point you’re trying to share on the wiki.
- This includes adding extra articles for every species, location, etc that your ship encounters. If a brief summary can be used on one article, leave it on one article. Consolidating information into one article is much better than creating another article that barely has any information in it.
Treat articles as personal command logs. BFMS exists for this reason!
Introduce contradictions with established fleet canon. We share this in-universe setting together as a community. Enjoy what has been established and get involved!
Write speculative or future events as established history. Q will not appreciate you jumping the gun here!
Be afraid to ask for help from the Science Office. We are here to help and support members.

9. Review and Quality Assurance

Members should create and contribute their work to our Wiki without the concern that everything they add must be constantly vetted by either the Science or Intelligence Offices. Member canon exists to encourage our members to create their own pocket within our great universe.

All wiki content is subject to review by the Science Office in consultation with the Intelligence Office.

This includes:

Newly created articles
Updates or expansions to existing articles
Images and other media uploaded to the wiki

When quality assuring content, the Science Office will generally assess whether:

Content follows this guide, any applicable development guides and the appropriate policies.
Required structures are present
Canon is respected
Images and media meet wiki standards

This guide is intended to make those expectations clear and transparent.