# Project Helix Hackathon

## Second Project Helix Hackathon

### Agenda

> I hear this is a hackathon, are you going to hack all day?

Although this is a hackathon, we won't be hacking all the time, there will also be plenty of programming and coding.

| Time      | Monday         | Tuesday            | Wednesday   | Thursday    | Friday    |
| --------: | -------------- | ------------------ | ----------- | ----------- | --------- |
|   Morning | -              | Helix Introduction | Programming | Programming | Demos     |
| Afternoon | Arrival        | Coding             | Coding      | Coding      | Departure |
|   Evening | Set-up, drinks | Hacking            | Team dinner | Hacking     | -         |

### Location

> Where is this going to happen? Do you have a windowless conference room blocked out?

At [Turmstübli](https://www.werkraumwarteckpp.ch/projekte/turmstuebli/)

[Burgweg 7, CH 4058 Basel](https://goo.gl/maps/GZKKqVFQG9S2)

How to come: [hackathonSeptBaselHowToCome.md](hackathonSeptBaselHowToCome.md)

Booking flights in and out of BSL or ZHR and a hotel in Basel is a good bet.

### Goal

> What are you planning to show at the end of the week?

As a result of the last Hackathon, we've changed the development environment and delivery pipeline quite massively, so as a level set/intro to helix we will walk through where we are and how things work for development and the publibly accessable "live" version.

For the Hackathon, we will be trying to get to a place where we can do an additional iteration of the a couple of the [markdown repos](https://github.com/adobeio/adobeio-documentation/blob/master/events/index.md) for [adobe.io](https://www.adobe.io/apis/cloudplatform/events/documentation.html) documentation and get to a place where those are working seamlessly from existing markdown in github to a live site that looks and feels like [adobe.io](https://www.adobe.io/apis/creativecloud/dreamweaver.html). 

As a stretch goal we would like to get to a place the marketing pages on adobe.io can also be represented in markdown and are rendered inspired by the spark page rendering with a custom header and footer.
For the sake of the Hackathon we are going to assume that all content is authored directly in Markdown on GitHub.

A couple of things we want to validate are:

- nontrivial content delivery using Helix
- responsive content using Helix
- development set-up and experience when building Helix components
- road to production level live delivery for adobe.io


### Attendees

> Who is going to be there? Can I come?

1. @davidnuescheler
2. @trieloff
3. @stefan-guggisberg
4. @tripodsan
5. @acapt
6. @dominique-pfister
7. @tiberiu44 a.k.a. @boros
8. @markusheer
9. @kgera
10. @simonwex
11. @lcrabb
12. @ruxandraburtica
13. @rofe (friday morning, maybe monday evening)
14. @cwoeltge
15. ~~@andreaskuefer (tuesday morning, maybe monday afternoon)~~


The Helix Hackathon (just like the rest of Project Helix) is an Open Development project. If you are interested and can make it to Basel, you are welcome to join.

Interested in attending? Just edit this file, add your name, and make a Pull Request.

### Preparation

> What can I do to prepare for the Hackathon?

1. Read the `README.md` and linked vision documents in this repo
2. Join `#helix-chat` on Slack
3. Install the `hlx` Command Line app and create your first project
4. Comment on the GitHub issues you think would be good candidates for the Hackathon

### Outcomes

The outcomes of the hackathon can be watched here: https://vimeo.com/290650915/6a68ba7af8 – please don't share the video URL outside Adobe, it is not for public consumption.