[support] Ten Commandments

[Steve Kessler]

I would agree with Patrick overall.  This is a good blog post for someone
but not *commandments* for the communities.

I was going to let someone else say this but it is also based somewhat
on opinion. There are best practices and coding guidelines but not
commandments.

On Thu, Sep 20, 2012 at 10:00 AM, Patrick Avella <me at patrickavella.com>wrote:

> I'm not a fan of this list, and if someone tried to push that on me
> here I'd be visibly upset. Some of the bullet points are good, maybe
> even great but:
>
>
> 2.    No PHP nodes.
> 3.    No PHP blocks. (A sample block module is available.)
> If I want to use PHP to insert a value into a link, I will, and see no
> problem with that. This is left up to the developer, not all PHP code
> needs to be in a module. PHP filter is part of core. When used
> responsibly there is no reason to not use it if it fits
> budget/time/needs.
>
> 4.    Minimize PHP in Views.
> Depending on the scope of the project, this can't always be enforced.
> Sometimes it's a lost more efficient to shove a little bit of PHP in a
> view than to have to recreate the view (and lose its support) from
> scratch in a module.
>
> 6.    Use Features for content types and views; and for other things
> that lend themselves thereto. Commit these to Git repository.
> I don't understand the love for features. It only supports "some"
> important modules, and needs a host of other modules (UUID, strongarm)
> before it starts to become actually useful. Bloat, bloat, bloat.
>
> 9.    CSS is your friend, use it before programmatic or theme styling
> as much as possible.
> No one is going to not tell me to not use the theme system. If I need
> to rearrange elements or make theme level changes, I will do so, and
> will not be told otherwise.
>
> 14. Links, including menus, should use relative URLs.
> This makes no sense. All menu links in drupal are absolute (they start
> at the domain root). It's a guideline where I work to never use
> relative URLs for files because they are not easily moved to new
> locations.
>
> But I knew I wouldn't like this list as soon as I saw the word
> "commandments". These guidelines sound like a lot of personal
> preference, and not a lot of realistic "in the fox hole" programming.
>
> Thanks,
> Patrick Avella
>
>
>
>
> On Thu, Sep 20, 2012 at 11:35 AM, Steve Kessler
> <skessler at denverdataman.com> wrote:
> > Changing . htaccess  is required in many cases.  That is not hacking
> core.
> >
> > I like to comment out core when editing . htaccess  and then add my
> changes
> > with a comment about what they are for.
> >
> > -Steve
> >
> >
> > On Thu, Sep 20, 2012 at 9:29 AM, Franz Iberl <f.iberl at amazonas-box.de>
> > wrote:
> >>
> >> Am 20.09.12 17:17, schrieb Walt Daniels:
> >> > Unfortunately hacking core, in particular .htaccess, is not optional
> on
> >> > some servers.
> >>
> >> Adapting .htaccess I do not consider as hacking core.
> >>
> >> Servus
> >>    Franz
> >> --
> >> [ Drupal support list | http://lists.drupal.org/ ]
> >
> >
> >
> >
> > --
> > Steve Kessler
> > Owner and Lead Consultant
> > Denver DataMan, LLC
> > 303-587-4428
> >
> >
> > --
> > [ Drupal support list | http://lists.drupal.org/ ]
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>



-- 
Steve Kessler
Owner and Lead Consultant
Denver DataMan, LLC
303-587-4428
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20120920/36e7b8e0/attachment.html