ftcorp
      • 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
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners 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
    • 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 Help
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
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners 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
    ## Shipment Status Message **DISCLAIMER** This document is the property of BluJay Solutions and the information contained herein is confidential. This document, either in whole or in part, must not be reproduced or disclosed to others or used for purposes other than that for which it has been supplied without BluJay Solutions’ prior written permission, or, if any part hereof is furnished by virtue of a contract with a third party, as expressly authorized under that contract. ## Table of Contents - Transaction Set Layout for the - ASC X12 - Version - Release - Revision 4. - Date: April - Purpose... - 214 Shipment Status Message......................................................... - Appendix A...................................................................................... - Appendix B..................................................................................... - Appendix C..................................................................................... - Examples ## Purpose... The intent of the SSM is to provide shippers, consignees, and their agents with the status of shipments in terms of dates, times, locations, route and identifying numbers. The Shipment Status (214) is a companion transaction to the Bill of Lading/Ship Manifest (204). ## 214 Shipment Status Message......................................................... **_BluJay Solutions:_** Receiver Id and Qualifier 124215133/01 (DUNS #) The usage codes on the Element Definitions are EDI 004010 Condition Designators. The BluJay Condition Designator is represented under the Values/Comments column. **_ISA and GS Format:_** ISA*00* *00* *01*SAMPLE *01* *040427*1106*U*00400*000000001*1*P*>~ GS*IM*SAMPLE*124215133*20040427*1106*001*X*004010~ **_Segment Id. Name Loop ID._** **Header** B10 Beginning Segment L11 Reference Number L11 Appointment Reference Number N1 Shipper Name N1 Location Name N3 Location Address Information N4 Location Geographic Location LX Sequential Number _LX_ AT7 Status Details _LX_ K1 Remarks _LX_ MS1 Equipment, Shipment, or Real Property Location _LX_ MS2 Equipment or Container Type _LX_ **Segment Information** Segment Id: **B 10** _– Beginning Segment for Shipment Status Message_ General Information: To transmit identifying numbers and other basic data relating to the transaction set_._ **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments B10 01 C 127 1/30 An Reference ID **Pro Number (Invoice Number)** B10 02 C 145 1/30 An Shipmen ID. Number ``` Used *See note ``` B10 03 M 140 02/04 Id SCAC **SCAC Code *See note** ***Note1:** The value is the **Primary Reference Number for BluJay Solutions Load.** This value is turned around from the B204 on the 204 ***Note2:** This value is turned around from the B202 on the 204. **Segment Information** Segment Id: **L11** _– Reference Number_ General Information: To transmit identifying numbers and descriptive information as specified by the reference number qualifier_._ **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments L11 01 C 127 1/30 An Reference Number **Order Number *See Note** L110 2 C 128 02/03 An Reference Num Qualifier ### OQ ***Note:** The value on the L1101 is populated from the 204 OID01. **Segment Information** Segment Id: **L11** _– Appointment Reference Number_ General Information: To transmit the appointment reference number for an appointment This is not required. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments L1101 C 127 1/30 An Reference Number **Appointment Reference Number *See Note** L1102 C 128 02/03 An Reference Num Qualifier ### AO ***Note:** The appointment reference number will only be applied to a load if there is an appointment being sent in via the 214. Also, only one appointment reference number can be passed in per 214. Therefore the pickup and delivery appointment reference numbers cannot be sent in one 214. **Segment Information** Segment Id: **L11** _– Reference Number_ General Information: To transmit identifying numbers and descriptive information as specified by the reference number qualifier. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments L1101 C 127 1/30 An Reference Number **Vehicle Number** L1102 C 128 02/03 An Reference Num Qualifier ### EQ **Segment Information** Segment Id: **N1** _– Shipper Name_ General Information: To identify the shipper associated with the load. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments N101 M 98 02/03 Id Entity Identifier Code. ### SH N102 C 93 01/60 An Name **Shipper name** N103 C 66 01/02 Id Identification Code Qual ### 9 N104 C 67 02/80 An Identification Code **D-U-N-S+4, D-U-N-S Number with Four Character Suffix *See Note** ***Note:** The DUNS+4 is used to indicate different locations of the same organization. For example it can be used to indicate different shipment docks at a particular company. The N104 value is turned around from N104 value on the 204 containing the N1 segment qualified by SH. **Segment Information** Segment Id: **N1** _– Driver Name_ General Information: To identify the driver associated with the load. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments N101 M 98 02/03 Id Entity Identifier Code. ### D N102 C 93 01/60 An Name **Driver Name** N103 C 66 01/02 Id Identification Code Qual ### ZZ N104 C 67 02/80 An Identification Code **Driver Reference** **Segment Information** Segment Id: **N1** _– Location Name_ General Information: To identify a party by type of organization, name and code. This information is required, and should only appear once in the 214. This information is used to determine which location the status code in the AT7 segment should be applied to. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments N101 M 98 02/03 Id Entity Identifier Code. ``` SF = Ship from ST = Ship to *See Note ``` N102 C 93 01/60 An Name **Used *See Note** N103 C 66 01/02 Id Identification Code Qual ### ZZ N104 C 67 02/80 An Identification Code **Used *See Note** ***Note:** This data comes from the N1 segment in the 204 where the N1 segment is qualified by SF or ST. There can only be one of these N1 segments per 214, because this information is used to determine which location the status code in the AT7 segment is associated with. For example if you wanted to put an appointment on the delivery location the delivery location N1 information from the 204 should be location here. **Segment Information** Segment Id: **N 3** _– Location Address Information_ General Information: To specify the location of the named party. This information ``` is required, and should only appear once in the 214. This information is used to determine which location the status code in the AT7 segment should be applied to. ``` **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments N3 01 M 166 01/55 An Address Information ``` Used *See Note ``` N3 02 O 166 01/55 An Address Information ``` Used *See Note ``` ***Note:** This N3 data comes from the corresponding location data in the 204. There can only be one of these N3 segments per 214, because this information is used to determine which location the status code in the AT segment is associated with. For example if you wanted to put an appointment on the delivery location the delivery location N3 information from the 204 should be location here. **Segment Information** Segment Id: **N4** _– Location Geographic Location_ General Information: To specify the geographic place of the named party. This information is required, and should only appear once in the 214. This information is used to determine which location the status code in the AT7 segment should be applied to. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments N4 01 O 19 02/30 An City Name **Used *See Note** N4 02 O 156 02/02 Id State or Province Code ``` Used *See Note ``` N403 O 116 03/15 Id Postal Code **Used *See Note** N404 O 26 02/03 Id Country Code **Used *See Note** ***Note:** This N4 data comes from the corresponding location data in the 204. There can only be one of these N4 segments per 214, because this information is used to determine which location the status code in the AT segment is associated with. For example, if you wanted to put an appointment on the delivery location the delivery location N4 information from the 204 should be location here. ****Note2:** The country codes will need to follow the ISO-3166 2/3 character country code abbreviations standards. The standards can be found at [http://www.iso.org/iso/english_country_names_and_code_elements.](http://www.iso.org/iso/english_country_names_and_code_elements.) **Segment Information** Segment Id: **LX** _– Sequential Number_ General Information: To reference a sequential number in a transaction set. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments LX01 M 554 01/06 N0 Assigned Number Not Used **Segment Information** Segment Id: **AT7** _– Shipment Status Details_ General Information: To specify the status of the shipment in terms of date and time. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments AT701 C 1650 02/02 Id Status Code ***See Appendix A** AT702 C 1651 02/02 Id Shipment Appointment Reason Code ``` *See Appendix B ``` AT703 C 1652 02/02 Id Shipment Appointment Status Code ``` *See Appendix C ``` AT704 C 1651 02/02 Id Shipment Appointment Reason Code ``` Date ``` AT705 C 373 08/08 Dt Date **Time** AT706 C 337 04/08 Tm Time **Time Code** (Time Zone) AT707 O 623 02/02 Id Time Code ***See Note** ***Note:** The **Shipment Appointment Reason Code** will be **NS** unless this message is an appointment. If it is an appointment, then the value will be **NA**. ``` The AT701 and AT702 are paired and used for shipment status messaging. The AT703 and AT704 are paired and are used for appointment messaging. 004010 guide lines require either one pair or the other, never both, to be used in a 214. ``` ``` A matrix of the support status and reason codes is listed on the next page. The supported combinations drive standard workflow actions in the TMS. ``` ``` The shipper may have the ability to use other status and reason codes that you have the ability to send. See the notes on the next page for additional information. ``` The table below contains the AT7 combinations support for the default 214 workflow. **Segment Value Information updated in Transportation Management** AT701 X3 The arrival date at the pickup location AT701 AF The departure date from the pickup location AT701 X1 The arrival date at the delivery location ( **Note** : If this is the final drop the load gets closed) AT701 CD The departure date from the delivery location AT701 AG ETA at the drop stop AT703 AA The appointment date at the pickup location AT703 AB The appointment date at the delivery location AT703 XA The date the appointment was recorded for the pickup location AT703 X9 The date the appointment was recorded for the delivery location AT703 EP The start date of the appointment date at the pickup location * AT703 LP The end date of the appointment date at the pickup location * AT703 ED The start date of the appointment date at the delivery location ** AT703 LD The end date of the appointment date at the delivery location ** * These are used in combination to create an appointment window at the pickup location ** These are used in combination to create an appointment window at the delivery location Many carriers have the ability to send additional AT7 dates that are valid in the X V4010- 214 Document. You are encouraged to send additional AT7 elements that your systems support. Additional code combinations should logically correspond to the AT7 Reason and Status code standards in appendix A, B, & C BluJay’s Transportation Management has a web based configuration tool that allows the Shipper to re-map AT7 combinations to supplement the supported AT7 scenarios. In addition the shipper can use dates of other AT7 scenarios to populate ‘shipper’ configurable dates for visibility When sending AT7 combinations, you **must always** meet the minimum requirements of the BluJay Solutions supported combinations. However, you may duplicate the date in other AT7 status/reason code combinations. If a shipper requires you to use a specific combination of Status and Reason codes, remember that you must still send the BluJay Solutions combination. **Segment Information** Segment Id: **K1** _– Remarks_ General Information: To transmit information in a free-form format for comment or special instruction. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments K101 O 61 01/30 An Trailer Loading Type **LIVE DROP** ***Note:** This data is used when scheduling appointments for shippers who have locations that are governed by Appointment Scheduling. **Segment Information** Segment Id: **MS1** _– Equipment, Shipment, or Real Property Locations_ General Information: To transmit location information for a check call. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments MS101 C 19 02/30 An City Name **Used *See Note** MS102 C 156 02/02 Id State of Province Code ``` Used *See Note ``` MS103 C 26 02/03 Id Country Code **Used *See Note** MS104 C 1654 07 /0 7 Id Longitude Code **Used *See Note** MS105 C 1655 07/07 Id Latitude Code **Used *See Note** ***Note:** The data is recommended if a status code of **AG** has been sent in the AT& segment. This will be used to show where the load is currently located. **Segment Information** Segment Id: **MS2** _– Equipment or Container Owner and Type_ General Information: To transmit the equipment number. **Element Definition** Element Usage Code Data Element # Min/Max Length Field Name Value/ Comments MS201 C 140 02/04 Id Standard Carrier Alpha Code ``` Not Used ``` MS202 C 207 01/10 An Equipment Number **Used** MS203 O 40 02/02 Id Equipment Description Code ``` Not Used ``` MS204 O 761 01/01 No Equipment Number Check Digit ``` Not Used ``` ## Appendix A...................................................................................... **Data Element 1650** A3 Shipment Returned to Shipper A7 Refused by Consignee A9 Shipment Damaged **_AF Carrier Departed Pick-up Location With Shipment AG Estimated Delivery_** AH Attempted Delivery AI Shipment has been Reconsigned AJ Tendered for Delivery AM Loaded on Truck AN Diverted to Air Carrier AP Delivery Not Completed AR Rail Arrival at Destination Intermodal Ramp AV Available for Delivery B6 Estimated to Arrive at Carrier Terminal BA Connecting Line or Cartage Pick-Up BC Storage in Transit C1 Estimated to Depart Terminal Location CA Shipment Cancelled **_CD Carrier Departed Delivery Location_** CL Trailer Closed Out CP Completed Loading at Pick-up Location D1 Completed Unloading at Delivery Location I1 In-Gate J1 Delivered to Connecting Line K1 Arrived at Customs L1 Loading OA Out-Gate OO Paperwork Received – Did not Receive Shipment or Equipment _P1 Departed Terminal Location_ PR U.S. Customs Hold at In-Bond Location R1 Received from Prior Carrier RL Rail Departure from Origin Intermodal Ramp S1 Trailer Spotted at Consignee’s Location SD Shipment Delayed **_X1 Arrived at Delivery Location_** X2 Estimated Date and/or time of Arrival at Consignee’s Location **_X3 Arrived at Pick-up Location_** X4 Arrived at Terminal Location X5 Arrived at Delivery Location Loading dock X6 En Route to Delivery Location X8 Arrived at Pick-up Location Loading Dock XB Shipment Acknowledged ## Appendix B..................................................................................... **Data Element 1651** A1 Missed Delivery A2 Incorrect Address A3 Indirect Delivery A5 Unable to Locate A6 Address Corrected – Delivery Attempted AA Mis-sort AD Customer Requested Future Delivery AE Restricted Articles Unacceptable AF Accident AG Consignee Related AH Driver Related AI Mechanical Breakdown AJ Other Carrier Related AK Damaged, Rewrapped in Hub AL Previous Stop AM Shipper Related AN Holiday – Closed AO Weather or Natural Disaster Related AP Awaiting Export AQ Recipient Unavailable – Delivery Delayed AR Improper International Paperwork AS Hold Due to Customs Documentation Problems AT Unable to Contact Recipient for Broker Information AU Civil Event AV Exceeds Service Limitations AW Past Cut-off Time AX Insufficient Pick-up Time AY Missed Pick-up AZ Alternate Carrier Delivered B1 Consignee Closed B2 Trap for Customer B4 Held for Payment B5 Held for Consignee B8 Improper Unloading Facility or Equipment B9 Receiving Time Restricted BB Held per Shipper BC Missing Documents BD Border Clearance BE Road Conditions BF Carrier Keying Error BG Other BH Insufficient Time to Complete Delivery BI Cartage Agent BJ Customer Wanted Earlier Delivery BK Prearranged Appointment BL Held for Protective Service BM Flatcar Shortage BN Failed to Release Billing BO Railroad Failed to Meet Schedule BP Load Shifted BQ Shipment Overweight BR Train Derailment BS Refused by Customer BT Returned to Shipper C1 Waiting for Customer Pick-up C2 Credit Hold C3 Suspended at Customer Request C4 Customer Vacation C5 Customer Strike C6 Waiting Shipping Instructions C7 Waiting for Customer Specified Carrier C8 Collect on Delivery Required C9 Cash Not Available From Consignee CA Customs (Import or Export) CB No Requested Arrival Date Provided by Shipper CC No Requested Arrival Time Provided by Shipper D1 Carrier Dispatch Error D2 Driver Not Available F1 Non-Express Clearance Delay F2 International Non-carrier Delay HB Held Pending Appointment NA Normal Appointment NS Normal Status P1 Processing Delay P2 Waiting Inspection P3 Production Falldown P4 Held for Full Carrier Load RC Reconsigned S1 Delivery Shortage T1 Tractor With Sleeper Car Not Available T2 Tractor, Conventional, Not Available T3 Trailer Not Available T4 Trailer Not Usable Due to Prior Product T5 Trailer Class Not Available T6 Trailer Volume Not Available T7 Insufficient Delivery Time ****Note** : All reason codes are supported. ## Appendix C..................................................................................... **Data Element 1651** AA Pick-up Appointment Date and/or Time AB Delivery Appointment Date and/or Time AC Estimated Delivery Appointment Date and/or Time ED Deliver No Earlier Than Date and/or Time EP Pick-up No Earlier Than Date and/or Time LD Deliver No Later Than Date and/or Time LP Pick-up No Later Than Date and/or Time X9 Delivery Appointment Secured on This Date and/or Time XA Pick-up Appointment Secured on This Date and/or Time ## Examples **Original 204 that Statuses will be Updated Against** ST*204*0001~ B2**ABCD**51707041**PP~ B2A*00~ PLD*0~ NTE*ZZZ*DRY~ N1*SH*SHIPPER ONE*9*188009216~ N3*641 PLACE DRIVE~ N4*PITTSBURGH*PA*15238*US~ G61*SH*Test Contact*TE*412- 406 - 5811~ N7***********TV****5300~ S5*1*LD*10080.0*L*0*PC*3763.0*E~ G62*10*20070309*Y*2359*ET~ AT5*ZZZ*** CARRIER CANNOT BREAK SEAL~ PLD*0~ N1*SF*PICKUP ONE*ZZ*12522~ N3*3255 TEST DRIVE.~ N4*MONTGOMERY*AL*36108~ G61*CN*CHRIS OBY*TE*5551255555 x420~ G61*A5*GLEN FALLS LOAD PLANNING*TE*8005555555~ OID*2032811***PC*672*L*10080.0*E*3763.0~ S5*2*UL*10080.0*L*0*PC*3763.0*E~ G62*68*20070312*Z*2359*ED~ PLD*0~ N1*ST*DELIVERY ONE*ZZ*63~ N3*1257 NORTH TEST ROAD~ N4*ROMEOVILLE*IL*60446~ OID*2032811***PC*672*L*10080.0*E*3763.0~ L3*10080*G**FC*1139.17****3763*E*0~ SE*33*0001~ **One Shipment Status Update in a 214 for a Delivery Location** ST*214*123~ B10*123456*51707041*ABCD~ L11*2032811*OQ~ N1*SH*SHIPPER ONE*9*188009216~ N1*ST*DELIVERY ONE*ZZ*63~ N3*1257 NORTH TEST ROAD~ N4*ROMEOVILLE*IL*60446*US~ LX*1~ AT7***AB*NA*20060427*0100*ET~ SE*10*123~ **Multiple Shipment Status Updates in a 214 for a Delivery Location** ST*214*123~ B10*123456*51707041*ABCD~ L11*2032811*OQ~ N1*SH*SHIPPER ONE*9*188009216~ N1*ST*DELIVERY ONE*ZZ*63~ N3*1257 NORTH TEST ROAD~ N4*ROMEOVILLE*IL*60446*US ~ LX*1~ AT7*X1*NS***20060427*0427*ET~ MS2**TRAILER0~ LX*2~ AT7*CD*NS***20060427*0427*ET~ SE*13*123~ **Multiple Shipment Status Updates in a 214 for a Pickup Location** ST*214*123~ B10*123456*51707041*ABCD~ L11*2032811*OQ~ N1*SH*SHIPPER ONE*9*188009216~ N1*SF*PICKUP ONE*ZZ*12522~ N3*3255 TEST DRIVE.~ N4*MONTGOMERY*AL*36108*US~ LX*1~ AT7***EP*NA*20060427*0100*ET~ AT7***LP*NA*20060427*0300*ET~ AT7*X3*NS***20060427*0427*ET~ AT7*AF*NS***20060427*0427*ET~ SE*13*123~

    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 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