<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
The idea isn't to replace all user-contributed content with a team of
Perl scripts. Rather, the idea is to use the scripts to help expedite a
complete overhaul of the core information while creating consistent
results. People manually adding examples, additional information on
usage nuances, crosslinks with relevant Codex pages, notes, etc will
still be crucial.<br>
<br>
As for wanting people to post things that you can respond to, I'm not
sure what you are asking for there.<br>
<pre class="moz-signature" cols="72">Chris Jean
<a class="moz-txt-link-freetext" href="http://gaarai.com/">http://gaarai.com/</a>
<a class="moz-txt-link-freetext" href="http://wp-roadmap.com/">http://wp-roadmap.com/</a></pre>
<br>
<br>
dave jaggy wrote:
<blockquote
cite="mid:9aa12a490901040002o7cfbf101yb240916376c9a6a3@mail.gmail.com"
type="cite">
<pre wrap="">It looks like the effort does worth it. Although it's not quite what I
expected or wanted it to be.
I still think (and as it turned out - I'm not the only one who does),
that user contributions in form of regular comments are very
important. Many interesting things at php.net are found in comments
and not in a description of a function itself. Comments may become a
base for wiki entry. As I said, users make comments more easily then
they write structured articles.
I respect Charles and what he does right now, but I do not see how I
can help. Perl is not my strong point and hence I can't contribute to
the parser-script. The only thing I can do in established context is
to edit texts on Function Reference page. Or, and that's more logical,
I should start editing inline documentation?.. Maybe we should remove
Codex Editing ability from Function Reference Part? Or somehow connect
it with inline documentation? Otherwise we will again get two
different and independent versions of documentation.
I'm new to wp-docs, so that I haven't got a single letter from it yet
for this conversation. Can anyone post anything, so that I could post
a response to a corresponding thread?
On Sat, Jan 3, 2009 at 5:40 AM, Jacob Santos <a class="moz-txt-link-rfc2396E" href="mailto:wordpress@santosj.name"><wordpress@santosj.name></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Well, like I said, If you get it started, then I'll join in and walk beside
you on your journey to achieving enlightenment. I would rather join in once
I have time and I can contribute something that would only take a few hours
or so a week. I'd be happy to add a few examples and improve the details,
but that would mean that the page already exists.
Your script will hopefully carefully update the existing codex pages and not
replace everything. The examples should always be applicable, unless there
is a regression or the specs change.
Good luck.
Jacob Santos
Charles K. Clarkson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello,
I sent a copy of this message to the WP-Hackers list for reference. Let's
keep further discussion on the Documentation list, please.
Thank you.
Jacob Santos wrote:
</pre>
<blockquote type="cite">
<pre wrap="">You should have mentioned the Perl automated script.
</pre>
</blockquote>
<pre wrap="">It started as a simple script with a few dozen lines that only I would
ever use to skip over common sections in the Codex and blossomed into a
multi-file, thousand line behemoth one long weekend. I didn't want to
disclose it in its current condition. It's pretty slim on documentation.
I did send Chris Jean a copy of it, however.
</pre>
<blockquote type="cite">
<pre wrap="">Hmm, it seems that whatever you conclude on, it will be interesting.
Hopefully, the conclusion will be sooner rather than later, because I
don't think any one else will attempt what you guys are doing at the
moment or at least not in the near future.
</pre>
</blockquote>
<pre wrap="">== Function Pages Planning ==
I just read the December Archives on the Hackers list. It looks like
there is some interest there by real life programmers and hackers who
are more familiar with the WordPress code and PHP than I am. Together we
should be able to come up with an easy to update version of the codex on
both a sample site and in the Codex Function Reference.
Hopefully we will use the inline documentation you started as our
starting point and provide updates for it as we move forward.
== Function Pages Progress ==
I intend to continue adding new function reference pages to the Codex
while we discuss implementation of future Codex Function Reference
pages. I'd like to see something up on the Codex rather than nothing
until we sort out the details. So, the planning phase shouldn't hold up
the action phase. We will just have to do some back-tracking later on.
I added about 82 new function pages in December. I hope to add more in
January. Wish us luck and perseverance. We'll need both.
Have A Happy New Year,
Charles Clarkson
</pre>
</blockquote>
<pre wrap="">_______________________________________________
wp-docs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wp-docs@lists.automattic.com">wp-docs@lists.automattic.com</a>
<a class="moz-txt-link-freetext" href="http://lists.automattic.com/mailman/listinfo/wp-docs">http://lists.automattic.com/mailman/listinfo/wp-docs</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>