Merge branch '143-document-be-group-concept' into 'develop'

Resolve "Document BE Group concept"

Closes #143

See merge request t3o/typo3.org!118

html/typo3conf/ext/t3org_layout/Configuration/PageTS/TceMain.txt

+TCEMAIN {
+   # Owner be_users UID for new pages:
+   permissions.userid = 1
+   # Owner be_groups UID for new pages:
+   permissions.groupid = 1
+
+   permissions {
+      # User can do anything (default):
+      user = 31
+      # Group can do anything
+      # (normally "delete" is disabled)
+      group = 31
+      # Everybody can at least see the page
+      # (normally everybody can do nothing)
+      everybody = show
+   }
+}

html/typo3conf/ext/t3org_layout/Documentation/administration/index.rst

+typo3.org Backend User Adminstration
+====================================
+
+Concept:
+-------
+
+Non Admin users, should receive at least one Role. The normal editor should get rights for the area he is responsible for.
+This is one of the "DBM (Database Mount)" groups.
+
+A user for
+
+* tHe role "editor" needs additional DBM groups to work
+* the "Powereditor" needs no further groups, as the powereditor can edit the whole tree (expect security data and some functional pages)
+
+
+Groups:
+-------
+
+
+=============================== ==========================================================================================
+title                           description
+=============================== ==========================================================================================
+PageTreeEditors	              Rights are set to enable any page action is enabled to this group. This group is set as a subgroup to any DBM group.
+Role: Editor                    This group provides std access to tables and editorial thing as well as basic user rights.
+Role: Powereditor               This kind of editor, is allowed to use every function and page mount (contains PageTreeEditors, Editor
+Role: News Editor               Allows to add and edit news (can be used without any other role)
+Role: Events                    Allows to add and edit events (can be used without any other role)
+Role: Association               Allows to edit Association pages and adds functions like Bannermanegment, memberdata
+Role: Security Team             Allows to edit the Team pages of the security team and allows to see and edit security bulletins
+Function: Certification Editor  Allows to edit certification data
+Function: Forms Editor	        Allows to edit forms
+Function: Roadmap	              Allows to edit the roadmap extension
+DBM Categories	                 This group carries PageTreeEditors as a subgroup and the db mount point set to "Categories".
+DBM Certification	              This group carries PageTreeEditors as a subgroup and the db mount point set to "Certification".
+DBM Community	                 This group carries PageTreeEditors as a subgroup and the db mount point set to "Community".
+DBM Documentation	              This group carries PageTreeEditors as a subgroup and the db mount point set to "Documentation".
+DBM Our Project	              This group carries PageTreeEditors as a subgroup and the db mount point set to "Our Project".
+DBM Quicklinks	                 This group carries PageTreeEditors as a subgroup and the db mount point set to "Quicklinks".
+DBM Support	                    This group carries PageTreeEditors as a subgroup and the db mount point set to "Support".
+DBM TYPO3 CMS	                 This group carries PageTreeEditors as a subgroup and the db mount point set to "TYPO3 CMS".
+==============================  ==========================================================================================
+
+

html/typo3conf/ext/t3org_layout/Documentation/concept/index.rst

+concept for typo3.org
+=====================
+
+
+Goals for typo3.org
+-------------------
+
+* TYPO3.org should provide its users easy and fast access to informations we want to transport
+* TYPO3.org should be the central information hub for our community
+* Increase number of TYPO3 users, community members, contributors and Association members
+* TYPO3.org should represent TYPO3 in a modern and professional way
+* TYPO3.org should likeable and friendly, like it’s community is
+
+Detailed document
+-----------------
+
+https://docs.google.com/document/d/1Zj-SDEH-da2RBOsnpsiiZ9-VGiNsgHXceEgfDXbWcT8/edit#heading=h.7ue47rmb7wx3

html/typo3conf/ext/t3org_layout/Documentation/editors_guide/index.rst

+editors guide
+=============
+
+Welcome to our typo3.org installation. As we work together in a large installation, it is important to keep our house clean.
+
+Folderstructure
+---------------
+
+====================== ===================================================
+Mount                  Description
+====================== ===================================================
+t3o_common             Main mount for all editors in the backend
+t3o_teams/...          entry point for teams (each team is able to access only it's own folder
+
+=====================  ===================================================
+
+Folderstructure /fileadmin
+--------------------------
+
+====================== ==================================================
+Folder                   Desc
+====================== ==================================================
+releases               contains keys
+resources              commit-msg hook for Git & Gerrit (see http://wiki.typo3.org/Contribution_Walkthrough_with_CommandLine)
+t3o_common-storage     Main folder for all content related files
+t3o_teams              Team related folders
+templates              This folder is needed for existing external integrations (f.e. PAYPAL Page) and contains example and placeholder images for internal use
+user_upload            Upload folder for files, which are not moved to their final position
+=====================  ==================================================
+
+
+Folderstructure /t3o_common-storage
+-----------------------------------
+
+====================== ==================================================
+Folder                   Desc
+====================== ==================================================
+documents              all documents, which should be downloaded (Association files, certification, branding, what_new_slides
+events                 Pictures of events (T3DD, camps, sprints)
+images                 Mail folder for all content images (banners, stock photos, logos, icons, ...)
+news                   Pictures for news entries, organized by "years  / month / article"
+videos                 Folder for videos
+=====================  ==================================================
+
+
+Folderstructure /t3o_teams
+-----------------------------------
+
+Each teams receive it's own folder, which is only accessible for the team it self.
+
+
+
+Important!
+----------
+
+Add always the source of the photo to the meta data. We need to enshure, that we don't hurt any picture rights
+
+
+
+Dont forget to
+--------------
+
+...dance, no in fact we have a small list of todos, which should follow:
+
+* add to all images alt (what can see at the image) and title (what do we want to tell) tags
+* add to all links a title tag (which tells, what you should expect behind the link)
+* add page description and usefule title tag (the SEO extension is your friend)
+
+Infos about filestorage

html/typo3conf/ext/t3org_layout/Documentation/index.rst

+typo3.org documentation
+=======================
+
+.. toctree::
+:maxdepth: 3
+
+      editors_guide/index.rst
+      administration/index.rst
+      concept/index.rst
+
+https://typo3.org
+-----------------
+
+This site is main for the TYPO3 community, TYPO3 Assocication and TYPO3 Users
+
+====================== ============== ============================== ======
+Name                   Function       email                          Admin
+====================== ============== ============================== ======
+Stefan Busemann        Product Owner  stefan.busemann@typo3.org      X
+Thomas Löffler         Team Leader    thomas.loeffler@typo3.org      X
+=====================  ============== ============================== ======