├── .devcontainer ├── Dockerfile └── devcontainer.json ├── .github └── workflows │ └── publish.yml ├── .gitignore ├── Dockerfile ├── README.md ├── content ├── contents.lr └── supporters │ ├── aaron-franco │ └── contents.lr │ ├── abe-stanway │ └── contents.lr │ ├── adam-mcgreggor │ └── contents.lr │ ├── adam-yeats │ └── contents.lr │ ├── alexandre-passant │ └── contents.lr │ ├── alexey-komissarouk │ └── contents.lr │ ├── alper-cugun │ └── contents.lr │ ├── andrew-mager │ └── contents.lr │ ├── andrew-nesbitt │ └── contents.lr │ ├── andrew-seward │ └── contents.lr │ ├── andy-piper │ └── contents.lr │ ├── angus-fox │ └── contents.lr │ ├── ankur-oberoi │ └── contents.lr │ ├── ariel-waldman │ └── contents.lr │ ├── carter-rabasa │ └── contents.lr │ ├── chad-mccallum │ └── contents.lr │ ├── chase-southard │ └── contents.lr │ ├── chris-weekly │ └── contents.lr │ ├── colin-loretz │ └── contents.lr │ ├── contents.lr │ ├── cristiano-betta │ └── contents.lr │ ├── daigo-fujiwara │ └── contents.lr │ ├── dan-cunningham │ └── contents.lr │ ├── daniel-appelquist │ └── contents.lr │ ├── daniel-knell │ └── contents.lr │ ├── derk-braakman │ └── contents.lr │ ├── dom-hodgson │ └── contents.lr │ ├── don-morrison │ └── contents.lr │ ├── dyego-cantu │ └── contents.lr │ ├── ezequiel-franca │ └── contents.lr │ ├── gunasekaran-sengodan │ └── contents.lr │ ├── hadley-beeman │ └── contents.lr │ ├── hannes-ebner │ └── contents.lr │ ├── jack-pearkes │ └── contents.lr │ ├── james-billingham │ └── contents.lr │ ├── james-cox │ └── contents.lr │ ├── james-darling │ └── contents.lr │ ├── james-parton │ └── contents.lr │ ├── james-smith │ └── contents.lr │ ├── jannette-mensch │ └── contents.lr │ ├── jason-grant │ └── contents.lr │ ├── jeremy-keith │ └── contents.lr │ ├── joe-nash │ └── contents.lr │ ├── joel-franusic │ └── contents.lr │ ├── johan-uhle │ └── contents.lr │ ├── john-bunting │ └── contents.lr │ ├── john-stevenson │ └── contents.lr │ ├── jonathan-gottfried │ └── contents.lr │ ├── jonathan-markwell │ └── contents.lr │ ├── jorge-zapico │ └── contents.lr │ ├── ketan-majmudar │ └── contents.lr │ ├── kevin-prince │ └── contents.lr │ ├── klaus-bravenboer │ └── contents.lr │ ├── manoj-nathwani │ └── contents.lr │ ├── margaret-gold │ └── contents.lr │ ├── martyn-davies │ └── contents.lr │ ├── matt-clements │ └── contents.lr │ ├── matt-stine │ └── contents.lr │ ├── matthew-cashmore │ └── contents.lr │ ├── matthew-forr │ └── contents.lr │ ├── mattias-arrelid │ └── contents.lr │ ├── melinda-seckington │ └── contents.lr │ ├── michael-wawra │ └── contents.lr │ ├── michel-jansen │ └── contents.lr │ ├── mijndert-stuij │ └── contents.lr │ ├── mike-elsmore │ └── contents.lr │ ├── olof-mathe │ └── contents.lr │ ├── otacilio-maia │ └── contents.lr │ ├── paolo-sinelli │ └── contents.lr │ ├── patricio-molina │ └── contents.lr │ ├── paul-lamere │ └── contents.lr │ ├── paul-osman │ └── contents.lr │ ├── richard-kastelein │ └── contents.lr │ ├── rob-finean │ └── contents.lr │ ├── robert-lee-cann │ └── contents.lr │ ├── sam-cook │ └── contents.lr │ ├── sam-machin │ └── contents.lr │ ├── sam-smith │ └── contents.lr │ ├── scott-motte │ └── contents.lr │ ├── seyi-ogunyemi │ └── contents.lr │ ├── shakti-goap │ └── contents.lr │ ├── sheila-thomson │ └── contents.lr │ ├── shyamal-ruparel │ └── contents.lr │ ├── stefano-paluello │ └── contents.lr │ ├── stephen-mount │ └── contents.lr │ ├── swift │ └── contents.lr │ ├── syd-lawrence │ └── contents.lr │ ├── tim-fogarty │ └── contents.lr │ ├── tim-messerschmidt │ └── contents.lr │ ├── tom-morris │ └── contents.lr │ ├── tom-scott │ └── contents.lr │ └── tracy-abrahms │ └── contents.lr ├── docker-compose.yml ├── models ├── document.ini ├── supporter.ini └── supporters.ini ├── requirements.txt ├── templates ├── document.html └── layout.html └── website.lektorproject /.devcontainer/Dockerfile: -------------------------------------------------------------------------------- 1 | # See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.241.1/containers/python-3/.devcontainer/base.Dockerfile 2 | 3 | # [Choice] Python version (use -bullseye variants on local arm64/Apple Silicon): 3, 3.10, 3.9, 3.8, 3.7, 3.6, 3-bullseye, 3.10-bullseye, 3.9-bullseye, 3.8-bullseye, 3.7-bullseye, 3.6-bullseye, 3-buster, 3.10-buster, 3.9-buster, 3.8-buster, 3.7-buster, 3.6-buster 4 | ARG VARIANT="3.10-bullseye" 5 | FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT} 6 | 7 | # [Choice] Node.js version: none, lts/*, 16, 14, 12, 10 8 | ARG NODE_VERSION="none" 9 | RUN if [ "${NODE_VERSION}" != "none" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi 10 | 11 | # [Optional] If your pip requirements rarely change, uncomment this section to add them to the image. 12 | # COPY requirements.txt /tmp/pip-tmp/ 13 | # RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \ 14 | # && rm -rf /tmp/pip-tmp 15 | 16 | # [Optional] Uncomment this section to install additional OS packages. 17 | # RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ 18 | # && apt-get -y install --no-install-recommends 19 | 20 | # [Optional] Uncomment this line to install global node packages. 21 | # RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g " 2>&1 -------------------------------------------------------------------------------- /.devcontainer/devcontainer.json: -------------------------------------------------------------------------------- 1 | // For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: 2 | // https://github.com/microsoft/vscode-dev-containers/tree/v0.241.1/containers/python-3 3 | { 4 | "name": "hackdaymanifesto", 5 | "build": { 6 | "dockerfile": "Dockerfile", 7 | "context": "..", 8 | "args": { 9 | // Update 'VARIANT' to pick a Python version: 3, 3.10, 3.9, 3.8, 3.7, 3.6 10 | // Append -bullseye or -buster to pin to an OS version. 11 | // Use -bullseye variants on local on arm64/Apple Silicon. 12 | "VARIANT": "3.10-bullseye", 13 | // Options 14 | "NODE_VERSION": "none" 15 | } 16 | }, 17 | // Configure tool-specific properties. 18 | "customizations": { 19 | // Configure properties specific to VS Code. 20 | "vscode": { 21 | // Set *default* container specific settings.json values on container create. 22 | "settings": { 23 | "python.defaultInterpreterPath": "/usr/local/bin/python", 24 | "python.linting.enabled": true, 25 | "python.linting.pylintEnabled": true, 26 | "python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8", 27 | "python.formatting.blackPath": "/usr/local/py-utils/bin/black", 28 | "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf", 29 | "python.linting.banditPath": "/usr/local/py-utils/bin/bandit", 30 | "python.linting.flake8Path": "/usr/local/py-utils/bin/flake8", 31 | "python.linting.mypyPath": "/usr/local/py-utils/bin/mypy", 32 | "python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle", 33 | "python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle", 34 | "python.linting.pylintPath": "/usr/local/py-utils/bin/pylint" 35 | }, 36 | // Add the IDs of extensions you want installed when the container is created. 37 | "extensions": [ 38 | "ms-python.python", 39 | "ms-python.vscode-pylance" 40 | ] 41 | } 42 | }, 43 | // Use 'forwardPorts' to make a list of ports inside the container available locally. 44 | // "forwardPorts": [], 45 | // Use 'postCreateCommand' to run commands after the container is created. 46 | // "postCreateCommand": "pip3 install --user -r requirements.txt", 47 | // Comment out to connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root. 48 | "remoteUser": "vscode", 49 | "features": { 50 | "git": "latest", 51 | "github-cli": "latest", 52 | "fish": "latest" 53 | } 54 | } -------------------------------------------------------------------------------- /.github/workflows/publish.yml: -------------------------------------------------------------------------------- 1 | name: publish 2 | 3 | on: 4 | push: 5 | branches: 6 | - "main" 7 | workflow_dispatch: 8 | 9 | permissions: 10 | contents: read 11 | pages: write 12 | id-token: write 13 | 14 | concurrency: 15 | group: "publish" 16 | cancel-in-progress: true 17 | 18 | defaults: 19 | run: 20 | shell: bash 21 | 22 | jobs: 23 | build: 24 | runs-on: ubuntu-20.04 25 | 26 | steps: 27 | - name: fetch code 28 | uses: actions/checkout@v2 29 | 30 | - name: setup pages 31 | id: pages 32 | uses: actions/configure-pages@v1 33 | 34 | - name: set python version 35 | uses: actions/setup-python@v4 36 | with: 37 | python-version: "3.10" 38 | 39 | - name: install node dependencies 40 | run: pip install -r requirements.txt 41 | 42 | - name: build 43 | run: lektor build --output-path ./build 44 | 45 | - name: upload artifact 46 | uses: actions/upload-pages-artifact@v1 47 | with: 48 | path: ./build 49 | 50 | deploy: 51 | environment: 52 | name: github-pages 53 | url: ${{ steps.deployment.outputs.page_url }} 54 | runs-on: ubuntu-latest 55 | needs: build 56 | steps: 57 | - name: deploy to pages 58 | id: deployment 59 | uses: actions/deploy-pages@v1 -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # General 2 | .DS_Store 3 | .AppleDouble 4 | .LSOverride 5 | 6 | # Icon must end with two \r 7 | Icon 8 | 9 | 10 | # Thumbnails 11 | ._* 12 | 13 | # Files that might appear in the root of a volume 14 | .DocumentRevisions-V100 15 | .fseventsd 16 | .Spotlight-V100 17 | .TemporaryItems 18 | .Trashes 19 | .VolumeIcon.icns 20 | .com.apple.timemachine.donotpresent 21 | 22 | # Directories potentially created on remote AFP share 23 | .AppleDB 24 | .AppleDesktop 25 | Network Trash Folder 26 | Temporary Items 27 | .apdisk 28 | 29 | # Byte-compiled / optimized / DLL files 30 | __pycache__/ 31 | *.py[cod] 32 | *$py.class 33 | 34 | # C extensions 35 | *.so 36 | 37 | # Distribution / packaging 38 | .Python 39 | build/ 40 | develop-eggs/ 41 | dist/ 42 | downloads/ 43 | eggs/ 44 | .eggs/ 45 | lib/ 46 | lib64/ 47 | parts/ 48 | sdist/ 49 | var/ 50 | wheels/ 51 | *.egg-info/ 52 | .installed.cfg 53 | *.egg 54 | MANIFEST 55 | 56 | # PyInstaller 57 | # Usually these files are written by a python script from a template 58 | # before PyInstaller builds the exe, so as to inject date/other infos into it. 59 | *.manifest 60 | *.spec 61 | 62 | # Installer logs 63 | pip-log.txt 64 | pip-delete-this-directory.txt 65 | 66 | # Unit test / coverage reports 67 | htmlcov/ 68 | .tox/ 69 | .coverage 70 | .coverage.* 71 | .cache 72 | nosetests.xml 73 | coverage.xml 74 | *.cover 75 | .hypothesis/ 76 | 77 | # Translations 78 | *.mo 79 | *.pot 80 | 81 | # Django stuff: 82 | *.log 83 | .static_storage/ 84 | .media/ 85 | local_settings.py 86 | 87 | # Flask stuff: 88 | instance/ 89 | .webassets-cache 90 | 91 | # Scrapy stuff: 92 | .scrapy 93 | 94 | # Sphinx documentation 95 | docs/_build/ 96 | 97 | # PyBuilder 98 | target/ 99 | 100 | # Jupyter Notebook 101 | .ipynb_checkpoints 102 | 103 | # pyenv 104 | .python-version 105 | 106 | # celery beat schedule file 107 | celerybeat-schedule 108 | 109 | # SageMath parsed files 110 | *.sage.py 111 | 112 | # Environments 113 | .env 114 | .venv 115 | env/ 116 | venv/ 117 | ENV/ 118 | env.bak/ 119 | venv.bak/ 120 | 121 | # Spyder project settings 122 | .spyderproject 123 | .spyproject 124 | 125 | # Rope project settings 126 | .ropeproject 127 | 128 | # mkdocs documentation 129 | /site 130 | 131 | # mypy 132 | .mypy_cache/ -------------------------------------------------------------------------------- /Dockerfile: -------------------------------------------------------------------------------- 1 | FROM python:3.4-alpine 2 | 3 | RUN apk add --no-cache \ 4 | git \ 5 | libffi-dev \ 6 | openssl-dev \ 7 | make \ 8 | g++ \ 9 | libffi \ 10 | nodejs 11 | 12 | COPY ./requirements.txt /app/requirements.txt 13 | 14 | RUN pip install --no-cache-dir --upgrade \ 15 | pip \ 16 | && pip install \ 17 | -r /app/requirements.txt 18 | 19 | COPY . /app 20 | 21 | WORKDIR /app 22 | 23 | EXPOSE 5000 24 | 25 | CMD ["lektor", "server", "--host", "0.0.0.0"] -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # The Hackday Manifesto 2 | 3 | ## Adding yourself as a supporter 4 | 5 | Fork this repository and create a `content/supporters/{your-name}/contents.lr` 6 | file, this file should resemble the following: 7 | 8 | ``` 9 | date: 2017-12-27 10 | --- 11 | name: John Doe 12 | --- 13 | organisation: Fake Inc. 14 | --- 15 | link: https://example.com/ 16 | ``` 17 | 18 |
19 |
date
20 |
The current date
21 |
name
22 |
Your full name as you expect it to show in the supporters section
23 |
organisation
24 |
If provided it will be shown alongside your name in the supporters section
25 |
link
26 |
If provided it will turn your name into a link in the supporters section
27 |
28 | 29 | Commit your changes, push them to GitHub, create a pull request and one of our 30 | helpful contributors will have it merged in. 31 | 32 | ## Editing 33 | 34 | The manifesto content can be found in `content/contents.lr` and the body section 35 | is a Markdown document. 36 | 37 | You can either edit the file in a text editor or launch the lektor admin and 38 | edit it from there. 39 | 40 | ## Running locally 41 | 42 | The Hackday Manifesto uses [Lektor](https://www.getlektor.com) to render the 43 | web content, and docker-compose to run locally. 44 | 45 | To get the development server running in order to see live previews of your 46 | changes or to use the lektor admin run the following command: 47 | 48 | ```sh 49 | docker-compose up 50 | ``` 51 | 52 | The site will now be accessible at http://localhost:5000/ 53 | 54 | -------------------------------------------------------------------------------- /content/contents.lr: -------------------------------------------------------------------------------- 1 | _model: document 2 | --- 3 | title: Welcome to Hackday Manifesto! 4 | --- 5 | body: 6 | 7 | So you're organising a hack day or hackathon? Here are some basic requirements 8 | to make your event a success, and avoid the common pitfalls that could otherwise 9 | ruin it. If you cannot provide any of the following, make it clear to guests 10 | before registration. Attendees are generally forgiving when clear communication 11 | is given. These are only guidelines, but exist to help you run a hack day in the 12 | easiest possible way. 13 | 14 | # Announcing the event 15 | 16 | Once you know when and how your event will take place, you'll want to tell the 17 | world about it. At a bare minimum, you should decide on a canonical place where 18 | all public information about the event lives - this might be a dedicated web 19 | site, an event on an existing event online service or some other place which is 20 | publicly accessible. 21 | 22 | Once you've decided where that location is, use tools like Twitter and Facebook 23 | to make people aware of the event, and also consider which Google Groups and 24 | mailing lists developers relevant to your event may be hanging out. Don't spam 25 | them, though - nobody enjoys that. 26 | 27 | ## Registration Optional 28 | 29 | If you require your attendees to register, make it clear what information is 30 | required for signing up and what the deadline for the registration is. If 31 | there's a maximum number of attendees the venue can handle, communicate how the 32 | selection process works and when/how people will be notified if they've been 33 | granted attendance or not. 34 | 35 | If there's a waiting list for the event, make sure to explain how it works. 36 | 37 | Most registration forms lets applicants enter name, contact details and food 38 | preferences/allergies (if applicable). Depending on your event and your venue, 39 | you might want to ask for additional information - this manifesto lists a few 40 | other topics which might make sense to add to the registration form. 41 | 42 | There are also a number of things you probably should _not_ ask for, like 43 | gender, religious preferences etc. 44 | 45 | # Venue 46 | 47 | ## Location 48 | 49 | The venue should be relatively easy for people from outside of town to locate, 50 | with good public transport links. If it's difficult to reach, try to provide 51 | alternative means of transportation, such as coaches to/from local transport 52 | hubs throughout the event. Provide a full address, and if necessary, 53 | additional instructions to all attendees well in advance of the event. 54 | 55 | Include instructions/contacts/getting in arrangements, too (i.e., what 56 | to do at reception/security desks). 57 | 58 | Print big signs that will guide your attendees to the venue (and in some case 59 | inside the venue). 60 | 61 | ## Accessibility 62 | 63 | Hack day venues should be accessible to everyone: at a bare minimum, there 64 | should be step-free access to all common parts of the building. If an attendee 65 | is blind or deaf, they should be able to participate too. Make sure your event 66 | signup forms mention accessibility and ask what accommodations might be needed. 67 | 68 | ## Insurance 69 | 70 | Does your venue have the relevant insurance? Are guests' belongings protected in 71 | case of fire or theft? If not, you should make them aware of the risks so they 72 | can take extra precautions. 73 | 74 | Do you, as an organizer have adequate insurance? 75 | 76 | ## Security 77 | 78 | Attendees will often be bringing a lot of expensive kit: laptops, tablets, etc. 79 | Make sure they have some security. If the venue does not have some form of 80 | lockers, can you run a cloakroom system? 81 | 82 | ## Secure sites and photo ID 83 | 84 | Are the rooms going to be available to non-attendees? Work out whether you are 85 | running a secure site and whether people need to bring photo ID; if so, tell 86 | them when they sign up and remind them close to the event date. For some people, 87 | showing photo ID may be a deal breaker. Not everyone will have 88 | 'government issued ID', either. Providing proof of address may be hard for some. 89 | 90 | # Dates 91 | 92 | ## Weekend or Not? 93 | 94 | Most hack days are held at the weekend as this allows people to attend without 95 | taking time off work. If you are planning a hack day that begins on a Friday, 96 | remember that this may limit the number of people willing to travel after work. 97 | 98 | ## Checking for clashes 99 | 100 | One of the most frustrating things for attendees to see is two similar events 101 | on the same day in the same area. To avoid this, check places like 102 | [Lanyrd](http://www.lanyrd.com), [Eventbrite](http://eventbrite.com), [Meetup](http://www.meetup.com), 103 | and ask on Twitter "is anything going on in X on X?". Remember that people may be 104 | travelling long distances for hack days, so even if an event is a few hundred 105 | miles away, you are still diluting your potential audience. 106 | 107 | # Overnight Events 108 | 109 | ## Sleeping provision 110 | 111 | If attendees are staying overnight, then a separate (dark, quiet) area should be 112 | available away from the hacking should people decide to sleep. If possible, this 113 | should be several areas potentially including dedicated areas, for example 114 | male/female/mixed, minors (+chaperones?), snorer/non-snorer, night-owls/early birds. 115 | 116 | ## Showers Optional 117 | 118 | Despite the stereotypes, most geeks like to keep clean. Only a few venues are 119 | able to provide showers - but if you can, you should. Make sure you tell 120 | attendees well in advance so they can bring towels and toiletries. 121 | 122 | # Network 123 | 124 | ## Your 4MB DSL isn't enough 125 | 126 | Hack days have special requirements: don't just trust anyone who tells you that 127 | "it'll be fine". Think about the networking issues, and verify that they work 128 | for the kind of capacity you are going to have. People from the venue or their 129 | commercial partner will tell you all sorts of things you want to hear but keep 130 | in the back of your mind that they may not have any clue what they are talking 131 | about. Given the importance of network access, if you are operating a commercial 132 | event consider requiring network performance as part of your contract with 133 | venues and suppliers. 134 | 135 | ## Rock solid WiFi 136 | 137 | Many commercial WiFi providers plan for much lower use than actually occurs at 138 | hack days. The network should be capable of handling at least 4 devices per 139 | attendee. 140 | 141 | ## Minimal firewalling 142 | 143 | As a minimum: ports used for SSH (22), DNS (53 — TCP & UDP), 144 | VPN (47, 500, 1701, 1723, 5500), HTTP (80), NTP (123 — UDP), 145 | HTTPS (443), Submissions (587), IMAPS (993), 146 | MQTT (1883), CVS (2401), Subversion (3690), XMPP/Jabber (5222), IRC (6665-9), 147 | and Git (9418), must be open and accessible, without the need of 148 | proxy servers, and preferably without perimeter-level malware checks. 149 | 150 | ## Subnet / DHCP capacity 151 | 152 | Subnet and DHCP server must have capacity for allocating 6 IPv4 (and 153 | optionally, IPv6) addresses (preferably a /29) per hacker. 154 | 155 | If NAT is not used, attendees should be informed in advance. 156 | 157 | ## WiFi security 158 | 159 | Use WPA2 security over an open WiFi network, to offer some basic protection 160 | against the monitoring of other users' network traffic. 161 | 162 | ## No device isolation 163 | 164 | Attendees should be reminded that when connected to the network, their devices 165 | may be accessible to all other devices on the network so they would be wise to 166 | secure them. 167 | 168 | Organisers should make it clear that they absolve themselves of 169 | liability for any intrusion or damage caused over the network. Attendees will 170 | want to share resources with other attendees (version control, for example) but 171 | while it would be wise for them to do so in a controlled manner it is ultimately 172 | up to each individual to be responsible for the security of their own devices, 173 | connected or otherwise. 174 | 175 | Attendees should be encouraged/advised to run their own firewalls, 176 | too, remembering that IPv6 exists. 177 | 178 | ## IP Whitelisting 179 | 180 | For events with 150 attendees or more, you will need to contact organisations 181 | such as Twitter, Google, and Freenode in advance to inform them of the increased 182 | number of connections from your IP range; they may have an existing process that 183 | you should use. 184 | 185 | In many cases, rate-limiting is handled by authentication, not IP 186 | address (ranges). 187 | 188 | For Freenode, email [iline@freenode.net](mailto:iline@freenode.net) with dates, 189 | expected number of attendees and IP addresses if possible. 190 | 191 | ## QoS and Monitoring 192 | 193 | Traffic shaping and monitoring should be employed to help prevent a few users 194 | abusing the connection to the detriment of all others. 195 | 196 | Deep packet inspection should not be used. 197 | 198 | ## Ethernet to the Chair Optional 199 | 200 | In case of WiFi collapse (or if you can't provide adequate WiFi at all) you 201 | should have ethernet available at the chairs. Have at least 100 megabit ethernet 202 | feeding into a gigabit backbone arranged in an (extended) star topology. 203 | If you go ethernet-only, announce this up-front. Regardless if you provide 204 | cables or attendees bring their own, you should have a big pile of spare 205 | cables at the venue. 206 | 207 | ## Single subnet Optional 208 | 209 | Both WiFi and ethernet should share a single subnet, allowing devices to 210 | communicate regardless of how they are connected to the network. 211 | 212 | # Power 213 | 214 | ## Power sockets 215 | 216 | You will need a minimum of 1.5 power sockets available for every seat. That's a 217 | minimum; many attendees will bring two, three, or more devices that require 218 | separate power. Have spare cables available. Make sure you have access to the 219 | fuses of all used power circuits, and review power requirements with the venue. 220 | 221 | ## Portable Appliance Testing 222 | 223 | As stated above, your attendees will be bringing two, three, or more devices 224 | making full PATs for every device an impossible endeavour. But if you are 225 | providing a lot of power strips it can be worth getting them tested. 226 | 227 | ## Isolated power for hardware hacks Optional 228 | 229 | Isolating the power for those doing hardware hacks is generally a good idea, 230 | don't let one soldering iron knock out the power for the entire venue. 231 | 232 | # Sustenance 233 | 234 | ## Dietary requirements 235 | 236 | Not everyone in the technical community is hyper-carnivorous. Be sure to 237 | check with your attendees for dietary requirements: food allergies, 238 | vegetarians, vegans and people with dietary restrictions. Make provisions 239 | to ensure they are provided for equally. If you’re on a budget, prioritise 240 | allergies and vegan alternatives; the vegan alternative will satisfy most 241 | non-allergy based requirements. Common food allergies include milk, eggs, 242 | nuts, fish, shellfish, soya, and wheat (gluten). 243 | 244 | It's important to note that that vegan meals exclude all animal products, 245 | not just meat, and therefore it should exclude eggs, cheese, milk, yoghurt, honey 246 | and much more. 247 | 248 | ## Breakfast 249 | 250 | If your event starts before 11am you should provide breakfast to attendees, 251 | either continental or cooked. 252 | 253 | ## Lunch 254 | 255 | You should provide a lunch for each day of the event, this should consist at 256 | least of sandwiches (or suitable alternatives for gluten intolerant folk). 257 | 258 | ## Dinner 259 | 260 | If your event runs later than 6pm or overnight you should provide attendees with 261 | a proper evening meal, not sandwiches or snacks (and not everybody likes/eats pizza). 262 | 263 | ## Overnight 264 | 265 | If your event runs through the night, you should arrange for food to be 266 | available throughout the night, either by periodically refreshing it or 267 | supplying something that can still be eaten after it has gone cold. 268 | 269 | ## Drinks 270 | 271 | A selection of coffee, green and black tea (plus milks, sugars), energy drinks, 272 | caffeinated and non-caffeinated soft drinks, juices and _water_ should be freely available to 273 | attendees throughout the event. 274 | 275 | ## Snacks 276 | 277 | Chocolate, sweets, biscuits, fruit, crisps, etc. should be freely available to 278 | attendees throughout the event. Try to ensure there are healthy options too. 279 | Fresh fruit, nuts and vegetable platters can provide sustainable high energy levels to 280 | developers through out an event. 281 | 282 | ## Alcohol 283 | 284 | Should be served as if you are the owner of your local bar because, in fact, 285 | you are. Check licensing rules with the venue, including where and when alcohol 286 | can be served and consumed and what time you need to stop serving. If you have underage attendees, 287 | make sure they're not served alcohol. Penalties for failing to do this could range 288 | from a fine to imprisonment for the person providing alcohol and loss of licence for the venue. 289 | 290 | # APIs / Datasets 291 | 292 | ## Presentations 293 | 294 | Presentations by API and dataset providers should be kept to a minimum, try to 295 | make it a quick introduction involving the company name, the type of data / 296 | platform they have, and who to speak to for more information. Have technical - 297 | not marketing - people give the presentation as they will be asked technical 298 | questions, both on stage and during the rest of the event. 299 | 300 | ## Working APIs 301 | 302 | The APIs pitched to attendees should be checked in advance by someone technical 303 | to confirm that they are suitable, work, and are of a high enough quality. 304 | 305 | ## Multiple clients 306 | 307 | All APIs should provide client libraries in at least three major 308 | languages unless there is good reason for them not to (such as the target 309 | platform only supporting a single language). 310 | 311 | (And if you haven't got the client libraries written, maybe you need an 312 | internal hack day to write them!) 313 | 314 | ## Clean datasets 315 | 316 | Datasets provided for use in the hack day should, where possible, be 317 | checked in advance by someone technical to ensure they are well 318 | structured and in a sensible format (CSV, XML, JSON, RDF etc., rather 319 | than Excel spreadsheets and PDFs). 320 | 321 | ## Thorough documentation 322 | 323 | All APIs and datasets should have thorough documentation, detailing format, any 324 | codes or abbreviations, as well as the underlying assumptions and business logic 325 | of what it represents. The documentation should be checked by someone technical 326 | before announcing the API. 327 | 328 | ## Local downloads 329 | 330 | Datasets -- especially large datasets -- should be available over the network 331 | from local servers without the need for registration, and where possible 332 | available on USB keys for even faster transfer. 333 | 334 | ## Make data explorable 335 | 336 | Try and ensure that large datasets are accompanied by smaller sample files so 337 | attendees can check them for suitability and write parsers using a small number 338 | of records before downloading and importing multi-gigabyte files. 339 | 340 | ## API Keys 341 | 342 | If an API requires a key to use it, then make sure that someone is on site and 343 | able to authorize the requests quickly, and with as little fuss as possible. 344 | 345 | ## Licensing 346 | 347 | Get clear licensing information from API and dataset providers ahead of time, 348 | and communicate those licences clearly to the attendees, remembering that those 349 | in the technical community often have strong opinions about open licences for 350 | data and code. 351 | 352 | ## Longevity 353 | 354 | Attendees are often averse to building on top of platforms and datasets that 355 | could disappear or will incur usage fees after an event, try to avoid companies 356 | making resources available only for the duration of the event and communicate 357 | clearly the risk of building on top of any alpha or beta APIs. 358 | 359 | # Demos 360 | 361 | ## Hack submissions 362 | 363 | If possible, have a shared, public listing of the hacks that have been 364 | submitted. This helps the judges, the attendees and bloggers/journalists who are 365 | covering the event. Hack submissions should be as straight forward as possible. 366 | You can use Google Docs, Etherpad or a wiki. Make sure that all attendees have 367 | write access and can concurrently edit. Plan for the hack listing to stay around 368 | as a historical record. Alternatively, there are hack submission services that 369 | will handle the logistics for you like [Hackathon.io](http://hackathon.io), 370 | [WeHack.it](http://wehack.it/), or [Devpost](https://devpost.com/). 371 | 372 | Anyone who hacks should be a allowed to demo at the end of the event, regardless 373 | of the quality or completeness. 374 | 375 | ## Time limit 376 | 377 | Each demo should be given a fixed time limit, standard times are 60, 90, 180, 378 | and 300 seconds. Tell presenters ahead of time, let them know how much time 379 | remains (either half time cards or an on-screen count down), and don't let them 380 | run over. 381 | 382 | ## Clear expectations 383 | 384 | Try and communicate clear expectations for the demos to all attendees from the 385 | beginning of the event. Some attendees will become frustrated when they see 386 | others demo-ing paper prototypes or Photoshop mockups when they believed a 387 | working implementation was required. If hacks do not meet these base 388 | requirements, they should not be able to win a prize. 389 | 390 | ## Audience vote 391 | 392 | If you have an "audience choice" prize, someone will attempt to game the system, 393 | either technically or by running an obnoxious "vote for me" campaign. Keep the 394 | prize for it relatively small, and give attendees a one-time token (a code on 395 | the reverse of their pass for large events, or a physical item for smaller ones) 396 | in order to vote. 397 | 398 | ## Judge selection 399 | 400 | The judges for your hack day should reflect the nature of your event. 401 | For standard hack days, judges should be primarily technical or knowledgable in the relevant thematic area (eg. musicians judging Music Hack Day). 402 | Try to avoid having businesspeople (VCs, non-technical founders, journalists, etc.) judge technical events, as it encourages hackers to build prototype businesses, not interesting hacks. 403 | Your judging panel should be chosen to allow participants to win a hack day based purely on technical merit, even if the hack is completely impractical as a business. 404 | 405 | ## Judge previews Optional 406 | 407 | If possible, let the judges meet all the teams for a few minutes, a couple of 408 | hours before the presentations. This means people don't need to cram their whole 409 | idea in 60 seconds, but instead can demo the product to their peers knowing the 410 | judges understand how technically awesome their product is. This also allows for 411 | judges to fully inspect if a product was actually implemented, or is just a 412 | bunch of screenshots - and how technically advanced their project is. 413 | 414 | # Audio / Video 415 | 416 | ## Support 417 | 418 | There should be staff on hand to help users set-up quickly for their demos, such 419 | as connecting to the projector. If the equipment at the venue allows it, have 420 | one demo presenting while the next is setting up. 421 | 422 | ## Video connectors 423 | 424 | For the demos, either have a set of adapters handy for (Apple Mac) Thunderbolt, Mini DisplayPort, VGA, 425 | DVI, and HDMI video outputs, or make sure attendees know the projector's inputs 426 | ahead of time so they can make sure they have the relevant adapters. 427 | 428 | ## Projector info 429 | 430 | Information on projector resolution, contrast, etc should be provided to 431 | attendees and speakers ahead of the event. 432 | 433 | ## Hardware and mobile hacks 434 | 435 | If mobile or hardware hacks are expected, equipment to demonstrate them on the 436 | device should be present. Have a camera feed or visualiser available on the big 437 | screen. State ahead of time if that'll be provided, to allow these to be demoed 438 | adequately. 439 | 440 | # Prizes 441 | 442 | ## Not every hack day needs prizes 443 | 444 | Some people go to hack days to learn, or to play. Having one team go home with 445 | enormous prizes and many other teams go home with nothing may sour the end of 446 | the event. Make sure it's not all about the money/toys. 447 | 448 | ## Prizes per team member 449 | 450 | Prizes must be divisible to encourage teamwork: it is very hard to slice an iPod 451 | into three bits. If you wish to give away physical goods there should be enough 452 | that they may be given to each member of a reasonably sized team. 453 | 454 | ## Available on the day 455 | 456 | Prizes should be on site on the day of judging and ready to be handed to 457 | attendees as the winners of the various prize categories are announced. 458 | Attendees should not need to claim a physical prize after the event unless said 459 | prize is dependent on winner. If the prize is not available on the day, clear 460 | printed instructions on how to claim must be provided instead. 461 | 462 | ## No cost to claim 463 | 464 | Attendees should not be required to pay a subscription or sign a contract in 465 | order to claim or make use of their prize. Requiring prizewinners to do so is 466 | likely to induce negative feelings in the winner towards the company providing 467 | the prize and the hack day organisers. 468 | 469 | ## Avoid service prizes 470 | 471 | Discounts and credit for an API, face time with a company's CEO, or development 472 | resources to continue a hack make for poor prizes (with obvious exceptions such 473 | as of companies offering music/video streaming services or online stores) and 474 | are likely to just disappoint the winning team. When organizations/individuals 475 | wish to pursue further development of a hack they should speak to the winning 476 | team separately. 477 | 478 | # Atmosphere and attitudes 479 | 480 | ## Don't make people feel unwelcome 481 | 482 | Avoid sexism and other discriminatory language or attitudes. Don't make any 483 | assumptions about your attendees. Get someone who is demographically very 484 | different from you to check your marketing material through to see if it makes 485 | sense and isn't offensive to someone who doesn't share your background. 486 | 487 | Many event attendees expect events to have and enforce a code of conduct. Having 488 | such a code encourages diversity of participation and can help to create and maintain a 489 | welcoming environment. It is highly recommended to adopt a code of conduct for 490 | your event. One such example is the [Hack Code of Conduct](http://hackcodeofconduct.org), 491 | and there are several other appropriate examples. You can either reference your chosen 492 | code of conduct directly or create your own customized version. 493 | Make sure to communicate clearly to attendees ahead of time the existence of this 494 | code and the enforcement policy behind it. 495 | In addition, the code should be linked prominently from the event web site and 496 | promoted by the event organizers and by members of the event's community. The code 497 | should be known to and practiced by event staff and volunteers and enforcement 498 | procedures should be clear. 499 | 500 | ## Make assumptions around privacy clear 501 | 502 | Tell people up front what level of privacy they should expect during the event. 503 | 504 | If you allow people to take photographs, tell photographers to respect people's 505 | privacy if they do not wish to be photographed: if someone objects to being 506 | photographed, they have a right to have that objection taken seriously. 507 | 508 | Sleeping areas should be explicitly marked as no photography as sleeping people 509 | are unable to implicitly consent to being photographed by not objecting. 510 | 511 | ## Do not charge attendees 512 | 513 | If developers are willing to donate their time -- which could otherwise be used 514 | for paid work or hanging out with family and friends -- they should not be 515 | charged for tickets. It shows a complete disrespect for the value of their 516 | time, and is likely to leave a bad feeling towards the organisers and 517 | sponsors. The developers are providing the sponsors a service in testing and 518 | showing the possibility of their APIs, data, products and services. 519 | 520 | ## Intellectual property 521 | 522 | The intellectual property rights of hacks produced at the event should belong to 523 | the attendees, and not to the organisers, sponsors, or partners, with the 524 | obvious exception of (a) hack days based around the further development of an open 525 | source project, or (b) commercially run hacks. 526 | 527 | Intellectual property can be a big issue; it is best to make expectations clear 528 | in advance, both to developers and to sponsors or data providers. 529 | 530 | ## What are you after? 531 | 532 | Have some idea what counts as success, but don't be too tight: people will 533 | surprise you! Some hack days are specifically focused on one language or tool, 534 | others on a theme, while others are meant for a particular open source project 535 | or problem that needs solving. The point of the event will inform how you do 536 | marketing, judging and many other aspects of the event. 537 | 538 | ## This is not a rock concert! 539 | 540 | Some hack days have hired bands or other entertainment. This is usually a bad 541 | idea. People are at the event to hack, and hacking requires extended periods of 542 | concentration. You don't need silence, but if you are thinking about putting on 543 | entertainment you may not understand exactly what the point of a hack day is. If 544 | you do insist on putting noisy entertainment on, don't be surprised if the 545 | people actually trying to build things go and hide in the lobby to carry on with 546 | what they are doing. 547 | 548 | ## Emergency plans 549 | 550 | Make sure you have a plan for attendees who are injured, fall ill or 551 | suffer any other emergencies. Have at least one designated first aider 552 | on call. Make sure you know where the first aid box is, and check it's 553 | appropriately stocked. Know the procedures for calling an ambulance, 554 | sounding the fire alarm, evacuation point, and logging incidents in 555 | the venue. Make sure attendees know who to turn to for help; a phone 556 | number, a few bright crew shirts and a central crew desk or wardrobe 557 | go a long way. A central point of contact will also help you deal with 558 | inevitable electric, network, venue- or food-related questions. 559 | 560 | ## Handling problematic people 561 | 562 | It's unlikely that you'll have to throw someone out, but just in case know what 563 | the procedures are, what you're legally able to do and what kind of misbehaviour 564 | would actually trigger ejection. Some events have instituted safe space and 565 | anti-harassment policies due to widely reported incidents of sexual harassment. 566 | 567 | ## Keep your crew safe too 568 | 569 | Working at a hack day, as a volunteer or otherwise, can be a stressful and demanding 570 | job. Make sure your crew are safe, happy and well-fed throughout, and that 571 | you've got enough staff to cope with emergencies or unexpected dropouts! 572 | 573 | ## Finally, remember to have fun! 574 | 575 | If you follow all these guidelines, prepare well in advance, and get plenty of 576 | rest before the big day, you'll maximize your odds of having an event that's 577 | not just successful, but enjoyable as well. Good luck! 578 | -------------------------------------------------------------------------------- /content/supporters/aaron-franco/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-08-19 2 | --- 3 | name: Aaron Franco 4 | --- 5 | organisation: CTO at ClickSlide Limited 6 | --- 7 | link: http://blog.clickslide.co 8 | -------------------------------------------------------------------------------- /content/supporters/abe-stanway/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Abe Stanway 4 | --- 5 | organisation: Hacker League 6 | --- 7 | link: http://hackerleague.org 8 | --- 9 | sort_key: 19 10 | -------------------------------------------------------------------------------- /content/supporters/adam-mcgreggor/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Adam McGreggor 4 | --- 5 | organisation: Developer Network Builder 6 | --- 7 | link: http://amyl.org.uk/ 8 | --- 9 | sort_key: 17 10 | -------------------------------------------------------------------------------- /content/supporters/adam-yeats/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-09-09 2 | --- 3 | name: Adam Yeats 4 | --- 5 | organisation: Developer Relations Engineer, Pusher 6 | --- 7 | link: http://twitter.com/adamyeats 8 | -------------------------------------------------------------------------------- /content/supporters/alexandre-passant/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-18 2 | --- 3 | name: Alexandre Passant 4 | --- 5 | organisation: Music and Data Geek 6 | --- 7 | link: http://apassant.net 8 | -------------------------------------------------------------------------------- /content/supporters/alexey-komissarouk/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Alexey Komissarouk 4 | --- 5 | organisation: PennApps 6 | --- 7 | link: http://pennapps.com 8 | --- 9 | sort_key: 23 10 | -------------------------------------------------------------------------------- /content/supporters/alper-cugun/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Alper Cugun 4 | --- 5 | organisation: Hack de Overheid 6 | --- 7 | link: http://hackdeoverheid.nl 8 | --- 9 | sort_key: 16 10 | -------------------------------------------------------------------------------- /content/supporters/andrew-mager/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Andrew Mager 4 | --- 5 | organisation: Hacker Advocate, Spotify 6 | --- 7 | link: http://mager.co 8 | --- 9 | sort_key: 24 10 | -------------------------------------------------------------------------------- /content/supporters/andrew-nesbitt/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-11 2 | --- 3 | name: Andrew Nesbitt 4 | --- 5 | organisation: Developer, Forward 6 | --- 7 | link: http://forwardtechnology.co.uk 8 | -------------------------------------------------------------------------------- /content/supporters/andrew-seward/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2015-03-25 2 | --- 3 | name: Andrew Seward 4 | --- 5 | organisation: Hack24 founder & organizer 6 | --- 7 | link: http://www.hack24.co.uk 8 | -------------------------------------------------------------------------------- /content/supporters/andy-piper/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2023-04-27 2 | --- 3 | name: Andy Piper 4 | --- 5 | organisation: 6 | --- 7 | link: https://andypiper.me 8 | --- 9 | sort_key: 9 10 | -------------------------------------------------------------------------------- /content/supporters/angus-fox/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2015-06-10 2 | --- 3 | name: Angus Fox 4 | --- 5 | organisation: CTO to go & Product Manager & Secretary, Social Developers London 6 | --- 7 | link: http://www.multizone.co.uk 8 | -------------------------------------------------------------------------------- /content/supporters/ankur-oberoi/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-02-20 2 | --- 3 | name: Ankur Oberoi 4 | --- 5 | organisation: Developer Evangelist, TokBox 6 | --- 7 | link: http://twitter.com/aoberoi 8 | -------------------------------------------------------------------------------- /content/supporters/ariel-waldman/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2014-04-27 2 | --- 3 | name: Ariel Waldman 4 | --- 5 | organisation: Global Instigator, Science Hack Day 6 | --- 7 | link: http://arielwaldman.com 8 | -------------------------------------------------------------------------------- /content/supporters/carter-rabasa/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-14 2 | --- 3 | name: Carter Rabasa 4 | --- 5 | organisation: Developer Evangelist, Twilio 6 | --- 7 | link: http://carter.rabasa.com 8 | -------------------------------------------------------------------------------- /content/supporters/chad-mccallum/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Chad McCallum 4 | --- 5 | organisation: HackDays Organizer 6 | --- 7 | link: http://hackdays.ca/ 8 | --- 9 | sort_key: 11 10 | -------------------------------------------------------------------------------- /content/supporters/chase-southard/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-13 2 | --- 3 | name: Chase Southard 4 | --- 5 | organisation: OpenLexington 6 | --- 7 | link: http://openlexington.org 8 | -------------------------------------------------------------------------------- /content/supporters/chris-weekly/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-05-11 2 | --- 3 | name: Chris Weekly 4 | --- 5 | link: http://chrisweekly.com/ 6 | -------------------------------------------------------------------------------- /content/supporters/colin-loretz/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Colin Loretz 4 | --- 5 | organisation: Reno Collective/Hack4Reno 6 | --- 7 | link: http://renocollective.com/ 8 | --- 9 | sort_key: 14 10 | -------------------------------------------------------------------------------- /content/supporters/contents.lr: -------------------------------------------------------------------------------- 1 | _model: supporters 2 | --- 3 | _hidden: yes 4 | -------------------------------------------------------------------------------- /content/supporters/cristiano-betta/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-09 2 | --- 3 | name: Cristiano Betta 4 | --- 5 | organisation: Geeks of London & ex-PayPal 6 | --- 7 | link: http://geeksoflondon.com/ 8 | --- 9 | sort_key: 5 10 | -------------------------------------------------------------------------------- /content/supporters/daigo-fujiwara/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-11-20 2 | --- 3 | name: Daigo Fujiwara 4 | --- 5 | organisation: Founder, Boston Baseball Hack Day 6 | --- 7 | link: http://about.me/daigofujiwara 8 | -------------------------------------------------------------------------------- /content/supporters/dan-cunningham/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2014-07-25 2 | --- 3 | name: Dan Cunningham 4 | --- 5 | organisation: Head of Geeklist Corps of Developers + #hack4good global organiser 6 | --- 7 | link: http://hack4good.io 8 | -------------------------------------------------------------------------------- /content/supporters/daniel-appelquist/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-07-24 2 | --- 3 | name: Daniel Appelquist 4 | --- 5 | organisation: Over the Air 6 | --- 7 | link: http://overtheair.org 8 | -------------------------------------------------------------------------------- /content/supporters/daniel-knell/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-09 2 | --- 3 | name: Daniel Knell 4 | --- 5 | organisation: Way Past Eleven 6 | --- 7 | link: http://danielknell.co.uk/ 8 | --- 9 | sort_key: 1 10 | -------------------------------------------------------------------------------- /content/supporters/derk-braakman/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-01-11 2 | --- 3 | name: Derk Braakman 4 | --- 5 | organisation: Product Manager API, Hyves 6 | --- 7 | link: http://developers.hyves.nl 8 | -------------------------------------------------------------------------------- /content/supporters/dom-hodgson/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Dom Hodgson 4 | --- 5 | organisation: Leeds Hack 6 | --- 7 | link: http://thehodge.co.uk 8 | --- 9 | sort_key: 2 10 | -------------------------------------------------------------------------------- /content/supporters/don-morrison/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Don Morrison 4 | --- 5 | organisation: Reno Collective/Hack4Reno 6 | --- 7 | link: http://renocollective.com/ 8 | --- 9 | sort_key: 15 10 | -------------------------------------------------------------------------------- /content/supporters/dyego-cantu/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2024-07-16 2 | --- 3 | name: Dyego Cantu 4 | --- 5 | organisation: PatoLivre Hacker Club 6 | --- 7 | link: https://patolivre.github.io/ 8 | -------------------------------------------------------------------------------- /content/supporters/ezequiel-franca/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2016-10-16 2 | --- 3 | name: Ezequiel França 4 | --- 5 | organisation: Brazilian Hackathon enthusiast, iOS Developer. 6 | --- 7 | link: http://ezefranca.com 8 | -------------------------------------------------------------------------------- /content/supporters/gunasekaran-sengodan/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2017-12-13 2 | --- 3 | name: Gunasekaran Sengodan 4 | --- 5 | organisation: Sitecore & Insite eCommerce Developer, Bangalore, India 6 | --- 7 | link: https://www.facebook.com/gunasekaran.sengodan 8 | -------------------------------------------------------------------------------- /content/supporters/hadley-beeman/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-09 2 | --- 3 | name: Hadley Beeman 4 | --- 5 | link: http://linkedgov.org/ 6 | --- 7 | sort_key: 7 8 | -------------------------------------------------------------------------------- /content/supporters/hannes-ebner/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Hannes Ebner 4 | --- 5 | organisation: Green Hackathon 6 | --- 7 | link: http://greenhackathon.com/ 8 | --- 9 | sort_key: 7 10 | -------------------------------------------------------------------------------- /content/supporters/jack-pearkes/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Jack Pearkes 4 | --- 5 | organisation: Developer Advocate, Kiip 6 | --- 7 | link: http://api.jack.ly 8 | --- 9 | sort_key: 25 10 | -------------------------------------------------------------------------------- /content/supporters/james-billingham/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2014-02-28 2 | --- 3 | name: James Billingham 4 | --- 5 | link: http://twitter.com/BillinghamJ 6 | -------------------------------------------------------------------------------- /content/supporters/james-cox/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-11-14 2 | --- 3 | name: James Cox 4 | --- 5 | organisation: Developer Evangelist, The Hackfest 6 | --- 7 | link: http://twitter.com/JamesAaronCox/ 8 | -------------------------------------------------------------------------------- /content/supporters/james-darling/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: James Darling 4 | --- 5 | organisation: Music Hack Day, Rewired State 6 | --- 7 | link: http://abscond.org/ 8 | --- 9 | sort_key: 5 10 | date: 2012-04-10 11 | --- 12 | name: James Darling 13 | --- 14 | organisation: Co-founder Music Hack Day and Rewired State 15 | --- 16 | link: http://abscond.org/ 17 | -------------------------------------------------------------------------------- /content/supporters/james-parton/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-01-06 2 | --- 3 | name: James Parton 4 | --- 5 | organisation: Twilio 6 | --- 7 | link: http://twilio.com 8 | -------------------------------------------------------------------------------- /content/supporters/james-smith/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-10-08 2 | --- 3 | name: James Smith 4 | --- 5 | organisation: Cleanweb UK 6 | --- 7 | link: http://cleanweb.org.uk 8 | -------------------------------------------------------------------------------- /content/supporters/jannette-mensch/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-14 2 | --- 3 | name: Jannette Mensch 4 | --- 5 | organisation: IxD & Hack Day participant 6 | --- 7 | link: http://design-mensch.de 8 | -------------------------------------------------------------------------------- /content/supporters/jason-grant/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Jason Grant 4 | --- 5 | organisation: Flexewebs 6 | --- 7 | link: http://flexewebs.com 8 | --- 9 | sort_key: 4 10 | -------------------------------------------------------------------------------- /content/supporters/jeremy-keith/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-05-12 2 | --- 3 | name: Jeremy Keith 4 | --- 5 | organisation: Founder, Science Hack Day 6 | --- 7 | link: http://adactio.com/ 8 | -------------------------------------------------------------------------------- /content/supporters/joe-nash/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-09-26 2 | --- 3 | name: Joe Nash 4 | --- 5 | organisation: HackSoc Nottingham founder & organiser 6 | --- 7 | link: http://hacksocnotts.co.uk 8 | -------------------------------------------------------------------------------- /content/supporters/joel-franusic/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-09-27 2 | --- 3 | name: Joel Franusic 4 | --- 5 | organisation: Developer Evangelist, Twilio 6 | --- 7 | link: http://joel.franusic.com 8 | -------------------------------------------------------------------------------- /content/supporters/johan-uhle/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-07-05 2 | --- 3 | name: Johan Uhle 4 | --- 5 | organisation: Freenerd, Music Hack Day organizer 6 | --- 7 | link: http://freenerd.de 8 | -------------------------------------------------------------------------------- /content/supporters/john-bunting/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-08-18 2 | --- 3 | name: John Bunting 4 | --- 5 | organisation: Tumblr API Lead 6 | --- 7 | link: http://blog.johnbunting.me 8 | -------------------------------------------------------------------------------- /content/supporters/john-stevenson/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2017-12-13 2 | --- 3 | name: John Stevenson 4 | --- 5 | organisation: Community Developer 6 | --- 7 | link: http://jr0cket.co.uk 8 | -------------------------------------------------------------------------------- /content/supporters/jonathan-gottfried/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-08-18 2 | --- 3 | name: Jonathan Gottfried 4 | --- 5 | organisation: Developer Evangelist at Twilio, hackathon organizer 6 | --- 7 | link: http://twitter.com/jonmarkgo 8 | -------------------------------------------------------------------------------- /content/supporters/jonathan-markwell/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Jonathan Markwell 4 | --- 5 | organisation: Inuda Community 6 | --- 7 | link: http://inuda.org/ 8 | --- 9 | sort_key: 6 10 | -------------------------------------------------------------------------------- /content/supporters/jorge-zapico/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Jorge Zapico 4 | --- 5 | organisation: Green Hackathon 6 | --- 7 | link: http://greenhackathon.com/ 8 | --- 9 | sort_key: 8 10 | -------------------------------------------------------------------------------- /content/supporters/ketan-majmudar/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-02-15 2 | --- 3 | name: Ketan Majmudar 4 | --- 5 | link: http://stereoartist.com) Developer (Titanium AppCamp & London Titanium organiser 6 | -------------------------------------------------------------------------------- /content/supporters/kevin-prince/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-09 2 | --- 3 | name: Kevin Prince 4 | --- 5 | organisation: Geeks of London 6 | --- 7 | link: http://geeksoflondon.com/ 8 | --- 9 | sort_key: 3 10 | -------------------------------------------------------------------------------- /content/supporters/klaus-bravenboer/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2015-02-02 2 | --- 3 | name: Klaus Bravenboer 4 | --- 5 | organisation: HackHumanity founder + organizer 6 | --- 7 | link: http://www.hackhumanity.org 8 | -------------------------------------------------------------------------------- /content/supporters/manoj-nathwani/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2015-08-20 2 | --- 3 | name: Manoj Nathwani 4 | --- 5 | organisation: Hackathon enthusiast, Banter Ventures 6 | --- 7 | link: http://manoj.ninja 8 | -------------------------------------------------------------------------------- /content/supporters/margaret-gold/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Margaret Gold 4 | --- 5 | organisation: Over the Air 6 | --- 7 | link: http://overtheair.org 8 | --- 9 | sort_key: 22 10 | -------------------------------------------------------------------------------- /content/supporters/martyn-davies/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-08-19 2 | --- 3 | name: Martyn Davies 4 | --- 5 | organisation: Coordinator, Music Hack Day 6 | --- 7 | link: http://martyndavies.me 8 | -------------------------------------------------------------------------------- /content/supporters/matt-clements/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-12 2 | --- 3 | name: Matt Clements 4 | --- 5 | organisation: Developer 6 | --- 7 | link: http://mattclements.co.uk 8 | -------------------------------------------------------------------------------- /content/supporters/matt-stine/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-09-26 2 | --- 3 | name: Matt Stine 4 | --- 5 | organisation: Community Engineer, Cloud Foundry 6 | --- 7 | link: http://www.mattstine.com 8 | -------------------------------------------------------------------------------- /content/supporters/matthew-cashmore/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Matthew Cashmore 4 | --- 5 | organisation: Hack Day Organiser 6 | --- 7 | link: http://thelondonbiker.com 8 | --- 9 | sort_key: 13 10 | -------------------------------------------------------------------------------- /content/supporters/matthew-forr/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-08-20 2 | --- 3 | name: Matthew Forr 4 | --- 5 | organisation: Baltimore Hackathon Organizer 6 | --- 7 | link: http://twitter.com/matthewforr 8 | -------------------------------------------------------------------------------- /content/supporters/mattias-arrelid/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Mattias Arrelid 4 | --- 5 | link: http://arrelid.com/ 6 | -------------------------------------------------------------------------------- /content/supporters/melinda-seckington/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-09 2 | --- 3 | name: Melinda Seckington 4 | --- 5 | organisation: Geeks of London & FutureLearn 6 | --- 7 | link: http://geeksoflondon.com/ 8 | --- 9 | sort_key: 4 10 | -------------------------------------------------------------------------------- /content/supporters/michael-wawra/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-05-06 2 | --- 3 | name: Michael Wawra 4 | --- 5 | organisation: Geek 6 | --- 7 | link: http://wawra.co.uk 8 | -------------------------------------------------------------------------------- /content/supporters/michel-jansen/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Michel Jansen 4 | --- 5 | link: http://micheljansen.org/ 6 | --- 7 | sort_key: 20 8 | -------------------------------------------------------------------------------- /content/supporters/mijndert-stuij/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-11 2 | --- 3 | name: Mijndert Stuij 4 | --- 5 | link: http://mijndertstuij.nl 6 | -------------------------------------------------------------------------------- /content/supporters/mike-elsmore/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-10-18 2 | --- 3 | name: Mike Elsmore 4 | --- 5 | organisation: Hackference founder & organiser 6 | --- 7 | link: http://elsmore.me 8 | -------------------------------------------------------------------------------- /content/supporters/olof-mathe/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-11-23 2 | --- 3 | name: Olof Mathé 4 | --- 5 | organisation: Art Hack Day organizer 6 | --- 7 | link: http://twitter.com/olofster 8 | -------------------------------------------------------------------------------- /content/supporters/otacilio-maia/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2017-12-13 2 | --- 3 | name: Otacilio Maia 4 | --- 5 | organisation: Co-Founder @ReciHub; LocalHackDay organizer 6 | --- 7 | link: http://otaciliomaia.com 8 | -------------------------------------------------------------------------------- /content/supporters/paolo-sinelli/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-10-30 2 | --- 3 | name: Paolo Sinelli 4 | --- 5 | organisation: WhyMCA co-founder & organiser 6 | --- 7 | link: http://www.whymca.org/ 8 | -------------------------------------------------------------------------------- /content/supporters/patricio-molina/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Patricio Molina 4 | --- 5 | organisation: Software developer, Wikipedist 6 | --- 7 | link: http://patriciomolina.com 8 | --- 9 | sort_key: 18 10 | -------------------------------------------------------------------------------- /content/supporters/paul-lamere/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-11 2 | --- 3 | name: Paul Lamere 4 | --- 5 | organisation: Music Hack Day 6 | --- 7 | link: http://MusicMachinery.com 8 | -------------------------------------------------------------------------------- /content/supporters/paul-osman/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-18 2 | --- 3 | name: Paul Osman 4 | --- 5 | organisation: Developer Evangelist, SoundCloud 6 | --- 7 | link: http://paulosman.me 8 | -------------------------------------------------------------------------------- /content/supporters/richard-kastelein/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-12-09 2 | --- 3 | name: Richard Kastelein 4 | --- 5 | organisation: Hackfest Organiser 6 | --- 7 | link: http://www.hackitarians.com 8 | -------------------------------------------------------------------------------- /content/supporters/rob-finean/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2014-01-17 2 | --- 3 | name: Rob Finean 4 | --- 5 | organisation: UK Hackathons & Jams 6 | --- 7 | link: http://www.meetup.com/UK-Hackathons-and-Jams/ 8 | -------------------------------------------------------------------------------- /content/supporters/robert-lee-cann/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Robert Lee-Cann 4 | --- 5 | organisation: Geeks of London 6 | --- 7 | link: http://geeksoflondon.com/ 8 | --- 9 | sort_key: 1 10 | -------------------------------------------------------------------------------- /content/supporters/sam-cook/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Sam Cook 4 | --- 5 | link: http://samlr.com/ 6 | --- 7 | sort_key: 10 8 | -------------------------------------------------------------------------------- /content/supporters/sam-machin/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-11 2 | --- 3 | name: Sam Machin 4 | --- 5 | organisation: Geek 6 | --- 7 | link: http://sammachin.com 8 | -------------------------------------------------------------------------------- /content/supporters/sam-smith/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-05-19 2 | --- 3 | name: Sam Smith 4 | --- 5 | organisation: organiser, ex-RS, wears semi-contradictory hats 6 | --- 7 | link: http://twitter.com/smithsam 8 | -------------------------------------------------------------------------------- /content/supporters/scott-motte/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-12-18 2 | --- 3 | name: Scott Motte 4 | --- 5 | organisation: Developer Evangelist, SendGrid 6 | --- 7 | link: http://scottmotte.com 8 | -------------------------------------------------------------------------------- /content/supporters/seyi-ogunyemi/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Seyi Ogunyemi 4 | --- 5 | link: http://micrypt.com/ 6 | --- 7 | sort_key: 12 8 | -------------------------------------------------------------------------------- /content/supporters/shakti-goap/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2016-11-21 2 | --- 3 | name: Shakti Goap 4 | --- 5 | organisation: InOut Founder & Lead Organizer 6 | --- 7 | link: https://hackinout.co 8 | -------------------------------------------------------------------------------- /content/supporters/sheila-thomson/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Sheila Thomson 4 | --- 5 | organisation: Kaikoda 6 | --- 7 | link: http://kaikoda.com 8 | --- 9 | sort_key: 3 10 | -------------------------------------------------------------------------------- /content/supporters/shyamal-ruparel/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2014-08-19 2 | --- 3 | name: Shyamal Ruparel 4 | --- 5 | organisation: LocalHackDay.mlh.io organizer 6 | --- 7 | link: http://ruparel.co 8 | -------------------------------------------------------------------------------- /content/supporters/stefano-paluello/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-10-15 2 | --- 3 | name: Stefano Paluello 4 | --- 5 | organisation: Geek, Pastesoft 6 | --- 7 | link: http://stefanopaluello.wordpress.com 8 | -------------------------------------------------------------------------------- /content/supporters/stephen-mount/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-04-30 2 | --- 3 | name: Stephen Mount 4 | --- 5 | organisation: Developer 6 | --- 7 | link: http://stemount.co.uk 8 | -------------------------------------------------------------------------------- /content/supporters/swift/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-10 2 | --- 3 | name: Swift 4 | --- 5 | organisation: Hacker League 6 | --- 7 | link: http://hackerleague.org/ 8 | --- 9 | sort_key: 21 10 | -------------------------------------------------------------------------------- /content/supporters/syd-lawrence/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-12 2 | --- 3 | name: Syd Lawrence 4 | --- 5 | organisation: Developer 6 | --- 7 | link: http://sydlawrence.com 8 | -------------------------------------------------------------------------------- /content/supporters/tim-fogarty/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2014-04-17 2 | --- 3 | name: Tim Fogarty 4 | --- 5 | organisation: Major League Hacking UK, HackSoc Nottingham 6 | --- 7 | link: http://twitter.com/tfogo 8 | -------------------------------------------------------------------------------- /content/supporters/tim-messerschmidt/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-08-17 2 | --- 3 | name: Tim Messerschmidt 4 | --- 5 | organisation: Developer Evangelist, PayPal 6 | --- 7 | link: https://twitter.com/SeraAndroid 8 | -------------------------------------------------------------------------------- /content/supporters/tom-morris/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-09 2 | --- 3 | name: Tom Morris 4 | --- 5 | link: http://tommorris.org/ 6 | --- 7 | sort_key: 2 8 | -------------------------------------------------------------------------------- /content/supporters/tom-scott/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2012-04-09 2 | --- 3 | name: Tom Scott 4 | --- 5 | link: http://tomscott.com/ 6 | --- 7 | sort_key: 6 8 | -------------------------------------------------------------------------------- /content/supporters/tracy-abrahms/contents.lr: -------------------------------------------------------------------------------- 1 | date: 2013-12-02 2 | --- 3 | name: Tracy Abrahms 4 | --- 5 | organisation: PDXNode organizer 6 | --- 7 | link: http://twitter.com/HackyGoLucky 8 | -------------------------------------------------------------------------------- /docker-compose.yml: -------------------------------------------------------------------------------- 1 | version: "3" 2 | 3 | services: 4 | default: 5 | build: . 6 | volumes: 7 | - .:/app 8 | ports: 9 | - "5000:5000" 10 | environment: 11 | LEKTOR_DEV: 1 12 | # command: lektor server --host 0.0.0.0 -f webpack -------------------------------------------------------------------------------- /models/document.ini: -------------------------------------------------------------------------------- 1 | [model] 2 | name = Page 3 | label = {{ this.title }} 4 | protected = yes 5 | 6 | [fields.title] 7 | label = Title 8 | type = string 9 | 10 | [fields.body] 11 | label = Body 12 | type = markdown -------------------------------------------------------------------------------- /models/supporter.ini: -------------------------------------------------------------------------------- 1 | [model] 2 | name = Supporter 3 | label = {{ this.name }} 4 | hidden = yes 5 | 6 | [fields.date] 7 | label = Date 8 | type = date 9 | 10 | [fields.name] 11 | label = Name 12 | type = string 13 | 14 | [fields.organisation] 15 | label = Organisation 16 | type = string 17 | 18 | [fields.link] 19 | label = Link 20 | type = string 21 | 22 | [fields.sort_key] 23 | label = Sort key 24 | type = sort_key -------------------------------------------------------------------------------- /models/supporters.ini: -------------------------------------------------------------------------------- 1 | [model] 2 | name = Supporters 3 | label = Supporters 4 | hidden = yes 5 | protected = yes 6 | 7 | [children] 8 | model = supporter 9 | order_by = -date, -sort_key, name -------------------------------------------------------------------------------- /requirements.txt: -------------------------------------------------------------------------------- 1 | Lektor == 3.3.6 2 | click == 8.1.2 -------------------------------------------------------------------------------- /templates/document.html: -------------------------------------------------------------------------------- 1 | {% extends "layout.html" %} 2 | {% block title %}{{ this.title }}{% endblock %} 3 | {% block body %} 4 |
5 |
6 |

The Hack Day Manifesto

7 | {{ 8 | this.body 9 | |replace('Optional'|safe, 'Optional'|safe) 14 | }} 15 |
16 | 17 | 18 |
19 |

Supporters

20 |
21 | {% for supporter in site.query('/supporters').include_undiscoverable(true).order_by('date', 'sort_key', 'name').all() %} 22 |
23 |

24 | {% if supporter.link %} 25 | {{ supporter.name }} 26 | {% else %} 27 | {{ supporter.name }} 28 | {% endif %} 29 |

30 |

{{ supporter.organisation }}

31 |
32 | {% endfor %} 33 |
34 | 35 |

36 | Fork this project on GitHub, add yourself, and send us a pull request. 37 |

38 |
39 |
40 | 41 | {% endblock %} 42 | -------------------------------------------------------------------------------- /templates/layout.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 26 | The Hack Day Manifesto 27 | 28 | 29 | 30 |
31 | {% block body %}{% endblock %} 32 |
33 | 34 | 39 | 40 | -------------------------------------------------------------------------------- /website.lektorproject: -------------------------------------------------------------------------------- 1 | [project] 2 | name = Hackday Manifesto 3 | --------------------------------------------------------------------------------