anchor.diff:  
   ==== Markdown to Asciidoc: Plugins
   
  +The plugins do the hard work of transforming `md`/`adoc` document to HTML format.
  +
   I changed the
   https://github.com/alxshelepenok/gatsby-starter-lumen/blob/fa2bac05139875408fe9f36bba59289ada3d3d6e/gatsby-config.ts#L92[Markdown plugin `gatsby-transformer-remark`]
   for
  
positive.code: }
  ----
  
  while and example of the Asciidoc document has a predefined header to be used
  and does not provide a plane text of the article. We need to use synopsis field
  to be specifially filled with text.
  The
  https://raw.githubusercontent.com/ochaloup/gatsby-from-scratch/main/hello-world/posts/2022/2022-10-08-a-test/index.adoc[example document]
  is below.
  
  [source,adoc]
  
negative.code: }
  ----
  
  That query could be investigated in GraphQL console (http://localhost:8000/___graphql) as running in dev mode.
  Both plugins places data into `{ nodes }` where the `node` represents one `md`/`adoc` document.
  
  This query example works with page metadata mainly. You can see the difference of how Asciidoc works with a pre-defined
  https://docs.asciidoctor.org/asciidoc/latest/document/header/[metadata structure]
  while Markdown has not get any predefined structure just key-value place under `frontmatter` part.
  On top the MDX plugin offers `excerp` which is a plane (not formatted) text. For Asciidoc I needed to work with special metadata placed in the document.
  
  The https://raw.githubusercontent.com/ochaloup/gatsby-from-scratch/main/hello-world/posts/2022/2022-10-01-first-post/index.mdx[example md document]
  is below.
  
  [source,mdx]
  