Last update8 years 46 weeks ago
June 28, 2004
Let me place the conclusion at the top: Despite the fact that I did not manage to get Drupal t-shirts and that the Drupal poster wasn't printed the way I expected it, LinuxTag was a success for the Drupal project and a very interesting experience for myself.
June 23, 2004
There will be a Drupal poster, Drupal leaflets, and - if I manage to get one - me wearing a Drupal t-shirt. I'll also demonstrate Drupal using a projector. I hope to be able to convert all the Zope people to happy Drupal users so show up and give me support.
Update by Dries: the poster and leaflets are made possible thanks to donations by Tipic and Morbus Iff, and thanks to the hard work of our contributors.
June 3, 2004
I'd be interested in seeing comments about other core areas I've missed or comments on the ones I've written about.
The 4.4.1 system usability report is more or less complete on the wiki. Installation usability and non-core module usability is still under development.
As we come up with redesign proposals, please post them in the new Design and usability forum under Designs, mockups and specifications.
May 23, 2004
It has been three weeks since we released Drupal 4.4.1 and some bugs have been fixed since then. No critical bugs were identified yet I'd like to release Drupal 4.4.2, a second maintenance release, shortly. It would be nice if you could help squash pending bugs as well as help test the DRUPAL-4-4 branch so we can start packaging Drupal 4.4.2 in one or two weeks from now.
May 18, 2004
On May 13, Movable Type announced that with version 3.0 they would be "Getting Their Pricing Right." The new licensing scheme--which only makes MT available for free for 1 author and up to 3 websites--is, as Mark Pilgrim has pointed out, a demonstration that "free enough" does not guarantee any freedoms in the long term. And so many current MT users are now searching for copyleft and/or open source blogging software alternatives.
May 17, 2004
May 7, 2004
May 5, 2004
One of the more interesting aspects of the Splinder/Motime project is the way that it takes advantage of a series of stand-alone modules written by Tipic, Inc. which showcase the flexibility of Drupal's module-based architecture.
The following is a summary of what we have been working on since the release of Drupal 4.4.0 (approximately one month ago), what we are currently working on, and what we like to work on.
May 4, 2004
The Drupal project has released version 4.4.1 of its open-source content management platform today. As no critical bugs have been identified, this is a minor bugfix and maintenance release. There are no new features in this installment.
As an open source software project maintained and developed by a community, Drupal is free to download and use. You can download Drupal 4.4.1 by clicking the link below:
The review is just shy of 2,000 words and covers many points about the system - for example the way in which the modules etc. are actually useful and not pointless - and even some bad points. Well if you want to know them you'll just have to read the review!
I post this here so anyone who is willing to read can read this review and decide for themselves if Drupal is for them. I know how hard it can be to decide on a CMS so this, hopefully, will help those still questioning Drupal make their mind up one way or another.
May 1, 2004
After an extensive testing period, the Drupal project has released version 4.4.0 of its open-source content management and community platform. The release of version 4.4.0 adds a number new features that improve Drupal's flexibility, performance, usability and accessibility. A list of the major changes and additions is provided below. For more information, please refer to the CHANGELOG.
You can download Drupal 4.4.0 from http://www.drupal.org/drupal/drupal-4.4.0.tgz.
April 21, 2004
This is the follow up to Open discussion on Drupal's themeing capabilities and templating engines., and is more technical in nature than the previous article. This article intends to go into depth about the nature of the current system, and what possible improvements could be made in the future.
It will attempt to refer to as much actual code as possible, so much so that I am starting to wonder wether it would not have been faster for me to just write the code and get it done with, however.. I also feel that it is important that contributing designers have a reference point for the nature of these changes, hence this discussion.
I am only indexing the current Drupal 4.4.0 contributed themes, as they are the only ones which would be able to support all the drupal features. Unsupported themes that should be indexed additionally should please be mentioned in the following discussion.
April 14, 2004
I am in the process of designing a new approach to the themeing system currently employed by Drupal. But first I feel I might need to explain a bit about the approach I am leaning towards. If you are interested in Drupal themeing, I would greatly appreciate if you read the entire post, as I would like as much input about what I am planning, as to better try to help Drupal designers. This is a rather in depth post, but contains some insights into the new system I am currently developing.
I feel that most of what we consider a 'Drupal theme' at this stage, is too complex, and too rigid a framework for most web designers attempting to work with our platform. I propose we rethink the theme system as it currently stands to be a more generic templating system. Specifically , most of cruft in themes can be attributed to completely seperate configuration settings and capabilities for each. This leaves us with a set of themes which are incompatible and different from each other, and if a designer wants a feature only another theme supports .. he is left with the choice of porting the feature to his current theme (not that easy for non programmers), or rebuilding his work on the new theme. The designer might even be faced with judgement calls regarding which set of features he would rather have.