Related Content from Around Faves
-
Behind the scenes inteviews with developers at Google talking about the reason they decided to build Chrome.
- Top priorities: Speed, Stability, and Security.
- Start of project was "V8" - a high JavaScript runtime.
- WebKit is the basis - because of the small code base.
- Google tested against millions on web pages, and is getting 99% "correct layout" in their automated tests.
- Minamilistic design.
- Open SourceGoogle comes off looking really good with this product launch - Microsoft is looking so "old school" and out-of-touch these days.
1 FaverViewed: 2 TimesQuoted: Watch a video from the development team on the thinking and features behind Google Chrome.www.google.com/chrome
- Tosh - yesterday1 FaverViewed: 3 Times
- matt - 2 days ago1 FaverViewed: 2 Times
drupal
-
Chris sent mail about this to the local Drupal Users Group a couple of days ago. Since I'm just learning Drupal now, I can definitely see a need for an integrated installer.
Drupal is excellent in it's modularity. The problem is, the core installation does very little. I'm up to about 20 installed modules on StartPad.org, and it's still a very basic site.
For example, here's the list of modules I've had to install (and why):
acl - basic user access control
adminrole - helper to give an administrator role permissions
cck - define custom content types
cck_address - a custom mailing address field type
cck_field_perms - set field level permissions
cck_map - display google map field
contemplate - custom formatting of content types
content_access - access control by content type
diff - display revision differences (wiki style)
forum_access - access control for forums
globalredirect - redirect (301) to canonical url aliases
google_analytics - insert google analytics
image - image upload
imce - rich text image upload
link - url field type
path_redirect - enable url aliases
pathauto - auto-generate alias (slug text)
tinymce - rich text editor
token - utility dictionary for other modules
views - generate custom views and filtersThere is really no reason that these are not packaged together as "core" - except you'd get some disagreement in the community about what to include (different rich editors, for example).
Drupal is an interesting start for a base. But I wonder why not start with Ruby/Rails/Radiant or Python/Django/Ellington. You've got to believe that PHP's days are numbered as a preferred platform choice. I can think of two reason FOR Drupal:
a) There's not a big community behind a single CMS based on those platforms.
b) This is more of a design/integration project, rather than a development project.Quoted: Chris Pirillo has announced a new, large scale open source CMS project that aims to de-geekify website tools (announcement video above). The project ...
http://chris.pirillo.com/2008/03/26/were-taking-an-open-direction-with-web-communities-are-you-in/
1 FaverViewed: 3 Times - geekglue - Aug 04 20081 FaverViewed: 2 Times
- mike - Jun 20 20081 FaverViewed: 2 Times
