Home
Random
Recent changes
Special pages
Community portal
Preferences
About Chesapeake Studios Wiki
Disclaimers
Chesapeake Studios Wiki
Search
User menu
Talk
Contributions
Create account
Log in
Editing
Chesapeake Studios Wiki:Writing guide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
<div style="background: linear-gradient(135deg, rgba(128, 0, 128, 1) 0%, rgba(75, 0, 130, 1) 50%, rgba(138, 43, 226, 1) 100%); color: #fff; padding: 20px 15px; text-align: center; text-shadow: 0 3px 6px rgba(0, 0, 0, 0.16), 0 3px 6px rgba(0, 0, 0, 0.23); border-left: 20px solid white; margin: 20px 10px 25px 10px;"> <p style="font-size: 20px; margin: 0;">This is the official policy of the Chesapeake Studios Wiki.</p> <p style="font-size: 18px; line-height: 1.8; margin: 15px 0 0 0;"> These policies set the standards for wiki article creation and community interaction. They can be amended at any point given the circumstances. </p> </div> <p style="font-size: 18px; margin: 20px 10px; line-height: 1.8;"> This is a guide for writing an article on the {{SITENAME}}. Our other policies are located [[Chesapeake Studios Wiki:Policy|here]]. This guide will serve as the way to structure, write, and layout a page. </p> ==Prior to writing a page== Before you begin writing a page on the Chesapeake Studios Wiki, it is crucial to familiarize yourself with our main [[Chesapeake Studios Wiki:Policy|Policy]] page. This will give you an understanding of the general principles we follow regarding content creation and organization on the wiki. By following these guidelines, we ensure that the information presented on the wiki remains consistent, well-structured, and of high quality. When creating a page for a new topic, it’s important to first ask yourself whether the subject truly warrants a standalone page. Does it have enough information to provide depth and avoid being a "stub"? Is it influential to the game, the community, or the studio's history? If the answer is yes, then it’s likely deserving of its own page. However, if the topic is too limited, too niche, or does not have enough relevance to the broader game or community, it may be better suited to an existing page. Here are some key points to consider when deciding whether a topic deserves a page: <div style="background: linear-gradient(135deg, rgba(128, 0, 128, 1) 0%, rgba(75, 0, 130, 1) 50%, rgba(138, 43, 226, 1) 100%); color: #fff; padding: 25px 20px; text-align: left; text-shadow: 0 3px 6px rgba(0, 0, 0, 0.16), 0 3px 6px rgba(0, 0, 0, 0.23); border-left: 20px solid white; margin: 20px 10px 30px 10px;"> <p style="font-size: 20px; margin-bottom: 15px;">'''What deserves a page'''</p> <p style="font-size: 18px; line-height: 1.8;"> Pages that should be created on the wiki include topics that are: </p> <ul style="font-size: 18px; line-height: 1.8;"> <li><strong>Key Elements of the Game:</strong> Any major gameplay mechanic, feature, or system that plays an integral role in the game's overall design and user experience. These include core game mechanics, features used across all game servers, and other elements that are pivotal to understanding how the game functions as a whole. If something is integral to gameplay and available to all players, it likely deserves a page.</li> <li style="margin-top: 5px;"><strong>Major Content and Features:</strong> Content that has been released as part of significant updates or patches, or content that has had a lasting impact on the game. This includes updates that significantly alter game mechanics, introduce new systems, or contribute to the overall narrative of the game. Special events or major content releases, if they influence gameplay or the player community, are often worth documenting.</li> <li style="margin-top: 5px;"><strong>Important Locations:</strong> Significant locations or areas in the game world that are key to the gameplay experience, story, or lore. These could include cities, structures, rooms, or entire regions of the game map. Locations that host important activities, such as gameplay areas or hubs for major events, also deserve dedicated pages.</li> <li style="margin-top: 5px;"><strong>Roles and Leadership Positions:</strong> Major leadership roles, such as the President, Vice President, or Chief of Staff, within the Chesapeake Studios game or the larger game community. These individuals hold significant influence over the game's direction and governance, and their roles are often crucial to the decision-making processes in the game world or within the organization itself.</li> <li style="margin-top: 5px;"><strong>Community Events and Influences:</strong> Major events that have shaped the community or the development of the game. These could include historic moments in the game's development, significant player-driven events, or milestones that have shaped the culture or identity of the community. Memes, inside jokes, or widely recognized community trends that are linked to the game's history and culture are also important to document.</li> <li style="margin-top: 5px;"><strong>Notable Game Developers and Contributors:</strong> Pages dedicated to key individuals, such as game developers, writers, designers, and community managers, who have contributed significantly to the game’s development or the community. Their work in creating or shaping the game deserves recognition. If a person has played an important role in the creation or management of the game or group, they should have a page, provided they have given their consent for it to be created.</li> <li style="margin-top: 5px;"><strong>Exclusivity or Temporary Content:</strong> Content that is only available for a short period, tied to a specific event, or offered as part of a limited-time promotion should have its own page IF it had a substantial, lasting impact on the game or community. Limited-time updates or exclusive content that does not have significant lasting value or influence should be summarized on broader update or event pages instead.</li> </ul> <p style="font-size: 20px; margin-top: 30px; margin-bottom: 15px;">'''What does not deserve a page'''</p> <p style="font-size: 18px; line-height: 1.8;"> While it’s important to give due recognition to important elements of the game and community, it’s equally important to refrain from creating pages for topics that do not meet these criteria. Below are categories of content that do not warrant their own dedicated pages on the wiki: </p> <ul style="font-size: 18px; line-height: 1.8;"> <li><strong>Minor Roles or Temporary Staff:</strong> Pages for individuals in minor or temporary positions, such as low-level staff, secretaries, or other temporary roles, should not be created. Instead, these roles should be summarized within the department pages. These pages are often redundant and do not contribute significantly to the game’s history or the understanding of its development.</li> <li style="margin-top: 5px;"><strong>Characters Played by Players:</strong> Player-controlled characters, even if they are central to role-playing on a particular server, are generally not significant enough to warrant individual pages. These characters usually have no lasting impact once the player leaves, and their existence is confined to the temporary context of a specific game instance or role-playing event. These can be mentioned in broader event or narrative pages where they are relevant, but they should not have their own dedicated page.</li> <li style="margin-top: 5px;"><strong>Unimportant Server-Specific Incidents:</strong> Events that occur within a single server and are part of specific role-playing or gameplay that do not have wider significance should not be written about as separate pages. These are often isolated occurrences that don’t impact the larger game or community. While they may be interesting or humorous, their relevance to the broader narrative of the game or community is minimal.</li> <li style="margin-top: 5px;"><strong>Rumors, Speculation, or Unverified Information:</strong> Avoid creating pages about rumors, unconfirmed leaks, or speculative content. If the information has not been officially verified or does not directly influence the development of the game, it should not be written about in detail. Speculative content can be added to discussion pages or community forums but should not form the basis of a factual article.</li> <li style="margin-top: 5px;"><strong>Minor Memes or In-Jokes:</strong> Memes and jokes that are not widely recognized or do not have a significant, lasting impact on the game's culture should not be given their own pages. While it’s fine to mention them in broader community culture sections, isolated jokes or memes that are fleeting or don’t contribute to the game’s identity should not be the focus of standalone pages.</li> <li style="margin-top: 5px;"><strong>Low-Impact or Temporary Game Features:</strong> Features or content that were quickly removed or updated with little lasting effect should not be the subject of their own pages. Temporary additions, minor tweaks, or experimental features that were ultimately scrapped or quickly overshadowed by larger updates should not be isolated in their own articles unless they had a major impact on gameplay or community perception.</li> </ul> <p style="font-size: 18px; margin-top: 25px; line-height: 1.8;"> In essence, creating pages is about documenting significant, lasting contributions to the game or community, whether through gameplay, content, or the people involved. Focus on content that has long-term relevance and broad impact. If in doubt, consider summarizing the topic in a broader, more relevant context. If a subject doesn’t contribute meaningfully to the larger picture of the game or the community, it likely doesn’t warrant its own page. </p> </div> ==Editing== Editing pages on the wiki can be done through the source editor, which is the preferred method for many experienced editors. Though it might seem daunting at first, the source editor is more flexible and powerful than the visual editor, allowing for a more consistent and streamlined process when creating or modifying pages. The source editor also supports advanced features like templates, which can simplify the process of formatting content and creating dynamic elements within the pages. Visual editing, on the other hand, is simpler to use but often leads to formatting issues, especially when it comes to templates, links, or more complex page structures. While it’s a good option for beginners or simple edits, we recommend using the source editor for more complicated tasks or when adding new sections to a page. If you are new to editing, we recommend reviewing [https://community.fandom.com/wiki/Help:Editing| Fandom's guide on editing], which provides a thorough overview of both the visual and source editors. If you need assistance with any aspect of editing, whether it's formatting, adding templates, or structuring your page, feel free to consult the help section or reach out to the wiki administrators. They are always available to assist and ensure that pages maintain a high standard of quality and organization. ==General Layout== Each page on the wiki should generally follow a standardized structure to ensure consistency across the site. However, there may be cases where a page requires a unique format due to its subject matter. The following layout should be used for most pages, but exceptions can be made where necessary. ===Infobox=== Every page should include an infobox unless it is not applicable to the topic at hand. An infobox is a compact table that provides quick, essential information about the subject, making it easy for readers to grasp key details at a glance. These are especially useful for articles on people, places, roles, and updates. To add an infobox to a page, select the appropriate template from [[:Category:Infoboxes|here]] and paste it at the top of the page. Fill out the infobox with relevant details such as names, roles, dates, and descriptions. Custom infoboxes are available for specific topics like roles or updates, and these should be used where appropriate. Here’s an example of the code for a role-based infobox: <pre> {{Role infobox | title1= | image1= | caption-image1=I | released= | role_information= | department= | requirements= | powers= | reports_to= | duties= }} </pre> This code will generate a standard infobox, but there are other infoboxes available for different types of pages. Each type of page (e.g., location, department, update) has its own template that helps organize information clearly and consistently. ===Content Organization=== Once the infobox is in place, begin organizing the content of the page. The goal is to provide readers with an informative, logical, and easy-to-navigate article. Be sure to use headings and subheadings to break up large sections of text. This will improve readability and make it easier for users to find specific information. Use [[Chesapeake Studios Wiki:wikilinks|wikilinks]] to link to related pages within the wiki. This not only helps connect the content but also boosts the discoverability of relevant articles. Additionally, be sure to add categories to each page at the bottom to group it appropriately for easy navigation across related topics. For example, if the page is about a major event, you would categorize it under "Events" and perhaps also under "History." Finally, review the content for clarity, grammar, and spelling before saving your changes. If you're unsure about any details, double-check the information and consult relevant sources. Editing is an iterative process, and it's always best to ensure the accuracy and quality of the content before publishing it. By following these guidelines, we can ensure that the wiki remains a valuable resource for all contributors and players alike. <div style="background: linear-gradient(135deg, rgba(128, 0, 128, 1) 0%, rgba(75, 0, 130, 1) 50%, rgba(138, 43, 226, 1) 100%); color: #fff; padding: 25px 20px; text-align: left; text-shadow: 0 3px 6px rgba(0, 0, 0, 0.16), 0 3px 6px rgba(0, 0, 0, 0.23); border-left: 20px solid white; margin: 20px 10px 30px 10px;"> <p style="font-size: 18px; line-height: 1.8; font-style: italic;"> Last Updated - November 17th, 2024 at 13:45 EST </p> </div>
Summary:
Please note that all contributions to Chesapeake Studios Wiki are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) (see
Chesapeake Studios Wiki:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)