Hello, I'm just studying DNN6. I would ask you to support me in designing some aspects of my portal to marine biology. 

The portal already exists, established 10 years ago with my CMS, but for now I will not appoint not affect your answers! :) 

The question is: I have to build more than 5000 pages, each page corresponds to a taxonomic category. 
Example: 

              Kingdom: Animalia 
                           Phylum: Mollusca 
                                Class: Gastropoda 
                                     Order: Prosobrachia 
                                          Family: Strombidae 
                                              Genus: Strombus 
                                                   Species: pugilis 

Each branch can have, of course, endless ramifications. 
Each page will be translated into at least two languages. 

So, I created many pages to build the branch of the shellfish, but without writing the species (only in the Mediterranean are over 200). 

I wonder, and I ask you, if there is a better way, more correct (Managing Taxonomies? But I do not think ...) 

Once written pages, I have over 20,000 images to associate with their respective classifications. 
I do not think I will use DNN for image management ... I must first learn how to create custom components ... I will see in the subsequently has. 

Each photo should be associated with a taxonomic category, then one of those pages created previously. 
I imagine that there will be a way to extract from a branch of DNN pages, and then use it as a taxonomy for the photos ... right?:) If not already in the modules, I think with c # ... right? :) 

Now the search. 

I should use the taxonomy (for me the pages created before) to navigate the content (photos, videos, drawings). 
Then I use another type taxonomy of the sea (Atlantic Ocean, Pacific, Indian Ocean, Mediterranean Sea, etc. ...) 

How? 

Tags / hierarchical taxonomy for each photo, then filter the tags. Right? Ideas? 

I know SharePoint well, but I still miss several elements to DNN. 

I can count on your help? 

Thank you. 

For a project like this I would first forget about the Idea of separate dnn pages.  Instead I would look at building a Module that lives on a single dnn tab/page.

This module would be used to generate your entire taxanomy structure using a database table.

The actual = PAGES accessible by an end user would then be dynamically constructed at runtime.

The same goes for search and indexing - the module could implement the dnn internal search provider or you could write your own search module if you have specific lookup needs.

For example - this forum is running basically inside a SINGLE module on a single page - but shows the user multiple forums and threads and individual comments - all created and managed at runtime - and it uses a custom search engine as well.

I would not see however that your custom module would need to be as complex - in fact from what you have said it would seem to be much less complex.

Westa

Creating a custom module to handle the data management and page rendering would make life a lot easier for you in the long run than manually dealing with thousands of individual pages inside dnn - that then need to be replicated for ever 'language' you want to support.

This is how I would handle it - create a new module that lets you enter each "page" of information as an entry in the database - with all your content, image links, taxanomy, update tracking, entry dates or whatever other information is of relevance.

This module could also be coded to provide you with search tools to locate pages by content, taxanomy, date of entry, date last updated, name of person who submitted data, name of person for entered data  etc etc.

The same module could also be coded to handle automatic language translation of each page into multiple languages using tools like the Google’s Language API - with the database holding each translation as a separate entry in the database.

You