Используется модуль propstar. Ничего особенного, но мне этого хватает.

Флекс ноде хорош, самому нарвится, но приходится думать о будущем, и выбирать что-то более поддерживаемое! )))

Вопрос задан корректно... задача заключается в том, чтобы выяснить, является ли данный набор: ССК , Views+ Category, полноценной заменой модулей: Book, Flexinode, Taxonomy, taxonomy_block, taxonomy_browse, taxonomy_context, taxonomy_html, taxonomy_menu!!

Судя по тому что входит в комплект модуля категорий, заменя происходит примерно так:
Book и Taxonomy = Category (wrappers modules)
taxonomy_browse = category_display
taxonomy_menu = category_menu
Т.о. отпадают несколько модулей, которые у3сиавливаются отдельно.

Если я ошибся, поправьте меня.

В том то и вопрос, что в конце концов планируется использовать ? ССК или Таксонометрию....
Вопрос стоит серьезный, поскольку не хочется столкнуться с тем, что все резко измениться, как это случилось с веткой друпала 4.5.х
И собственно дабы переходить на новые возможности, МНЕ НУЖНо оределиться с тем, что использовать.
И собственно из-за чего затевался этот дневник )))

Кстати касательно все того же ССК, на друпал.орг наткнулся на рассуждениеце...

I've spent lots of time with Flexinode and now I'm using CCK. All my solutions are based on them so I have several comments which may be useful for others.

1. Themes.
Flexinode is very inconvenient when theming node page or teaser - you need to use $node->flexinode_4 or $node->flexinode_11 to access fields. Flexinode content is called 'flexinode-7' or 'flexinode-15'. There is no ability to access content type or field by a normal name (i.e. 'field_genre' or 'field_inspiration'). I have my own version of Flexinode with new features: content type name and field name but it is still quite inconvenient to use.
No such problems in CCK!

2. Teasers.
Thanks a lot to CCK authors for empty body and teaser fields! Since we have an ability to create text area field we don't need hardcoded body any more. Flexinode generated body from its fields and that body was UGLY. All normall sites MUST create their own templates to display node page or teasers, so there is no need to generate bodies. The only huge lack is that search.module will not find any CCK nodes because they have empty bodu and no search hooks implemented. But CCK_Search.module is already in development. It will provide an ability to customize seearch index for CCK nodes.

3. CCK has far less fields available.
I reviewed CCK pages several days ago and found that there are lots of fields already developed (may be even more than for Flexinode).
IMPORTANT: imagefield is much more better than it was for Flexinode (more correct file processing and all thumbnails logic was taken into imagecache.module). I'm going to create an audiofield.module and videofield.module for CCK soon.

4. Data structure.
Agree with Ber. It looks properly normalized in Flexinode (which is assumed to be good) but it is very bad for indexing and writing search queries. So, altering table structure on the fly is a very good solution to build an optimal database.

5. Core & CCK.
If CCK will be taken into core, Drupal becomes not only a CMS but a powerfull platform wich will be completely better than any other CMS. This is my dream

6. Flexinode is easier to administrate then CCK.
I didn't understand why CCK is harder but okay ... Ber, you are a professional (I know because I'm using your quicktags.module)... Easiness should not attract professionals:) Our aim is power!

7. CCK is easier for Drupal developers.
You are right that it is more difficult to develop a CCK module but it is easier to develop a site using CCK and its already developed modules. Such site is easier to maintain.

My own conlusion
-----------------
After I started using CCK instead of Flexinode my development time reduces twice.
Proposition for everybody: let's study CCK and help authors to make it better and integrate into core. I myself gave up with my improvements of Flexinode and started to work for CCK.

Довольно интересно разложено все... да и со временем, народ всеж перейдет на ССК)))

Имхо!!! Что посоветуете? Использовать модуль категории, или остаться на таксонометрии?)))