---
title: testing note
tags: testing, update-medium, manager:holford
---

==Separate branches worked! I will now trial a process to tag Stefan in the commit so he can check the new page. The `update` is this comment.==

It did not work when I committed to the branch that held everything together. I am trying now to update pages one by one and then put them into a branch that had dummy pages for the others.

Here is another test. I am only updating this note, but not the other. Will I be able to merge this in GitHub?

What happens when I commit this direct to GitHub?

This is a test. I'm adding something new here.

Here's another change.

Here I'm adding something more.

Aaaand another change.

<!--
Here's a comment: ABC. Let's see whether this comment can be found in the rendered HTML.
-->

[TOC]

<span style="color:green">[link](https://c19vax.scibeh.org) in green</span>

# Vega-Lite

{
  "$schema": "https://vega.github.io/schema/vega-lite/v4.json",
  "data": {"url": "https://vega.github.io/editor/data/barley.json"},
  "mark": "bar",
  "encoding": {
    "x": {"aggregate": "sum", "field": "yield", "type": "quantitative"},
    "y": {"field": "variety", "type": "nominal"},
    "color": {"field": "site", "type": "nominal"}
  }
}

I can edit this note!

# A header!

[link](https://hackmd.io/@scibehC19vax/contributors)

# Stuff to add to landing page in subsequent versioning

Some of this was commented out of the launch version. It is here so we can paste straight in and avoid intermediate editing appearing.

## Media coverage

Read what the media have said about the _Handbook_ and Wiki [here](https://c19vax.scibeh.org/mediacoverage).

## (From earlier draft of FAQ)

:::spoiler Do you have a masterlist of resources?

<br>

Please visit [this page](https://c19vax.scibeh.org/resources) for master list of all our resources.
:::

## How can I use this resource?
:::spoiler Policy-makers

<br>

If you're a policy maker, you might want to start with the pages on [policies](https://c19vax.scibeh.org/policy).
:::

:::spoiler Practitioners

<br>

Do you need to communicate about vaccines to patients, your community, or stakeholders? You might want to check out the pages on [communication](https://c19vax.scibeh.org/communication).

:::

:::spoiler Journalists

<br>

Reporting on COVID-19 vaccinations? These pages are a good place to start.
:::

:::spoiler Researchers

<br>

Looking for research related to different aspects of COVID-19 vaccination behaviour? Start with our [concept map](https://c19vax.scibeh.org/#Insights) for insights, and explore the nodes and their links.

You might also find our list of external [resources](https://c19vax.scibeh/resources) useful.

:::

:::spoiler Curious readers

<br>

Just curious about the topic and want to know more? We advise starting to explore the [concept map](https://c19vax.scibeh.org/#Insights) to see the different topics and how they are inter-related.

:::

# Testing Twitter

> [name=Dawn H] Another test (I like this one!):

<a href="https://twitter.com/STWorg/status/1346969671732490241"> _{Share the handbook!}</a>

{%twitter 1346969671732490241 %}

> [name=Dawn H] I don't think there is a direct Twitter embed.
> The below is Twitter's 'embed tweet' code, but I don't think this is what we're looking for since it just copies the text.

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">The COVID-19 Vaccine Communication Handbook: A practical guide for improving vaccine communication &amp; fighting misinformation <a href="https://t.co/3s5JWBvi0m">https://t.co/3s5JWBvi0m</a> <br><br>Our new handbook (PDF+living wiki), which helps fighting the spread of misinformation about COVID-19 vaccines. <a href="https://twitter.com/hashtag/c19vaxwiki?src=hash&amp;ref_src=twsrc%5Etfw">#c19vaxwiki</a> 1/n <a href="https://t.co/pRpkcJgVfC">pic.twitter.com/pRpkcJgVfC</a></p>&mdash; Stephan Lewandowsky (@STWorg) <a href="https://twitter.com/STWorg/status/1346969671732490241?ref_src=twsrc%5Etfw">January 6, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

> [name=Dawn H] We can try adding something like the below to the feedback footer:

_{[Share the _Handbook_ on Twitter](https://twitter.com/STWorg/status/1346969671732490241).}

# A test of PDF embeds

## Using OSF
<iframe src="https://mfr.de-1.osf.io/render?url=https://osf.io/f6a48/?direct%26mode=render%26action=download%26mode=render" width="100%" scrolling="yes" height="0px" marginheight="0" frameborder="0" allowfullscreen webkitallowfullscreen></iframe>

## Using Figshare
<iframe src="https://widgets.figshare.com/articles/13521605/embed?show_title=1" width=100% height=100% frameborder="0"></iframe>

<br><br>

>[name=Dawn H] `width=100%` fixes the extended width problem on mobile, but the same code for height makes it way too short.
> The version below may be a good fix for now:

<br><br>

<iframe src="https://widgets.figshare.com/articles/13521605/embed?show_title=1" width=100% height="680px" frameborder="0"></iframe>

## Testing polis

Embedding directly doesn't work; I'm just goint to go with a [link](https://pol.is/5pfyh8myca).

<div class='polis' data-conversation_id='5pfyh8myca'></div>
<script async src='https://pol.is/embed.js'></script>