you'll need to know at least the basics of CSS, XHTML, etc to "do it right."
Why would you need any technical knowledge if iWeb does not grant you access to the code at all, unless you're f*cking the web for some tool/trick to enable you to edit the code?
However, I just sent a request to Mac that they treat iWeb as more of a Content Management System that could handle all the database issues of a growing community. EG: Certain authorised users that I allow onto my blog could also post articles, not just comments, and maybe iWeb could set up a forum structure as well.
Yes, and maybe even let us create Apple.com-like websites with the press of a button.
Sure if my dreams come true I might be locked into mobileme forever, but at least I'd HAVE my activist site and forum running... now I'm to chicken to really put my hand up for my group because I just don't know backend stuff confidently enough to fix it when stuff goes wrong.
You're not stuck at all. iWeb lets you upload files to an external FTP.
"Technically its not an open source CMS, but what it represents is a step in the right direction. This program was Apples first attempt at a web publishing system and works in unison with the .mac (now MobileMe) system. If Apple ever spent any time focusing on delivering a fully outfitted program by adding more to what is already a fantastic system with iWeb, there would be no need for any other CMS. I would keep an eye on Apple in the future for just such a program in their iLife suite. iWeb"
Poor retarded guy the one you quoted.
There would be no need for any other CMS. Yeah, sure! Why would anyone need something like Wordpress, which is the best combination between community & original developer effort? We don't let our users f*ck up our CMS, but we do let THEM provide us the images which will be used in the next version, as well as allow them to share themes/plug-ins,
and even contribute at some parts of the bug-fixing process. It would take Apple a separate division in order to equal Wordpress...
I'm wondering how much of this database management stuff I can get away with NOT knowing if I use something like Wordpress.
All you've got to do is get a domain, get some database information, edit a file, go through the 30-seconds web browser-based installation process, and you're all set. Three years ago, it took me 10 minutes to find out how to do FTP uploading. Just click
here.
Hi all,
just wondering what extra functionality it would take to turn iWeb into one of the above CMS's but with the Mac "point and click" interface so new users NEVER had to know XHTML, CSS, PHP or any of that... and how worried any coders are that this might one day happen?
And to answer this question, you guys are missing an important point: iWeb is part of the iLife suite, which is distributed freely with every new Mac, or you can pay $79 for the
entire suite when an update comes out. Compare this price to the price of RapidWeaver (the direct, although way more powerful, rival), $79
just for it, and you can tell why iWeb is never going to be anywhere near half as good as
professional. The application is bloated, and I can say without a doubt that the FreeBSD installation process is way more user-friendly than iWeb's web site builder. It would take an entire development team to work on the application itself. And then, because it is part of the iLife suite, we need to make iPhoto, iMovie, Garage Band, and the rest of the suite, just as good. So they would need 5 separate development teams which publish better products than most of the competitors, and sell them at 1/5 the price. This is not going to happen anywhere in the near future.
The iLife suite is something basic, to be used by the normal OS X customer. It has to come with every operating system, and Apple did the easiest thing to do: beautiful yet bloated applications, slightly updated each year. I've got rid of the entire suite, it simply occupies too much of my 160GB HDD...
