[Typo3-marketing] suggestion on workflow of new pages

[Robert Lemke]

Hi folks,

when did you have a free weekend the last time? I swear, it's worth it! I've 
been hiking in the mountains near Taragona with great sunny 13° and a clear 
sky ...

On Saturday 15 January 2005 10:31, Juergen Egeling wrote:
> All of the "in progress sites" should be on webservers in
> DNS names, that are unofficial, where we can work on, and
> only people that know the DNS can read it. E.g.
> For the new demo.typo3.com the "working se

This is a must. Today I will finish my written concept for typo3.org and 
publish it, regarding TYPO3 related sites and subdomain here's a quick 
overview:

  - We should use as few second level domains as possible (currently only
    typo3.org and typo3.com). Other domains are registered to prevent other
 people from doing that (like typo3assoc.org etc.)

  - When it makes sense we should use subdomains for subsites in order to
 make it easier separating them technically. Good examples are:
 
 bugs.typo3.org, association.typo3.org, edu.typo3.com, lists.typo3.org

 If these sites need some shared data like frontend users or news, we
 should syncronize that by some authentication service, SOAP or RSS
 feeds. 

 The goal is to make each site as robust and independend as we
 can, so if for example typo3.com gets hacked we can still communicate
 on association.typo3.org in order to take the neccessary measures. (Even
 better would be a secret communication server ...)

  - The existing sites which reside in the same installation (typo3.com
 and typo3.org etc.) should be separated at *some point* - but not now.
 It makes sense to first deploy the news system and analyze what crosslinks
 exist that would break.

  - When a new website is created we mustn't use the real subdomain / domain 
 for it while developing. In the case of demo.typo3.com it might be
 dev.demo.typo3.com. If the new site resides within the big typo3.org/
 typo3.com installation, we can easily handle that by using proper
 domain records.

> I suggest the same with all other stuff going on, as this
> takes out the the pressure on explaining why some pages
> are in non english, and gives the translators more time.
> The "old" pages are not as bad as "new pages" in non english,
> IMHO.

I agree.

-- 
Robert Lemke
Assessor - TYPO3 Association
http://association.typo3.org