**Concept National Pages** **Maintenance ownership** * The national pages will be hosted on typo3.org and avaliable in a subnavigation as well. * Several people can have access to one single instance * Access is taken care of centrally by Ben the community manager **What for?** * Have a welcome page in the local language. * Information of TYPO3 activity in your region/country. * Foster the local community building and TYPO3 marketing. * Overruling typo3.xxx domains by an official TYPO3 country website **Risks:** * Updating is not taken care of. * ..... **Solutions:** * Having the national pages within the typo3.org installation as subdomain landingpages ( "countryShortName.typo3.org", eg. de.typo3.org). * Having default content on these pages that already supplies the page with enough up2date content. **Standard Content** * All typo3.org news relevant for that country. There are two ways to achive that: * Authors of English news decide that this is relevant for a country, too. By adding it to a specific country category it is displayed on that national page (in English, though). [ben] are you sure thata the news should be in english if the welcome page is in the local lang? * [Roberto]In my opinion, all information should be translated: we need a team that translated into national language quickly. For example, an Italian user that connects to the Italian page, do not want to find information in English, otherwise it looks on the main page. * National committes can translate existing news. Translated news get displayed autmatically on the national pages. [ben] translation in this case would mean a new news item right. i thin kit would be an overkill to work with language overlays. it is hard to say for me i have been out of the business for a while. please explain. * National committes can add news in their language only. These news only get displayed on the national pages.[ben] So that means new news categories? [Roberto] or new folder * All typo3.org events relevant for that country: * Event organizers can send in the event details in English and in one or more localizations that make them appear also on national pages. * All international events in a country (e.g. T3CON, intl. T3Camps, T3SAIL) will be shown, too, but in English language, which is fine for int'l events. [Roberto] better translated * Dates of upcoming releases. Which do not need too much localization (just the labels and the date format). * Local TYPO3 PSL: A copy of the PSL but preselected on the country of the page (that preselection can be changed by the visitor of course to find PSLs in other countries too). [ben] we should really ask the tech guys how this could be realised. I would rather say it is the same plugin, but then configured differently. Not a copy. [Roberto] on PSL page there is a filter country * Filtered Listing of local TUGs. [ben]what exactly is the filtering here? * Filtered screenshots of local TYPO3 show cases from the case study / reference module of typo3.org. [ben] The references are tied to companies on typo3.org, right? I guess those are just screenshots with some description then? **Obligatory content:** Obligatory content is content that has to be provided by the national team: * translation of \url{http://typo3.org/about/typo3-the-cms/} * translation of language labels for the PSL extension * translation of language labels for events extension * translation of welcome text (to be written) * translation of TYPO3 international * [roberto] List of Certified Integrator and association members? **Individual content:** Can be added by the national teams as news only - to make sure the content is up2date. **Site Navigation Structure:** * Home (news latest, events, latest, welcome text, references, other widgets that can be easily provided) * hidden: News List \& Detail View * About (translation of \url{http://typo3.org/about/typo3-the-cms/)} * Community * Events List \& Detail View * Local TUGs * PSL * Contact to the national team (with a short introduction of it's members) * TYPO3 International (external link to typo3.org)