diff options
Diffstat (limited to 'communities/174bg/handbook')
| -rw-r--r-- | communities/174bg/handbook/.gitignore | 2 | ||||
| -rw-r--r-- | communities/174bg/handbook/README.md | 3 | ||||
| -rw-r--r-- | communities/174bg/handbook/public/index.html | 1761 | ||||
| -rw-r--r-- | communities/174bg/handbook/wrangler.jsonc | 20 |
4 files changed, 0 insertions, 1786 deletions
diff --git a/communities/174bg/handbook/.gitignore b/communities/174bg/handbook/.gitignore deleted file mode 100644 index 9397005..0000000 --- a/communities/174bg/handbook/.gitignore +++ /dev/null @@ -1,2 +0,0 @@ -/node_modules/ -/.wrangler
\ No newline at end of file diff --git a/communities/174bg/handbook/README.md b/communities/174bg/handbook/README.md deleted file mode 100644 index f534e2e..0000000 --- a/communities/174bg/handbook/README.md +++ /dev/null @@ -1,3 +0,0 @@ -# 174BG Handbook - -This handbook is a guide for members of the 174th Battle Group community. It contains all the information you need to know about the community and our operations. It is a living document, so please check back often for updates. diff --git a/communities/174bg/handbook/public/index.html b/communities/174bg/handbook/public/index.html deleted file mode 100644 index fe2cdcd..0000000 --- a/communities/174bg/handbook/public/index.html +++ /dev/null @@ -1,1761 +0,0 @@ -<!doctype html> -<html lang="en"> - <head> - <meta charset="UTF-8" /> - <meta name="viewport" content="width=device-width, initial-scale=1.0" /> - <title>174th Battle Group Handbook</title> - <style> - /* table styles */ - table { - width: 100%; - border-collapse: collapse; - margin-bottom: 1em; - } - - th, - td { - border: 1px solid #ddd; - padding: 0.5em; - text-align: left; - } - - th { - background-color: #f4f4f4; - } - - body { - display: flex; - align-items: flex-start; - } - - /* table of contents styles */ - nav#table-of-contents { - width: 240px; - min-width: 180px; - flex-shrink: 0; - position: sticky; - top: 0; - max-height: 100vh; - overflow-y: auto; - margin: 0; - box-sizing: border-box; - } - - nav#table-of-contents ul { - margin: 0; - padding-left: 1em; - list-style: none; - } - - nav#table-of-contents ul:first-child { - padding-left: 0; - } - - nav#table-of-contents li { - margin: 0; - line-height: 1.4; - } - - nav#table-of-contents a { - font-size: 0.8em; - text-decoration: none; - } - - nav#table-of-contents .toc-toggle { - background: none; - border: none; - cursor: pointer; - font-size: 0.6em; - padding: 0 3px 0 0; - color: inherit; - vertical-align: middle; - line-height: 1; - } - - nav#table-of-contents li.toc-collapsed > ul { - display: none; - } - - main { - flex: 1; - padding: 1em 2em; - box-sizing: border-box; - min-width: 0; - text-align: justify; - } - </style> - </head> - <body style="margin: 0; font-family: sans-serif"> - <nav id="table-of-contents"></nav> - <main> - <article id="introduction"> - <h1>174th Battle Group Handbook</h1> - <p> - This handbook is intended to provide a comprehensive overview of the - 174th Battle Group, its structure, operations, and guidelines for - members. It serves as a reference for both new recruits and seasoned - members to ensure consistency and efficiency within the group. - </p> - </article> - - <article id="using-this-handbook"> - <h2>Using This Handbook</h2> - <p> - This handbook is organized into sections that cover various aspects of - the 174th Battle Group. Each section is designed to provide clear and - concise information on specific topics. - </p> - <p> - Members are encouraged to familiarize themselves with the contents of - this handbook and refer to it regularly to ensure they are adhering to - the standards and expectations of the 174th Battle Group. - </p> - </article> - - <article id="departments"> - <h2>Departments</h2> - <p> - Departments govern specific gameplay loops and organisational - activities across the group. Unlike divisions, which define a member's - operational role, departments cut across divisional boundaries; a - member belongs to both a division and a department. For example, an - engineer holds a rank within the Auxiliary division but belongs to the - Engineering department; a combat medic serves in the Marine division - but belongs to the Medical department alongside dedicated medical - officers in Auxiliary. - </p> - <ul> - <li> - <strong>Command:</strong> Responsible for overall leadership, - strategy, and decision-making. - </li> - <li> - <strong>Operations:</strong> Responsible for planning and executing - missions. - </li> - <li> - <strong>Human Resources:</strong> Manages recruitment, training, and - personnel welfare. - </li> - <li> - <strong>Medical:</strong> Responsible for the health and medical - readiness of all personnel, including both field first aid and - primary care. - </li> - <li> - <strong>Engineering:</strong> Responsible for the maintenance, - repair, and construction of ships, equipment, and facilities. - </li> - <li> - <strong>Logistics:</strong> Manages supplies, equipment, and - transportation. - </li> - <li> - <strong>Mining:</strong> Oversees resource extraction and - management. - </li> - </ul> - </article> - - <article id="divisions"> - <h2>Divisions</h2> - <p> - The 174th Battle Group is organised into three distinct divisions: - Naval, Marine, and Auxiliary. This structure reflects the - fundamentally different operational environments and skill sets - required to execute the full spectrum of the group's missions. - Divisions define a member's operational role: how and where they do - what they do. They are distinct from departments, which govern - specific gameplay loops and functions that cut across all divisions. - </p> - - <section id="naval-division"> - <h3>Naval</h3> - <p> - The Naval division encompasses all personnel whose primary role - involves the operation, command, or crew of spacecraft. Naval - personnel are responsible for projecting force across space, - maintaining control of key transit corridors, and providing fire - support and transport capability to the broader group. - </p> - <p> - A dedicated naval structure is necessary because ship operations - demand a distinct chain of command, specialised technical knowledge, - and a culture built around vessel readiness and fleet coordination. - Conflating ship crews with ground forces would dilute accountability - and obscure the specific competencies each role demands. - </p> - </section> - - <section id="marine-division"> - <h3>Marine</h3> - <p> - The Marine division encompasses all personnel whose primary role - involves ground combat, boarding actions, facility assault or - defence, and close-quarters operations. Marines are the group's - primary fighting force on foot, responsible for securing objectives - that cannot be taken from orbit alone. - </p> - <p> - A separate marine structure is necessary because ground and boarding - operations require a different tactical doctrine, equipment - standard, and leadership model to ship-based roles. Marines must - train and operate independently of the fleet while remaining able to - integrate seamlessly with Naval assets, a relationship that works - best when each division has its own coherent hierarchy and identity. - </p> - </section> - - <section id="auxiliary-division"> - <h3>Auxiliary</h3> - <p> - The Auxiliary division encompasses all personnel whose primary role - involves enabling the operational effectiveness of the Naval and - Marine divisions. Auxiliary personnel ensure the group can sustain - itself independently, maintain its assets, and generate the - resources required for prolonged operations. - </p> - <p> - A dedicated auxiliary structure is necessary because enablement - roles require their own doctrine, career progression, and leadership - chain. Embedding auxiliary personnel into operational divisions - risks subordinating their work to short-term tactical priorities; a - separate division ensures that logistics, medical readiness, and - resource generation receive sustained command attention and are - treated as strategic priorities in their own right. - </p> - </section> - </article> - - <article id="ranks"> - <h2>Ranks</h2> - <p> - The 174th Battle Group uses a rank system to denote hierarchy and - roles within its divisions. Below is a breakdown of the ranks for each - division: - </p> - <table> - <thead> - <tr> - <th></th> - <th>Description</th> - <th>Naval</th> - <th>Marine</th> - <th>Auxiliary</th> - </tr> - </thead> - <tbody> - <tr> - <td><a href="#rank-0">Rank 0</a></td> - <td>Entry-level</td> - <td>Cadet</td> - <td>Private</td> - <td>Trainee</td> - </tr> - <tr> - <td><a href="#rank-1">Rank 1</a></td> - <td>Proven experience</td> - <td>Ensign</td> - <td>Corporal</td> - <td>Technician</td> - </tr> - <tr> - <td><a href="#rank-2">Rank 2</a></td> - <td>Specialised role</td> - <td>Lieutenant</td> - <td>Sergeant</td> - <td>Specialist</td> - </tr> - <tr> - <td><a href="#rank-3">Rank 3</a></td> - <td>Tactical leadership</td> - <td>Captain</td> - <td>Major</td> - <td>Supervisor</td> - </tr> - <tr> - <td><a href="#rank-4">Rank 4</a></td> - <td>Operational leadership</td> - <td>Commodore</td> - <td>Commander</td> - <td>Chief</td> - </tr> - <tr> - <td><a href="#rank-5">Rank 5</a></td> - <td>Strategic command</td> - <td>Admiral</td> - <td>General</td> - <td>Marshal</td> - </tr> - </tbody> - </table> - - <section id="rank-0"> - <h3>Rank 0: Entry Level</h3> - <p> - Assigned to all new recruits on joining the group. No prior - experience or requirements. Members at this rank are expected to - complete their initial training period before advancing. - </p> - </section> - - <section id="rank-1"> - <h3>Rank 1: Proven Experience</h3> - <p> - Requires demonstrated competence and commitment following the - initial training period. Members at this rank have shown they can - operate reliably within their division. - </p> - </section> - - <section id="rank-2"> - <h3>Rank 2: Specialised Role</h3> - <p> - Requires established expertise in a specific discipline within their - department. Rank 2 is the minimum rank required to hold a defined - role within a department. - </p> - </section> - - <section id="rank-3"> - <h3>Rank 3: Tactical Leadership</h3> - <p> - The lowest leadership rank. Requires the demonstrated ability to - lead a small team and take responsibility for their performance and - welfare. Members at this rank are expected to make tactical - decisions independently. - </p> - </section> - - <section id="rank-4"> - <h3>Rank 4: Operational Leadership</h3> - <p> - Requires a proven track record of tactical leadership at Rank 3. - Members at this rank lead other leaders, coordinating multiple teams - or assets toward a broader operational objective. - </p> - </section> - - <section id="rank-5"> - <h3>Rank 5: Strategic Command</h3> - <p> - The highest rank within each division. Reserved for members who have - demonstrated sustained operational leadership at the highest level. - Responsible for divisional direction, long-term capability, and - representing the division in group-wide decisions. - </p> - </section> - </article> - - <article id="command-structure"> - <h2>Command Structure</h2> - <p> - The 174th Battle Group is governed by a council of three: the Admiral - (Naval), the General (Marine), and the Marshal (Auxiliary). Each holds - Rank 5 within their division and together form the highest - decision-making authority in the group. No single individual outranks - the others; authority at the top level is collective. - </p> - - <section id="chain-of-command"> - <h3>Chain of Command</h3> - <p> - Within each division, authority flows downward by rank. Members - follow the orders of the nearest ranking member above them in their - own division. Rank 3 is the lowest rank at which a member holds - formal leadership responsibility; members below Rank 3 are not - expected to direct others. - </p> - <p> - Department heads hold authority within their domain regardless of - divisional rank. A member must follow direction from their - department head on matters within that department's scope. However, - the council of Rank 5s may override any department head by vote. - </p> - </section> - - <section id="operational-authority"> - <h3>Operational Authority</h3> - <p> - During active operations, a ship's captain holds complete authority - over everything that occurs aboard their vessel. This applies to all - personnel on board regardless of division or department, including - Marine and Auxiliary members embarked for a mission. Captains are - expected to exercise this authority in accordance with group - procedures; the scope of their authority is operational, not - administrative. - </p> - </section> - - <section id="decision-making"> - <h3>Decision-Making</h3> - <p>Decisions are made at the lowest appropriate level:</p> - <ul> - <li> - <strong>Major decisions</strong> — changes to group structure, - policy, or direction — are made by a vote of the Rank 5 council. A - majority is required to pass. - </li> - <li> - <strong>Routine decisions</strong> within a division or department - are made by the relevant division leader or department head - without requiring a council vote. - </li> - <li> - <strong>Community votes</strong> may be called for decisions that - affect the group broadly. All members Rank 1 and above are - eligible to participate. - </li> - </ul> - </section> - </article> - - <article id="joining-process"> - <h2>Joining Process</h2> - <p> - The following describes the full path from initial contact to - confirmed membership. Every step applies to all applicants without - exception; officers do not have the authority to bypass the process - for any individual. - </p> - - <section id="prerequisites"> - <h3>Prerequisites</h3> - <p> - Before applying, a prospective member must meet all of the following - requirements. Applications that do not meet these criteria will not - proceed. - </p> - <ul> - <li> - <strong>Age:</strong> Applicants must be at least 18 years old. - The 174th Battle Group operates as an adult community; this - requirement is non-negotiable. - </li> - <li> - <strong>Star Citizen account:</strong> Applicants must own a copy - of Star Citizen and hold a verified RSI account in good standing. - The group does not accept applicants who have not purchased the - game. - </li> - <li> - <strong>No prior bans:</strong> Applicants must not have been - previously banned from the 174th Battle Group or from any other - group known to leadership. Known ban histories must be disclosed - during the interview; undisclosed prior bans discovered later are - grounds for immediate removal. - </li> - </ul> - </section> - - <section id="application"> - <h3>Application</h3> - <p> - The joining process begins when a prospective member joins the - group's Discord server. On joining, they are automatically presented - with a short questionnaire covering basic information: their RSI - handle, their age, their prior Star Citizen experience, and their - areas of interest within the group. - </p> - <p> - Once the questionnaire is submitted, an available officer will - arrange a voice interview. This is conducted on the group's Discord - server and is the primary vetting step. The interview serves three - purposes: to verify the information provided in the questionnaire, - to assess whether the applicant is a good fit for the group's - culture and expectations, and to give the applicant the opportunity - to ask questions before committing. - </p> - <p> - Following the interview, the officer makes an accept or decline - decision. If the applicant is declined, the officer must provide a - brief reason. Declined applicants may reapply after 30 days unless - the decline was on the grounds of a prior ban or conduct, in which - case the matter is referred to the Rank 5 council. - </p> - </section> - - <section id="onboarding"> - <h3>Onboarding</h3> - <p> - Accepted applicants are onboarded immediately following the - interview. The following steps are completed before the new recruit - participates in any group activity: - </p> - <ul> - <li> - <strong>Discord role:</strong> The Rank 0 role is assigned, - granting access to member-only channels. - </li> - <li> - <strong>RSI org invite:</strong> An invitation to join the group's - RSI organisation is sent. The recruit is expected to accept within - 48 hours. - </li> - <li> - <strong>Introduction post:</strong> The recruit posts a brief - introduction in the designated welcome channel. This is not - optional; it is the first step in becoming known to the group. - </li> - <li> - <strong>Mentor assignment:</strong> The recruit is assigned a - mentor: an experienced member, Rank 2 or above, from their area of - interest. The mentor is the recruit's primary point of contact - throughout the probation period. - </li> - </ul> - <p> - Division assignment is not made at this stage. Recruits enter the - group as undeclared and spend the probation period determining where - they fit before the formal assignment is made. - </p> - </section> - - <section id="probation-period"> - <h3>Probation Period</h3> - <p> - All new members begin at Rank 0 and remain on probation until they - advance to Rank 1. The probation period has no fixed end date; it - concludes when the recruit meets the advancement requirements. - During this period, the recruit has full access to group activities - but does not hold a formal role and may not exercise any authority - over other members. - </p> - <p>Training during probation is structured around two activities:</p> - <ul> - <li> - <strong>Shadowing:</strong> Recruits attend operations and - activities alongside experienced members. This is the primary way - recruits learn the group's procedures, communication standards, - and expectations in practice. Recruits are expected to observe - before acting and to ask their mentor when uncertain. - </li> - <li> - <strong>Department drills:</strong> Departments organise periodic - drills covering their specific discipline: ship combat and - formation flying for Naval, FPS exercises and boarding drills for - Marine, and field repair and resource operations for Auxiliary. - Recruits are expected to attend drills relevant to their intended - area and to treat them as a required part of their training, not - an optional extra. - </li> - </ul> - <p> - Mentors are expected to provide regular feedback to the recruit - throughout the probation period and to raise any concerns with their - division leader or department head promptly. Recruits who are - struggling should be given guidance before any formal escalation. - </p> - </section> - - <section id="advancing-to-rank-1"> - <h3>Advancing to Rank 1</h3> - <p> - Advancement from Rank 0 to Rank 1 marks the end of probation and - formal entry into the group as a full member. To advance, a recruit - must satisfy all of the following: - </p> - <ul> - <li> - <strong>Minimum participation:</strong> The recruit must have - attended at least three group sessions. Sessions count only if the - recruit was an active participant, not merely present. - </li> - <li> - <strong>Drill attendance:</strong> The recruit must have attended - at least one drill run by the department of their intended - division. This is the single most concrete indicator of whether - they are prepared for the role. - </li> - <li> - <strong>Minimum time:</strong> At least two weeks must have - elapsed since the recruit joined. This ensures that advancement - reflects consistent participation over time, not a concentrated - burst of activity. - </li> - <li> - <strong>Rank 3 sign-off:</strong> A Rank 3 or above officer, - typically the recruit's mentor or their division leader, must - confirm that the recruit is ready to advance. This sign-off - reflects a judgment that the recruit understands and upholds the - group's standards and is a good fit for full membership. - </li> - </ul> - <p> - On advancing to Rank 1, the recruit's division is formally assigned - based on the area they trained in. If the recruit has not settled on - a division, the assigning officer and mentor will make the - recommendation based on what was observed during probation. The - recruit is granted the Rank 1 Discord role for their division and is - eligible to begin working toward a defined role within their - department. - </p> - </section> - </article> - - <article id="rules-of-engagement"> - <h2>Rules of Engagement</h2> - <p> - The Rules of Engagement define when and how members of the 174th - Battle Group are authorised to use force. All members are expected to - know and follow these rules at all times. Failure to do so may result - in disciplinary action. - </p> - - <section id="authorised-use-of-force"> - <h3>Authorised Use of Force</h3> - <p>Force is authorised only under the following conditions:</p> - <ul> - <li> - <strong>Direct hostile action:</strong> A target has taken hostile - action against group members or assets. - </li> - <li> - <strong>Demonstrated hostile intent:</strong> A target has - displayed clear hostile intent, such as weapons charged and - directed at group personnel or an aggressive approach with no - communication. - </li> - <li> - <strong>Standing orders:</strong> Command has designated the - target hostile by standing order prior to the engagement. - </li> - <li> - <strong>Active contract or mission objective:</strong> The target - is identified as an objective within a sanctioned mission or - contract. - </li> - <li> - <strong>Defence of a neutral or civilian:</strong> A neutral or - civilian is under active attack and the group has the capacity to - intervene. - </li> - </ul> - </section> - - <section id="escalation-and-warning"> - <h3>Escalation and Warning</h3> - <p> - Unless a member or the group is under active fire, a warning must be - issued before engaging. Members must make a reasonable attempt to - communicate intent and allow the target an opportunity to stand - down. If the target does not respond or continues to advance, force - may be used under the applicable condition above. - </p> - <p> - Offensive engagements, where the group initiates contact against a - target not currently attacking, require explicit authorisation from - a Rank 4 or higher officer, or from the council. Individual members - may not initiate offensive action on their own authority. - </p> - </section> - - <section id="civilians-and-neutrals"> - <h3>Civilians and Neutrals</h3> - <p> - The default stance toward civilians and neutral parties is to avoid - interaction entirely. Members must not provoke, threaten, or engage - neutral parties without authorisation. If a neutral becomes a direct - threat, the escalation process applies before force may be used. - </p> - </section> - - <section id="surrendered-and-fleeing-enemies"> - <h3>Surrendered and Fleeing Enemies</h3> - <p> - Enemies who surrender or attempt to flee must be pursued and - captured where possible. Lethal force against a surrendered or - fleeing enemy is a last resort, permitted only when capture is not - feasible and the enemy remains an active threat. Rank 3 and above - may authorise the release of a captured enemy if operational - circumstances require it. - </p> - </section> - - <section id="prohibited-actions"> - <h3>Prohibited Actions</h3> - <p> - The following actions are prohibited at all times, regardless of - orders: - </p> - <ul> - <li> - <strong>Impairing medical vessels:</strong> Medical ships must not - be attacked, disabled, or obstructed unless the vessel is - confirmed hostile and the group has its own medical capacity - available. - </li> - <li> - <strong>Destroying escape pods:</strong> Escape pods must never be - destroyed. Members are expected to pursue and capture them where - possible. - </li> - <li> - <strong>Griefing:</strong> Harassment, repeated unprovoked - attacks, and any conduct intended to ruin the experience of other - players is strictly prohibited. - </li> - </ul> - </section> - - <section id="friendly-fire"> - <h3>Friendly Fire</h3> - <p> - All friendly fire incidents, accidental or otherwise, must be - reported to the commanding officer immediately and documented. - Members involved must stand down and await instruction before - continuing the engagement. - </p> - </section> - - <section id="target-verification"> - <h3>Target Verification</h3> - <p> - Before engaging any target, members must have visual confirmation of - hostile action or recognised hostile markings. Uncertainty is not - sufficient grounds to open fire. If a member cannot confirm a target - is hostile, they must hold fire and seek clarification from their - commanding officer. - </p> - </section> - </article> - - <article id="code-of-conduct"> - <h2>Code of Conduct</h2> - <p> - The Code of Conduct sets out the standards of behaviour expected of - all members of the 174th Battle Group. It applies across all group - platforms and activities: in-game, on Discord, on any other group - tools, and on external platforms when a member is visibly representing - the group. Membership is conditional on upholding these standards. - </p> - - <section id="expected-behaviour"> - <h3>Expected Behaviour</h3> - <p>All members are expected to:</p> - <ul> - <li> - Treat all members and non-members with respect at all times. - </li> - <li> - Refrain from harassment, hate speech, and discrimination in any - form. - </li> - <li>Follow the orders of ranking members during operations.</li> - <li> - Raise disputes through proper channels rather than through direct - confrontation. - </li> - <li>Be honest with leadership and fellow members.</li> - </ul> - </section> - - <section id="disciplinary-process"> - <h3>Disciplinary Process</h3> - <p> - Discipline is handled on a case by case basis. There are no fixed - tiers; the response is proportionate to the severity and context of - the conduct in question. - </p> - <ul> - <li> - <strong>Informal warning:</strong> Any Rank 3 or above may issue - an informal warning for minor conduct issues. - </li> - <li> - <strong>Formal warning:</strong> A Rank 4 officer or department - head may issue a formal warning for more serious or repeated - issues. - </li> - <li> - <strong>Removal:</strong> Removal from the group requires a vote - of the Rank 5 council. A majority is required to pass. - </li> - </ul> - <p> - Members subject to disciplinary action have the right to present - their account of events before a decision is reached. Inactivity is - not treated as a conduct issue and is governed separately. - </p> - </section> - - <section id="grounds-for-immediate-removal"> - <h3>Grounds for Immediate Removal</h3> - <p> - The following offences result in immediate removal from the group - without prior warning. The council may vote to make the removal - permanent. - </p> - <ul> - <li>Cheating or exploiting game mechanics.</li> - <li> - Doxxing or sharing personal information about another member - without their consent. - </li> - <li>Hate speech or discrimination of any kind.</li> - <li>Threatening or blackmailing members.</li> - </ul> - </section> - - <section id="appeals"> - <h3>Appeals</h3> - <p> - Any member who has received a formal warning or been removed from - the group may appeal the decision to the full Rank 5 council. The - council will review the appeal and reach a final decision by - majority vote. Appeal decisions are binding. - </p> - </section> - </article> - - <article id="leave-of-absence"> - <h2>Leave of Absence</h2> - <p> - A Leave of Absence allows members to step back from group activities - temporarily without losing their standing. Members are encouraged to - give notice rather than simply going quiet, both out of courtesy and - to ensure their absence is not misread as disengagement. - </p> - - <section id="requesting-leave"> - <h3>Requesting Leave</h3> - <p> - Members going on leave should post a notice in the designated - Discord channel. There is no hard notice period; as much advance - notice as possible is appreciated but not required. The notice - should include an expected return date if known, and a rough - duration if not. - </p> - </section> - - <section id="duration"> - <h3>Duration</h3> - <p> - There is no maximum leave duration. Members may be absent for as - long as necessary. If leave extends significantly beyond the - originally stated period, members are encouraged to post an update - in the leave channel so leadership can plan accordingly. - </p> - <p> - Members holding Rank 3 or above must check in at least once per - month during an extended absence. This ensures that leadership - positions can be managed appropriately and that the group is not - left without visibility over its senior members. - </p> - </section> - - <section id="rank-during-leave"> - <h3>Rank During Leave</h3> - <p> - A member's rank is held for them while on leave. Where operational - necessity requires it, a leadership position may be temporarily - filled by another member during the absence. On return, the original - rank is fully restored. - </p> - </section> - - <section id="returning-from-leave"> - <h3>Returning from Leave</h3> - <p> - On returning from leave, members should check in with their - department head or division leader before resuming normal - activities. This ensures they are briefed on anything that changed - during their absence and can be reintegrated smoothly. - </p> - </section> - - <section id="unannounced-absence"> - <h3>Unannounced Absence</h3> - <p> - If a member goes inactive without notice, a Rank 3 or above will - attempt to make contact before any further action is taken. - Unannounced absence is not treated as a conduct issue unless contact - goes unanswered for an extended period, at which point the matter - may be escalated to the disciplinary process. - </p> - </section> - </article> - - <article id="fleet-composition"> - <h2>Fleet Composition</h2> - - <section id="fleet-design-principles"> - <h3>Design Principles</h3> - <p> - The fleet composition must adhere to the following design - principles: - </p> - <ul> - <li> - <strong>Self-Sufficiency:</strong> We are disconnected from UEE - supply lines, so we need to be able to maintain and repair our - ships independently. - </li> - <li> - <strong>Versatility:</strong> Our fleet must be capable of - handling a wide range of missions, from combat to exploration to - trade. - </li> - <li> - <strong>Quality over Quantity:</strong> We will prioritize - maintaining a smaller fleet of high-quality, well-maintained ships - over a larger fleet of lower-quality vessels. - </li> - </ul> - </section> - - <section id="standard-issue-ships"> - <h3>Standard Issue Ships</h3> - <p> - Though we may have access to a variety of ships, the following are - the standard issue ships that we will maintain in our fleet: - </p> - - <section id="space-superiority-fighter"> - <h4>Space Superiority Fighter</h4> - <p> - A fast and agile fighter designed for space combat, capable of - engaging enemy ships and screening for larger vessels. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Scorpius - </li> - <li> - <strong>Vanduul Variant:</strong> - <a href="https://starcitizen.tools/Glaive_(replica)" - >Glaive (replica)</a - >. For missions where we need to blend in with Vanduul forces or - operate in Vanduul-controlled space. - </li> - </ul> - </section> - - <section id="anti-capital-ship"> - <h4>Anti-Capital Ship</h4> - <p> - A heavily armed ship designed to take on larger capital ships, - equipped with powerful weapons such as torpedoes and beam weapons - able to penetrate heavy armor. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Tiburon - </li> - </ul> - </section> - - <section id="ground-bomber"> - <h4>Ground Bomber</h4> - <p> - A ship designed to deliver powerful ordnance against ground - targets. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Retaliator - </li> - <li> - <strong>Scorched-Earth Variant:</strong> - A2 Hercules Starlifter. For missions where we need to deny the - enemy access to resources or territory, capable of delivering - powerful area-of-effect weapons to destroy infrastructure and - resources. - </li> - </ul> - </section> - - <section id="stealth-bomber"> - <h4>Stealth Bomber</h4> - <p> - A ship designed to deliver powerful ordnance against high-value - targets while avoiding detection, equipped with advanced stealth - technology and capable of penetrating enemy defenses to strike - critical infrastructure or capital ships. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Eclipse - </li> - </ul> - </section> - - <section id="dropship"> - <h4>Dropship</h4> - <p> - A ship designed to transport troops and equipment to and from the - battlefield whilst providing close air support and protection, - capable of deploying forces directly into combat zones without the - need for an escort or support. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Valkyrie - </li> - <li> - <strong>Vehicle Variant:</strong> - Asgard. A smaller version of the Valkyrie but with a larger - cargo bay designed to transport vehicles and heavy equipment, - capable of deploying forces directly into combat zones without - the need for an escort or support. - </li> - </ul> - </section> - - <section id="stealth-dropship"> - <h4>Stealth Dropship</h4> - <p> - A ship designed to transport troops and equipment to and from the - battlefield while avoiding detection, equipped with advanced - stealth technology and capable of deploying forces directly into - combat zones without the need for an escort or support. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Prowler - </li> - </ul> - </section> - - <section id="boarding-ship"> - <h4>Boarding Ship</h4> - <p> - A ship designed to transport boarding parties and equipment for - boarding operations, able to quickly and efficiently deploy forces - onto enemy vessels or structures. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Legionnaire - </li> - </ul> - </section> - - <section id="ship-of-the-line"> - <h4>Ship of the Line</h4> - <p> - A heavily armed and armored ship designed to serve as the backbone - of our fleet, capable of engaging enemy capital ships and - providing support for smaller vessels. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Perseus - </li> - </ul> - </section> - - <section id="command-ship"> - <h4>Command Ship</h4> - <p> - A ship designed to serve as the command center for our fleet, - equipped with advanced communication and sensor systems to - coordinate fleet operations and provide situational awareness as - well as dedicated medical facilities to support our personnel - during extended missions. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Idris-K - </li> - <li> - <strong>Patrol Variant:</strong> - Polaris. A lighter and more agile variant designed for - reconnaissance and patrol missions, capable of operating - independently or as part of a larger fleet. - </li> - </ul> - </section> - - <section id="carrier"> - <h4>Carrier</h4> - <p> - A ship designed to serve as a mobile staging point for our fleet, - capable of launching and recovering smaller vessels and providing - support for extended missions. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Kraken - </li> - </ul> - </section> - - <section id="interdictor"> - <h4>Interdictor</h4> - <p> - A ship designed to disrupt enemy communications and sensor - systems, capable of jamming or hacking enemy vessels to gain an - advantage in combat or reconnaissance. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Vanguard Sentinel - </li> - </ul> - </section> - - <section id="ambulance"> - <h4>Ambulance</h4> - <p> - A ship designed to provide medical support and evacuation for our - personnel, equipped with advanced medical facilities and capable - of transporting injured personnel to safety. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Terrapin Medic - </li> - <li> - <strong>Rescue Variant:</strong> - Cutlass Red. For search and rescue operations, capable of - quickly reaching and extracting personnel from dangerous - situations. - </li> - <li> - <strong>Field Hospital Variant:</strong> - Apollo Medivac. For advanced medical care during extended - missions, equipped with state-of-the-art medical facilities and - staffed by highly trained medical personnel. - </li> - </ul> - </section> - - <section id="minelayer"> - <h4>Minelayer</h4> - <p> - A ship designed to deploy mines and other area-denial weapons, - capable of creating defensive perimeters or disrupting enemy - movements. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Nautilus - </li> - </ul> - </section> - - <section id="snub-fighter"> - <h4>Snub Fighter</h4> - <p> - A small and agile fighter designed for hit-and-run tactics, - capable of quickly engaging and disengaging from enemy forces. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Fury - </li> - <li> - <strong>Snub Bomber Variant:</strong> - Fury MX. Designed to deliver overwhelming missile firepower - against enemy targets, capable of quickly engaging and - disengaging from combat while delivering devastating strikes. - </li> - </ul> - </section> - - <section id="anti-swarm-ship"> - <h4>Anti-Swarm Ship</h4> - <p> - A ship designed to engage and destroy smaller aerospace threats - such as enemy fighters and ordnance, equipped with multiple - rapid-fire weapons and advanced targeting systems to effectively - counter many targets in parallel as well as providing overwhelming - suppression against ground targets. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Hammerhead - </li> - </ul> - </section> - - <section id="mining-vessel"> - <h4>Mining Vessel</h4> - <p> - A ship designed to extract and process resources from asteroids - and other celestial bodies, equipped with advanced mining - equipment and storage facilities to support sustained mining - operations. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Mole (Orion once available) - </li> - </ul> - </section> - - <section id="salvage-vessel"> - <h4>Salvage Vessel</h4> - <p> - A ship designed to extract and process resources from derelict - ships and other space debris, equipped with advanced salvage - equipment and storage facilities to support sustained salvage - operations. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Reclaimer - </li> - </ul> - </section> - - <section id="mothership"> - <h4>Mothership</h4> - <p> - A large and heavily equipped ship designed to serve as a mobile - base of operations for our fleet, capable of supporting extended - missions and providing facilities for repair, resupply, and - personnel support. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Ironclad Assault - </li> - </ul> - </section> - - <section id="freighter"> - <h4>Freighter</h4> - <p> - A large cargo ship designed for transporting goods and resources - across the galaxy, equipped with extensive storage facilities and - advanced navigation systems for long-distance travel. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Hull C (Hull E once available) - </li> - </ul> - </section> - - <section id="refueler"> - <h4>Refueler</h4> - <p> - A ship designed to provide fuel and other resources to other - vessels in space, equipped with advanced refueling systems and - storage facilities to support extended operations. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Starfarer Gemini - </li> - </ul> - </section> - - <section id="datarunner"> - <h4>Datarunner</h4> - <p> - A ship designed to transport sensitive data and information across - the galaxy, equipped with advanced security systems and storage - facilities to ensure the safe delivery of critical information. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Herald - </li> - </ul> - </section> - - <section id="exploration-vessel"> - <h4>Exploration Vessel</h4> - <p> - A ship designed for deep space exploration, equipped with advanced - sensors, long-range communication systems, and living quarters to - support extended missions in uncharted regions of the galaxy. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Carrack - </li> - </ul> - </section> - - <section id="repair-ship"> - <h4>Repair Ship</h4> - <p> - A ship designed for repairing and maintaining other vessels in - space, equipped with advanced repair systems, tools, and storage - facilities to support extended operations. - </p> - <ul> - <li> - <strong>Primary Ship:</strong> - Crucible - </li> - </ul> - </section> - </section> - </article> - - <article id="gear-loadouts"> - <h2>Gear Loadouts</h2> - <p> - The following loadouts are the standard issue equipment for members of - the 174th Battle Group, organized by division. - </p> - - <section id="marine-loadouts"> - <h3>Marine Loadouts</h3> - - <section id="heavy-loadout"> - <h4>Heavy Loadout</h4> - <ul> - <li> - <strong>Undersuit:</strong> - Stoneskin Undersuit - </li> - <li> - <strong>Helmet:</strong> - Morozov-SH Helmet - </li> - <li> - <strong>Armor:</strong> - Morozov-SH Core - </li> - <li> - <strong>Arms:</strong> - Morozov-SH Arms - </li> - <li> - <strong>Legs:</strong> - Morozov-SH Legs - </li> - <li> - <strong>Weapons:</strong> - <ul> - <li>Pulverizer LMG</li> - <li>TripleDown Shotgun Pistol</li> - </ul> - </li> - </ul> - </section> - - <section id="scout-loadout"> - <h4>Scout Loadout</h4> - <ul> - <li> - <strong>Undersuit:</strong> - Stoneskin Undersuit - </li> - <li> - <strong>Helmet:</strong> - Arden-SL Helmet - </li> - <li> - <strong>Armor:</strong> - Arden-SL Core - </li> - <li> - <strong>Arms:</strong> - Arden-SL Arms - </li> - <li> - <strong>Legs:</strong> - Arden-SL Legs - </li> - <li> - <strong>Weapons:</strong> - <ul> - <li>P6-LR Sniper Rifle</li> - <li>Yubarev Pistol</li> - </ul> - </li> - </ul> - </section> - - <section id="tactical-loadout"> - <h4>Tactical Loadout</h4> - <ul> - <li> - <strong>Undersuit:</strong> - Stoneskin Undersuit - </li> - <li> - <strong>Helmet:</strong> - DustUp Helmet Tactical - </li> - <li> - <strong>Armor:</strong> - DustUp Core Tactical - </li> - <li> - <strong>Arms:</strong> - DustUp Arms Tactical - </li> - <li> - <strong>Legs:</strong> - DustUp Legs Tactical - </li> - <li> - <strong>Weapons:</strong> - <ul> - <li>Killshot Rifle</li> - <li>S-38 Pistol</li> - </ul> - </li> - </ul> - </section> - </section> - - <section id="navy-loadouts"> - <h3>Navy Loadouts</h3> - - <section id="crew-loadout"> - <h4>Crew Loadout</h4> - <ul> - <li> - <strong>Undersuit:</strong> - Stoneskin Undersuit - </li> - <li> - <strong>Helmet:</strong> - Calico Helmet Tactical - </li> - <li> - <strong>Armor:</strong> - Calico Core Tactical - </li> - <li> - <strong>Arms:</strong> - Calico Arms Tactical - </li> - <li> - <strong>Legs:</strong> - Calico Legs Tactical - </li> - <li> - <strong>Weapons:</strong> - <ul> - <li>Arclight Pistol</li> - </ul> - </li> - </ul> - </section> - - <section id="turret-gunner-loadout"> - <h4>Turret Gunner Loadout</h4> - <p> - Turret gunners are exposed to harsh conditions and potential enemy - fire, so their loadout prioritizes durability and protection while - still allowing for effective operation of their weapons. - </p> - <ul> - <li> - <strong>Undersuit:</strong> - Stoneskin Undersuit - </li> - <li> - <strong>Helmet:</strong> - ADP-mk4 Helmet - </li> - <li> - <strong>Armor:</strong> - ADP-mk4 Core - </li> - <li> - <strong>Arms:</strong> - ADP-mk4 Arms - </li> - <li> - <strong>Legs:</strong> - ADP-mk4 Legs - </li> - <li> - <strong>Weapons:</strong> - <ul> - <li>Arclight Pistol</li> - </ul> - </li> - </ul> - </section> - - <section id="pilot-loadout"> - <h4>Pilot Loadout</h4> - <p> - Pilots are responsible for navigating and controlling the ship, so - their loadout focuses on mitigating g-forces. - </p> - <ul> - <li> - <strong>Undersuit:</strong> - Tailwind Flight Suit - </li> - <li> - <strong>Helmet:</strong> - Tailwind Flight Helmet - </li> - <li> - <strong>Weapons:</strong> - <ul> - <li>Arclight Pistol</li> - </ul> - </li> - </ul> - </section> - </section> - - <section id="auxiliary-loadouts"> - <h3>Auxiliary Loadouts</h3> - - <section id="engineer-loadout"> - <h4>Engineer Loadout</h4> - <ul> - <li> - <strong>Undersuit:</strong> - Novikov Exploration Suit - </li> - <li> - <strong>Helmet:</strong> - Novikov Helmet - </li> - <li> - <strong>Weapons:</strong> - <ul> - <li>Cambio SRT</li> - <li>APX Fire Extinguisher</li> - </ul> - </li> - <li> - <strong>Gadgets:</strong> - <ul> - <li> - Pyro RYT Multi-Tool with TruHold Tractor Beam Attachment - </li> - </ul> - </li> - </ul> - </section> - </section> - </article> - </main> - </body> - <script> - document.addEventListener("DOMContentLoaded", () => { - console.log("DOMContentLoaded"); - - generateTableOfContents(); - - replaceWordsWithLinks(); - }); - - function generateTableOfContents() { - const headings = document.querySelectorAll("h1, h2, h3, h4, h5, h6"); - const toc = document.getElementById("table-of-contents"); - const rootList = document.createElement("ul"); - toc.appendChild(rootList); - - let currentList = rootList; - let currentLevel = 0; - const listStack = {}; - - headings.forEach((heading) => { - const level = parseInt(heading.tagName[1]); - if (!heading.id) { - heading.id = heading.textContent - .trim() - .toLowerCase() - .replace(/[^\w\s-]/g, "") - .replace(/\s+/g, "-"); - } - const tocLink = document.createElement("a"); - tocLink.textContent = heading.textContent; - tocLink.href = `#${heading.id}`; - const tocItem = document.createElement("li"); - tocItem.dataset.level = level; - tocItem.appendChild(tocLink); - - if (currentLevel === 0) { - rootList.appendChild(tocItem); - listStack[level] = rootList; - currentList = rootList; - currentLevel = level; - } else if (level === currentLevel) { - currentList.appendChild(tocItem); - } else if (level > currentLevel) { - const nestedList = document.createElement("ul"); - const lastItem = currentList.lastElementChild; - (lastItem || currentList).appendChild(nestedList); - listStack[level] = nestedList; - currentList = nestedList; - currentLevel = level; - nestedList.appendChild(tocItem); - } else { - currentList = listStack[level] || rootList; - currentList.appendChild(tocItem); - currentLevel = level; - } - }); - - // Add toggle buttons to items that have nested lists - toc.querySelectorAll("li").forEach((li) => { - const nested = li.querySelector(":scope > ul"); - if (nested) { - const toggle = document.createElement("button"); - const liLevel = parseInt(li.dataset.level); - const collapsed = liLevel >= 2; - toggle.className = "toc-toggle"; - toggle.textContent = collapsed ? "▶" : "▼"; - if (collapsed) li.classList.add("toc-collapsed"); - toggle.addEventListener("click", (e) => { - e.preventDefault(); - li.classList.toggle("toc-collapsed"); - toggle.textContent = li.classList.contains("toc-collapsed") - ? "▶" - : "▼"; - }); - li.insertBefore(toggle, li.firstChild); - } - }); - } - - function replaceWordsWithLinks() { - const linkMap = { - "A2 Hercules Starlifter": - "https://starcitizen.tools/A2_Hercules_Starlifter", - "Apollo Medivac": "https://starcitizen.tools/Apollo_Medivac", - Asgard: "https://starcitizen.tools/Asgard", - Carrack: "https://starcitizen.tools/Carrack", - Crucible: "https://starcitizen.tools/Crucible", - "Cutlass Red": "https://starcitizen.tools/Cutlass_Red", - Eclipse: "https://starcitizen.tools/Eclipse", - "Fury MX": "https://starcitizen.tools/Fury_MX", - Fury: "https://starcitizen.tools/Fury", - Hammerhead: "https://starcitizen.tools/Hammerhead", - Herald: "https://starcitizen.tools/Herald", - "Hull C": "https://starcitizen.tools/Hull_C", - "Hull E": "https://starcitizen.tools/Hull_E", - "Idris-K": "https://starcitizen.tools/Idris-K", - "Ironclad Assault": "https://starcitizen.tools/Ironclad_Assault", - Kraken: "https://starcitizen.tools/Kraken", - Legionnaire: "https://starcitizen.tools/Legionnaire", - Mole: "https://starcitizen.tools/Mole", - Nautilus: "https://starcitizen.tools/Nautilus", - Orion: "https://starcitizen.tools/Orion", - Perseus: "https://starcitizen.tools/Perseus", - Polaris: "https://starcitizen.tools/Polaris", - Prowler: "https://starcitizen.tools/Prowler", - Reclaimer: "https://starcitizen.tools/Reclaimer", - Retaliator: "https://starcitizen.tools/Retaliator", - Scorpius: "https://starcitizen.tools/Scorpius", - "Starfarer Gemini": "https://starcitizen.tools/Starfarer_Gemini", - "Terrapin Medic": "https://starcitizen.tools/Terrapin_Medic", - Tiburon: "https://starcitizen.tools/Tiburon", - Valkyrie: "https://starcitizen.tools/Valkyrie", - "Vanguard Sentinel": "https://starcitizen.tools/Vanguard_Sentinel", - "Arclight Pistol": "https://starcitizen.tools/Arclight_Pistol", - "Arden-SL Arms": "https://starcitizen.tools/Arden-SL_Arms", - "Arden-SL Core": "https://starcitizen.tools/Arden-SL_Core", - "Arden-SL Helmet": "https://starcitizen.tools/Arden-SL_Helmet", - "Arden-SL Legs": "https://starcitizen.tools/Arden-SL_Legs", - "Calico Arms Tactical": - "https://starcitizen.tools/Calico_Arms_Tactical", - "Calico Core Tactical": - "https://starcitizen.tools/Calico_Core_Tactical", - "Calico Helmet Tactical": - "https://starcitizen.tools/Calico_Helmet_Tactical", - "Calico Legs Tactical": - "https://starcitizen.tools/Calico_Legs_Tactical", - "DustUp Arms Tactical": - "https://starcitizen.tools/DustUp_Arms_Tactical", - "DustUp Core Tactical": - "https://starcitizen.tools/DustUp_Core_Tactical", - "DustUp Helmet Tactical": - "https://starcitizen.tools/DustUp_Helmet_Tactical", - "DustUp Legs Tactical": - "https://starcitizen.tools/DustUp_Legs_Tactical", - "Killshot Rifle": "https://starcitizen.tools/Killshot_Rifle", - "Morozov-SH Arms": "https://starcitizen.tools/Morozov-SH_Arms", - "Morozov-SH Core": "https://starcitizen.tools/Morozov-SH_Core", - "Morozov-SH Helmet": "https://starcitizen.tools/Morozov-SH_Helmet", - "Morozov-SH Legs": "https://starcitizen.tools/Morozov-SH_Legs", - "P6-LR Sniper Rifle": "https://starcitizen.tools/P6-LR_Sniper_Rifle", - "Pulverizer LMG": "https://starcitizen.tools/Pulverizer_LMG", - "S-38 Pistol": "https://starcitizen.tools/S-38_Pistol", - "Stoneskin Undersuit": "https://starcitizen.tools/Stoneskin_Undersuit", - "TripleDown Shotgun Pistol": - "https://starcitizen.tools/TripleDown_Shotgun_Pistol", - "Yubarev Pistol": "https://starcitizen.tools/Yubarev_Pistol", - "ADP-mk4 Arms": "https://starcitizen.tools/ADP-mk4_Arms", - "ADP-mk4 Core": "https://starcitizen.tools/ADP-mk4_Core", - "ADP-mk4 Helmet": "https://starcitizen.tools/ADP-mk4_Helmet", - "ADP-mk4 Legs": "https://starcitizen.tools/ADP-mk4_Legs", - "Tailwind Flight Helmet": - "https://starcitizen.tools/Tailwind_Flight_Helmet", - "Tailwind Flight Suit": - "https://starcitizen.tools/Tailwind_Flight_Suit", - "Novikov Exploration Suit": - "https://starcitizen.tools/Novikov_Exploration_Suit", - "Novikov Helmet": "https://starcitizen.tools/Novikov_Helmet", - "APX Fire Extinguisher": - "https://starcitizen.tools/APX_Fire_Extinguisher", - "Cambio SRT": "https://starcitizen.tools/Cambio_SRT", - "Pyro RYT Multi-Tool": "https://starcitizen.tools/Pyro_RYT_Multi-Tool", - "TruHold Tractor Beam Attachment": - "https://starcitizen.tools/TruHold_Tractor_Beam_Attachment", - }; - - const walker = document.createTreeWalker( - document.body, - NodeFilter.SHOW_TEXT, - null, - false, - ); - - const nodes = []; - while (walker.nextNode()) nodes.push(walker.currentNode); - - for (const node of nodes) { - const parent = node.parentNode; - if (parent && parent.tagName !== "A") { - let text = node.textContent; - let replaced = false; - - for (const [word, url] of Object.entries(linkMap)) { - const regex = new RegExp(`\\b${word}\\b`, "g"); - if (regex.test(text)) { - const link = document.createElement("a"); - link.href = url; - link.textContent = word; - text = text.replace(regex, link.outerHTML); - replaced = true; - - console.log(`Replaced "${word}" with link to ${url}`); - } - } - - if (replaced) { - const tempDiv = document.createElement("div"); - tempDiv.innerHTML = text; - while (tempDiv.firstChild) { - parent.insertBefore(tempDiv.firstChild, node); - } - parent.removeChild(node); - } - } - } - } - </script> -</html> diff --git a/communities/174bg/handbook/wrangler.jsonc b/communities/174bg/handbook/wrangler.jsonc deleted file mode 100644 index 45a030f..0000000 --- a/communities/174bg/handbook/wrangler.jsonc +++ /dev/null @@ -1,20 +0,0 @@ -{ - "$schema": "https://esm.sh/wrangler@4.90.1/config-schema.json", - "compatibility_date": "2026-03-29", - "account_id": "424d9dabd39849818d9e22366a20e4d6", - "name": "174bg-handbook", - "assets": { - "directory": "./public/", - "not_found_handling": "single-page-application", - }, - "minify": true, - "observability": { - "enabled": true, - }, - "routes": [ - { - "pattern": "handbook.174bg.net", - "custom_domain": true, - }, - ], -} |