[Webcomp-main] Article in PHP|Arch

[<ja...@po...>]

Hi Developers

Please read text below. I think, we need make better web site with=20
documentation.=20

      Akelavlk

> I agree that many developers won't know what dotPHP is, and we're=20
happy to
> help you introduce it to them.  I want it to be crystal clear that=20
I am not
> interested in publishing a manual for dotPHP.  Any article that is=20
written
> for php|a about open-source projects needs to be deeper than manual
> material.  It definitely needs to explore the introductory side,=20
but the
> article should take it to the next level.  Questions you should=20
answer
> through explanation and code:
>=20
> Why do I care about this project?
> How can it help me solve real problems?
> How can I extend this for my own use?
> What funky issues am I going to run into?
> Are there limitations that I should be aware of?
> Is there a really sweet implementation detail in the project itself=20
that
> would educate?
>=20
> I really like the type of article that shows how a framework or=20
component
> library was conceived, and how and why things were implemented.  I=20
don't
> want writing an article for php|a to become a vehicle for=20
documenting a
> project.  The base project documentation needs to be there, first. =20
It is
> for this reason that php|a does not usually feature "frameworks" or
> "libraries".  We want to be a grassroots "how-to" publication, not=20
a user
> manual.
>=20
> I hope that came off as encouraging.  I am trying to encourage you=20
to not
> focus on gaining publicity for your project, but rather to show why=20
it is
> useful for the community, and share your development knowledge,=20
too.  If you
> want publicity for your project, talk to our news guy.  If you want=20
to teach
> the community about something that will really benefit them in day-
to-day
> development, let's write an article.
>=20
> Here's my suggestion for an outline:
>=20
> 1. Introduction to DotPHP.
>     - what is it
>     - why do I care
>     - a few examples of components and their use
>     - interesting implementation details
>         - any groundbreaking ideas or technologies?
>     - more information is available...
> 2. Hello world application
>     - basic application
> 3. How to modify existing component
>     - extending and changing behaviours
>     - implementation details to be aware of when doing this
> 4. How to create new component
>     - rules that need to be followed
>     - implementation details to be aware of when doing this
> 5. A real-world application tying everything together
>     - something semi-simple that uses an extended or new component
>     - what are the benefits to the application from using your stuff
> 6. Wrapping up
>     - next directions for dotPHP
>     - any else you'd like to say
>=20
> What do you think?  Given my above explanation of what we're=20
looking for,
> and the above article outline, are you still interested in writing=20
this?  I
> want to make sure you're doing it for the right reasons.
>=20
> Thanks again.  I look forward to hearing from you.
> Pete.
> --
> Peter James
> Editor-in-Chief, php|architect Magazine
> pe...@ph...
>=20
> php|architect
> The Magazine for PHP Professionals
> http://www.phparch.com
>=20
>=20

=0A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D REKLA=
MA =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=0AVyrazne zlavy pocitacov a prislusenstva=0ASun=
 Fire V210 server v cenach uz od 125.000,- Sk bez DPH=0ANavstivte nas na ad=
rese http://www.somi.sk/sun/lowend_servery.php=0A=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=0A