beeldengeluid / data-stories Goto Github PK

in markdown:
![Wordcloud van de Top 100 meest voorkomende onderwerpen (toegekend door archivarissen) ](./Screenshot-MediaSuite-WordCloud-resourceviewer.png)

• Philo to start shared document and enter first draft
• Mari to enter first draft
• Philo to proofread draft
• Mari to proofread draft
• Philo to incorporate feedback
• Philo to create landscape hero image of Matthijs VN
• Muriel to proofread final version

http://mediasuitedatastories.clariah.nl/

It’s a nice idea to show a video on top of a data viz screenshot, but to encode this in a gif is a bad idea because it results in huge (>50MB) files that load slowly on the web.

We could come up with alternatives, but as a first step I’d propose to remove the animated videos and use a static image instead.

Locations which have zero mentions are coloured green, which is not continuous with the otherwise blue colour scale in use. This is confusing as it may signal that green countries have mentions while they haven't. It would be better to use white as colour for non mentioned countries.

also this visualisation should contain a key to indicate which shades of colour signify which intensity. I think a previous version contained a key like this?

Corona story uses references and appendix subpages. these should not be listed on the home page.

as requested by @mwigham :)

• publish Forestry CMS commits to non-production branch

then we merge to production branch later when happy.

Tasks:
Check the availability of the following data for items with 'coronavirus' or 'covid-19' in their description, scenedesc description or subtitles:

• Subtitles
• Speaker labelling
• Visualise the availiability

Acceptance criteria;

• we know the availability of this data for the coronavirus corpus
• we know the size of the coronavirus corpus

Our first version of the site shows the stories in order of publication. In an individual story, the footer has links to the previous and next story. We need to reconsider how to handle navigation in the light of the plans for modular data stories, when dates can be less important than themes, or use of shared resources

Tasks:

• Consider what is of importance to the reader when navigating, given the modular style of data stories
• Work out how to support finding important related stories with clear navigational controls, including returning to the main page

Acceptance criteria:

• A reader can find related content and get back to the main page easily

link: http://mediasuitedatastories.clariah.nl/

perhaps easiest to remove the caption in Flourish?

if we end up using timelens...

ref: https://www.gatsbyjs.org/blog/2019-11-21-how-to-convert-an-existing-gatsby-blog-to-use-mdx/

• research options and choose i18n library
• get translations from Muriel for intro and about texts
• integrate translated DWDD article
• enable routing for en and nl versions
• add language switch
• deploy

This could be solved fairly straight forward via one of the following:

• Vercel Git integration (in use for MediaScape)
• Netlify
• some build & deploy workflow via GitHub Actions (some example actions to investigate)
• https://surge.sh/

to be discussed between @phivk and @MartijnBNG