As new PRs come in the docs start to be a little chaotic. I think it's important to make the structure clearer to enable faster contributions.

I'm thinking about the following structure:

• README.md - general info about the repository, links to docs/new-users.md and docs/technical-users.md should be in the beginning
• docs/ - folder for all the other READMEs that don't belong to any other s

Can we create a new "Consumer Electronics" category for TechSpecs API https://techspecs.readme.io/.

This is an API that provides the easiest way to get the detailed technical specifications of any consumer electronics product in the world.

Here I would to talk about some problems with RTL Languages and their solutions.
I will explain all the points here, and we can have a discussion about it.
and maybe add a section that talking about these problems & solution in Guidelines in CONTRIBUTING

**The base discussion on this issue starts o

We have a lot of is_prime (or similar) functions: https://github.com/TheAlgorithms/Python/search?p=4&q=is_prime, https://github.com/TheAlgorithms/Python/search?q=isPrime, data_structures/hashing/number_theory/prime_numbers, etc. Shall we use one common function for that exactly identical

Is your feature request related to a problem? Please describe.
I've set up a new tauri project following docs on tauri.studio, and my newly-generated app had bundle.identifier set to com.tauri.dev.

For macOS apps (and probably other OSes) this identifier has to be globally unique for every app. It can be problematic when developers forget to customize it. An existing example tauri app

What about create a design pattern directory with the most popular design patterns examples?
We can create some rules like: have to be an explanation about the design pattern, the structure and one real world example.
The directory can be:

(folder) Design Patterns
-- (folder) Abstract Factory
-- -- AbstractFactory.js
-- -- AbstractFactoryTest.js
-- -- REAME.md

I can send some :