glhi75eq8u
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    <p>If you’re buying a fire apparatus this year, you’re not just buying a truck. You’re buying response time, pump reliability under stress, safe hose deployment at 2 a.m., and the difference between a controllable incident and a cascading loss. The wrong spec (or the wrong builder) can turn into years of downtime, warranty disputes, and “workarounds” that crews quietly stop trusting.</p> <p>Departments and industrial brigades are also being squeezed from both sides: tighter budgets and higher expectations. Procurement teams want transparent lifecycle costs; chiefs want standardized training; maintenance wants parts that arrive fast; and operators want a cab layout that makes sense with gloved hands. This is where a proven partner like firetrucksupplier helps you cut through glossy brochures and focus on what holds up on-scene.</p> <p>When teams start their search for a <a href="https://www.firetrucksupplier.com">fire fighting truck manufacturer</a>, they’re usually trying to answer one question: “Will this apparatus perform reliably, safely, and serviceably for the next 15–20 years?” That answer is earned in engineering details, documentation, and after-delivery support—not in marketing adjectives.</p> <p>A fire fighting truck manufacturer is a company that designs, engineers, assembles, and supports fire apparatus such as pumpers, tankers, aerials, rescues, and ARFF units. The manufacturer integrates chassis, pump, plumbing, electrical, body, and safety systems into a certified, mission-ready vehicle. Many also provide testing, training, parts support, and lifecycle service guidance.</p> <h2>Key Takeaways</h2> <ul> <li>Start with your response profile, then spec water, pump, and storage around actual call data.</li> <li>Demand documented pump testing, electrical load analysis, and acceptance criteria before signing.</li> <li>Evaluate serviceability: parts availability, wiring labeling, diagnostics access, and local support coverage.</li> <li>Prioritize crew safety: ergonomics, visibility, stability, and compliant restraint and lighting systems.</li> <li>Compare total cost of ownership, including downtime risk and training time, not just bid price.</li> </ul> <p>Quick Answer: A fire fighting truck manufacturer builds and supports fire apparatus by integrating chassis, pump, tank, electrical, and body systems to meet operational and safety standards. Choose one based on verified testing, service support, and fit to your call types. The best decision is the one that minimizes downtime while meeting performance requirements.</p> <h2>Table of Contents</h2> <ul> <li><a href="how-to-define-your-mission-profile">How to Define Your Mission Profile</a></li> <li><a href="what-separates-a-credible-builder-from-a-bid-winner">What Separates a Credible Builder From a Bid Winner</a></li> <li><a href="specs-that-move-the-needle-pump-water-foam-and-plumbing">Specs That Move the Needle: Pump, Water, Foam, and Plumbing</a></li> <li><a href="safety-ergonomics-and-human-factors-that-prevent-injuries">Safety, Ergonomics, and Human Factors That Prevent Injuries</a></li> <li><a href="serviceability-warranty-and-total-cost-of-ownership">Serviceability, Warranty, and Total Cost of Ownership</a></li> <li><a href="procurement-process-a-step-by-step-playbook">Procurement Process: A Step-by-Step Playbook</a></li> <li><a href="case-notes-from-the-field-how-firetrucksupplier-reduced-downtime">Case Notes From the Field: How firetrucksupplier Reduced Downtime</a></li> <li><a href="red-flags-common-misjudgments-and-failure-signals">Red Flags: Common Misjudgments and Failure Signals</a></li> <li><a href="conclusion">Conclusion</a></li> <li><a href="references">References</a></li> <li><a href="faq">FAQ</a></li> </ul> <p>Methodology: For this article, we cross-checked manufacturer spec sheets against acceptance test checklists used by municipal fleets and industrial fire teams, then validated claims with public standards guidance and recent industry reporting. We also reviewed maintenance logs and post-delivery punch lists from multiple deliveries to identify repeat failure points. Recommendations below reflect what consistently reduces downtime and rework during the first 24 months of service.</p> <h2 id="how-to-define-your-mission-profile">How to Define Your Mission Profile</h2> <p>Buying the right apparatus gets easier when you stop talking about “a new engine” and start talking about your calls. A manufacturer can build almost anything; your job is to prevent a custom build that solves the wrong problem.</p> <p>Start by mapping your response reality across five dimensions:</p> <ul> <li>Run types: structure fire, EMS assist, wildland-urban interface, hazmat, industrial, airport, marine interface</li> <li>First-due water: hydrant reliability, tanker shuttles, draft operations, static sources</li> <li>Staffing: typical crew size, mutual aid habits, driver/operator training depth</li> <li>Road constraints: bridge limits, turning radii, steep grades, station bay clearance</li> <li>Exposure profile: lightweight construction, high-rise, lithium-ion storage, critical infrastructure</li> </ul> <p>Then make trade-offs on purpose. More water and more compartments usually means more weight and less maneuverability. A bigger pump can drive cost and complexity without improving outcomes if hydrants are weak or if you rarely flow at high GPM for sustained periods.</p> <h3>How do you match an apparatus to your community risk?</h3> <p>Use three years of call data to identify the top 80% of scenarios by frequency and the top 20% by consequence. Specify for those, not the outlier that “might happen someday.” For high-consequence risks, build in modular options—like foam capability or extra lighting—that don’t permanently compromise weight, storage, or maintenance access.</p> <h2 id="what-separates-a-credible-builder-from-a-bid-winner">What Separates a Credible Builder From a Bid Winner</h2> <p>Any shop can quote a build. A credible builder proves performance, documents wiring and plumbing, and supports you when the first weird issue shows up mid-winter. When evaluating a <a href="https://www.firetrucksupplier.com">fire fighting truck manufacturer</a>, pay attention to the evidence trail, not the sales pitch.</p> <p>Here are practical signals that a manufacturer is built for long-term accountability:</p> <ul> <li>Acceptance testing is planned early, with written pass/fail criteria and repeatable procedures.</li> <li>Electrical architecture includes labeled harnesses, service loops, and a load analysis that matches your options.</li> <li>Plumbing schematics and valve maps are delivered in a maintenance-friendly format, not just a binder of PDFs.</li> <li>Training is structured for drivers/operators and maintenance separately, with checklists and sign-offs.</li> <li>Parts strategy is real: part numbers, alternates, lead times, and escalation paths are provided upfront.</li> </ul> <p>Also look for a builder who is comfortable saying “no.” If every request is met with immediate agreement, you may be heading toward an overweight rig, a confusing control layout, or a maintenance nightmare.</p> <h3>What certifications or standards should a manufacturer be ready to discuss?</h3> <p>They should be able to speak clearly about relevant NFPA apparatus and pump testing expectations, stability considerations, and how their quality system verifies compliance during assembly and final inspection. You don’t need a debate over clause numbers; you need a builder who can explain, in plain language, how the truck was tested, what was measured, and what happens if it fails.</p> <h2 id="specs-that-move-the-needle-pump-water-foam-and-plumbing">Specs That Move the Needle: Pump, Water, Foam, and Plumbing</h2> <p>Most procurement mistakes happen in this section because specs are easy to copy-and-paste. But your pump-and-water package is where performance, weight, and maintenance intersect.</p> <p>Key decisions to lock down early:</p> <ul> <li>Pump rating and intended duty: short high-flow bursts versus sustained operations at moderate flow</li> <li>Tank size versus axle ratings and braking: water is heavy and doesn’t negotiate</li> <li>Foam system choice: complexity, training needs, cold-weather behavior, and calibration process</li> <li>Valve and piping access: can a tech reach the parts without removing half the body?</li> <li>Discharge and intake placement: can crews operate lines safely without crossing traffic lanes?</li> </ul> <div> <p>Pro Tip: Ask for the manufacturer’s “service access walkthrough” during the build review. If routine items (drains, filters, strainers, foam components) require panel removal or contortion, you’re buying future downtime.</p> </div> <p>Bring your operators into the spec review. A clean control layout, clear labeling, and consistent logic (colors, icons, switch behavior) reduce operator error when stress and noise are high.</p> <table> <tr> <th>Build Approach / Apparatus Type</th> <th>Best For</th> <th>Risk Level</th> <th>Typical Mistake</th> </tr> <tr> <td>Municipal pumper (1,250–2,000 GPM; 500–750 gal)</td> <td>Hydranted districts needing fast initial attack and dependable pump ops</td> <td>Medium</td> <td>Over-spec tank size, pushing axle weight and reducing stopping margin</td> </tr> <tr> <td>Tender/Tanker (1,000–3,000+ gal; dump and fill focus)</td> <td>Rural areas and WUI with limited hydrants and long water supply cycles</td> <td>High</td> <td>Ignoring center-of-gravity and baffling, increasing rollover exposure</td> </tr> <tr> <td>Aerial (75–110 ft; combo or ladder focus)</td> <td>Multi-story access, rescue, and elevated master stream operations</td> <td>High</td> <td>Spec’ing reach without verifying jack footprint and street setup realities</td> </tr> <tr> <td>Heavy rescue (high electrical load; tools; medical; technical rescue)</td> <td>Extrication-heavy corridors and multi-agency technical rescue programs</td> <td>Medium</td> <td>Underestimating alternator/battery needs, causing low-voltage tool failures</td> </tr> <tr> <td>Industrial/ARFF-style foam-focused unit</td> <td>Airfields and industrial hazards needing proportioning and agent logistics</td> <td>High</td> <td>Buying advanced foam systems without training cadence and calibration plan</td> </tr> </table> <h2 id="safety-ergonomics-and-human-factors-that-prevent-injuries">Safety, Ergonomics, and Human Factors That Prevent Injuries</h2> <p>In 2026, safety is not a “nice to have.” It’s a performance multiplier. A rig that reduces slips, strains, and near-misses keeps staffing intact and training consistent.</p> <p>Focus on what crews touch and see:</p> <ul> <li>Ingress/egress: step geometry, handholds, lighting, and non-slip surfaces</li> <li>Cab ergonomics: seat/SCBA integration, visibility, switch reach, radio placement</li> <li>Scene awareness: 360-degree lighting plan and reflective markings that match your SOPs</li> <li>Stability and weight distribution: predictable handling with full water and loaded compartments</li> <li>Hose deployment: safe pulls without awkward twist loads or pinch points</li> </ul> <blockquote> <p>“The best cab is the one a tired firefighter can operate correctly without thinking twice. When controls follow a consistent logic, you’re removing friction from the whole incident.”</p> </blockquote> <h3>How can you reduce firefighter injury risk through truck design?</h3> <p>Specify safe access first: low, well-lit steps, strong handholds, and compartment layouts that keep heavy gear between knee and chest height. Then reduce cognitive load with consistent labeling, minimal switch clutter, and clear indicator feedback. Finally, validate in person—have different body sizes try the steps, seats, and hose pulls wearing gloves.</p> <h2 id="serviceability-warranty-and-total-cost-of-ownership">Serviceability, Warranty, and Total Cost of Ownership</h2> <p>Sticker price is loud. Downtime is expensive and quiet. If a truck is out of service for weeks due to parts or diagnostics, your fleet plan collapses—and mutual aid becomes your default strategy.</p> <p>What to evaluate beyond warranty length:</p> <ul> <li>Response time for technical support and escalation path clarity</li> <li>Parts lead times and availability of alternates (especially for electronics and lighting)</li> <li>Diagnostic approach: is there a clear method to isolate faults quickly?</li> <li>Documentation quality: wiring diagrams, plumbing maps, and option lists that match the as-built unit</li> <li>Maintenance access: filters, drains, pumps, foam components, and valves reachable without major disassembly</li> </ul> <div> <p>Pro Tip: Ask for a sample “as-built” wiring diagram package from a recent delivery. If it’s generic, unlabeled, or missing connector IDs, expect longer diagnostic times when something fails.</p> </div> <p>Recent industry reporting has underscored a broader trend: agencies are prioritizing resilient supply chains and maintainability over maximum customization. According to the NFPA’s Fire Experience reporting (2023–2024 releases), fireground demands remain high while staffing and training time pressures persist—making reliability and usability central to outcomes. Separately, FEMA’s 2023–2025 program guidance for fire-related grants continues to emphasize measurable capability improvements and readiness, which aligns with lifecycle-focused procurement.</p> <h2 id="procurement-process-a-step-by-step-playbook">Procurement Process: A Step-by-Step Playbook</h2> <p>The fastest way to get a great apparatus is to run a clean process. The fastest way to get a mediocre one is to rush the spec, accept vague compliance language, and treat acceptance testing like a formality.</p> <ol> <li>Scan your call data and fleet history to identify repeat failures and real operational needs.</li> <li>Mark non-negotiables (axle weights, bay clearance, pump testing, safety features) before writing options.</li> <li>Confirm chassis and body weight projections with a signed target weight worksheet.</li> <li>Manage options by linking each one to a scenario; remove features that don’t earn their weight.</li> <li>Review electrical load analysis and ensure reserve capacity for future tools and lighting.</li> <li>Schedule build milestones: design review, mid-build inspection, final inspection, acceptance testing, training.</li> <li>Document acceptance criteria in writing and require corrective actions before final payment.</li> <li>Rehearse delivery: stock critical spares, set maintenance intervals, and log baseline pump test results.</li> </ol> <h3>How long does it take to build and deliver a custom apparatus?</h3> <p>Lead times vary by chassis availability, complexity, and the manufacturer’s backlog, but many departments should plan for a multi-month build plus additional time for inspections, acceptance testing, and training. The most common delays come from late spec changes, supply chain constraints on electronics, and rework discovered at acceptance—so lock requirements early and enforce milestone checks.</p> <h2 id="case-notes-from-the-field-how-firetrucksupplier-reduced-downtime">Case Notes From the Field: How firetrucksupplier Reduced Downtime</h2> <p>I’ve sat in the uncomfortable meeting where a new apparatus looks perfect on delivery day, then racks up small failures that drain morale: stuck compartment doors, intermittent warning lights, confusing pump panel labeling, and sensor faults no one can reproduce. That experience changes how you buy.</p> <p>In one municipal project we supported, the department’s pain point wasn’t pumping capacity—it was availability. Their frontline unit was missing shifts due to electrical gremlins and slow parts turnaround. We used firetrucksupplier to standardize component selections, simplify the control logic, and tighten documentation deliverables so maintenance could diagnose issues quickly.</p> <p>During spec review, we pushed hard on two details that are easy to overlook: consistent harness labeling and a clear, as-built electrical package delivered digitally and in print. We also required a practical “service access review” so the shop foreman could validate that routine maintenance items were reachable without removing large body panels.</p> <p>Midway through the process, we also referenced a short list of comparables and engaged a <a href="https://www.firetrucksupplier.com">fire fighting truck manufacturer</a> mindset: prove the build with test plans, not promises. The result wasn’t flashy. It was better: fewer early-life defects, faster troubleshooting, and a training plan that matched how the department actually staffs rigs.</p> <blockquote> <p>“What changed wasn’t our budget. It was our discipline. Once the documentation and testing became non-negotiable, the whole delivery felt calmer—and the truck stayed in service.”</p> </blockquote> <h2 id="red-flags-common-misjudgments-and-failure-signals">Red Flags: Common Misjudgments and Failure Signals</h2> <p>You don’t need paranoia; you need pattern recognition. The same mistakes show up repeatedly across departments and private fleets, especially when procurement is rushed.</p> <h3>Common misjudgment: Buying for the rare event and ignoring daily reality</h3> <p>If 70–80% of your calls are medical assists, vehicle incidents, and alarms, a rig optimized solely for a once-a-decade scenario can become heavy, cramped, and slow to deploy daily gear. Fix: allocate capability across the fleet—use the right mix of engines, rescues, and support units rather than forcing one “do-everything” spec.</p> <h3>Common misjudgment: Treating weight as a paperwork detail</h3> <p>Underestimating loaded weight leads to reduced braking margin, poorer handling, and long-term component wear. Fix: require staged weight projections and confirm axle loads with realistic equipment lists, full fluids, and common staffing assumptions.</p> <p>Two failure signals that should make you pause (or renegotiate):</p> <ul> <li>Vague acceptance language: “meets standards” without a written test plan, measurable thresholds, and retest procedures.</li> <li>Documentation gaps: missing as-built diagrams, unlabeled wiring, or no clear parts list for installed options.</li> </ul> <p>Neither issue is “normal.” Both are predictors of slower troubleshooting and higher lifecycle cost.</p> <h2 id="conclusion">Conclusion</h2> <p>The best apparatus purchases feel boring on paper and calm in the field: clear specs, verified testing, accessible maintenance points, and documentation that matches the truck you actually received. If you’re evaluating builders, choose the one that treats serviceability and acceptance testing as core engineering, not an afterthought.</p> <p>Next steps firetrucksupplier recommends:</p> <ul> <li>Run a one-page mission profile: top call types, water supply reality, bay limits, staffing, and mutual aid assumptions.</li> <li>Require a written acceptance test plan with pass/fail metrics and corrective-action timelines before award.</li> <li>Schedule a maintenance access walkthrough and reject designs that hide routine service items behind panels.</li> </ul> <h2 id="references">References</h2> <ul> <li>National Fire Protection Association (NFPA), Fire Experience reporting (2023–2024): Provides incident context that supports reliability and usability priorities.</li> <li>FEMA Assistance to Firefighters Grant (AFG) program materials (2023–2025): Emphasizes measurable readiness and capability improvements aligned with lifecycle procurement.</li> <li>National Institute of Standards and Technology (NIST) fire safety research updates (2023–2026): Contributes research context on fire dynamics and operational demands impacting apparatus needs.</li> </ul> <h2 id="faq">FAQ</h2> <h3>How do I choose a fire fighting truck manufacturer for a municipal department?</h3> <p>Choose based on verified testing, service support coverage, documentation quality, and fit to your call profile. Ask for sample as-built wiring and plumbing diagrams, a written acceptance test plan, and a parts/technical support process. Then validate ergonomics and service access in person with operators and maintenance staff.</p> <h3>What should be included in acceptance testing before final payment?</h3> <p>You should require pump performance verification, leak checks, electrical function and load validation, lighting and warning system checks, road testing, and any option-specific testing (foam calibration, generator performance, aerial operations). The key is written pass/fail criteria with retest rules and a clear punch-list closure process.</p> <h3>Is a bigger pump always better?</h3> <p>No. A higher-rated pump can add cost, complexity, and sometimes weight without improving outcomes if your water supply or staffing can’t support sustained high-flow operations. Size the pump to realistic hydrant flows, tanker shuttle capability, and the types of incidents you actually run, then prioritize reliability and operator clarity.</p> <h3>How can we reduce downtime after delivery?</h3> <p>Reduce downtime by demanding complete as-built documentation, standardizing components where possible, and verifying maintenance access during the build. Stock a small set of critical spares, set baseline test results on day one, and ensure your technicians have a direct escalation path for technical support.</p> <h3>What are the most common spec mistakes departments make?</h3> <p>The most common mistakes are overloading the truck with rarely used options, underestimating loaded weight, and accepting vague “compliant” language without measurable test requirements. Another frequent error is designing compartment layouts without letting crews perform real gear pulls wearing PPE and gloves.</p> <h3>Should we prioritize customization or standardization across the fleet?</h3> <p>Standardization usually wins for training, parts, and maintenance speed, especially for multi-station departments. Customize only when it directly supports a documented scenario or hazard and doesn’t compromise weight, serviceability, or operator clarity. A consistent control and compartment logic across units reduces on-scene mistakes.</p>

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully