Compare commits
11 Commits
1333203ade
...
master
| Author | SHA1 | Date | |
|---|---|---|---|
| 2e21174561 | |||
| da6a99e71a | |||
| beb307fe78 | |||
| ff4f9fc598 | |||
| 8817061171 | |||
| 8ca0e988bc | |||
| 5e41a0e18c | |||
| a36f130593 | |||
|
|
221035eb4e | ||
|
|
11f46e2b95 | ||
|
|
d04320aeab |
3
.gitmodules
vendored
Normal file
@@ -0,0 +1,3 @@
|
||||
[submodule "writedown"]
|
||||
path = writedown
|
||||
url = https://github.com/dyne/writedown
|
||||
142
MCL.md
@@ -1,15 +1,6 @@
|
||||
|
||||
## IMPACT
|
||||
`Aspra: this should be moved to chapter 8 i.e. metrics`
|
||||
Because of its decentralised and innovative nature, LEDGER MarCom's pragmatic impact cannot be measured in a linear and progressive way a priori. By leveraging from the evaluators and mentors communities, together with consortium partners, LEDGER will aim at building independent and autonomous groups which will endorse LEDGER's model and value proposition in order to disseminate in their civi, policymaking, developmental and business practices in a decentralised way and throughout the six verticals animating MVPs production.
|
||||
|
||||
More than quantitative KPIs, MarCom will aim at involving communities and individuals who have a prior engagement in their activities which overlaps, completely or in part, with LEDGER’s values and value proposition. The updating and further dissemination of LEDGER’s output should count on communities who have already an ethos that is compatible with decentralised data governance.
|
||||
In this context, LEDGER aims at providing a decentralised development ecosystem, which can serve the rods communities’ needs in terms of both technical and marketability standpoints.
|
||||
|
||||
|
||||
## Content Production Management and Distribution Strategy for LEDGER
|
||||
|
||||
The role of Ledger in terms of the marketing and communication strategy can be thought as the **Attractor** that aims to create a larger community by bringing together the following four communities: citizens and consumers, software developers, policymakers and commercial entities. Emphasis will be put on the engagement of those parties, which in turn will contribute to the communication and dissemination of Ledger's values as emerging from the Strategic Research and Innovation Work Programme and the descending business value proposition. Ledger as an attractor is a dynamic process in which such communities, and related stakeholders, will converge over time to provide a space for direct engagement and production of optimal exploitation strategies around the project's outcomes.
|
||||
The role of Ledger in terms of the marketing and communication strategy (MarCom hereafter) can be thought as the _Attractor_ that aims to create a larger community by bringing together the following four communities: citizens and consumers, software developers, policymakers and commercial entities. Emphasis will be put on the engagement of those parties, which in turn will contribute to the communication and dissemination of Ledger's values as emerging from the Strategic Research and Innovation Work Programme and the descending business value proposition. Ledger as an attractor is a dynamic process in which such communities, and related stakeholders, will converge over time to provide a space for direct engagement and production of optimal exploitation strategies around the project's outcomes.
|
||||
|
||||
Unlike most Push Marketing practices endorsed in the conventional market place, LEDGER’s MarCom strategy shall aim at pulling in and securing the involvement of the proper parties, i.e. those who can understand and appreciate LEDGER’s ethos values and business value proposition. Marketing activities will be organised at the light of the marketability needs of each vertical in order to promote a collaborative economy framework wherein each contributing party will acknowledge a direct and impactful engagement. (for details see sec. 4)
|
||||
|
||||
@@ -27,83 +18,80 @@ The software community will be engaged mailnly with the use of public code repos
|
||||
|
||||
Policymakers are the communities that have a remarkable negotiable power in terms of project outreach outside the MVPs lab environment. Thus, at the policymaking level, LEDGER MarCom strategy will target both individuals and groups who have a stake into the outcomes of the project. LEDGER will therefore encourage marketing, communication and dissemination activities to influence opinion and decision making processes within the policy domain by directly informing and attending to events promoted first and foremost by the Commission and relevant Directorates General, esp. those relevant to the implementation of solutions to problems affecting LEDGER’s verticals.
|
||||
|
||||
### Business communities `aspra: I suggerst name change and shortening of this paragraph.`
|
||||
LEDGER success will be measured in terms of uptake of its MVPs by the market populated by citizens and consumers enabled to access business models that serve their needs while avoiding to ask anything in exchange without their previous knowledge and consent. As a result and thanks to FBA and BLM’s leading roles, consumers and business communities will be involved as a central dissemination and communication channel to promote and grow LEDGER’s values and value proposition. Both are structurlly interwoven, in that values cannot be framed independently of the value proposition underpinning them. This will in fact be the primary marketing and communication strategy for the project, because it is, to our knowledge, the aspect that mostly characterises LEDGER when compared to other in ether public or private endeavours in the decentralised data governance areas.
|
||||
### Business Perspectives
|
||||
LEDGER success will be measured in terms of uptake of its MVPs by the market populated by citizens and consumers enabled to access business models that serve their needs while avoiding to ask anything in exchange without their previous knowledge and consent. As a result and thanks to FBA and BLM’s leading roles, consumers and business communities will be involved as a central dissemination and communication channel to promote and grow LEDGER’s values and value proposition. Both are **structurally interwoven**, in that values cannot be framed independently of the value proposition underpinning them. This will in fact be the primary marketing and communication strategy for the project, because it is, to our knowledge, the aspect that mostly characterises LEDGER when compared to other in ether public or private endeavours in the decentralised data governance areas.
|
||||
|
||||
Indeed, business communities are getting more and more aware about the topics and importance of the agenda that LEDGER is embodying. In turn, they are central for the uptake and upscaling of MVPs from LEDGER in that they can enjoy the adequate position and community outreach for large scale adoption of LEDGER’s venture builder solutions.
|
||||
|
||||
To synthesize?
|
||||
|
||||
|
||||
## 1. Editorial guidelines
|
||||
|
||||
This editorial guidelines are here to provide all partners and involved participants with the essential information that needs to be distributed in all the stages of the duration of the LEDGER project as well as after the closing of the project in order to additionally provide with fulfilling the projects goals.
|
||||
These editorial guidelines are meant to provide all partners and involved participants with the essential information that needs to be distributed in all stages of the LEDGER project as well as after the closing of the project. In the following paragraphs, the content creation, internal validation, as well as the distribution and evaluation of the impact is analysed and exposed and the necessary workflow is drafted.
|
||||
|
||||
Content Creation, internal validation, distribution and evaluation of impact is analysed and exposed and the necessary workflow drafted.
|
||||
All content developed for the project communication should attract participants to both Open Calls of the project. It should clearly express the characteristics, ethos and values of the Ledger project and it should be available for change, so that it can reflect the evolution of the project in all iterations during its 3 years duration. The MarCom of the project shall equally promote and document the development of the project through the sum of the participants work, the evolution of the technologies and the progress being made in each vertical.
|
||||
|
||||
Content should attract participants for the first as well as the second Open Call of the project; express the characters of the ledger project through and within the single project highlights and results and be available to be changed to reflect the evolution of the project in his itearations during the 3 years. Communication and marketing of the project should equally promote and document the development of the project through the sum of the participants work, the evolution of the technologies and the progress being made in each vertical. Content distribution tactics and special needs are as well hinted.
|
||||
|
||||
The guidelines will be visible to the participants, however it is expected that close monitoring of the communication spaces and some hands-on editing will be necessary in time by the Dyne.org communication team and to be validated through pair review between partners.
|
||||
|
||||
The following document will be in place to ensure best possible compliance with the guidelines:
|
||||
- LEDGER project consortium partners, will be informed specifically about the time in the project where they should provide with promotional material and other communications content
|
||||
- Consortium partners in charge of organizing events and bootcamps as previously agreed on, will be instructed to provide with ways (access) in order to create video documentation and other content both for external and internal communication and for general documentation .
|
||||
As part of the communication coordination meetings in LEDGER project producing and enabling production of communication, marketing and documentation material will be addressed accordingly.
|
||||
Editorial guidelines will also be visible to the participants. However, it is expected that close monitoring of the communication spaces and some re-iterations of editing will be necessary by the Dyne.org communication team and they will need to be validated through pair review between partners.
|
||||
|
||||
Moreover, this document is in place to ensure the best possible compliance with timelines and guidlines; in particular:
|
||||
- The LEDGER project consortium partners will be informed specifically about the timelines in the project when they are expected to provide with promotional material and other communications content.
|
||||
- The Consortium partners in charge of organising events and bootcamps as previously agreed on, will be instructed to provide access to other partners and collaborators in order to facilitate the creation of video documentation and other produced content both for external and internal communication and documentation.
|
||||
|
||||
## 2. Structure of the materials and creation workflow
|
||||
|
||||
Production of communication materials and the act of communicate follows this first diagram.
|
||||
Internally there are two main repository for shared materials: files, images, tempates, modules, temporary sharing, project folders etc. go on cloud.dyne.org, code and documentation and collectively written complex documents go on gitea.dyne.org.
|
||||
Internally there are two main repository for shared materials: files, images, templates, modules, temporary sharing, project folders etc. go on cloud.dyne.org, code and documentation and collectively written complex documents go on gitea.dyne.org.
|
||||
|
||||

