anchor.diff:  ...
   ----
   
  -in case of `asciidoc` it's needed to get all data, parse it and group it in typescript afterwards. See my way here:
  +Thus for `asciidoc` it's needed to get all data, parse it and group it in typescript afterwards. See my way here:
  +
   * get all data: https://github.com/ochaloup/blog.chalda.cz/blob/efdec3c4e5b84a9ed0ff35c4f6c72b9ca4e5e242/src/hooks/use-tags-list.ts#L14
   * parse and group to get `totalCount`: https://github.com/ochaloup/blog.chalda.cz/blob/efdec3c4e5b84a9ed0ff35c4f6c72b9ca4e5e242/src/utils/group-tags.ts#L11
   
  
positive.code: yarn start
  ----
  
  The Lumen is started at localhost in dev mode.
  The site can be accessed at http://localhost:8000
  (graphql at http://localhost:8000/___graphql).
  
  === React GraphQL and Gatsby
  
  All data that Gatsby works with comes through the GraphQL processing (i.e., React).
  The Markdown and Asciidoc plugins processes the documents and the results are consumed with GraphQL queries.
  Components queries _title_, _tags_, _generated HTML_ etc. That data is places to pages dependent on the visual demands.
  
  The most of the work for met on moving from Markdown to Asciidoc was the remapping of the Markdown GraphQL queries that the _Lumen Starter_ uses and to change them for Asciidoc.
  
  My work with tutorial tried to work with `adoc` and `md` data (MDX plugin is used) side by side.
  You can see e.g., here https://github.com/ochaloup/gatsby-from-scratch/blob/main/hello-world/src/pages/index.js#L40
  
  [source,graphql]
  ----
  
negative.code: }
  ----
  
  The
  https://raw.githubusercontent.com/ochaloup/gatsby-from-scratch/main/hello-world/posts/2022/2022-10-08-a-test/index.adoc[example adoc document]
  is below.
  
  [source,adoc]
  