Story progress bar is being displayed for too long.

for example anna_perfectappworld has text

• anna_perfectappworld

Put padding or margin on the Dragzone for responsive

would be great

-> wouldn't it be great

a linked format (...)

-> a linked format,

close bracket in parallax.js

Create a starting HTML & CSS setup

• HTML Barebone
• CSS Reset, etc

No idea how, maybe something that moves?

The presentation for the pitch on Thursday.

if it isn't online then a fallback should be provided. (image?)

We still need to buy:

• paperclips: Hema (nieuwstraat) or maybe in the one euro shop (zuidstraat)
• wool: Veritas is het goedkoopst (City2 - nieuwstraat) of ook Hema

What everyone already brings:

Haroen:

• led xmas lights

Lisa

• frame
• black sheet for behind the frame
• 4D glutenvrije pinguin snoepjes

Use of a different formula for the story progress.

Would just fill the text box and probably send an event to update.

The stickers are overprinted and need to be cut

The Facebook share image is pretty creepy:

Maybe a more textual one would work better in that context?

It's smaller than the others, and thus has a different header than the others.

Since it's basically RDFa.info/play, but stripped down, it seems logical that we should link there.

add dots like on swissair or a line that fills either right or on the top

Move navigation arrow higher from bottom on bigger screens.

We're now standardised on Datex, but the correct way is DATEX.

Has to have icons and stuff

maybe not necessary after merge with vocab (#83)

Section 8 better image responsive behaviour

Third easily could be dropped.

Creating / Searching open source assets for front-end design.

Don't need a "validate button", do that action on the callback of dragula

before the blue part, we can use .internal-link and with a href of the next section to move smoothly into the next section.

Maybe also take care of that after stopping to scrolljack? might be necessarey

currently the "example" in iframe before the blue section is just the "one parking" example. This should be the full https://osoc16.github.io/jekyll-term-generator/parking/ and be live. Also needs explanations of what to set up (as well as the demo for datex2-linker and the second example)

when opening the page the iframe already shows the complete parking app which is a bit weird :)

but first: an example

(idea by @PieterJanPauwels)

Right now some of the sections became broken again, namely #section3 and some others as well

going from small owner to large parking garage, would cover all the steps, explaining RDFa, json-ld, harvesting data, reusing data.

cc @LisaDebontridder

In need of a JSON-LD tutorial/guide text for section 9

This would mean

• incorporating the /terms
• using vocab.datex.org as a github.io cname
• making sure that https is not enabled

1. arrow
2. clear text

see also #88 which apparently isn't fixed yet.

• Add titles for Anna and John, JSON and RDFA
• maybe add a line like in the footer

1. better text in the badge (don't encourage clicking on it that much)
2. visualisation before editor
3. call to action

The text in section 8 isn't self-explanatory.

leave out the "main" bullets

reported by @pietercolpaert

They don't fit on my screen and should thus either scroll or split up.

Right now they get replaced to emojis on iOS 😂 so we should probably use an icon. @PjGeeroms had a different idea of how they should look

When clicking an arrow it doesn't always go to the full page now :)

Fix space between paragraphs and the line-height of the RDFA & JSONLD sections

The website should nowhere use moby link. It should all be datex.org.

• <title>
• description
• misc tags
• favicons

Let's dive into two preferred ways to publish data

Converting the parking data from http://datatank.stad.gent/4/mobiliteit/bezettingparkingsrealtime
to open linked data (JsonLD)

in section RDFa

Right now #section5 isn't totally clear, it is too broad while it should still be focussed on parkings and close the example

"that's" -> "that is" ...

• branding
• copywriting
• design for intro page

Currently the about page only leads to the footer, according to @LisaDebontridder it makes more sense to have an /about page/folder that would explain in more detail, and also house for example the press release.