anchor.diff:  
   * `public/` is not to be touched. it's automatically generated and it contains output of the build process (part of `.gitignore`)
   * `static/` contains data that are copied to `public/` as they are. used for placing image files etc.
  -* `content/` is not a standard Gatsby directory but it's usually used by the plguins (`md`, `adoc`). it's configured at
  +* `content/` is not a standard Gatsby directory but it's usually used by the plugins (`md`, `adoc`). it's configured at
      https://github.com/alxshelepenok/gatsby-starter-lumen/blob/3a6dbc17ca00ad4ccc84e82a840b59c3824ab709/gatsby-config.ts#L20[gatsby-config.ts]
   * `src/` directory contains code
   ** `src/pages/` contains pages that's are generated directly at the path (e.g., it's a place for `index.js`)
   ** `src/templates` templates used in programatically build pages
  -** `src/compontents` react directory, contains react components that can be used within `templates`
  +** `src/components` react directory, contains react components that can be used within `templates`
   ** `src/hooks/` react directory, hooks that can be invoked from components retrieving data, &hellip;
   ** `src/utils/` react directory, utilities
   ** `src/types/` react directory, for typescript types definitions
  
positive.code: 
  ==== A JavaScript project
  
  As non-javascript developer I want to start with few things around the JS projects in general.
  
  * dependencies are defined in `package.json`
  * JS world uses many package managers - default `npm`, better `yarn`, newer a and faster `pnpm`
    (I chose `yarn`)
  * `yarn install` downloads `js` dependencies and places them under `$PWD/node_modules`
  * when dependencies are installed a `lock` files (`yarn.lock`, `package-lock.json`) are created.
    They ensures the same versions of the libraries are used when building subsequently on other environments.
    They are https://stackoverflow.com/questions/44552348/should-i-commit-yarn-lock-and-package-lock-json-files[recommended to be pushed to github].
  * when working with TypeScript the configuration file is `tsconfig.json`. It configures how the transpiler
    built the final `js` file.
  * `package.json` contains section `"scripts"` that defines automation of different commands.
    Any defined `script` command may be executed with `npm run <command>` or `yarn <command>`.
  
  ==== A Gatsby project
  
negative.code: === React GraphQL and Gatsby
  
  All data that Gatsby works with comes through the GraphQL processing (i.e., React).
  The Markdown and Asciidoc plugins process the documents and the results are consumed through GraphQL queries.
  The components of the data are for example _title_, _tags_, _generated HTML_ etc.
  The React component may then use that at particular places of the page.
  
  The most of the work for met on moving from Markdown to Asciidoc was the remapping of the Markdown GraphQL queries
  for Asciidoc.
  
  My work was to work with `adoc` and `md` data (MDX plugin is used) side by side.
  With that there could be seen the differences in the query structure.
  The `gatsby-transformer-remark` works with a similar structure as the `mdx` plugin.
  You can see this example here https://github.com/ochaloup/gatsby-from-scratch/blob/main/hello-world/src/pages/index.js#L40
  