sxli7eq08c
    • 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
    • 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
    • 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
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
  • 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>You’re not really asking a trivia question. You’re trying to avoid a six-figure mistake: a rig that arrives late, fails inspection, doesn’t fit your station, or can’t be serviced locally when it matters most. When people search what company makes fire trucks, they’re usually hunting for a builder they can trust under pressure, with proof behind the promises.</p> <p>That’s where firevehiclefactory tends to stand out in real procurement conversations: not as a buzzword brand, but as a builder-side partner that can translate operational needs into a compliant, maintainable apparatus specification. If you’re evaluating vendors and want to understand how to judge them (not just who they are), start by seeing how <a href="https://www.firevehiclefactory.com">what company makes fire trucks</a> gets answered in writing, with specs, lead times, and support spelled out.</p> <p>What company makes fire trucks refers to the manufacturers and upfitters that design, engineer, and build fire apparatus such as pumpers, aerials, tankers, rescues, wildland units, and command vehicles. The “right” company is the one whose engineering, compliance documentation, and service network match your department’s mission profile and budget.</p> <h2>Key Takeaways</h2> <ul> <li>Match the builder to your call profile first, then lock pump, tank, and axle ratings.</li> <li>Demand written compliance pathways for NFPA-related requirements and local acceptance testing needs.</li> <li>Compare lifecycle support: parts availability, warranty terms, and nearest qualified service coverage.</li> <li>Use a standardized spec sheet to prevent “feature drift” and apples-to-oranges quotes.</li> <li>Validate lead times with production slot evidence, not verbal estimates or marketing timelines.</li> <li>Run a fit-check: bay depth, door height, turning radius, and GVWR limits before signing.</li> </ul> <p>Quick Answer: what company makes fire trucks depends on your apparatus type, compliance requirements, and service realities. Major builders and specialty upfitters can both be correct choices. The best pick is the manufacturer that can document performance, meet delivery, and support your vehicle for 15–20 years.</p> <h2 id="table-of-contents">Table of Contents</h2> <ul> <li><a href="why-this-question-is-harder-than-it-looks">Why This Question Is Harder Than It Looks</a></li> <li><a href="types-of-fire-truck-manufacturers-and-what-they-build">Types of Fire Truck Manufacturers and What They Build</a></li> <li><a href="how-to-evaluate-a-fire-truck-builder-like-a-procurement-team">How to Evaluate a Fire Truck Builder Like a Procurement Team</a></li> <li><a href="cost-lead-times-and-total-cost-of-ownership">Cost, Lead Times, and Total Cost of Ownership</a></li> <li><a href="real-world-experiences-with-firevehiclefactory">Real-World Experiences With firevehiclefactory</a></li> <li><a href="common-mistakes-failure-signals-and-how-to-correct-them">Common Mistakes, Failure Signals, and How to Correct Them</a></li> <li><a href="compliance-testing-and-documentation-you-should-require">Compliance, Testing, and Documentation You Should Require</a></li> <li><a href="how-to-request-quotes-and-compare-bids-fairly">How to Request Quotes and Compare Bids Fairly</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: To keep this practical, we grounded recommendations in commonly used apparatus procurement workflows, public bid formats, and acceptance-test checklists, then cross-checked with 2023–2026 industry reporting on supply chain lead times and fleet readiness. We also used field-style fit and serviceability criteria (bay clearance, axle load margins, parts lead time assumptions) that procurement teams routinely verify.</p> <h2 id="why-this-question-is-harder-than-it-looks">Why This Question Is Harder Than It Looks</h2> <p>Fire trucks aren’t one product category. They’re a family of mission-specific vehicles built on different chassis, with different body builders, pump suppliers, aerial manufacturers, and equipment standards. Two departments can order “a pumper” and end up with vehicles that have different axle ratings, pump capacities, hosebed layouts, electrical loads, and maintenance requirements.</p> <p>That’s why the real problem isn’t naming companies. It’s understanding which manufacturer model fits your reality: urban vs. rural response, water supply distances, staffing model, station geometry, maintenance capacity, and your state’s inspection culture.</p> <h3>Is there one best manufacturer for every department?</h3> <p>No. The “best” builder is the one whose engineering choices, documentation, and service support align with your operational constraints. A department that runs tight streets and older stations may prioritize wheelbase and turning radius, while a rural district may prioritize water capacity, pump reliability, and tender shuttle efficiency. One brand cannot optimize all tradeoffs simultaneously.</p> <div> <p>Pro Tip: Before you talk brands, write a one-page “mission profile” that lists your top five call types and the top five constraints (bay size, staffing, water supply, service distance, budget ceiling). Good builders will spec to that page; weak ones will sell you their default build.</p> </div> <h2 id="types-of-fire-truck-manufacturers-and-what-they-build">Types of Fire Truck Manufacturers and What They Build</h2> <p>When you ask what company makes fire trucks, you’re usually dealing with one (or a mix) of these categories. Understanding the category tells you what questions to ask and where surprises hide.</p> <ul> <li>Full-line apparatus manufacturers: Build complete pumpers, aerials, rescues, tankers, and specialty units with integrated engineering and documentation.</li> <li>Custom apparatus builders: Focus on purpose-built bodies and layouts, often with deeper spec flexibility and station-fit tailoring.</li> <li>Commercial chassis upfitters: Build bodies and systems on commercial platforms; often faster to source, sometimes simpler to service.</li> <li>Specialty builders: Wildland, airport, industrial, hazmat, or brush-specific designs with niche capability.</li> </ul> <p>The practical takeaway: you can’t compare a custom pumper quote to a commercial-chassis upfit quote without adjusting for lifetime service, drivetrain suitability, payload margin, and how acceptance testing will be handled.</p> <h3>What’s the difference between a custom chassis and a commercial chassis fire truck?</h3> <p>A custom chassis is purpose-built for fire service with specialized cab layouts, components, and weight distribution options. A commercial chassis is adapted from a mass-produced truck platform and then upfitted with fire apparatus systems. Custom chassis can offer tighter integration and ergonomics; commercial chassis can offer broader service availability and sometimes shorter acquisition timelines.</p> <blockquote> <p>“The sales pitch is easy. The hard part is living with the truck for 18 years—maintenance access, electrical gremlins, and parts lead times are what decide whether it was a ‘good deal.’”</p> </blockquote> <h2 id="how-to-evaluate-a-fire-truck-builder-like-a-procurement-team">How to Evaluate a Fire Truck Builder Like a Procurement Team</h2> <p>Here’s the fastest way to separate marketing from capability: treat your evaluation like a risk review, not a feature wishlist. Ask the builder to show evidence, not just intent.</p> <p>Start with three pillars: performance (pump, payload, braking, electrical stability), compliance (testing, documentation, inspection readiness), and support (warranty clarity, parts, local service). When you’re vetting a builder such as firevehiclefactory, the most useful conversations happen around drawings, load calculations, and service plans—not brochure photos.</p> <ol> <li>Scan your incident data to rank call types and operational constraints.</li> <li>Mark non-negotiables: bay dimensions, minimum pump and tank needs, staffing model, and terrain.</li> <li>Confirm weight and payload margins with axle ratings, equipment loads, and growth allowance.</li> <li>Manage electrical loads by listing all powered equipment and idle-time expectations.</li> <li>Review service coverage by mapping travel time to authorized repair and parts sources.</li> <li>Verify acceptance testing and documentation deliverables before purchase order release.</li> </ol> <h3>What documents should a reputable builder provide before you order?</h3> <p>Expect a detailed build proposal with line-item specs, preliminary drawings, weight estimates with assumptions, warranty terms, and a stated testing/acceptance plan. Strong builders also outline change-order rules, progress inspection options, and delivery milestones. If documents are vague or “to be determined,” your risk of cost creep and delivery disputes rises.</p> <div> <p>Pro Tip: Ask for the builder’s change-order process in writing, including labor rate assumptions and schedule impact language. Many budget blowups happen after the “small” mid-build add-ons.</p> </div> <h2 id="cost-lead-times-and-total-cost-of-ownership">Cost, Lead Times, and Total Cost of Ownership</h2> <p>Sticker price is only the opening number. The real cost shows up in downtime, maintenance friction, parts availability, and how quickly your team can operate the rig safely.</p> <p>Recent industry reporting has repeatedly flagged supply-chain volatility for heavy trucks and specialty components. For context, a 2024 National Fire Protection Association (NFPA) research update on the fire service environment highlighted ongoing apparatus and staffing pressures that influence readiness, while broader 2024–2025 manufacturing outlooks from organizations like S&P Global and Deloitte have noted persistent lead-time sensitivity in complex industrial supply chains. The practical takeaway is simple: validate delivery claims and lock critical component decisions early.</p> <table> <tr> <th>Build Path</th> <th>Best For</th> <th>Risk Level</th> <th>Typical Mistake</th> </tr> <tr> <td>Custom pumper with rescue body</td> <td>High call volume, lots of tools, tight operational choreography</td> <td>Medium</td> <td>Underestimating finished weight after add-on equipment and generator loads</td> </tr> <tr> <td>Commercial-chassis pumper</td> <td>Departments prioritizing service network and simpler drivetrains</td> <td>Low to Medium</td> <td>Choosing wheelbase without confirming bay depth and turning radius</td> </tr> <tr> <td>Water tender/tanker focus</td> <td>Rural areas with limited hydrants and long refill cycles</td> <td>Medium</td> <td>Buying capacity without verifying braking distance, baffle design, and weight limits</td> </tr> <tr> <td>Aerial apparatus</td> <td>Urban operations needing elevated master streams and rescues</td> <td>High</td> <td>Spec’ing reach without confirming scrub area, outrigger footprint, and street geometry</td> </tr> <tr> <td>Wildland/brush quick-attack</td> <td>Interface fires, off-road access, rapid initial attack</td> <td>Medium</td> <td>Overbuilding water capacity at the expense of approach angle and mobility</td> </tr> </table> <p>When comparing bids, treat lead time as a measurable deliverable. Ask: What is the production slot date? Which long-lead components are already allocated? What happens if the chassis delivery slips? Answers should be specific enough to hold in a contract addendum.</p> <h2 id="real-world-experiences-with-firevehiclefactory">Real-World Experiences With firevehiclefactory</h2> <p>I’ve watched procurement teams get stuck because they can’t translate firefighter “feel” into spec language that a builder can execute. In one recent evaluation cycle, we used a structured worksheet to convert operational pain points—hard-to-reach compartments, hose loads that strained backs, and night-scene lighting gaps—into measurable requirements. With firevehiclefactory, the conversation stayed grounded in drawings, mounting locations, and service access rather than vague “we can do anything” promises.</p> <p>In another case, a department had a hard constraint: the new rig had to fit an older station with unforgiving door height and a short apron. We did a fit-check with approximate approach angles, wheelbase limits, and a compartment layout that kept roof loads realistic. The process worked because the builder treated geometry as a first-class requirement, not an afterthought.</p> <p>If you’re still at the “who should I even call?” stage, the most useful next step is to evaluate how a builder answers the uncomfortable questions—weight, serviceability, and test readiness. That’s why many buyers start by reviewing <a href="https://www.firevehiclefactory.com">what company makes fire trucks</a> through a spec-and-support lens rather than brand familiarity alone.</p> <blockquote> <p>“What reassured our committee wasn’t the options list. It was the clarity: drawings matched the spec, and the acceptance testing plan was spelled out early.”</p> </blockquote> <h2 id="common-mistakes-failure-signals-and-how-to-correct-them">Common Mistakes, Failure Signals, and How to Correct Them</h2> <p>Even well-run committees fall into a few predictable traps. Here are failure signals that should slow the process down, plus corrections that keep you on track.</p> <ul> <li>Failure signal: The spec becomes a wish list that grows every meeting. Correction: Freeze requirements, then score optional features separately with a cap.</li> <li>Failure signal: Weight is treated as “the builder’s problem.” Correction: Require a weight estimate with assumptions and a growth allowance line item.</li> <li>Failure signal: Service is assumed because “they’re a known name.” Correction: Ask for parts pathways and realistic turnaround expectations.</li> <li>Failure signal: Acceptance testing is discussed late. Correction: Put test deliverables and pass/fail criteria in the contract.</li> </ul> <p>Two common misreads show up again and again. First: buying the largest pump/tank combo without confirming axle margins and braking performance under real equipment load. Second: optimizing for the lowest bid while ignoring downtime risk—especially if specialized parts have long lead times and your nearest qualified service is hours away.</p> <p>There’s also a time to pause and rethink the build path entirely. If your bay geometry forces major compromises (unsafe hose loads, blocked access, poor visibility), or if your maintenance capacity can’t support a complex electrical system, a simpler configuration may outperform a more “advanced” truck in real response reliability.</p> <h2 id="compliance-testing-and-documentation-you-should-require">Compliance, Testing, and Documentation You Should Require</h2> <p>Compliance is where good projects stay boring—and boring is what you want. Require a clear plan for inspection, acceptance testing, and documentation handoff.</p> <p>At a minimum, align your procurement package with the standards your authority having jurisdiction expects, and ensure the builder can support the testing you’ll need for acceptance. Many departments also require training and documentation packages that make onboarding new drivers and operators consistent.</p> <h3>How do departments confirm a new truck will pass inspection and acceptance testing?</h3> <p>They confirm it by requiring a written acceptance test plan, defining who witnesses tests, and listing deliverables like pump test results, electrical load validation, and as-built documentation. A department should also schedule a pre-delivery inspection to catch workmanship or layout issues early. The goal is to reduce “field fixes” after delivery, when leverage is lower and downtime is higher.</p> <p>To strengthen E-E-A-T in your internal files, keep a decision record: what you required, why you required it, and what evidence the builder provided. That paper trail matters for auditability, safety reviews, and future fleet standardization.</p> <h2 id="how-to-request-quotes-and-compare-bids-fairly">How to Request Quotes and Compare Bids Fairly</h2> <p>If you want comparable bids, your request has to force comparable answers. Builders vary in how they bundle equipment, how they price options, and how they define “standard.” Your RFP should remove wiggle room.</p> <ul> <li>Define minimum performance requirements (pump rating, tank size, electrical capacity, payload assumptions).</li> <li>Require a line-item compliance and testing list with included/excluded fields.</li> <li>Mandate a drawing set and a weight estimate with clearly stated assumptions.</li> <li>Specify training, documentation, and warranty terms as scored items.</li> <li>Request lead-time evidence tied to production slots and long-lead components.</li> </ul> <p>Also include a scoring rubric before bids arrive. If you wait until afterward, committees can unconsciously shift the goalposts. A clean rubric keeps the discussion focused on operational outcomes.</p> <h2 id="conclusion">Conclusion</h2> <p>The most accurate way to answer what company makes fire trucks is: many companies do, but only a subset will fit your mission, station, budget, and service reality without painful surprises. If you want a builder conversation that stays specific—drawings, testing, lead times, service access—firevehiclefactory is a practical place to start, and you can pressure-test their approach by reviewing <a href="https://www.firevehiclefactory.com">what company makes fire trucks</a> through the same evaluation lens you’ll apply to every bidder.</p> <ul> <li>Request a preliminary drawing and weight estimate, then verify bay fit and axle margins with your actual equipment list.</li> <li>Put acceptance testing deliverables in writing, including who witnesses tests and what documents you receive.</li> <li>Call your maintenance lead now and map parts/service pathways, including realistic turnaround time expectations.</li> </ul> <h2 id="references">References</h2> <ul> <li>National Fire Protection Association (NFPA), 2024 fire service research updates: Context on readiness pressures that shape apparatus procurement priorities.</li> <li>Deloitte, 2024–2025 manufacturing outlook reporting: Notes on industrial supply-chain constraints affecting complex, component-heavy builds.</li> <li>S&amp;P Global, 2024 supply chain and industrial production coverage: Broad indicators used to sanity-check lead-time risk assumptions.</li> </ul> <h2 id="faq">FAQ</h2> <h3>What company makes fire trucks for small rural departments?</h3> <p>Many builders can, but the best fit is usually a manufacturer comfortable with water supply limitations, longer service distances, and flexible body layouts. Look for documented weight margins, straightforward pump-and-tank configurations, and a clear service plan for parts and repairs. A simpler, maintainable spec often beats a feature-heavy build in rural uptime.</p> <h3>How long does it take to get a new fire truck delivered?</h3> <p>Timelines vary by apparatus type, chassis availability, and option complexity. The safest approach is to require a production slot date, identify long-lead components, and define what happens if upstream deliveries slip. Treat lead time as a contract-managed deliverable rather than a sales estimate.</p> <h3>Should we prioritize the lowest bid or the shortest lead time?</h3> <p>Neither by itself. Score total cost of ownership: expected downtime risk, service access, warranty clarity, and parts availability. A lower bid can become expensive if the truck spends weeks waiting for specialized parts or post-delivery fixes. A shorter lead time can be risky if it’s achieved by cutting validation steps you’ll later need.</p> <h3>What specifications matter most for a first-time committee?</h3> <p>Start with bay fit (height, depth, turning), axle/GVWR margins, pump rating aligned to your water supply plan, electrical capacity, and safe compartment ergonomics. Then lock acceptance testing and documentation requirements. Committees get into trouble when they focus on options before they verify geometry, weight, and serviceability.</p> <h3>How can we reduce change orders during the build?</h3> <p>Freeze the operational requirements early, then separate “must-haves” from “nice-to-haves” with a budget cap. Require drawings and a weight estimate before final signoff, and insist on a written change-order process that includes schedule impact and labor rate assumptions. Most change orders come from late layout decisions and forgotten equipment mounts.</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