|
||||

|
||||
|
||||
Folder structure for the communication cross partners and with participants is to be kept in git or in nextcloud to availability of the consortium and the participants when necessary. Structure is the one summarised in the following tree.
|
||||
|
||||
Workflow and use instructions will be put in readme.md as it is custom with documentation in FLOSS development.
|
||||
Workflow and use instructions will be put in readme.md in the appropriate folders as it is custom with documentation in FLOSS development creating a seamless and interchangeable workflow between documentation and other communication oriented production.
|
||||
|
||||
Follows the proposed taxonomy replicated as a structure of folders
|
||||
What follows the proposed taxonomy replicated as a structure of folders
|
||||
|
||||
```
|
||||
|
||||
Communication
|
||||
├── 1.Brand
|
||||
├── 2.Moodboards
|
||||
│ ├── 1.Health
|
||||
│ ├── 2.Economy
|
||||
│ ├── 3.Mobility
|
||||
│ ├── 4.Public-Services
|
||||
│ ├── 5.EnergyAndSustainability
|
||||
│ └── 6.OpenInnovativeProjects
|
||||
├── 3.Texts
|
||||
│ ├── 1.Internal-EU
|
||||
│ ├── 2.External
|
||||
│ └── 3.Divulgative
|
||||
├── 4.NGI-Identity
|
||||
├── 5.SoftwareDocumentation
|
||||
├── 6.TV
|
||||
├── 7.Gadgets
|
||||
├── 8.Other
|
||||
├── 9.projects-firstround
|
||||
│ ├── 1.Health
|
||||
│ │ └── example-project-folder
|
||||
│ │ ├── press
|
||||
│ │ └── promo
|
||||
│ ├── 2.Economy
|
||||
│ ├── 3.Mobility
|
||||
│ ├── 4.Public-Services
|
||||
│ ├── 5.EnergyAndSustainability
|
||||
│ └── 6.OpenInnovativeProjects
|
||||
|
||||
1.Brand
|
||||
2.Moodboards
|
||||
1.Health
|
||||
2.Economy
|
||||
3.Mobility
|
||||
4.Public-Services
|
||||
5.EnergyAndSustainability
|
||||
6.OpenInnovativeProjects
|
||||
3.Texts
|
||||
1.Internal-EU
|
||||
2.External
|
||||
3.Divulgative
|
||||
4.NGI-Identity
|
||||
5.SoftwareDocumentation
|
||||
6.TV
|
||||
7.Gadgets
|
||||
8.Other
|
||||
9.projects-firstround
|
||||
1.Health
|
||||
- example-project-folder
|
||||
- press
|
||||
- promo
|
||||
2.Economy
|
||||
3.Mobility
|
||||
4.Public-Services
|
||||
5.EnergyAndSustainability
|
||||
6.OpenInnovativeProjects
|
||||
|
||||
```
|
||||
|
||||
What is about the LEDGER-NGI Brand is collected in 1. Brand,
|
||||
2.Moodboards is the proposed way to collect emotional and visual contents at this stage, to be replicated with projects and kept as reference and documentation.
|
||||
3. is the vault for reference text, divided in tree registers, the internal and eu jargon text, the text made and meant for external communication and the divulgative one, intended for general audience. This allows to make text easy to find.
|
||||
1. What is about the LEDGER-NGI Brand is collected in 1. Brand;
|
||||
2. Moodboards is the proposed way to collect emotional and visual contents at this stage, to be replicated with projects and kept as reference and documentation.
|
||||
3. is the vault for reference text, divided in tree registers, the internal and eu jargon text, the text made and meant for external communication and the outreach one, intended for general audiences. This should allow to make text easy to find and reusable.
|
||||
|
||||
### 2.1 General communication groups
|
||||
|
||||
The general componence and cross appartenence of people to a group is indicated in the following diagram. Sets are in different color and they overlap when is necessary, while the diameter of the circle gives an idea of the number of people involved in the group. We will use similar representation further on.
|
||||
Appartenence of all participants to a group is indicated in the following diagram. Sets are in different color and they overlap when is necessary, while the diameter of the circle gives an idea of the number of people involved in the group. We will use similar representation further on.
|
||||
|
||||

