Main title

In unhcrdown: UNHCR Branded Templates for R Markdown Documents

knitr::opts_chunk$set(echo = TRUE,
                      fig.retina = 2,
                      fig.showtext = TRUE,
                      dev = "ragg_png",
                      dpi = 300)

This is part 1 {-}

This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires.

This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing. Finally, be sure to remove this message! This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires.

It is further proof that refugee movements and the broader issue of migration of populations ... is a global challenge that cannot be confined to a few countries.

Filippo Grandi

This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.

Second level {-}

Finally, be sure to remove this message! This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires. This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.

Finally, be sure to remove this message! This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing. Finally, be sure to remove this message! This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires.

This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.

Finally, be sure to remove this message! This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires. This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing. Finally, be sure to remove this message! This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires.

This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.

Finally, be sure to remove this message! This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires. This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.

Finally, be sure to remove this message!This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing. Finally, be sure to remove this message! This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires. This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing. Finally, be sure to remove this message! This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires. This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.

Second level {-}

Finally, be sure to remove this message! This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing. Finally, be sure to remove this message! This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires.

This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.

Finally, be sure to remove this message! This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires. This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.

And now part 2 {-}

This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires.

Second level {-}

This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.

Finally, be sure to remove this message!

And now part 3 {-}

This file is what a user will see when they select your template. Make sure that you update the fields in the yaml header. In particular you will want to update the output field to whatever format your template requires.

Second level {-}

This is a good place to demonstrate special features that your template provides. Ideally it should knit out-of-the-box, or at least contain clear instructions as to what needs changing.

Finally, be sure to remove this message!

unhcrdown documentation built on April 3, 2025, 10:49 p.m.