[wp-hackers] 1.3a2 CVS

[David Chait]

Gee, figure it's time to throw in my 2c! ;)

I'm with Sebastian.  Overall, for the average user, a single file to edit is
a FEATURE, not a bug to be fixed.

Now, if things are broken out into sub-templates that don't NEED to be
edited, that the 'base' index is still where all the core action is, then
that might be a solution.  But if you are asking the average user to edit
more than one or two files, forget it -- you just confused them, and
significantly increased the potential for something screwy.

Again, I'd rather see that only things get broken out that are really more
encapsulated pieces, that an above-average used might want to muck with, but
the average user wouldn't care to change.  ADD to that EXTENSIVE inline
comments in the base index.php file, to show the 'sections' that you'd
otherwise be thinking of breaking out right now... ;)

-d

----- Original Message ----- 
From: "Sebastian Herp" <newsletter at scytheman.net>
To: <hackers at wordpress.org>
Sent: Monday, September 06, 2004 8:42 AM
Subject: Re: [wp-hackers] 1.3a2 CVS


> I agree that it might be easier for the "unwashed masses" if they only
> have to one small file with not so much php in it for small changes.
> But, if i imagine me being a newbie to wordpress, just having found out
> that such a great software exists. I would hit my head against any wall
> i can find, if i had to open 10+ files/pages just for initial layout,
> and probably use something easier such as blogger.com, etc ...
>
> I think that one file for everything is the a feature and not something
> that needs to be fixed. Everything is in there and i don't have to
> search for the template that is responsible for this and that. And i
> think that the average wordpress user is not thaaaat stupid, that he/she
> can not edit php-files :) ... or in this case ONE php-file *g*
>
> Greetings,
> Sebastian
>
> P.S.: Would an upgrade not destroy all the small changes we made in
> those templates? So we would have to backup all those files and maybe
> edit all new templates to match those old files if something big changed
> ...
>
> P.P.S.: How many people exist who are afraid of php, know a littlebit
> html and have their own webserver with a mysql database? Not so many, i
> think. And even they might want to see the whole picture (one file) and
> not multiple small pictures. They more likely have their computer-guy
> who changes their site for them or use a template they found on the
> internet ... and again this would be easier if it's just a index.php and
> a wp-layout.css ...
>
> Craig Hartel wrote:
>
> > Make it as simple for the users as possible. Certainly what Kitty has
> > proposed is not overkill at all, IMO. If it makes it a bit tougher on
> > the hackers and devs, well, too bad. :) Are you making this software
> > for hackers and devs, or for the unwashed masses, of which I am a
> > proud member?
> >
> > Right or wrong, there has been much "discussion" over templates and
> > how "bad" the default template is. I'm not here to debate that one way
> > or the other. I'm here to point out that perception is 85% of reality,
> > and there has been much bemoaning of the current template. People are
> > starting to believe that it is so.
> >
> > Power to the people! :)
> >
> > Craig Hartel
> > Nuclear Moose
>