I'm looking for advice.

[siaweb]

Good day to everyone. A botanist friend of mine asked me to make a plant site for his group. I want to ask you some advice. I know how to implement this on another engine for easier administration of it. I just understand that they will have a lot of information and since they will make transfers to each other. How would it make it easier for them to edit their 10,000 pages approximately.
Here is an example of the hierarchy of their website of the future. 
Catalog - Group - Category - Subcategory - Type - Article

I will be grateful for any hints. 
With respect to SIA

[BrendonKoz]

Good day, SIA. Some questions for clarification:

1. "they will make transfers to each other" -- This may not have translated properly. Will there be multiple websites where data will be maintained and integrated into both, or is this referring to many people making edits to individual items/pages?
2. "How would it make it easier for them to edit their 10,000 pages approximately?" -- ProcessWire has some options for various forms of access levels, whether it be page-level access, field-level access, or simple role-based access; you can also override with custom rules using PW's hooks. The question you asked though of, "how to make it easier," would depend on the needs of the project, how they expect to use it, and how you end up building that solution out. ProcessWire provides the basic options, but it's up to us to improve it per project using the tools that PW offers.
3. Your "hierarchy" is flat. Were newlines removed in the paste? You provided a hierarchy, but what do you want to know relating to it and ProcessWire?

[siaweb]

17 minutes ago, BrendonKoz said:

Good day, SIA. Some questions for clarification:

1. "they will make transfers to each other" -- This may not have translated properly. Will there be multiple websites where data will be maintained and integrated into both, or is this referring to many people making edits to individual items/pages?
2. "How would it make it easier for them to edit their 10,000 pages approximately?" -- ProcessWire has some options for various forms of access levels, whether it be page-level access, field-level access, or simple role-based access; you can also override with custom rules using PW's hooks. The question you asked though of, "how to make it easier," would depend on the needs of the project, how they expect to use it, and how you end up building that solution out. ProcessWire provides the basic options, but it's up to us to improve it per project using the tools that PW offers.
3. Your "hierarchy" is flat. Were newlines removed in the paste? You provided a hierarchy, but what do you want to know relating to it and ProcessWire?

1. There will be 1 multilingual website. This refers to a group of people who will translate the same article into different languages.
2. The document structure in ProcessWire is very simple and 10,000 pages will not look very good. In terms of navigating through them. User access is not a problem. It seems to me that the current structure of editing elements/pages will not be very convenient for them. As an example, I'll put wordpress there, it's simple.
3. Sorry, I didn't really understand this question.
Hierarchy example:
1.Catalog 
 1.1 Group 1
1.1.1 Category 1
  1.1.2 Category 2
  1.1.3 xxxx
1.1.1.1.Subcategory
 1.2 Group 2
1.2.1
1.3 Group 2
  1.2.3

and there will be more and more ramifications. This is an example of a catalog. 
PS. you can use the car catalog as an example, although it is smaller.