                          | #{Page.type.charAt(0).toUpperCase() + Page.type.slice(1)}
              nav(role="navigation")
                  li(class={active: Page.active.home}): a(href="/") Home
                  li(class={active: Page.active.docs}): a(href="/docs") Docs
                  li: a(href="https://api.spacy.io/displacy", target="_blank") Demo
                  li(class={active: Page.active.blog}): a(href="/blog") Blog
              main#content
                  block
              script(src="/resources/js/prism.min.js")
              // Details polyfill
 
</s> remove   - var url = "https://api.spacy.io/displacy/?full=" + sentence.replace(/\s+/g, "%20")
 </s> add   - var url = "https://displacy.spacy.io/displacy/?full=" + sentence.replace(/\s+/g, "%20") </s> remove     - var url = "https://api.spacy.io/displacy/?full=" + sentence.replace(/\s+/g, "%20")
 </s> add     - var url = "https://displacy.spacy.io/displacy/?full=" + sentence.replace(/\s+/g, "%20") </s> remove Lets take the example sentence on https://api.spacy.io/displacy/index.html
 </s> add Lets take the example sentence on https://displacy.spacy.io/displacy/index.html </s> remove         p What I'm particularly excited about is the potential for displaCy as an #[a(href="https://api.spacy.io/displacy/?manual=Robots%20in%20popular%20culture%20are%20there%20to%20remind%20us%20of%20the%20awesomeness%20of%20unbounded%20human%20agency" target="_blank") annotation tool]. It may seem unintuitive at first, but I think it will be much better to annotate texts the way the parser operates, with a small set of actions and a stack, than by selecting arcs directly. Why? A few reasons:
 </s> add         p What I'm particularly excited about is the potential for displaCy as an #[a(href="https://displacy.spacy.io/displacy/?manual=Robots%20in%20popular%20culture%20are%20there%20to%20remind%20us%20of%20the%20awesomeness%20of%20unbounded%20human%20agency" target="_blank") annotation tool]. It may seem unintuitive at first, but I think it will be much better to annotate texts the way the parser operates, with a small set of actions and a stack, than by selecting arcs directly. Why? A few reasons: </s> remove p #[a(href="https://api.spacy.io/displacy") displaCy] lets you peek inside spaCy's syntactic parser, as it reads a sentence word-by-word. By repeatedly choosing from a small set of actions, it links the words together according to their syntactic structure. This type of representation powers a wide range of technologies, from translation and summarization, to sentiment analysis and algorithmic trading.  #[a(href="/blog/displacy") Read more.]
 </s> add p #[a(href="https://displacy.spacy.io/displacy") displaCy] lets you peek inside spaCy's syntactic parser, as it reads a sentence word-by-word. By repeatedly choosing from a small set of actions, it links the words together according to their syntactic structure. This type of representation powers a wide range of technologies, from translation and summarization, to sentiment analysis and algorithmic trading.  #[a(href="/blog/displacy") Read more.]
                li: a(href="https://displacy.spacy.io/displacy", target="_blank") Demo
                          | #{Page.type.charAt(0).toUpperCase() + Page.type.slice(1)}
              nav(role="navigation")
                  li(class={active: Page.active.home}): a(href="/") Home
                  li(class={active: Page.active.docs}): a(href="/docs") Docs
                li: a(href="https://displacy.spacy.io/displacy", target="_blank") Demo
                  li(class={active: Page.active.blog}): a(href="/blog") Blog
              main#content
                  block
              script(src="/resources/js/prism.min.js")
              // Details polyfill
keep keep keep keep replace keep keep keep keep keep
 move displacy to its own subdomain 
website/src/jade/header.jade