|
||||
|
||||
@@ -114,20 +102,21 @@ Let's go to give a close look to the communication materials gathered so far and
|
||||
Chapter 3 refers to the materials for communication, were they are stored, how they need to be used.
|
||||
|
||||
### 3.1. Brand (/Communication/1.Brand)
|
||||
LEDGER project has to be integrated into NGI brand guidelines `ref??` and has to be divagated in the contexts created by NGI. At the same time the communication aim of LEDGER wants to outreach to communities of FLOSS developers and more marginal communities that might be alienated by the language, both visual and in other ways narrative of a traditional campaign. This document aims to be a guide that includes this perspective.
|
||||
LEDGER project has to be integrated into NGI brand guidelines and has to be divagated in the contexts created by NGI. At the same time the communication aim of LEDGER wants to outreach to communities of FLOSS developers and more marginal communities that might be alienated by the language, both visual and in other ways narrative of a traditional campaign. This document aims to be a guide that includes this perspective.
|
||||
|
||||
#### 3.1.1. brand book for LEDGER project
|
||||
A Brand book is a very good tool for general communication. It can evolve from the coordinate communication already studied for Ledger Project.
|
||||
A Brand book is a very good tool for general communication (1). It can evolve from the coordinate communication already studied for Ledger Project.
|
||||
It includes though some simplified answers to generic questions that allow to present the project properly to any of the people involved.
|
||||
It includes as well a general visual guideline.
|
||||
The book is a living doc that includes synonyms and explanations for key concepts.
|
||||
|
||||
You can find as an example the brand book on NGI here:- https://www.ngi.eu/resources/promo-materials/
|
||||
(1) You can find as an example the brand book on NGI here:- https://www.ngi.eu/resources/promo-materials/
|
||||
|
||||
Another excelent tool for expressing the narrative of the project is questions and answers. In FLOSS development this often took the form of FAQ.
|
||||
Another excellent tool for expressing the narrative of the project is questions and answers. In FLOSS development this often took the form of FAQ. **Always Collect good questions!**
|
||||
|
||||
Questions have to be gathered and answered and then a list of frequently recurring ones can be assembled.
|
||||
For the first phase of the project we refer to quesions and answer that help internally to all participants to answer to anyone asking to the basic questions regarding the project giving as such a good answer to a generic audience.
|
||||
|
||||
For the first phase of the project we refer to questions and answer that help internally to all participants to answer to anyone asking to the basic questions regarding the project giving as such a good answer to a generic audience.
|
||||
|
||||
##### Examples of Questions and Answers:
|
||||
- Q: What are you busy with?
|
||||
@@ -136,7 +125,6 @@ For the first phase of the project we refer to quesions and answer that help int
|
||||
|
||||
this tool will be elaborated by partners and included in the communication material as soon as it will be available.
|
||||
|
||||
[WORD CLOUDS GO Here]
|
||||
|
||||
|
||||
#### 3.1.2. general guidelines
|
||||
@@ -154,7 +142,9 @@ Some Examples of the textual material that will be compiled for the many editing
|
||||
|
||||
[I include here below the text we already have in this register, I will decouple it from the file later on.]
|
||||
|
||||
##### Basic information and main goals of the LEDGER project
|
||||
NOTE: In the mean time NGI has changed completely the logo and the brand guidelines (may 2019) compliance is requested before September 2019
|
||||
|
||||
##### Basic information and main goals of the LEDGER project as implied by the Verticals
|
||||
|
||||
LEDGER - Decentralised Data Governance for the Next Generation Internet - is a project funded by the European Commission (GA 825268 - http://ledgerproject.eu/). Between 2019 and 2021, the LEDGER project has the mandate to distribute financial support to third parties in a cascade funding framework named Venture Builder Programme.
|
||||
|
||||
@@ -230,9 +220,9 @@ The successful project will be characterised by the interference of the four dif
|
||||
The envisioned concepts should relate in a way introduced by the Free Culture Movement and F/OSS based economies.
|
||||
|
||||
|
||||
#### 3.4.1 Virtuose creation
|
||||
#### 3.4.1 Virtuos creation
|
||||
|
||||
Semiotic square of virtuose creation
|
||||
Semiotic square of virtuos creation
|
||||
|
||||
> image should be remade to fit brand identity
|
||||
|
||||
@@ -254,6 +244,7 @@ NGI has a set of wide area communication tools in place we are request to contri
|
||||
|
||||
### 3.6. Software Documentation (/Communication/5.SoftwareDocumentation)
|
||||
> Fill in guidelines for acceptable and good documentation, role of public and private GIT etc
|
||||
> standard guidelines for github are ok
|
||||
|
||||
### 3.7. TV and Web integration Materials (/Communication/6.TV-Web)
|
||||
|
||||
@@ -296,11 +287,13 @@ We are available to procure a professional WEB TV studio and a crew to assemble
|
||||
- Stickers
|
||||
|
||||
all we might come up with; the design will be kept here.
|
||||
NB: some stuff has been sent over by ngi
|
||||
|
||||
### 3.9. Other (/Communication/8.Others)
|
||||
|
||||
To say to Andres if he please replicate communication folder on google docs here were appropriate.
|
||||
- Whitepapers templates
|
||||
- Roll-up
|
||||
NB: fredd:One Ledger Rollup is now with dyne.org
|
||||
- Poster
|
||||
- Vision Poster
|
||||
- Presentation templates
|
||||
@@ -325,7 +318,6 @@ We want to share some important performance indicators upfront with all particip
|
||||
- Early stage to delivery: The teams might be composed by individuals, but also by employees from small or medium enterprises, in which cases the group will be closely evaluated for their human-centric approach and the will to collaborate with the rest of the LEDGER community.
|
||||
|
||||
|
||||
|
||||
## 6. Participants
|
||||
How we will treat Participants
|
||||
|
||||
@@ -353,12 +345,12 @@ Here a selection of the materials of the participants: names and logos, short pi
|
||||
|
||||
## 7. Distribution of contents
|
||||
|
||||
- Web site (founding box)
|
||||
- Founding Box Community (founding box app)
|
||||
- Web site (Funding Box)
|
||||
- Funding Box Community (Funding box community platform)
|
||||
- Social (dyne.org network, public space)
|
||||
|
||||
### 7.1. Sharers and influencers
|
||||
- Founding Box Community [to paste a description here]
|
||||
- Funding Box Community [to paste a description here]
|
||||
- Influencer List (special list?)
|
||||
- Internal mailinglist
|
||||
- External Mailing list
|
||||
@@ -370,8 +362,8 @@ How to treat press in events, in press releases, modules and templates
|
||||
Overview and guidelines
|
||||
`missing content`
|
||||
|
||||
### 7.4. FoundingBox social network and communities
|
||||
In dept guideline for partners on how to use FoundingBox app
|
||||
### 7.4. FundingBox social network and communities
|
||||
In dept guideline for partners on how to use FundingBox app
|
||||
`missing content`
|
||||
|
||||
### 7.5. Social Media
|
||||
@@ -382,5 +374,5 @@ Other social Network Hashtag policies
|
||||
`missing content`
|
||||
|
||||
## 8. Metrics
|
||||
How do we measure the impact of our communication, how do we keep track of it and how and when do we correct the range of our communication narratives on this project?
|
||||
`missing content`
|
||||
Because of its decentralised and innovative nature, LEDGER MarCom's pragmatic impact cannot be measured in a linear and progressive way a priori. By leveraging from the evaluators and mentors communities, together with consortium partners, LEDGER will aim at building independent and autonomous groups which will endorse LEDGER's model and value proposition in order to disseminate in their civi, policymaking, developmental and business practices in a decentralised way and throughout the six verticals animating MVPs production.
|
||||
More than quantitative KPIs, MarCom will aim at involving communities and individuals who have a prior engagement in their activities which overlaps, completely or in part, with LEDGER’s values and value proposition. The updating and further dissemination of LEDGER’s output should count on communities who have already an ethos that is compatible with decentralised data governance.
|
||||
|
||||
15
README.md
@@ -1,10 +1,13 @@
|
||||
Content is at the moment as follows:
|
||||
Revision 3 16 July 2019
|
||||
by fredd
|
||||
|
||||
- Marcom.md document is the contribution of Radium, as on pad 17 jan 8:20 with small typos corrected
|
||||
- layout.md contains the contribution of Elena and Fredd and is a practical documents
|
||||
- MCL.md is the main document
|
||||
- live doc is on gitea to be monitored with git
|
||||
|
||||
my first merge of the docs is in MCL.md that therefore is the one to read to give compartments
|
||||
|
||||
the index of the doc has been worked up on pad https://pad.dyne.org/code/#/1/edit/1vtinoUpsmYruHjDHiW+Ng/CrTbI64coYYuDY72TIheqOkW/
|
||||
|
||||
Structures of folders has to be kept aligned with doc!
|
||||
|
||||
NB:
|
||||
- Structures of folders has to be kept aligned with doc!
|
||||
- Careful with the extra files that are due for the use of writedown, do not delete anything. Ref: writedown.dyne.org
|
||||
- obsolete documents have been moved under the old/ folder
|
||||
|
||||
34
config.zsh
Normal file
@@ -0,0 +1,34 @@
|
||||
# Writedown
|
||||
# generic configuration defaults for rendered files
|
||||
|
||||
WRITEDOWN_TITLE="LEDGER Communication Plan"
|
||||
WRITEDOWN_AUTHOR="Dyne.org"
|
||||
WRITEDOWN_AFFILIATION="Dyne.org Foundation"
|
||||
WRITEDOWN_DATE="Wednesday 18 October 2017"
|
||||
WRITEDOWN_TAGS="[communication, growth, hacking, community, development]"
|
||||
|
||||
# number for each section
|
||||
WRITEDOWN_NRSEC=yes
|
||||
# table of contents
|
||||
WRITEDOWN_TOC=yes
|
||||
# bibliographic citation style (see writedown/citstyle)
|
||||
WRITEDOWN_CITSTYLE=harvard-kings-college-london
|
||||
# font size
|
||||
WRITEDOWN_FONTSIZE=14pt
|
||||
# bibtex file for bibliographic sources
|
||||
# WRITEDOWN_BIB=./views/references.bib
|
||||
# latex template (header and footer)
|
||||
#WRITEDOWN_LATEX_TEMPLATE=/usr/share/pandoc/data/templates/latex.tex
|
||||
|
||||
# different formats as supported by pandoc.
|
||||
# to activate uncomment and fill, then use dash (-) as first argument
|
||||
# i.e: ./writedown/render -
|
||||
# WRITEDOWN_OUTPUT_FORMAT=epub
|
||||
# WRITEDOWN_OUTPUT_EXTENSION=epub
|
||||
|
||||
# default pandoc base command
|
||||
# WRITEDOWN_PANDOC="pandoc --smart --standalone -f markdown
|
||||
|
||||
# Experimental features are commented below
|
||||
|
||||
# WRITEDOWN_ZOTERO="no"
|
||||
BIN
pub/LEDGER_Communication_Plan.docx
Normal file
BIN
pub/LEDGER_Communication_Plan.pdf
Normal file
0
views/abstract.txt
Normal file
|
Before Width: | Height: | Size: 132 KiB After Width: | Height: | Size: 132 KiB |
|
Before Width: | Height: | Size: 191 KiB After Width: | Height: | Size: 191 KiB |
|
Before Width: | Height: | Size: 170 KiB After Width: | Height: | Size: 170 KiB |
|
Before Width: | Height: | Size: 172 KiB After Width: | Height: | Size: 172 KiB |
|
Before Width: | Height: | Size: 257 KiB After Width: | Height: | Size: 257 KiB |
1
views/index.txt
Normal file
@@ -0,0 +1 @@
|
||||
MCL.md
|
||||
179
views/template.tex
Normal file
@@ -0,0 +1,179 @@
|
||||
\documentclass[a4paper]{extarticle}
|
||||
\usepackage{lmodern}
|
||||
$if(fontsize)$
|
||||
\usepackage[$fontsize$]{extsizes}
|
||||
$endif$
|
||||
\usepackage{fullpage}
|
||||
\usepackage{longtable}
|
||||
\usepackage{booktabs}
|
||||
\usepackage{amssymb,amsmath}
|
||||
\usepackage{ifxetex,ifluatex}
|
||||
\usepackage{fixltx2e} % provides \textsubscript
|
||||
\ifnum 0\ifxetex 1\fi\ifluatex 1\fi=0 % if pdftex
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage[utf8x]{inputenc}
|
||||
\else % if luatex or xelatex
|
||||
\ifxetex
|
||||
\usepackage{mathspec}
|
||||
\else
|
||||
\usepackage{fontspec}
|
||||
\fi
|
||||
\defaultfontfeatures{Ligatures=TeX,Scale=MatchLowercase}
|
||||
\fi
|
||||
% use upquote if available, for straight quotes in verbatim environments
|
||||
\IfFileExists{upquote.sty}{\usepackage{upquote}}{}
|
||||
% use microtype if available
|
||||
\IfFileExists{microtype.sty}{%
|
||||
\usepackage{microtype}
|
||||
\UseMicrotypeSet[protrusion]{basicmath} % disable protrusion for tt fonts
|
||||
}{}
|
||||
\usepackage{hyperref}
|
||||
\hypersetup{unicode=true,
|
||||
pdftitle={$title$},
|
||||
pdfauthor={$author$},
|
||||
$if(keywords)$
|
||||
pdfkeywords={$for(keywords)$$keywords$$sep$; $endfor$},
|
||||
$endif$
|
||||
pdfborder={0 0 0},
|
||||
breaklinks=true}
|
||||
\urlstyle{same} % don't use monospace font for urls
|
||||
\usepackage{xcolor}
|
||||
$if(listings)$
|
||||
\usepackage{listings}
|
||||
\lstset{
|
||||
basicstyle=\ttfamily,
|
||||
% numbers=left,
|
||||
numberstyle=\footnotesize,
|
||||
stepnumber=2,
|
||||
numbersep=5pt,
|
||||
backgroundcolor=\color{black!10},
|
||||
showspaces=false,
|
||||
showstringspaces=false,
|
||||
showtabs=false,
|
||||
tabsize=2,
|
||||
captionpos=b,
|
||||
breaklines=true,
|
||||
breakatwhitespace=true,
|
||||
breakautoindent=true,
|
||||
linewidth=\textwidth
|
||||
}
|
||||
$endif$
|
||||
\usepackage{color}
|
||||
\usepackage{fancyvrb}
|
||||
\newcommand{\VerbBar}{|}
|
||||
\newcommand{\VERB}{\Verb[commandchars=\\\{\}]}
|
||||
\DefineVerbatimEnvironment{Highlighting}{Verbatim}{commandchars=\\\{\}}
|
||||
% Add ',fontsize=\small' for more characters per line
|
||||
\newenvironment{Shaded}{}{}
|
||||
\newcommand{\KeywordTok}[1]{\textcolor[rgb]{0.00,0.44,0.13}{\textbf{{#1}}}}
|
||||
\newcommand{\DataTypeTok}[1]{\textcolor[rgb]{0.56,0.13,0.00}{{#1}}}
|
||||
\newcommand{\DecValTok}[1]{\textcolor[rgb]{0.25,0.63,0.44}{{#1}}}
|
||||
\newcommand{\BaseNTok}[1]{\textcolor[rgb]{0.25,0.63,0.44}{{#1}}}
|
||||
\newcommand{\FloatTok}[1]{\textcolor[rgb]{0.25,0.63,0.44}{{#1}}}
|
||||
\newcommand{\ConstantTok}[1]{\textcolor[rgb]{0.53,0.00,0.00}{{#1}}}
|
||||
\newcommand{\CharTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{{#1}}}
|
||||
\newcommand{\SpecialCharTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{{#1}}}
|
||||
\newcommand{\StringTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{{#1}}}
|
||||
\newcommand{\VerbatimStringTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{{#1}}}
|
||||
\newcommand{\SpecialStringTok}[1]{\textcolor[rgb]{0.73,0.40,0.53}{{#1}}}
|
||||
\newcommand{\ImportTok}[1]{{#1}}
|
||||
\newcommand{\CommentTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textit{{#1}}}}
|
||||
\newcommand{\DocumentationTok}[1]{\textcolor[rgb]{0.73,0.13,0.13}{\textit{{#1}}}}
|
||||
\newcommand{\AnnotationTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{{#1}}}}}
|
||||
\newcommand{\CommentVarTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{{#1}}}}}
|
||||
\newcommand{\OtherTok}[1]{\textcolor[rgb]{0.00,0.44,0.13}{{#1}}}
|
||||
\newcommand{\FunctionTok}[1]{\textcolor[rgb]{0.02,0.16,0.49}{{#1}}}
|
||||
\newcommand{\VariableTok}[1]{\textcolor[rgb]{0.10,0.09,0.49}{{#1}}}
|
||||
\newcommand{\ControlFlowTok}[1]{\textcolor[rgb]{0.00,0.44,0.13}{\textbf{{#1}}}}
|
||||
\newcommand{\OperatorTok}[1]{\textcolor[rgb]{0.40,0.40,0.40}{{#1}}}
|
||||
\newcommand{\BuiltInTok}[1]{{#1}}
|
||||
\newcommand{\ExtensionTok}[1]{{#1}}
|
||||
\newcommand{\PreprocessorTok}[1]{\textcolor[rgb]{0.74,0.48,0.00}{{#1}}}
|
||||
\newcommand{\AttributeTok}[1]{\textcolor[rgb]{0.49,0.56,0.16}{{#1}}}
|
||||
\newcommand{\RegionMarkerTok}[1]{{#1}}
|
||||
\newcommand{\InformationTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{{#1}}}}}
|
||||
\newcommand{\WarningTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{{#1}}}}}
|
||||
\newcommand{\AlertTok}[1]{\textcolor[rgb]{1.00,0.00,0.00}{\textbf{{#1}}}}
|
||||
\newcommand{\ErrorTok}[1]{\textcolor[rgb]{1.00,0.00,0.00}{\textbf{{#1}}}}
|
||||
\newcommand{\NormalTok}[1]{{#1}}
|
||||
\usepackage{graphicx,grffile}
|
||||
\makeatletter
|
||||
\def\maxwidth{\ifdim\Gin@nat@width>\linewidth\linewidth\else\Gin@nat@width\fi}
|
||||
\def\maxheight{\ifdim\Gin@nat@height>\textheight\textheight\else\Gin@nat@height\fi}
|
||||
\makeatother
|
||||
% Scale images if necessary, so that they will not overflow the page
|
||||
% margins by default, and it is still possible to overwrite the defaults
|
||||
% using explicit options in \includegraphics[width, height, ...]{}
|
||||
\setkeys{Gin}{width=\maxwidth,height=\maxheight,keepaspectratio}
|
||||
\IfFileExists{parskip.sty}{%
|
||||
\usepackage{parskip}
|
||||
}{% else
|
||||
\setlength{\parindent}{0pt}
|
||||
\setlength{\parskip}{6pt plus 2pt minus 1pt}
|
||||
}
|
||||
|
||||
% previously included by writedown in options.sty
|
||||
\setlength{\parindent}{1.25em}
|
||||
\setlength{\parskip}{.2em}
|
||||
\usepackage{etoolbox}
|
||||
\AtBeginEnvironment{quote}{\parskip 1em}
|
||||
|
||||
\setlength{\emergencystretch}{3em} % prevent overfull lines
|
||||
\providecommand{\tightlist}{%
|
||||
\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
|
||||
\setcounter{secnumdepth}{0}
|
||||
% Redefines (sub)paragraphs to behave more like sections
|
||||
\ifx\paragraph\undefined\else
|
||||
\let\oldparagraph\paragraph
|
||||
\renewcommand{\paragraph}[1]{\oldparagraph{#1}\mbox{}}
|
||||
\fi
|
||||
\ifx\subparagraph\undefined\else
|
||||
\let\oldsubparagraph\subparagraph
|
||||
\renewcommand{\subparagraph}[1]{\oldsubparagraph{#1}\mbox{}}
|
||||
\fi
|
||||
% END OF CONFIG ------------------------------------------
|
||||
|
||||
% START OF CONTENT ------------------------------------------
|
||||
|
||||
\title{$title$}
|
||||
$if(subtitle)$
|
||||
\providecommand{\subtitle}[1]{}
|
||||
\subtitle{$subtitle$}
|
||||
$endif$
|
||||
$if(author)$
|
||||
\author{$for(author)$$author$$sep$ \and $endfor$}
|
||||
$endif$
|
||||
$if(institute)$
|
||||
\providecommand{\institute}[1]{}
|
||||
\institute{$for(institute)$$institute$$sep$ \and $endfor$}
|
||||
$endif$
|
||||
\date{$date$}
|
||||
$if(logo)$
|
||||
\logo{\includegraphics{$logo$}}
|
||||
$endif$
|
||||
|
||||
\newcommand{\passthrough}[1]{\lstset{mathescape=false}#1\lstset{mathescape=true}}
|
||||
|
||||
\begin{document}
|
||||
|
||||
\maketitle
|
||||
|
||||
\begin{abstract}
|
||||
$abstract$
|
||||
\end{abstract}
|
||||
|
||||
\providecommand{\keywords}[1]{\textbf{\textit{Keywords---}} #1}
|
||||
$if(keywords)$
|
||||
\keywords{$for(keywords)$$keywords$$sep$; $endfor$}
|
||||
$endif$
|
||||
|
||||
\pagebreak[4]
|
||||
{
|
||||
\setcounter{tocdepth}{3}
|
||||
\tableofcontents
|
||||
}
|
||||
\pagebreak[4]
|
||||
|
||||
$body$
|
||||
|
||||
\end{document}
|
||||