views:

325

answers:

12

Hi,

I'm building quite a large site, no e-commerce, but a a lot of specific content to be managed. For some reason, the client wants Wordpress. There is no way of getting around this...

I've used Wordpress before to rapidly develop blogs, but that's about it. If anything goes beyond the scope of Wordpress I'll use a framework in something (Rails/Cake).

This build is going to require custom plug-ins and widgets, so what I'm asking is how is the best way to go about learning how Wordpress and best practices for plug-ins and widgets?

+4  A: 

Hit up the wordpress site. Seems obvious, but they have lots and lots of good docs and information.

http://codex.wordpress.org/Developer_Documentation

DavidYell
+2  A: 

Start here http://codex.wordpress.org and dig deeper. I am currently using WordPress as a CMS and customizing it quite heavily. It is possible if you know the right hooks, how the templating works etc.

I also think the new API search interface is quite handy: http://wpdocs.labs.thedextrousweb.com/

eteubert
A: 

If you are more used to Rails/Cake then present this as the more viable option to the client.

Banford
+1  A: 

I am a big fan of css-tricks.com. Chris covers a lots of topics, including Wordpress stuff with some good screencasts too.

http://css-tricks.com/video-screencasts/

Matt
Chris also wrote a book with Jeff Starr: "Digging into Wordpress" http://digwp.com/
peirix
A: 

Hi Smickie

OK a couple of things - think about changing your mind on WP, the new version (Not yet public) WP3.0 goes a LOT further than any prev. version of WP. Link to WP 3.0 download You may find that this answers/solves a few more of your "custom" problems than you imagine. Beyond that writing widgets is not to hard. At the end of the day they all use the same WP - PHP class. Once you have that code (too long to post here I think?) you can manipulate the code at will. The hardest part I usually find - and you may also - is actually in the theme not in the backend. As clients usually attempt to "stuff" many plugins into their system. Big prob. is that not all plugins are well written and some conflict. Sometimes "client" education on plugins is hard.

With regards to best practice - follow the WP guidelines, pretty simple, and remember to use wp_enrique for your JS includes rather than hard code them into the head.

If you need any help/advice etc. feel free to shout

RussP
A: 

i check smashingmagazine.com for tutorials, plugins, themes, tips, hacks

speckyboy.com is also a regular place i go to

usually it is more like google the task at hand and see ;)

the best way to learn, install a demo and play around or read a book along from wordpress ( the dummies series or something) that will make sure u cover all the basics and get some fun experience

Happy wordpressing

mireille raad
+2  A: 

There is an absolutely awesome book (and e-book) called "Digging Into WordPress". Highly recommended. Solid advice, excellent descriptions and good code. They're really quite good at explaining things. If you buy a physical book you also get the PDF. The other nice thing is that if you buy it you get future updates as well, so that when WP goes through changes, you get the new versions of the PDF as it's updated.

You can find it at http://digwp.com/

Strider
I don't find it so awesome: as I said below all wordpress books including the one you quote are more a bunch of hacks than a pedagogical book.
A: 

WARNING: A little shameless self promotion here:

If you use TextMate I maintain a bundle specifically to help make working with WordPress easier. Check it out: http://top-frog.com/projects/wordpress-textmate-bundle/

If you're using BBEdit I've also got a simple function, action and filter clipping set: http://top-frog.com/projects/wordpress-clippings-for-bbedit/

On top of that, like others have said, check out the WordPress codex for getting started. If you go straight for WP 3.0 it'll be out of beta by the time you go live. Skip the download links and check it out straight over SVN while its still being developed: http://core.svn.wordpress.org/trunk

I've got my site running on 3.0b2 and my work site is on the same thing. Its a nice improvement and the custom-post-types feature goes a long way to making WordPress much nicer to work with as a CMS.

If you're looking for a theme framework check out Carrington: http://carringtontheme.com/ - starting with Carrington JAM (short for Just Add Markup) you get a really nice bare bones theme to start building on. Much better than Sandbox, IMHO. Carrington takes a little while to wrap your head around but once you do its quite nice and easy to extend. Very handy for complex sites.

Also keep an eye on:

http://markjaquith.wordpress.com/
http://josephscott.org/

Gipetto
A: 

Wordpress is a great platform but documentation is clearly not at the same quality level as traditional software editors.

All Wordpress Books are written by consultants which seems to be willing more to show off their technical knowledge with a bunch of hacks instead of being really pedagogical and take you step by step from the fundamental of architecture to the uppest level.

Wordpress could have been redevelopped with a standard MVC Framework I'm surprised nobody tried.

The question wasn't "are wordpress docs good?", it was "where can I learn about wordpress?". I have got huge value from the codex over the years. And I'm not sure why one would compare its docs with those of "software editors".
Greg
A: 

Broadly speaking, there only one thing you need to learn to get started with writing plugins and such for WordPress, and that is how hooks work. Check out the functions "add_action" and "add_filter". Once you have that, the source code is your best friend. For the most part it's quite well commented. You figure out what you want to make happen, you identify the best "hook" to attach your code to, and then you use one of those two functions to insert your custom code into the mix.

That's basically how I started out. I learned about using hooks and joined the wp-hackers email list.

Here;s a good place to start: http://codex.wordpress.org/Plugin_API

Strider