davestewart

Kalessin,
Thanks for the reply.

1. Ok. So you’re saying it’s best to write my own custom functions? Using raw data where I can, and regexp-ing the rest? Sounds doable.
And I get your point about the standard install.

2. I’m all up on semantic markup. I’ll rephrase (and possibly edit the original post’s question) was why is *data* and *markup* mixed. (This is really a follow-on question from #1)

3. Oh come on! The effort it takes to write a function definition is negligible!! Writing a function might take hours, days, or even weeks.

A definition that extracts the arguments, and specifies the return type, would take 5 minutes. A basic example perhaps another 10!

As I’ve said, with little consistency in function return-types, I’d waste more than 5 minutes trying to work out what’s going on. Multiply that by 1000s of users and… well, you get the picture.

“Memo to all staff: please document your functions, then email the webmaster who will publish them online.”

With regards to me putting in the effort, I understand where you’re coming from, but a misplaced work ethic I think:

“All of the documentation at the Codex has been produced by users like you and me!” reads to me as “We can’t be assed to finish the job! We’d rather get onto something more interesting!”

Let’s get everyone up to speed with the basics of documentation then let the newly-informed give something back once they know what the hell is supposed to do what.

I’m ALL up for development time, but this is a job half-done, I’m afraid, and you’re not going to be changing my mind on this one.

In this age of web apps and free frameworks, documentation is a prerequisite.

https://docs.jquery.com/Main_Page
https://www.prototypejs.org/api
https://codeigniter.com/user_guide/toc.html

Thanks for the input,
Cheers,
Dave

Just create a new theme and remove the comments php / html from the post pages.

Simple if you know some basic PHP / HTML.