docs: improve frontend dev instructions

site/src/docs/contributing/frontend/index.md

@@ -2,9 +2,21 @@
 title: Frontend Development Guidelines
 ---
 
-### Frontend development
+## Prerequisites
 
-#### Installation
+Frontend for Remark42 is built with [Preact](https://preactjs.com) and [Redux](https://redux.js.org).
+
+::: note 💡
+We highly recommend checking out Preact documentation.
+TLDR: Preact replicates React API and compatible with its libraries.
+:::
+
+In order to inject Remark42 widgets into websites we use `iframe` and `postMessage` for communication between a site and the widget.
+Simple widgets like [counter widget](https://remark42.com/docs/configuration/frontend/#counter-widget) can be injected as a script because it doesn't have it's own interface.
+
+While development we setup environment which imitates real world example. We serve the page which uses Remark42 config and inject all of the widgets on it. You can check it on our [demo site](https://demo.remark42.com/web/). After successful installation you should have the same page running locally.
+
+## Installation
 
 You must have at least 2GB RAM or swap enabled for building.
 
@@ -15,14 +27,14 @@ You must have at least 2GB RAM or swap enabled for building.
 Running `pnpm i` will set up pre-commit hooks into your git repository. They are used to reformat your frontend code using `prettier` and lint with `eslint` and `stylelint` before every commit.
 
 ::: note 🚨
-use `127.0.0.1` and not `localhost` to access the server, as otherwise, CORS will prevent your browser from authentication to work correctly.
+Use `127.0.0.1` and not `localhost` to access the server, as otherwise, CORS will prevent your browser from authentication to work correctly.
 :::
 
-#### Development
+## Development
 
-##### Run frontend locally against demo.remark42.com
+### Run frontend with remote backend
 
-This variant of running Remark42 frontend code is preferred when you make a translation or visual adjustments that are easy to see without extensive testing.
+You can run frontend against demo instance of Remark42. This method of running Remark42 frontend code is preferred when you make a translation or visual adjustments that are easy to see without extensive testing. For this method we use our demo instance of Remark42 served on https://demo.remark42.com
 
 For local development mode with Hot Reloading, use `pnpm start:app`. In this case, `webpack` will serve files using `webpack-dev-server` on `127.0.0.1:9000`. By visiting <http://127.0.0.1:9000/web/>, you will get a page with the main comments' widget communicating with a demo server backend running on `https://demo.remark42.com`. But you will not be able to log in with any OAuth providers due to security reasons.
 
@@ -36,7 +48,7 @@ npx cross-env REMARK_URL=http://127.0.0.1:8080 pnpm dev:app
 If you want to redefine env variables such as `PORT` on your local instance, you can add the `.env` file to the `./frontend` folder and rewrite variables as you wish. For such functional, we use `dotenv`.
 :::
 
-##### Run whole local environment
+### Run frontend with backend locally
 
 This option of running Remark42 frontend code is preferred when you need extensive testing of your code changes, as you'll have your backend and configure it as you want, for example, enable any auth and notifications method you need to test. You can use that set up to develop and test both frontend and backend.
 
@@ -61,54 +73,54 @@ Developer build running by `webpack-dev-server` supports devtools for [React](ht
 
 It starts Remark42 backend on `127.0.0.1:8080` and adds local OAuth2 provider "Dev". To access the frontend running by Node, go to <http://127.0.0.1:9000/web/>. By default, you would be logged in as `dev_user`, defined as admin. You can tweak any of the [supported parameters](https://remark42.com/docs/configuration/parameters/) in corresponded yml file.
 
-##### Manual testing after changes
+### Manual testing after changes
 
 Frontend Docker Compose config (`compose-dev-frontend.yml`) by default skips running backend related tests.
 
 ::: note 🚨
 Before submitting your changes as a Pull Request, run the backend using the `docker-compose -f compose-dev-frontend.yml build --build-arg SKIP_FRONTEND_BUILD=""; docker-compose -f compose-private.yml up` command and test your changes against <http://127.0.0.1:8080/web/>, frontend, built statically (unlike frontend on port 9000, which runs dynamically). That is how Remark42 authors will test your changes once you submit them.
 :::
 
-#### Static build
+## Static build
 
 Remark42 frontend can be built statically, and that's how the production version works: frontend is built and then resulting files embedded into the backend, which serves them as-is. Node is not running when a user starts Remark42, only the backend written in Go programming language, which also serves pre-built frontend HTML and JS and CSS files.
 
 Run `pnpm build` inside `./frontend`, and result files will be saved in `./frontend/apps/remark42/public`.
 
-### Code Style
+## Code Style
 
 - The project uses TypeScript to analyze code statically
 - The project uses Eslint and Stylelint to check the frontend code. You can manually run via `pnpm lint`
 - Git Hooks (via husky) installed automatically on `pnpm i`. They check and try to fix code style if possible, otherwise commit will be rejected
 - If you want IDE integration, you need Eslint and Stylelint plugins to be installed. Also, you have configure Eslint for work in subdirectory. For example you have to add configuration for VSCode like that `"eslint.workingDirectories": ["frontend/apps/remark42"]`
 
-### CSS Styles
+## CSS Styles
 
 - Now we are migrating to CSS Modules, which is a recommended way of stylization. A file with styles should be named like `component.module.css`
 - Old component styles use BEM notation (at least it should): `block__element_modifier`. Also, there are `mix` classes: `block_modifier`
 - The new way to name CSS selectors is camel-case like `blockElemenModifier` and use `clsx` to combine it
 - Component base style resides in the component's root directory with a name of component converted to kebab-case. For example, `ListComments` style is located in `./app/components/list-comments/list-component.tsx`
 - Any other files should also be named in kebab-case. For example, `./app/utils/get-param.ts`
 
-### Imports
+## Imports
 
 - Imports for TypeScript, JavaScript files should be without extension: `./index`, not `./index.ts`
 - If the file resides in the same directory or subdirectory, the import should be relative: `./types/something`
 - Otherwise, it should be imported by absolute path relative to `src` folder like `common/store` which mapped to `./app/common/store.ts` in webpack, tsconfig, and Jest
 
-### Testing
+## Testing
 
 - Project uses [Jest](https://jestjs.io) as test framework
 - [Testing Library](https://testing-library.com) is used as UI test utilities (there are still tests with Enzyme but we are in process of migration)
 - Jest checks files that match regex `\.(test|spec)\.ts(x?)$`, i.e., `comment.test.tsx`, `comment.spec.ts`
 - Tests are running on push attempt
 - Example tests can be found in `./app/components/auth/auth.spec.ts`, `./app/store/user/reducers.test.ts`
 
-### Notes
+## Notes
 
 Frontend part being bundled on docker env gets placed on `/src/web` and is available via `http://{host}/web`. For example, `embed.mjs` entry point will be available at `http://{host}/web/embed.mjs`
 
-### Learn More
+## Learn More
 
 - [How to Add a New Locale](https://remark42.com/docs/contributing/translations/)
 - [Remark42 Instance Parameters](https://remark42.com/docs/configuration/parameters/)