I am trying to setup a new site about languages and linguistics. I post on this forum to get the advice of people that have more experience in Drupal.
I have choosen Drupal because it is simple, has easy to understand code, is extensible, works with Postgres (though does not use its power) and looks good. There are things I do not like in Drupal, but maybe it is becase I do not understand things well (I am playing with it only a week now, and I do not have much spare time :-( for it)
In the case of my site Drupal is not a CMS only - it is going to be an interface to a linguistic database. I did not want my site to be a bunch of freeform nodes that display in a nice CMS. It is supposed to be a database of linguistic data that displays and gets modified as easily, as any other Drupal content, but is well structured and can be exported to an XML document that can be later converted to a book (PDF or OpenOffice doc for example) and downloaded by an interested user. I decided to write a separate module for each kind of data (classification node, part of speech description, thematic vocabulary, lesson, exercise etc - I am still thinking how it is supposed to be organised), that takes care of editing and displaying its content. This modules are node modules, so Drupal takes care of many things, like for example comments, promoting to main page etc. - but I had to trade the design of the database in exchange. I decided that each "piece of data" will be kept in node's body as an XML or PHP, teaser will be standard HTML. I do not want to modify existing Drupal code (though simetimes I would like to do it :-) ) in order to be able to upgrade in the future, but I had to do some minor changes - like displaying teaser on the edit form. I miss access restrictions on the node level.