[Typo3] RealURL For Dummies?

[Alex Heizer]

Hi all,

First, with any issues about documentation, here is what is already 
going on, just for the record. If these things need to be changed, 
please suggest alternatives that are workable that solve a global 
problem, not "well we need such-and-so document". Putting a bandage on a 
cut is a quick fix, and we need to be healing the whole body. :)

1. It has been asked on the official doc team that documentation 
discussions happen there. If you see a need for a document, please sign 
up and raise the issue there.
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-documentation

2. There is already a doc team. If you want to help out by volunteering 
to author a "needed" piece of documentation, please alert the doc team. 
There may already be a document in existence that you are unaware of, 
which will save you a lot of time. In addition, if the document does not 
exist, the information that should be in the document may exist, which 
will save you a lot of time.

3. There are already discussions on the doc list about how best to 
create/review/supplement documentation (the process, locations and 
systems in use). Please review that archive and make suggestions on that 
list about your ideas for how best to work with the documentation if you 
feel it should be different than the direction it is already heading in.

4. There is already a list of suggested documentation to be reviewed on 
the TYPO3 US forum. All of the documentation will be reviewed and/or 
created, but we need to prioritize so that we can get the most-needed 
items completed first and available to those who need them. Please 
contribute instead of discuss, since contributions help things get done 
quicker than mailing list discussions. If you haven't signed up yet, 
please go to http://test.typo3.us/forum/ and become part of the solution.

5. Kasper and others in the association have stated their desires that 
they want TYPO3 to become more popular in the US market. They have also 
stated that "English" means "US-English". Further, the default language 
for the TYPO3 English mailing list states quite clearly "English (USA)". 
The TYPO3 English language is US English. Let's move on.

6. If TYPO3 is to become more popular in the US, all of the 
documentation will have to be "cleaned up" and presented in a way that 
satisfies the sensibilities of the US market. This means anyone in the 
US who can make a decision or advise a decision-maker about implementing 
TYPO3 or any CMS. This is not negotiable, this is about giving the 
market what it needs, regardless of personal preferences by mailing list 
members about "US English" and "UK English". Let's move on.

7. There are many initiatives that can be found on http://test.typo3.us 
to improve the marketing of TYPO3 to the US market, the documentation is 
just one of those initiatives. As has been pointed out here many times, 
check the site for what is happening before suggesting what people 
"should" do. If you have a new idea about something, please raise it, 
there is a thread on the t3us forum for this. If you begin a new 
discussion about something that has already been decided and is in the 
works without checking the site, you are wasting everyone's time, and we 
could use your writing skills on the project instead of having them sit 
in our inboxes.

8. If after checking with the doc team to see if the document or 
information exists, or http://test.typo3.us to see if your idea for a 
project exists and are still not satisfied, please feel free to create 
your own site. You can also let us all know what it is so that we can 
benefit from the information, too.

I am sure I may have missed a few points. Please don't look for 
loopholes to argue about, we can use your energy making TYPO3, and its 
accompanying information and documentation better.

Thanks,
Alex