Science Guide: Wiki Submission & Involvement
More actions
How to Use This Guide
1. Purpose of the Bravo Fleet Wiki
The Bravo Fleet Wiki exists to support collaborative storytelling by providing a shared, in-universe reference for subjects that appear in Bravo Fleet writing. This includes ships, stations, locations, organisations, governments, species, events, phenomena, and other material useful to members.
Bravo Fleet maintains a shared setting. The Intelligence Office is responsible for defining Bravo Fleet canon, including major historical events, current political conditions, Starfleet activity, and other fleet-wide developments. The Science Office maintains and develops the Bravo Fleet Wiki and Bravo Fleet Map to help record and present that information.
Recommended
- Support current and future storytelling
- Be useful to members beyond the original contributor
- Remain compatible with established Bravo Fleet canon
- Be written from an in-universe perspective unless clearly stated otherwise
- Not create unnecessary duplication of material already available on the Bravo Fleet Wiki, BFMS, Memory Alpha, or other suitable references
Keep the purpose in mind: The wiki is not intended to be a complete recreation of Star Trek canon, a personal command log, or a place for out-of-character commentary. It should serve as a shared reference to help members understand and use the Bravo Fleet setting.
2. Getting Involved
All Bravo Fleet members may contribute to the Bravo Fleet Wiki in accordance with the Science Office Policy and the definitions of Fleet Canon established by the Intelligence Office.
Recommended
- Developing their own Ship, Station, or Command Unit articles
- Creating suitable Member Canon articles for story-relevant subjects
- Updating Member Canon articles after major story developments
- Improving formatting, links, categories, and clarity on Member Canon articles
- Adding relevant images and media
- Suggesting corrections, additions, or improvements to Fleet Canon articles through their discussion pages
All Bravo Fleet members can have a wiki account. Members needing access can contact the Bravo Fleet Science Officer through Discord.
Members are welcome to ask the Bravo Fleet Science Officer and their wonderful team for help with article planning, wiki formatting, categorisation, image use, or any other part of contributing to the wiki.
3. Required Minimum Standards for Wiki Contributions
Required
- Have a clear subject and purpose
- Add useful information that supports storytelling or setting development
- Be written in a clear, neutral, reference-style tone
- Use an in-universe perspective unless limited out-of-character guidance is appropriate
- Remain compatible with established Star Trek canon, Bravo Fleet canon, and approved Intelligence Office guidance
- Not create unnecessary duplication of existing articles or external references
- Use appropriate section headings where needed
- Include relevant internal links where appropriate
- Be placed in appropriate categories where applicable
- Follow the required standards in any relevant Science Office article development guide
Articles do not need to be long to be useful. A concise, well-organised article that gives members the right information is often more helpful than a long article full of details that are difficult to reuse.
Maintenance templates: Articles that need further development may be marked with an appropriate maintenance template. Maintenance templates are intended to identify areas for improvement and do not prevent members from continuing to edit or expand the article.
4. Fleet Canon and Member Canon
4.1 Fleet Canon and Member Canon
The Bravo Fleet Wiki contains two broad categories of content:
Fleet Canon
Content approved by the Intelligence Office and applicable across Bravo Fleet. These pages are marked with a canon icon.
Member Canon
Content created by members for their own stories, ships, stations, commands, or related material.
Member Canon is not lesser or meaningless. It exists because some material is specific to a member's stories or area of play and does not have enough fleet-wide impact for every member to know, follow, or account for it. Other members may reference Member Canon where useful, but it is not expected to shape the wider shared setting unless it is later elevated to Fleet Canon.
Fleet Canon and Member Canon are defined by the Intelligence Office. The Science Office maintains the wiki structure, categories, and article presentation that help members identify and use this material.
4.2 Contributing to Fleet Canon Articles
Required
Members must not directly edit Fleet Canon articles.
If a member identifies an error, omission, outdated information, formatting issue, or potential improvement to a Fleet Canon article, they must add their suggestion to the article's discussion page.
The discussion page can be accessed using the Discussion tab on the relevant Fleet Canon article.
Suggestions should clearly explain the proposed change and include supporting information or sources where appropriate.
The Science Office and Intelligence Office will review suggestions and make changes to the Fleet Canon article where appropriate.
Adding a suggestion to a discussion page does not guarantee that the proposed change will be accepted or implemented.
Required
If a member is unsure whether an article is Fleet Canon, they should check for the relevant Fleet Canon identification or contact the Science Office before making changes.
5. Article Creation and Development
5.1 Required Before Creating or Expanding an Article
Required
Before creating or substantially expanding an article, members must check whether a related page already exists. A new article may not be needed if the information can be included clearly within an existing article.
Required
Members must not recreate articles that are created or maintained by another office. Certain article types, most notably ships and stations, are created by the Logistics Office when an asset is approved through Prestige. These pages usually include essential infobox data, categorisation, and basic structure.
Members can develop Logistics-created articles but must not recreate them from scratch.
Technical, administrative, and canon-tracking information added by the Logistics Office, Intelligence Office, or Science Office must be retained. Members who believe this information needs changing must contact the Science Office before removing or substantially altering it.
Where a Science Office article development guide exists for the article type, members must follow its required standards when developing the article.
5.2 Common Article Types
Members may create articles on story-relevant subjects that provide useful information, do not conflict with established canon, and follow this guide.
Common types of Member Canon articles include:
- Locations - Planets, settlements, regions, systems, colonies, or other places relevant to a member's stories. These articles should identify the location and use the relevant quadrant, region, or location category where appropriate.
- People - Notable non-player characters, such as Starfleet staff, heads of government, diplomats, scientists, civilian figures, or other recurring background characters. Articles should not normally be created for player characters or primary fiction characters already listed on BFMS. Link to the relevant BFMS character page instead, using code such as
[[bfms_char:13085|Teylas Ramar]]. - Governments and organisations - Local governments, colony administrations, regional councils, political groups, non-government organisations, or other factions relevant to Bravo Fleet storytelling.
- Species - Species articles may be appropriate where there is enough distinct information to justify a separate page. Where only limited information is needed, it may be better to include species information within a related government, location, or organisation article.
- Ships - Ships in the Bravo Fleet registry are created through the Logistics Office. Articles for other ships require approval from the Intelligence Office and Science Office before creation.
- Command Units - Members may create articles for their Command Units, including Divisions, Squadrons, and Flotillas, where those formations are recorded on BFMS.
- Phenomena - Wormholes, spatial anomalies, temporal anomalies, vortices, parallel universes, alternate timelines, spaceborne lifeforms, or similar story-relevant phenomena may be appropriate where they support a member's stories. These articles should clearly explain what the phenomenon is, where or when it appears, how it affects storytelling, and any limits on its use. Phenomena that could substantially affect Bravo Fleet canon, such as major stable wormholes, recurring temporal access, multiversal travel, or large-scale threats, should be discussed with the Intelligence Office before creation.
5.3 When a Separate Article Is Not Needed
Recommended
Members should not create a separate article when a short summary within an existing article would suffice. Consolidating related information usually makes the wiki easier to use.
A separate article is normally not needed where:
- The subject only needs a few sentences of explanation
- The subject exists only to support one paragraph in another article
- The information would be more useful as part of a related location, government, species, ship, station, Command Unit, or phenomenon article
- The article would duplicate information already found elsewhere
If a proposed article does not fit one of the usual categories, members are encouraged to ask the Bravo Fleet Science Officer and their wonderful team before creating it.
5.4 Command Unit Articles
Required
Members must not create separate articles for sub-units within the same BFMS Command Unit.
For more detailed guidance, members must follow the Science Office development guide for Command Unit articles.
6. Writing Style and Perspective
6.1 Required Writing Standards
Required
- From an in-character, in-universe perspective
- In a neutral, reference-style tone
- With current facts usually written in the present tense
- With historical events usually written in the past tense
Required
- Include references to television episodes, films, seasons, or production details
- Include references to Bravo Fleet missions, campaigns, or Fleet Actions by title in the main article text
- Include backstage or behind-the-scenes commentary
- Include contributor notes or personal commentary, except where limited guidance is appropriate in an In Play section
- Present speculative or future events as established history
The default assumption is that an article reflects what Starfleet, the Federation, or another suitable in-universe source could reasonably know.
6.2 Recommended Writing Practice
Recommended
Wiki articles should include enough detail to support storytelling without overwhelming the reader.
Where there is deliberate uncertainty, such as incomplete knowledge of a government, species, phenomenon, or historical event, articles may describe competing theories, limited information, or unresolved questions.
Articles should not include excessive detail that does not support storytelling or help members understand the subject. Where real-world or established Star Trek canon already exists, it is often better to link externally to Memory Alpha, Wikipedia, or another suitable reference rather than reproduce large amounts of information.
6.3 In-Universe Framing Examples
References to established Star Trek events or Bravo Fleet events are allowed where relevant, but they should be framed as historical events within the setting.
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."
The acceptable examples describe events as part of the setting. The unacceptable examples describe stories, episodes, or fleet activities from an out-of-character perspective.
6.4 Footnotes
Optional
Footnotes may be used to provide optional source links or context without disrupting an article's in-universe framing.
Footnotes are most useful for:
- Linking to BFMS missions or stories
- Linking to Memory Alpha, Wikipedia, or another suitable external reference
- Supporting a brief point without adding out-of-character detail to the main article text
Required
7. Structure and Headers
7.1 Required Structure
Required
Required structures identified in the relevant Science Office article development guide must be retained where applicable.
Where an article type has an appropriate infobox template, members must use that template unless the relevant Science Office guide states otherwise.
7.2 Recommended Structure
Recommended
Articles should use clear section headers where they help organise information. Consistent structure improves readability and makes articles easier to review and develop.
Some article types, such as specifications, governments, ships, stations, locations, Command Units, and phenomena, may have recommended headers or article structures described in more detailed Science Office development guides. Where such guides exist, members should use them as the starting point for article development.
Members are encouraged to look at similar articles for examples of structure, formatting, and appropriate level of detail.
7.3 In Play Sections
Optional Required Where Specified
Some articles include an In Play section. This section gives members brief guidance on how the subject may be used or portrayed in storytelling.
An In Play section is optional unless required by a specific article development guide.
An In Play section should normally:
- Be brief, usually no more than half a dozen points
- Describe general behaviour, reputation, limitations, or important portrayal notes
- Help members use the subject consistently
- Not include detailed story summaries or future predictions
This is the main place where limited out-of-character guidance may be appropriate, especially where an idea cannot be clearly explained in the main in-universe article text.
7.4 Templates and Categories
Required Where Applicable
Members wishing to create a new template, category, or subcategory must contact the Science Office before doing so.
Members must also contact the Science Office before making changes to an existing template or category that would affect multiple wiki pages or change how that template or category is used.
Members may suggest new templates, categories, or other wiki-wide structures to the Science Office.
8. Links and References
Internal and external links help members move between related information. They should be used where they add value, but should not overwhelm the article.
8.1 General Linking Practices
Recommended
Members should use internal links for relevant Bravo Fleet Wiki articles where those links help the reader understand the subject.
Members should use BFMS character links for characters recorded on BFMS, rather than creating unnecessary character articles.
Members should link to the same article only on the first relevant mention in a section, unless repeating the link would genuinely help the reader.
Before creating a new article, members should search the wiki first. A related article may already exist, or the new information may fit better within an existing page.
8.2 Recommended Linking Practices
Recommended
External links to Memory Alpha, Wikipedia, or other suitable references may be used where they are more appropriate than reproducing existing information.
Links should support the article. They should not be added so frequently that the text becomes difficult to read.
8.3 Linking to Memory Alpha
Members can use the built-in ma: interwiki link code when linking to Memory Alpha.
Example
[[ma:USS Enterprise-E|USS ''Enterprise''-E]]
This creates a link to the Memory Alpha article for USS Enterprise-E while allowing the displayed text to follow Bravo Fleet Wiki formatting.
9. Images and Media
9.1 Required Image Standards
Required
- Be relevant to the article or subject with which they are associated
- Be uploaded in a supported format: JPG, PNG, or GIF
- Be kept below 12 MB
- Be placed within an appropriate image category
- Include clear credit and a source link where the image uses someone else's work
- Comply with the Creative Integrity Policy, including any requirements relating to generative artificial intelligence, image modification, attribution, source links, and permitted use
Required
Members must not upload modified versions of someone else's work unless this is permitted under the Creative Integrity Policy. This includes images edited, altered, expanded, restyled, or otherwise transformed using generative artificial intelligence tools.
9.2 Expected Image Practice
Recommended
Members should review the existing images before uploading a new file to prevent duplication.
If an uploaded image duplicates an existing file, the Science Office may remove the duplicate and direct members to use the existing image.
Images should support the article rather than overwhelm it.
Images should be useful, relevant, and connected to the subject. Members should not add images simply to fill space.
9.3 Categorising Images
Required
Images must be categorised either during upload or immediately afterwards.
Categorisation helps similar images, such as dedication plaques, mission patches, ships, stations, and locations, remain easy to find.
Image subcategories can be found under Category:Images.
To categorise an image, add the relevant category to the image summary when uploading the file, or edit the image after upload to add the category.
Example
This is an image of Starbase Example. [[Category:Images-Starbases]]
If a suitable image subcategory does not exist, members must contact the Science Office before creating a new subcategory.
9.4 Image Credits and Source Links
Required
Credit should identify:
- The title or subject of the image
- The name or username of the original artist or creator
- A link to the original work
- Any relevant permission, licence, or usage terms where applicable
Example
Matthys Clark by AnnexAX https://www.deviantart.com/annexax/art/Matthys-Clark-1024873903
If the original source is no longer available, members should include as much source information as possible and note this in the file description.
10. Creative Integrity and Generative Artificial Intelligence
Required
All use of generative artificial intelligence in connection with the Bravo Fleet Wiki is governed by the Creative Integrity Policy. This includes article text, uploaded images, image modification, source material, attribution, and any other wiki contribution created or supported by generative artificial intelligence.
This guide may provide guidance on formatting, categorisation, wiki use, and article development for material created or supported by generative artificial intelligence, but it does not define separate rules for generative artificial intelligence outside the Creative Integrity Policy.
Members should refer to the Creative Integrity Policy and the Generative AI in your Writing guide before using generative artificial intelligence in connection with wiki contributions.
Content that does not comply with the Creative Integrity Policy may be removed, corrected, or referred to the appropriate Bravo Fleet office for review.
11. Quick Reference
At a glance: This section summarises the main requirements and recommendations in this guide. Members should refer to the relevant section above for full guidance.
11.1 Required
Required
- Respect established Star Trek canon, Bravo Fleet canon, and Intelligence Office guidance
- Follow the required standards in this guide and any relevant Science Office article development guide
- Use required structures, templates, notices, categories, and tracking information where applicable
- Retain technical, administrative, and canon-tracking information added by the Intelligence Office, Logistics Office, or Science Office unless authorised to change it
- Use Fleet Canon article discussion pages to suggest corrections, additions, or improvements
- Contact the Science Office before creating new templates, categories, or subcategories
- Contact the Science Office before making changes to templates or categories that would affect multiple wiki pages
- Place uploaded images in an appropriate category
- Credit uploaded images that use someone else's work and include the required source information
- Follow the Creative Integrity Policy for all use of generative artificial intelligence, image modification, attribution, source links, and permitted use
11.2 Recommended
Recommended
- Write with future reuse in mind
- Keep content relevant, clear, and expandable
- Use internal links where appropriate
- Check whether a page already exists before creating a new one
- Update Member Canon articles following major story developments
- Look at similar articles for examples of structure and formatting
- Review existing images before uploading new files
- Ask the Bravo Fleet Science Officer and their wonderful team for help when needed
11.3 Do Not
Required
- Directly edit Fleet Canon articles
- Add Fleet Canon labels or categories to articles
- Recreate articles created or maintained by another Bravo Fleet office
- Treat articles as personal command logs
- Create unnecessary articles for every minor species, location, event, or object
- Create separate articles for sub-units within the same BFMS Command Unit
- Present speculative or future events as established history
- Use out-of-character episode, campaign, mission, or production framing in the main article text
- Remove required structures, tracking information, or office-added material without contacting the Science Office first
- Create new templates, categories, or subcategories without contacting the Science Office first
- Upload someone else's images without the credit and source information required by the Creative Integrity Policy
- Upload or modify images in a manner that does not comply with the Creative Integrity Policy
12. Review and Support
Members do not normally need approval before creating or improving suitable Member Canon wiki content, unless this guide, a relevant Science Office article development guide, or a Bravo Fleet policy states otherwise.
Member Canon exists to encourage members to develop their own part of the Bravo Fleet setting where that material does not have fleet-wide impact.
Science Office Review
Review may include:
- Newly created articles
- Updates or expansions to existing articles
- Images and other media uploaded to the wiki
- Formatting, categories, links, and article structure
During review, the Science Office will usually consider the following:
| Area Reviewed | Requirement Level | What This Means |
|---|---|---|
| Required standards | Required | The contribution meets the minimum standards in this guide and any relevant development guide. |
| Canon and continuity | Required | The article does not contradict established Star Trek canon, Bravo Fleet canon, or Intelligence Office guidance. |
| Article purpose | Required | The article has a clear subject and provides useful information for storytelling or setting development. |
| Structure and formatting | Required Where Applicable | Required templates, headers, categories, links, and office-added material are present where applicable. |
| Images, media, and creative integrity | Required Where Applicable | Uploaded files are relevant, categorised, credited where required, and compliant with the Creative Integrity Policy, including any requirements relating to generative artificial intelligence, image modification, attribution, source links, and permitted use. |
Articles requiring further development may be marked with an appropriate maintenance template. Maintenance templates are intended to support improvement and do not prevent members from continuing to edit, expand, or develop the article.
Contribute with Confidence
This guide is intended to make expectations clear and help members contribute confidently to the Bravo Fleet Wiki. If something is unclear, ask the Bravo Fleet Science Officer and their wonderful team.