anchor.diff:  ==== Markdown to Asciidoc: GraphQL
   
   The next step was to change all the GraphQL queries from Markdown structure to Asciidoc one.
  -It's quite similar while a bit different in details.
  -What's the worse was a fact that Markdown header properties is capable to work with a list
  -while asciidoc consider all header properties as a string. I need to do quite a boring manual
  -parsing of e.g., tags.
  -
  -The GraphQL queries are all over the code so it was quite boresome work. The good thing was there are tests (`yarn test`)
  +The GraphQL queries are quite similar while a bit different in details.
  +
  +The GraphQL queries are spread all over the code so it was quite boresome. The good thing was there are tests (`yarn test`)
   that helped me to undrestand what I forgot to cover. An example of such difference of the query is covered above
  -or you can check github
  +or you can check the github links here:
   
   * `md` remark plugin : https://github.com/alxshelepenok/gatsby-starter-lumen/blob/fa2bac05139875408fe9f36bba59289ada3d3d6e/src/hooks/use-categories-list.ts#L12
   * `adoc` asciidoc plugin : https://github.com/ochaloup/blog.chalda.cz/blob/efdec3c4e5b84a9ed0ff35c4f6c72b9ca4e5e242/src/hooks/use-categories-list.ts#L12
  
positive.code: }
  ----
  
  That query could be investigated in GraphQL console (http://localhost:8000/___graphql).
  The data generated by both plugins are structured in a bit different form
  that comes for example from fact that Asciidoc works with a pre-defined
  https://docs.asciidoctor.org/asciidoc/latest/document/header/[header metadata]
  while Markdown with no specific spec here.
  
  Both plugins retrieves data from the `{ nodes }` where the `node` represents one `md`/`adoc` document.
  
  Then the MDX plugin offers excerp which is a plane text of the article and then
  metadata is represented at header in key/value form.
  The https://raw.githubusercontent.com/ochaloup/gatsby-from-scratch/main/hello-world/posts/2022/2022-10-01-first-post/index.mdx[example document]
  is below.
  
  [source,mdx]
  
negative.code: that's in https://github.com/ochaloup/blog.chalda.cz/blob/efdec3c4e5b84a9ed0ff35c4f6c72b9ca4e5e242/src/utils/highlightCode.ts[highlightCode.ts].
  The `hightlight.js` was added to
  https://github.com/ochaloup/blog.chalda.cz/blob/efdec3c4e5b84a9ed0ff35c4f6c72b9ca4e5e242/package.json#L70[`package.json`]
  and then the utility function is called from
  https://github.com/ochaloup/blog.chalda.cz/blob/efdec3c4e5b84a9ed0ff35c4f6c72b9ca4e5e242/src/components/Post/Post.tsx#L27[the template of posts].
  
  
  ==== Markdown to Asciidoc: CSS Style changes
  
  This part is not finished and not examined well. I needed to adjust styling that the default one does not work
  nicely with HTML generated by Asciidoc transformer.
  
  The base was adding some asciidoctor styles that I borrowed from github of
  https://github.com/asciidoctor/asciidoctor-stylesheet-factory/tree/main/sass[asciidoctor-stylesheet-factory].
  