Skip to content

Commit 866dc34

Browse files
authored
added a separate spoilers section (#2304)
1 parent f926569 commit 866dc34

File tree

1 file changed

+15
-2
lines changed

1 file changed

+15
-2
lines changed

docs/conf/portland/2025/example-proposal.rst

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,22 @@ Include a list of takeaways that our audience can learn from your talk, such as:
1616

1717
- Lessons the audience can apply in their own work
1818
- Ideas the audience should research further
19-
- Spoilers that provide details about the talk
2019

21-
Avoid walls of text. We recommend that you limit your abstract to a maximum of 300 words.
20+
Avoid walls of text. The ideal length for an abstract is between 100 and 300 words.
21+
22+
Detailed Spoilers
23+
-----------------
24+
25+
Use this section to share specifics about the content of your talk that will give us a better sense of its depth. These spoilers are for the *selection committee* only and won’t be shared publicly, but will help us ensure your session is a good fit.
26+
27+
In this section, please include:
28+
29+
- Specific examples, case studies, or methodologies that will be covered in your talk.
30+
- In-depth explanations of technical processes or workflows.
31+
- Key takeaways that will be explored in detail, including any particular challenges or outcomes you’ll be addressing.
32+
- Anything else that will give us a better understanding of the content you’ll be presenting.
33+
34+
We’d love to see how your talk will deliver real value to our audience. The more specific you can be about your content here, the better we’ll be able to assess whether it will resonate with our attendees.
2235

2336
Who and Why
2437
-----------

0 commit comments

Comments
 (0)