|
| 1 | +--- |
| 2 | +marp: true |
| 3 | +theme: cdl-poster |
| 4 | +size: A0 |
| 5 | +--- |
| 6 | + |
| 7 | +```poster-layout |
| 8 | +TTTTTTTTTTTTTTTTTTTTTTTTTTTT |
| 9 | +IIIIIIIIMMMMMMMMMMMMRRRRRRRR |
| 10 | +IIIIIIIIMMMMMMMMMMMMRRRRRRRR |
| 11 | +IIIIIIIIMMMMMMMMMMMMRRRRRRRR |
| 12 | +IIIIIIIIMMMMMMMMMMMMRRRRRRRR |
| 13 | +CCCCCCCCDDDDDDDDDDDDRRRRRRRR |
| 14 | +CCCCCCCCDDDDDDDDDDDDRRRRRRRR |
| 15 | +CCCCCCCCDDDDDDDDDDDDRRRRRRRR |
| 16 | +CCCCCCCCDDDDDDDDDDDDRRRRRRRR |
| 17 | +``` |
| 18 | + |
| 19 | +## T: Your poster title goes here |
| 20 | + |
| 21 | +## A brief subtitle that captures the main finding or question |
| 22 | + |
| 23 | +**Author One**¹, **Author Two**¹², **Author Three**² |
| 24 | + |
| 25 | +¹ Department of Psychological and Brain Sciences, Dartmouth College | ² Collaborating Institution |
| 26 | + |
| 27 | +## I: Introduction and motivation |
| 28 | + |
| 29 | +<div class="note-box" data-title="Orient your audience"> |
| 30 | + |
| 31 | +Start with the **broad question** your research addresses. Why should the reader care? Narrow from the big picture to your specific contribution in 3–5 sentences. |
| 32 | + |
| 33 | +</div> |
| 34 | + |
| 35 | +<div class="note-box" data-title="What to include"> |
| 36 | + |
| 37 | +- The **big-picture problem** your work addresses |
| 38 | +- Why existing approaches fall short |
| 39 | +- Your specific **research question** or hypothesis |
| 40 | +- A visual or diagram that captures the core idea |
| 41 | + |
| 42 | +</div> |
| 43 | + |
| 44 | +<div class="note-box" data-title="Less is more"> |
| 45 | + |
| 46 | +Aim for **minimal text** and **maximal visual impact**. A reader should grasp your motivation in under 30 seconds. Use a figure instead of a paragraph wherever possible. |
| 47 | + |
| 48 | +</div> |
| 49 | + |
| 50 | +## M: Methods |
| 51 | + |
| 52 | +<div class="definition-box" data-title="Experimental design"> |
| 53 | + |
| 54 | +Describe your **paradigm** concisely: number of participants, key conditions, stimuli, and procedure. A flow diagram is ideal here. |
| 55 | + |
| 56 | +</div> |
| 57 | + |
| 58 | +<div class="definition-box" data-title="Analysis pipeline"> |
| 59 | + |
| 60 | +Show your pipeline as a visual flow: **collection → preprocessing → modeling → validation**. A diagram works best here. |
| 61 | + |
| 62 | +</div> |
| 63 | + |
| 64 | +<div class="definition-box" data-title="Figures over formulas"> |
| 65 | + |
| 66 | +Prefer **diagrams and flowcharts** over dense notation. Limit to one or two key formulas at most. |
| 67 | + |
| 68 | +</div> |
| 69 | + |
| 70 | +<div class="definition-box" data-title="Tools and code"> |
| 71 | + |
| 72 | +List key software and libraries used. If your code is open source, include a link or QR code to the repository. |
| 73 | + |
| 74 | +</div> |
| 75 | + |
| 76 | +## R: Results |
| 77 | + |
| 78 | +<div class="example-box" data-title="Tell a story with your data"> |
| 79 | + |
| 80 | +Lead with your **most critical result** first, then provide supporting evidence. Every figure should have a clear, self-explanatory takeaway message. |
| 81 | + |
| 82 | +</div> |
| 83 | + |
| 84 | +<div class="example-box" data-title="Figure 1: Main result"> |
| 85 | + |
| 86 | +Place your **primary finding** here. The figure should be self-explanatory — a reader should understand the key message without reading surrounding text. |
| 87 | + |
| 88 | +</div> |
| 89 | + |
| 90 | +<div class="example-box" data-title="Figure 2: Supporting evidence"> |
| 91 | + |
| 92 | +Additional results that **support or extend** your main finding. Use tables for quantitative comparisons, or multi-panel figures for consistency across conditions. |
| 93 | + |
| 94 | +</div> |
| 95 | + |
| 96 | +<div class="example-box" data-title="Statistical reporting"> |
| 97 | + |
| 98 | +Report key statistics concisely. Use a small **table** for multiple comparisons, or annotate figures directly with significance markers. |
| 99 | + |
| 100 | +</div> |
| 101 | + |
| 102 | +<div class="example-box" data-title="Common pitfall"> |
| 103 | + |
| 104 | +Don't overcrowd this section. **Two or three well-designed figures** are far more effective than five cramped ones. Leave white space for visual breathing room. |
| 105 | + |
| 106 | +</div> |
| 107 | + |
| 108 | +<div class="example-box" data-title="Figure 3: Replication"> |
| 109 | + |
| 110 | +If applicable, show that your findings **generalize** across datasets, conditions, or participant groups. This strengthens the impact of your main result. |
| 111 | + |
| 112 | +</div> |
| 113 | + |
| 114 | +## C: Conclusions and future directions |
| 115 | + |
| 116 | +<div class="tip-box" data-title="Summary of findings"> |
| 117 | + |
| 118 | +Restate your **key findings** in 2–3 bullet points. Connect them back to the motivating question from the introduction. |
| 119 | + |
| 120 | +</div> |
| 121 | + |
| 122 | +<div class="tip-box" data-title="Broader impact"> |
| 123 | + |
| 124 | +Explain why your findings **matter** beyond the specific experiment — theoretical, clinical, or practical implications. |
| 125 | + |
| 126 | +</div> |
| 127 | + |
| 128 | +<div class="tip-box" data-title="Limitations"> |
| 129 | + |
| 130 | +Acknowledge **limitations** honestly and note how future work might address them. |
| 131 | + |
| 132 | +</div> |
| 133 | + |
| 134 | +<div class="tip-box" data-title="Future directions"> |
| 135 | + |
| 136 | +- Next experiments you plan to run |
| 137 | +- Extensions of the current approach |
| 138 | +- Open questions raised by your findings |
| 139 | + |
| 140 | +</div> |
| 141 | + |
| 142 | +## D: References and acknowledgments |
| 143 | + |
| 144 | +<div class="warning-box" data-title="References"> |
| 145 | + |
| 146 | +Include **5–10 key citations** most relevant to your work. Use a numbered list with abbreviated journal names. Prioritize citations the reader might actually look up. |
| 147 | + |
| 148 | +</div> |
| 149 | + |
| 150 | +<div class="warning-box" data-title="Acknowledgments and funding"> |
| 151 | + |
| 152 | +Thank funding agencies (with grant numbers), collaborators, and lab members. Mention shared resources and institutional support. |
| 153 | + |
| 154 | +</div> |
| 155 | + |
| 156 | +**Contact**: your.email@dartmouth.edu | **Web**: context-lab.com | **Code**: github.com/ContextLab |
0 commit comments