Date: Tue, 6 Mar 2012 12:54:24 -0800 (PST)
From: Mathieu <mathieu.lindem...@gmail.com>
To: pinax-users@googlegroups.com
Cc: t...@rizumu.us
Message-ID: <17373303.1153.1331067264387.JavaMail.geo-discussion-forums@ynll40>
In-Reply-To: <22803468.8.1331065752810.JavaMail.geo-discussion-forums@pbcjk1>
References: <5d096de6-4244-4046-b32a-284087f871d9@l24g2000yqm.googlegroups.com>
 <27381540.60.1327418483193.JavaMail.geo-discussion-forums@yqia35>
 <CAM6jyTBKEtzE+WRAGqQaFFjH9GE=xetup0Wmnr_PdOLDsQ7zBw@mail.gmail.com>
 <27986816.211.1330785331566.JavaMail.geo-discussion-forums@ynbq18>
 <22803468.8.1331065752810.JavaMail.geo-discussion-forums@pbcjk1>
Subject: Re: [pinax-users] Re: where all the documentation
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1151_24189538.1331067264385"

------=_Part_1151_24189538.1331067264385
Content-Type: multipart/alternative; 
	boundary="----=_Part_1152_8076697.1331067264386"

------=_Part_1152_8076697.1331067264386
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I am comfortable reading code. That's why I was able to customize and build=
=20
my own websites based on the starter projects. And that's why I still=20
consider Pinax is a great tool I want to keep using.

Now, some information cannot be guessed simply by reading the code. And the=
=20
deployment process is part of that "unguessable" information. A sign of=20
that is the obsolete information available on Pinax's website. The=20
designers did agree that there is a need to share instructions on how to=20
deploy a Pinax app. Unfortunately, the instructions are now obsolete.

I am not the only one to beg the dev team to share information so that the=
=20
community can appropriate Pinax. It's a great tool that deserves a minimal=
=20
viable documentation.

Le mardi 6 mars 2012 15:29:12 UTC-5, wongobongo a =C3=A9crit :
>
> Pinax users need to be comfortable reading code to get the most out of it=
.=20
> As mentioned earlier, Pinax lacks comprehensive written documentation, bu=
t=20
> the code is eminently readable.
>
>
>
------=_Part_1152_8076697.1331067264386
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

I am comfortable reading code. That's why I was able to customize and build=
 my own websites based on the starter projects. And that's why I still cons=
ider Pinax is a great tool I want to keep using.<br><br>Now, some informati=
on cannot be guessed simply by reading the code. And the deployment process=
 is part of that "unguessable" information. A sign of that is the obsolete =
information available on Pinax's website. The designers did agree that ther=
e is a need to share instructions on how to deploy a Pinax app. Unfortunate=
ly, the instructions are now obsolete.<br><br>I am not the only one to beg =
the dev team to share information so that the community can appropriate Pin=
ax. It's a great tool that deserves a minimal viable documentation.<br><br>=
Le mardi 6 mars 2012 15:29:12 UTC-5, wongobongo a =C3=A9crit&nbsp;:<blockqu=
ote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left=
: 1px #ccc solid;padding-left: 1ex;">Pinax users need to be comfortable rea=
ding code to get the most out of it. As mentioned earlier, Pinax lacks comp=
rehensive written documentation, but the code is eminently readable.<div><b=
r></div><div><br></div></blockquote>
------=_Part_1152_8076697.1331067264386--

------=_Part_1151_24189538.1331067264385--