Skip to content

Latest commit

 

History

History
141 lines (102 loc) · 9.02 KB

5-bsl.md

File metadata and controls

141 lines (102 loc) · 9.02 KB

Helix Hackathon Part V

May 20-24 2019 - Basel, Switzerland

Fifth Project Helix Hackathon

The fifth Project Helix Hackathon will happen in Basel, Switzerland during the week of May 20th. If you feel like attending, please sign up here.

(See the Hackathon Archive for past Hackathons)

Location

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

orangerie-basel.jpg

The hackathon will take place at the Orangerie at Grellingerstrasse 75, 4052 Basel. The nearest international airports are BSL and ZRH.

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 & Demo Format Programming Documentathon Demos
Afternoon Airport Transfer & Arrival Coding Documentaton Coding Departure & Airport Transfer
Evening Set-up, drinks Hacking Team dinner Hacking -

We will have two documentathons; during these, each of us will work to improve the documentation on some helix component they did not write themselves:

  • What is the api of that component
  • Why was it build?
  • What is it good for?
  • What should it not be used for?
  • Are there any caveats to using that module?

The goal of this event is to improve the documentation, share knowledge of parts of helix and reduce the truck factor in the helix team.

Lodging

Recommended hotels for our out-of-town visitors:

  • Sevogelhof - Bed & Breakfast in historic 19th century building in the Gellert borough(5 min walk)
  • ibis budget simple & modern 1-star hotel (8 min walk)
  • Novotel modern 4-star hotel (10 min walk)
  • DASBREITEHOTEL - ecologically & socially sustainable hotel overlooking the Rhine (15 min walk, or 2 min by tram #3 + 8 min walk)
  • Motel One - great 1-star hotel in the city center, right next to Adobe Basel (20 min walk, or 7 min by tram #14 + 3 min walk)
  • Hotel Alfa classic 3-star hotel in Birsfelden (20 min walk, or 3 min by tram #3 + 8 min walk)
  • Radisson Blu modern 4-star hotel in the city center (22 min walk, or 5 min by tram #14 + 7 min walk)
  • Hotel Euler century-old 4-star hotel at the train station (19 min walk, or 4 min by tram #14 + 8 min walk)

Goal

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

  • Refine our on-call policy (see here for initial discussion)
  • Discuss and work on next UI iteration with @kamendola
  • Where and how do we document Helix?
  • Improve Developer Experience for devs new to Helix, see helix-cli/711 (@stefan-guggisberg, @rofe, ...)
  • Integration with project management tools (@bdelacretaz), looking at parallels with similar work that I'm doing for assets management.

Attendees

Who is going to be there? Can I come?

  1. @rofe
  2. @tripodsan
  3. @kptdobe
  4. @simonwex
  5. @koraa
  6. @trieloff (Monday-Thursday night)
  7. @stefan-guggisberg
  8. @kgera
  9. @kamendola
  10. @bdelacretaz (Tuesday-Thursday)
  11. @dominique-pfister
  12. @lkrapf (Thursday)
  13. @asanso (Thursday)
  14. @acollign (Thursday)
  15. @meryllblanchet (Tuesday, Wednesday evening, Friday)
  16. @raho (Tuesday, Wednesday evening, Friday)
  17. @dunguyen (Tuesday, Wednesday evening, Friday)
  18. @davidnuescheler (Monday afternoon-Thursday night)
  19. @anfibiacreativa (Wednesday to Friday)

We have room for 20 people. First come, first served :)

Please share this page with people inside Adobe that you'd like to invite. Add yourself to the list if you want to attend.

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
  5. Check out the changes made to Helix since the last Hackathon

Changes

For occasional contributors to Helix it can get hard to keep track of what has changed in Helix since the last hackathon. Below, you can find a curated (i.e. incomplete) list of some of the most interesting changes to Helix since the fourth Hackathon, i.e. Feb 1st, 2019.

Helix CLI

  • You can no longer use custom Docker containers for Helix, and Helix is using the Adobe I/O Runtime standard node.js by default, which speeds up cold starts v0.13.4
  • When starting a Helix project, make sure to run hlx auth, which will authenticate the Helix GitHub app with your repository v0.13.9
  • You can now use .env files to keep track of frequenly used environment variables like HLX_FASTLY_AUTH v0.13.9
  • hlx publish now uses a remote service to update your Fastly config, so that you always have the lastest VCL, even when your hlx is slightly outdated. You can specify with service to use with the new --api-publish flag v0.13.12
  • There is no longer a binary distribition for macOS. You have to install Helix CLI now using npm i -g @adobe/helix-cli v0.13.13
  • The default pipelines are now even more customizable using the new before and after extension points v0.13.13
  • In production, static assets will now get URLs that are immutable and can be cached in the browser for a long time. This improves performance v2.0.0
  • Selective publishing is possible through the --only and --exclude flags in hlx publish. All non-matched strains will get published with the latest configuration from master. v2.1.0
  • You can now create (but not yet use) cgi-bin actions v2.2.0
  • Helix supports JSX as an additional templating language v2.5.0

Helix Pipeline

  • The content.html property has been removed from the context v0.11.0
  • In section-content-detection, the is-paragraph class name is now called is-text v1.0.0
  • The HTML pipeline now has additional extension points with before and after that can be used in a pre.js v1.1.0
  • Some pipeline steps are now allowed to mutate the return value (this disables merging for the current step) v1.2.0
  • The context dumps in (logs/debug) now have more meaningful file names v1.3.0
  • HTML heading tags (h1, h2, etc.) now have id attributes, so that they can be used as link targets for deep linking v1.5.0
  • The XML pipeline exposes the same extension points as the HTML pipeline v1.7.0
  • Markdown documents can now have internal embeds (include another Markdown document) v1.8.0
  • HTML in Markdown is now supported v1.8.0
  • Links to static assets are now detected and rewritten into URLs that are cachable for a long time v1.10.0
  • HTTP headers can now be set from a HTL template by using <link> or <meta> tags v1.11.0
  • The HTML pipeline now parses the complete HTML document before it is rendered, allowing modifications through the hast extension point v1.12.0

Other Parts of Helix