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.

[Ivan Gretsky]

5 hours ago, siaweb said:

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.

It seems that you're seeing the main problem in those plants' pages presentation in admin. You do not want to see all those 10 thousand pages in a tree. I can relate to that.

One possible solution would be to use Page Lister. This way you would see all those pages in a list no matter where they are in a tree. You would be able to search those pages by any their fields. Basic version is included in the core (see the screenshot below). A more powerful Pro version is a cool thing to have though and 100% worth its money.

You can still have the pages in the tree hierarchy, or have all the plants under one common parent and linked to categories via page reference fields.

[BrendonKoz]

I'm still personally having trouble properly understanding the vision of where the problem is. SIA has seen the car example (at least one of them, there are a few). I understand that there are potential hierarchies of some sort of data, but how that data relates to individual plants/pages, to other levels within the hierarchy, and how SIA is envisioning the page tree to look, it's hard to make any recommendations. 😞

Maybe the first hierarchical level in the page tree is the CATALOG (version/periodical?). These are individual entries that are the (only?) allowed children of HOME.

Allowed children of CATALOG would then be GROUPs (though I'm not sure what this is a group of or how it relates to CATALOG or CATEGORY).

CATEGORY is next, so it's the only allowed child of GROUP. Since we're talking about PLANTS, I'm not sure what "Category" relates to within GROUP or how it is defined. I would think make genus, or species, or type of plant as defined by the organization (Annual, Perennial... Perhaps the hardiness zone? Seed or Bulb?)

That's a lot of clicking to get to specific (plants?) items within the site, but it does limit the amount of difficulty in finding specific items within a page tree containing 10,000 items under a single node.

...

There are ways that the above defined data hierarchy could be architected within ProcessWire so that it is not as rigid as mentioned. Fields used as attributes (ex: tagging) can go a long way here, along with what @Ivan Gretsky mentions in the Listers to offer secondary predefined navigation options to supplement the page tree. There's also the very powerful admin live search which can even be customized. That is extremely quick, assuming an item's title is already known.

I would like to make clear that if you're more confident in your use of WordPress and already understand how you would build that site out using that tool, then it may be a better option for you. I'm trying to understand the more nuanced parts of this particular job request in order to give some possible suggestions of how ProcessWire could be used to mimic what you'd get out of WordPress as they can be, for most scenarios, used interchangeably (with the limitation on custom plugins and/or themes).

[poljpocket]

7 hours ago, siaweb said:

As an example, I'll put wordpress there, it's simple.

How would your structure look like in WordPress?

[siaweb]

2 hours ago, Ivan Gretsky said:

It seems that you're seeing the main problem in those plants' pages presentation in admin. You do not want to see all those 10 thousand pages in a tree. I can relate to that.

One possible solution would be to use Page Lister. This way you would see all those pages in a list no matter where they are in a tree. You would be able to search those pages by any their fields. Basic version is included in the core (see the screenshot below). A more powerful Pro version is a cool thing to have though and 100% worth its money.

You can still have the pages in the tree hierarchy, or have all the plants under one common parent and linked to categories via page reference fields.

Thanks for the answer, I've already considered what you recommended and I'm still thinking about it.

Edited 10 hours ago by siaweb

[siaweb]

27 minutes ago, poljpocket said:

How would your structure look like in WordPress?

On Wordpress, just the headings are selected and that's it. The list of everything that is at the level of the category and not lower drops out. Which, in terms of filling and changes, I consider a good practice for an unprepared person.

Edited 10 hours ago by siaweb

[siaweb]

1 hour ago, BrendonKoz said:

There's also the very powerful admin live search which can even be customized. That is extremely quick, assuming an item's title is already known.

I will study this issue, it promises a lot for me.

 

1 hour ago, BrendonKoz said:

I would like to make clear that if you're more confident in your use of WordPress and already understand how you would build that site out using that tool, then it may be a better option for you. I'm trying to understand the more nuanced parts of this particular job request in order to give some possible suggestions of how ProcessWire could be used to mimic what you'd get out of WordPress as they can be, for most scenarios, used interchangeably (with the limitation on custom plugins and/or themes).

I don't really want to use it.

 

Thanks for attention.