Skip to main content

Documents Management

Which document platform to use

WeWorking canon allGoogle agreeDocs thereenables areyou tooto manyshare information in a fluid and integrated way with others by taking comments and suggestions. However, it is not secure for sharing sensitive information. Remember to make final versions "View Only" so they can’t be changed.

For docs with sensitive info or spicy actions work in Cryptpad with password protection in place.

Document Format & Structure

  • Don't use italics. See Accessible documents lying& around!outreach Hopefully,materials these.

    tips
    • will help us all be less overwhelmed by being more organised.

  • Add Document Specs (aim, date and origin of the doc) at the top of your documents. It makes clear to everyone reading what the doc seeks to achieve and prevents docs being circulated that spread misinformation. See below for a template

  • Karla is the preferred sans serif font for XR UK documents

  • For titles use XR’s FUCXed CAPS if you can download integrate it. This isn't possible in Google Docs, so use Oswald instead

  • For important documents that will be circulated publicly, please use the Style Guide for guidance on formatting, sizing of graphic design visuals etc. Please.

    note
    • that
  • Karla is

    Make the preferred sans serif font for XR UK documents.

    Working on Google Docs enables you to share information in a fluid and integrated way with others by taking comments and suggestions. However, it is not secure for sharing sensitive information, and there are concerns about how muchname of the contentdoc onclear Googleand Docsdifferent to other docs.

  • Keep it short - rebels are overloaded with information!

  • Do not include spicy information or implicate organisers.

Document Specs template

Try to include as many of these as you can at the top of your docs, but not all are compulsory. E.g. If the status of a doc is ‘finished’ (and is for an event/specific rebellion) it may benot beingalways harvested.require Remembera timeline.

Date Created:			DD/MM/YY
Author: 				Name and role
Contributors:			Names and roles or groups / circles
Stakeholders: 			Names and roles or groups / circles
Intended distribution:  Groups, circles, people - or "Do not share!"
Status: 				FINISHED/DRAFT/IN PROGRESS/Safe enough to maketry
finalPurpose: 				versionsTo switcheddo tothis, View Only so they can’t be changed.


For docs with sensitive infothat or spicythe actionsother
workTimeline:				inFor Cryptpadthis withweek/that passwordmonth/that protectionduration
inFeedback:				place.
Please use comments/email mail@mail.mail
Back to top