[php-fundamentals] Background Story

[Paul Court]

I'm just going to put this out there, if you like it run with it - if not, send it right back!


What do you think of having an underlying "story" that each relevant tutorial / chapter / resource uses for its examples? (Snake Oil Ltd developing its widget database!)

IE. A topic in Branching might cover working on WidgetDB V2.0 while maintaining the V1.0 branch for bug fixes. Each VCS (git, svn, etc) could use the same example story. This way, a user could run through the "course" and choose different combinations like NetBeans, ZF, BZR or TextMate, CakePHP, git and still follow the same example story?

Paul

--
You received this message because you are subscribed to the "PHP Fundamentals" group.
To post: send email to php-fund...@googlegroups.com
To unsubscribe: send email to php-fundamenta...@googlegroups.com
For more options: http://groups.google.com/group/php-fundamentals?hl=en

[Paul Court]

Just adding these two comments from Stefan and Stuart as I didn't set the reply-to: on my original post.

On 25 May 2010, at 19:53, Stefan Koopmanschap wrote:

> I quite like this idea. This will make it much easier for authors and
> readers alike to read and follow the steps.

On 25 May 2010, at 16:50, Stuart Herbert wrote:

> Hi Paul,
>
> +1
>
> Best regards,
> Stu
> --

Regards
Paul

> --
> Stefan Koopmanschap
> http://www.stefankoopmanschap.nl/
> http://www.leftontheweb.com/

[Phil Moorhouse]

It's a good idea, if the stories are defined first before asking
someone to write the article for their chosen tool, then at least
they'll be some sort of coherence between each article. It might fall
apart a little bit if something is very difficult / impossible to do
with a particular tool though.

[Stuart Herbert]

One of the techniques I use when training new developers at work is to get them to tackle a task twice.  First time, they get to do it their way.  Second time, they have to learn how to do it our way.  This compare-and-contrast approach is excellent at making folks actually think ... and we could re-use this approach in the storytelling, to not only show people how something could be done, but also help them understand why.

Just a suggestion :)

Best regards,

Stu

--

--
Stuart Herbert

e: stu...@stuartherbert.com
t: +44 7966 284577
w: http://www.stuartherbert.com/
b: http://blog.stuartherbert.com/

[Phil Moorhouse]

Another thing that just came to mind, is using the same section
headings for every wiki article so that it's easy to compare and
contrast between them.

e.g.

Overview (short summary of the tool)
Pros
Cons
Example Usage (e.g. our story from the OP).
Further Reading (links to the official site, recommended docs,
tutorials, etc)

> > php-fundamenta...@googlegroups.com<php-fundamentals%2Bunsu...@googlegroups.com>

> > > >> For more options:
> >http://groups.google.com/group/php-fundamentals?hl=en
>
> > > > --
> > > > Stefan Koopmanschap
> > > >http://www.stefankoopmanschap.nl/
> > > >http://www.leftontheweb.com/
>
> > --
> > You received this message because you are subscribed to the "PHP
> > Fundamentals" group.
> > To post: send email to php-fund...@googlegroups.com
> > To unsubscribe: send email to

> > php-fundamenta...@googlegroups.com<php-fundamentals%2Bunsu...@googlegroups.com>