TDF/LibreOffice Brochure-Type: QA Specific

From The Document Foundation Wiki
Jump to: navigation, search

Welcome to the LibreOffice Brochure-Type: QA Specific

This wiki is the workspace for the elaboration of a LibreOffice QA Specific brochure. The purpose is to systematically construct the content/text leading to the design/construction of its brochure. The content/text will be built in steps:

Step 1: Identify the different points to be included in the brochure

  • use point form for the content
  • use as many points as possible as these will later be picked through for the writing of the text


Step 2: Write the text according to the points from step 1.

  • proof the text
  • get approval from the marketing team and oversight by Italo/Charles


Step 3: Put text on the official template

  • add icons/graphics where necessary (may need some help from design team)
  • trim/add text where necessary
  • white space is not a bad thing; give the eyes a rest


Step 4: Complete Official/Community Brochure Versions

  • get approval from marketing/design teams as well as oversight from Italo/Charles
  • once approved complete Official A4/USLtr and Community A4/USLtr brochures
  • have marketing/design team do one last verification


Step 5: Complete a .pdf Version for Electronic Posting

  • get approval from marketing/design teams as well as oversight from Italo/Charles
  • once approved complete a .pdf version for electronic postings on websites, for emails etc.
  • the format of the electronic may change depending on the needs, but a generic-ready format should suffice for most needs
  • have marketing/design team do one last verification


Step 5:Announce on Projects list
{"cc_re__cc_re__cc_by_sa_3_0": ["ooter-info-credits\">This page was last edited 13:41:30, 2014-03-15 by <a href=\"/User:CleanupBot\" title=\"User:CleanupBot\">Dennis Roczek</a>. Based on work by <a href=\"/WikiAction/edit/User:Pilavi?redlink=1\" class=\"new\" title=\"User:Pilavi (page does not exist)\">Pierre Lavigne</a> and <a href=\"/User:Marcpare\" title=\"User:Marcpare\">Marc Par\u00e9</a>.</li>\n\t\t\t\t\t\t\t\t\t\t\t<li id=\"footer-info-copyright\">Please note that all contributions to The Document Foundation Wiki are considered to be released under the <a href=\"https://creativecommons.org/licenses/by-sa/3.0/\">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>, unless otherwise specified. This does not include the source code of LibreOffice, which is licensed under the GNU Lesser General Public License (<a href=\"https://www.libreoffice.org/download/license/\">LGPLv3</a>). \"LibreOffice\" and \"The Document Foundation\" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subjec"], "copyright__copyright__copyright": ["marketing/design team do one last verification\n\n\nStep 5: Complete a .pdf Version for Electronic Posting\n\n  \u2022 get approval from marketing/design teams as well as oversight from Italo/Charles\n  \u2022 once approved complete a .pdf version for electronic postings on websites, for emails etc.\n  \u2022 the format of the electronic may change depending on the needs, but a generic-ready format should suffice for most needs\n  \u2022 have marketing/design team do one last verification\n\n\nStep 5:Announce on Projects list", "marketing/design team do one last verification\n\n\nStep 5: Complete a .pdf Version for Electronic Posting\n\n  \u2022 get approval from marketing/design teams as well as oversight from Italo/Charles\n  \u2022 once approved complete a .pdf version for electronic postings on websites, for emails etc.\n  \u2022 the format of the electronic may change depending on the needs, but a generic-ready format should suffice for most needs\n  \u2022 have marketing/design team do one last verification\n\n\nStep 5:Announce on Projects list", "marketing/design team do one last verification\n\n\nStep 5: Complete a .pdf Version for Electronic Posting\n\n  \u2022 get approval from marketing/design teams as well as oversight from Italo/Charles\n  \u2022 once approved complete a .pdf version for electronic postings on websites, for emails etc.\n  \u2022 the format of the electronic may change depending on the needs, but a generic-ready format should suffice for most needs\n  \u2022 have marketing/design team do one last verification\n\n\nStep 5:Announce on Projects list", "marketing/design team do one last verification\n\n\nStep 5: Complete a .pdf Version for Electronic Posting\n\n  \u2022 get approval from marketing/design teams as well as oversight from Italo/Charles\n  \u2022 once approved complete a .pdf version for electronic postings on websites, for emails etc.\n  \u2022 the format of the electronic may change depending on the needs, but a generic-ready format should suffice for most needs\n  \u2022 have marketing/design team do one last verification\n\n\nStep 5:Announce on Projects list", "marketing/design team do one last verification\n\n\nStep 5: Complete a .pdf Version for Electronic Posting\n\n  \u2022 get approval from marketing/design teams as well as oversight from Italo/Charles\n  \u2022 once approved complete a .pdf version for electronic postings on websites, for emails etc.\n  \u2022 the format of the electronic may change depending on the needs, but a generic-ready format should suffice for most needs\n  \u2022 have marketing/design team do one last verification\n\n\nStep 5:Announce on Projects list", "marketing/design team do one last verification\n\n\nStep 5: Complete a .pdf Version for Electronic Posting\n\n  \u2022 get approval from marketing/design teams as well as oversight from Italo/Charles\n  \u2022 once approved complete a .pdf version for electronic postings on websites, for emails etc.\n  \u2022 the format of the electronic may change depending on the needs, but a generic-ready format should suffice for most needs\n  \u2022 have marketing/design team do one last verification\n\n\nStep 5:Announce on Projects list", "marketing/design team do one last verification\n\n\nStep 5: Complete a .pdf Version for Electronic Posting\n\n  \u2022 get approval from marketing/design teams as well as oversight from Italo/Charles\n  \u2022 once approved complete a .pdf version for electronic postings on websites, for emails etc.\n  \u2022 the format of the electronic may change depending on the needs, but a generic-ready format should suffice for most needs\n  \u2022 have marketing/design team do one last verification\n\n\nStep 5:Announce on Projects list", "marketing/design team do one last verification\n\n\nStep 5: Complete a .pdf Version for Electronic Posting\n\n  \u2022 get approval from marketing/design teams as well as oversight from Italo/Charles\n  \u2022 once approved complete a .pdf version for electronic postings on websites, for emails etc.\n  \u2022 the format of the electronic may change depending on the needs, but a generic-ready format should suffice for most needs\n  \u2022 have marketing/design team do one last verification\n\n\nStep 5:Announce on Projects list"]}