Color combination cheatsheets for the current graphics guide-in-progress! It's a much more complicated guide than the initial step-by-step guide to running an event, and it's going to include a lot more resources (cheatsheets, fillable templates, glyphs, free-to-use backgrounds and accent images, etc.) so it's taking about as long as expected. In the meantime, it seemed like a good idea to release these into the wild for general reference!
The combinations listed will be slightly hit or miss based on your screen; if a combination marked as "yes" (with the check mark) doesn't look readable to you, don't use it! Conversely, even if a combination marked as "no" (with the X) does look readable, you still shouldn't use it because your screen is the outlier in this regard and you want to cater to the lowest common denominator here. If it's marked as "no," don't use it at all; if it's marked as "yes," use it only if it looks good on your screen.
These will be explained in more detail when the guide for which they've been created is finished, but that's gonna be a while.
I think I'm supposed to be having more trouble seeing the combinations marked "no" because a lot of them are extremely easy for me to read. Like, apart from the colors that blend into each other and complementary colors, I don't see any problems, especially with the web colors. Can a screen really affect this so much that half the "no" combinations are still perfectly legible for me? I even looked at them through my phone camera pointed at my laptop screen, and I could still read the same ones as when I'm just looking at my laptop directly.
I'm honestly just asking because I'm curious. I'd probably never use most of the "no" combinations anyway, even if I can read them just fine.
A screen 100% can make that much of a difference—it can also depend on the browser you're using, the color mode your device is set to, the amount of backlight, and a billion other things of which even I, the person who made these charts, am not fully aware. These are also saved as PNGs, which have better color retention than JPEGs, so that impacts the clarity and retention of color through iterations. Most people don't use PNGs, though, and most social platforms forcibly convert PNGs to JPEGs anyway; the only reason I forced through PNGs for these is because I wanted that clarity to be retained over time.
It can also be based on your own personal color perception! The perception of (I think?) red is tied to the X chromosome, so if you have two of those you're likely to have greater perception of nuance in color altogether; likewise, if you've worked in an artistic or visual field from a young age, your eyes have been "trained" via exposure to perceive color better, and are likely to have fewer issues with regard to contrast and eyestrain.
A lot of the "no" combinations honestly look decently legible to me on my tablet screen, my main monitor and my phone—but on my sister's laptop they're eyestrain central. In at least a handful, the contrast is good with regard to values, but often the hue causes it to look like it's ready to fight the sun for the "most harmful to human vision" award.
Again, these charts are based on catering to the lowest common denominator here, so it's better to play it safe than to end up with something illegible or accidentally give someone a migraine.
ALSO editing to add: I designed these with really heavy lines in order to try to make them all as clear as possible; most text is not going to have lines this heavy, and these charts are meant as reference for the creation of specifically text-heavy graphics.
This is one part of the current guide-in-progress; it's currently only available here on tumblr, but will be available on the SYWMAFW website when the full guide is complete.
You've seen this graphic before in Fanworks Step by Step, with a simple breakdown; it's time now to get into what it all means!
▌ 1. Header
▌ 2. Event dates
▌ 3. Day listings
▌ 4. Event prompts
▌ 5. Social links
▌ NOT NUMBERED: Dividers, border, background.
Check below the cut for details!
A prompt list graphic has five (5) required features; the rest will be based on your own tastes, preferences, and level of skill in graphic design.
▌1 · Header
Should be the most prominent text element on the graphic, as this is what prospective participants need to see in order to decide if they're interested. The theme should be prominent and clear from a quick glance, although leaning into more thematic elements in styling is definitely encouraged.
▌2 · Event Dates
This section should also be set apart from the list itself, although it doesn't need to be as prominent as the header. This is counterintuitive, since the dates are probably the second most important piece of information with regard to planning and organization, but they are less important to participants than the prompts!
▌3 · Day Listings
These are less important all around, but should be stylistically distinct in order to create a sense of "flow" through the graphic; like columns in a spreadsheet or headings in a paper, these are the guideposts by which the prompts themselves are arranged.
▌4 · Event Prompts
This graphic's raison d'être! As the reason it exists in the first place, these need to be set apart from the rest of the graphic in some way. Whether this is done with typefaces, color, styling or spacing (or some combination thereof), the most important thing is that they're easily readable.
▌5 · Social Links
The most important direction on the graphic, these must be included. There's a chance that the list will be posted on its own into a group chat or reposted to a different social platform, and people need to know where to go to participate! Conversely, you don't want the social links standing out too much, as they can take attention away from the rest of the image, and that can damage the first impression of prospective participants.
▌Unmarked Elements
On this graphic this includes the background, which in this case is white with a thick grey border, and the dividers between elements, which is an interpunct for delineation between the day listing and the prompts, and a spaced slash for separating main and alternate prompts. You can also divide elements strictly by using different styles, or even by using other elements in the graphic—in the sample, the line showing the event dates is used to separate the header from the prompts!
For comparison, here's a finished prompt list graphic that was actually used in a fan week event, and the same graphic broken down into individual elements defined above:
You can see all five required elements represented clearly in the finished graphic; the positioning of these elements is different than the sample, but it follows all the same rules.
Here's the breakdown, presented in order from left to right and top to bottom:
The header (1) is placed at the top of the image and separated from the rest of the image both with the graphics used as dividers, but also because it's larger than the rest of the text and written in all caps. It lists the year in Roman numerals in order to thematically match with the fandom in question (Final Fantasy VII), each entry for which is numbered using Roman numerals.
The day listing (3) is shown next, also in Roman numerals, and separated from the prompts themselves through a combination of placement (being on the previous line) and graphical elements (the horizontal lines defining the numbers as subheadings).
The event prompts (4) are styled and divided in two ways, thanks to featuring three prompts total. The "main" prompts are a single word, as is traditional, while the alternate prompt is a short phrase, separated from the main prompts by being dropped onto another line and styled very differently.
The event dates (2) are placed in the footer of the graphic and written in Arabic numerals instead, in order to make it easy to read, while the actual text styling is identical to the header, pulling the image together.
There is only one social link (5) listed, and the platform for that link isn't mentioned—this is because, for this event, the URL is identical on both tumblr and twitter, which are the two main social platforms for the fandom in question, and also the only two where the event was advertised. (If the fandom in question were more active on other platforms and that URL wasn't available, they would have been listed individually as appropriate.)
The background and dividers in this case are quite complex, featuring imagery modified from official art, which will be detailed in the Advanced Design section in the full upcoming guide.
If you're still stuck on how to set up a prompt graphic from scratch, here's a whole gaggle of very basic prompt graphic templates that you can literally just fill in!
Previews of a couple of the simple templates being made for the graphics guide-in-progress. These are by far the most plain of the templates, made in G○○gle Sheets* so as to be fillable even without any special software. The concept here is that if you can spell, you can make an event graphic, then just screenshot the page and post it.
There are much more graphically complex templates in-progress for CSP (and PS), but those are more advanced and operate under the assumption that the event organizer has some graphic design experience under their belt. The simple batch, which has six template styles in multiple color variations (for a total of 20 templates altogether), uses only base typefaces native to the platform and primarily utilizes glyphs for flourish rather than embedding a lot of images, which can be hard to place and scale and format correctly for folks with no graphic experience whatsoever.
If anyone wants access to these templates prior to the release of the guide (as it's a very complex work so it's not likely to be out until summer proper) drop me an ask here or on my main blog @getvalentined and I'll give you a link!
*I thought about using G○○gle Slides since there's more image editing options there, but I found spacing much harder to control, and the fixed aspect ratio was also a limitation I couldn't accept and don't want anyone else locked into either. Likewise, I didn't do anything in Canѵa or other online image editors because they're not as user friendly as "fill in and screenshot."
I've unlocked reblogs on the Fan Weeks Step By Step guide! While it's still best viewed on the site (link in the post), I think that getting some circulation of the slightly less user-friendly version would still be a good thing.
Color combination cheatsheets for the current graphics guide-in-progress! It's a much more complicated guide than the initial step-by-step guide to running an event, and it's going to include a lot more resources (cheatsheets, fillable templates, glyphs, free-to-use backgrounds and accent images, etc.) so it's taking about as long as expected. In the meantime, it seemed like a good idea to release these into the wild for general reference!
The combinations listed will be slightly hit or miss based on your screen; if a combination marked as "yes" (with the check mark) doesn't look readable to you, don't use it! Conversely, even if a combination marked as "no" (with the X) does look readable, you still shouldn't use it because your screen is the outlier in this regard and you want to cater to the lowest common denominator here. If it's marked as "no," don't use it at all; if it's marked as "yes," use it only if it looks good on your screen.
These will be explained in more detail when the guide for which they've been created is finished, but that's gonna be a while.
So you wanna make a fan week event, huh? Maybe you have a favorite pairing or character that you don't think gets enough love, or enough attention from a specific angle—and you know that if you want something done right, it's best to do it yourself! Even saying that, though, organizing events is hard, especially when you don't know what you need or where to start.
That's where this guide comes in!
Here's what you need to have a successful fan week event:
A theme for the event
External interest in the theme
A hosting platform
A list of prompts
Guidelines for participation
Time to manage the event
And here are some things that, believe it or not, you DON'T need:
A popular theme
A big audience
Fancy graphics
Permission from other fans
Got it? Excellent! Now, let's get into the most basic breakdown of the steps to organizing a fan week event. Details on the things you need, some things you don't, and things you might not have thought of but won't want to forget.
Look for existing events + optional: talk to the event organizer
Choose the theme + optional: do an interest check
Choose the date
Create event accounts
Compose event prompts + optional: get feedback on prompts
Compose participation guidelines
Create a FAQ
Create event graphics + optional: get a friend to proofread
Do final organization + optional: make an organizational document
Post and schedule event prompts
GO TIME: RUN THE EVENT!
Conclude the event + optional: prep to do it again next year
Who knew that running a fan week event was a 12 step program? Weird.
Anyway, now that you know the basics, let's get into the details! Click below the cut for way more information than you ever wanted but hopefully as much as you need to organize and run your event with confidence!
(Alternately, check out the guide on the SYWMAFW site for easier navigation.)
▌ 1. Look for existing events.
Chances are you've already done this, but if not you'll want to dig around before you do literally anything else. If there is already an active fan week event for the character, pairing, or whatever else you've been brainstorming, then you're in luck! Someone else already did all the heavy lifting, and you can just participate in the next round of the existing event. This is what we call "living the dream."
▌ 1a. Talk to the existing event organizer. (OPTIONAL)
If the event that exists isn't to your tastes and you want to create your own event anyway, it's in the best interests of everyone that you try to make contact with the event organizer and let them know what you're doing. You don't want to look like a competitor, or imply that you find the other organizer's efforts to be lacking! Although some fans become possessive, most will just be excited that more people want to spread the love. Remember, nobody can stop you from doing your event, but a good fandom experience is built on being courteous, so it's best to try not to inadvertently create bad blood.
▌ 2. Choose the theme.
Fan week events are usually themed around a specific character or pairing, but there are no rules here! Your event can be centered on anything you want. An organization within the source material, a specific holiday or season, a color—the most important thing is that you hammer down exactly what the theme means to you, so that you can explain it clearly to possible participants.
▌ 2a. Do an interest check. (OPTIONAL)
While it's not required, it can be helpful to know how many people are interested in the concept of your event. This can be done on your own social media, in a Discord server, or even just in a conversation with friends. The most quantifiable way of doing this would be to run a poll, although that can be a double-edged sword. If the poll doesn't go very far or get much exposure, the small sample size can imply disinterest and be quite disheartening.
If you choose to run a poll, make sure that you do your best to boost it as far and wide as possible; ask your friends to reblog the post, share it around in your other fandom spaces, really put it out there so that you have the best possible chance of getting a genuine indication of interest.
▌ 3. Choose the date.
This guide is based around the organization of a one-week event, but your event can be any term you think is appropriate: single day, a weekend, a month, just make sure you have a set term and can put it on a calendar. This is also one point where you'll want to do a little fandom specific research to make sure that your chosen dates don't overlap with similar events or important dates in the fandom or the source material so as to avoid stepping on anyone else's toes. (Example: Say your fandom has two big pairings, A/B and B/C. You probably shouldn't schedule A/B Ship Week to run over C's birthday. This is how ship wars start, and good event organizers don't start ship wars!)
You also want to make sure that the date chosen is far enough out for you to both organize and properly boost the event! Six weeks is the minimum recommended term from interest check to event, but eight weeks is much better. This will also depend on what time of year you intend to run the event—if it's overlapping with a holiday or takes place during a busy time of year, you'll want to start spreading the word even earlier and keep boosting it regularly, or else interested parties may forget, or even miss out on the discovery that happening in the first place.
▌ 4. Create event accounts.
It may seem counterproductive to spend time making accounts when you don't have anything else for the event yet, but doing this first is a great way to help encourage yourself to keep at it! Organizing fandom events is a lot more work than people think, and having somewhere to put the fruits of your labor (and interact with people who are eager to participate in the event you're creating) makes a huge difference in maintaining the motivation needed to get through it.
For the moment, tumblr is the best platform for fandom week events as far as ease of organization goes, while Twitter is the best for exposure; the recommended course of action is to make an account for the event on both platforms, with tumblr linked as the event hub and twitter used as a secondary platform. This will be further explained in Organization Hacks when it's completed, but you'd want to finish reading this guide before jumping to that one anyway!
For events open to fanfiction, it is not recommended to make an AO3 collection at this time unless there's a specific concern about losing the event name to a URL squatter (which isn't really a thing that happens on the Archive, but anything is possible).
Other alternative platforms include PillowFort, which is recommended for hosting visual art that is disallowed by tumblr's community guidelines (artists may not be comfortable hosting this work on Twitter based on their policy of treating all uploads as free to be scraped for machine generation engines), and DreamWidth, which may be more familiar to fans who miss the days of LiveJournal events and communities.
▌ 5. Compose event prompts.
You're finally here: the fun part! The first fun part, anyway. You probably started this with at least some concept of prompts in mind, but don't be afraid to take all the time you need to get them just right! These will make or break fan participation in your event, so really put some thought into it.
Most events offer prompts that are a single word, with many offering a main prompt and an alternate prompt for each given day. However, it's important to remember that a lot of creators aren't particularly inspired by a single word; order to garner the greatest possible level of interest, you may want to to have a single word main prompt, and a short theme-appropriate quote or phrase as the alternate prompt.
▌ 5a. Get feedback on prompts. (OPTIONAL)
This doesn't mean post all of them in advance and let the general public decide what is and isn't good, mind you. Allowing entirely uncurated feedback on a themed event's main aspect will generally result in a prompt list that tried to please everyone and instead pleases no one. Ask people whose opinions you trust, and try not to set up public calls for feedback in a way that people can "check the results" on the chance that you decide you don't like the general consensus after all. You're the one organizing this event, put some trust in your own judgment!
▌ 6. Compose participation guidelines.
This is one of the harder parts of organization, because at least some of those guidelines need to be specific to your event and your fandom specifically, so you can't just copy/paste all your guidelines from somewhere else. You can, however copy/paste most of your guidelines from somewhere else—specifically, the Recommended General Guidelines Document provided for anyone reading this guide!
Please make sure you read through and modify the content of the above document to suit your event! If you don't care as much about ratings or care more about the type of content allowed in your event, the guidelines need to reflect that. For more information on creating your own guidelines, check out Guidance On Guidelines when it's available—and once you've finished reading through all the steps in this guide.
When you're done composing and formatting your event guidelines, save the post as a draft. It will go live later.
▌ 7. Create a FAQ.
Another hard part! How can you have frequently asked questions if your event is brand new and no one has ever asked you about it? The trick here is that there are questions that are asked frequently of any event, and you can get a basic list of these from the Recommended Basic FAQ Document provided for anyone reading this guide.
As with the event guidelines, save this post as a draft to set live later.
▌ 8. Create event graphics.
This is the part where a lot of people balk, and it's understandable. Graphics are hard, and not everyone has the skill or even the interest to create them! However, contrary to popular belief, these don't need to be super fancy professional grade design. Your fan week graphics do not need to be worthy of the Louvre.The "required" graphics for any fan week event are as follows:
A header image
An icon (also called a "profile pic" or PFP)
The event prompt list in image form
That's it. Literally. You don't need a fancy header for every single prompt—although you can absolutely do that if you want to—or a custom-built blog theme for the event account. You don't need custom artwork to count down the days leading up to the event. You need a header, an icon, and a prompt list.The header and icon should be used on every platform where the event is active, including AO3 if applicable, and a general rule of thumb is that either the header or the icon should have the URL of the event written on it, but even that isn't entirely necessary.The prompt list should be constructed similarly to the following:
(Check alt text for a description.)
Recommended Design
Content: event name, date(s), list of prompts, and social media handles.
Colors: accent, aside, body, and background. (Not too many!)
Styles: title, subtitle, body, and footer. (Must be readable.)
A more comprehensive breakdown of the basic graphic design standards featured in this example will be available in Getting Into Graphics when completed.
The two most important elements of your event graphics are readability and cohesion. Even just maintaining the same color scheme for all event graphics will create a sense of cohesion that will help the event look like you've put as much work into it as you actually have. Even if you choose not to use a custom theme on tumblr, setting the accent and background colors of the event account blog to match the color scheme of your graphics makes a world of difference in the presentation of the event!
For folks who like to do the graphical side of things, here are a few others you can make to look even more fancy, without working too hard:
Mini headers for event pages (directory, FAQ, guidelines, etc.)
Mini headers for each day of the event listing each prompt (make sure to also include the prompts as text in the body of the post)
A thank you to be posted at the close of the event (this can literally be something as simple as the prompt graphic with the words "thank you for participating!" scrawled over it in a different color)
When posting the prompt list, make sure you also have a written version of the prompts in the post, preferably tucked beneath a cut/readmore. This assures that even if the image doesn't load (tumblr is a Functional Webbed Site, after all) people can still see the list! Likewise, the nicest graphics in the world won't matter to a screenreader, so this also falls under the need for the prompt list to be readable.
For full-bore professional grade graphic design, you can create a fully custom theme. However, this isn't generally recommended, as the ever-changing nature of web design standards and tumblr's opaque documentation on accepted versus deprecated modifiers and styles in their themes can cause organizers to get lost in the weeds for weeks when they could be working on other tasks that are actually necessary for the event. (Learn from my mistakes.)
Also, for the love of fandom, do not create anything for your event using generative AI. Just don't do it. Not only is this the equivalent of shooting the event in the foot before it's even stood up on its own due to the very legitimately negative opinion toward machine generation within most creative spaces (99.99% of fandom creatives will refuse to participate in an event run by someone who is pro-genAI), but also runs the risk of real legal issues due to the inherently unethical method by which all machine generation engines function. Just don't do it. I don't care if you can't draw. Don't do it.
▌ 8a. Get a friend to proofread (OPTIONAL)
This is listed as optional but it is highly recommended. It's harder to see errors in things that you created, particularly when you've been working on those things for a long period time—and by this point, you'll probably have been chipping away at this project for days if not weeks. Get a second pair of eyes on it if you can.
▌ 9. Do final organization.
This is the boring part. It's not time to post the prompts yet, but it is time to post your event's guidelines, FAQ, and any other nitty-gritty event information you've been working on; it's recommended to backdate these entries to keep them from showing up on the dashboard, and turn off reblogs to avoid old versions of these posts circulating about the site.
You may also want to create a guide on how to add work to the AO3 collection—authors should be able to add work to the collection themselves the moment you open it rather than relying on you to add each work manually. Check out this guide created for @sephesisweek on tumblr as an example.
▌ 9a. Make an organizational document. (OPTIONAL)
Again, while this is optional, it is highly recommended. In a plain text document, copy/paste or manually write out the block of tags that you intend to use when posting event prompts, as well as a list of all the organizational, rating, content and other tags to be used on reblogged prompt fills. Any tag that you intend to reuse regularly should be placed in this document to keep the organization straight.
It's also recommended to paste in the URLs of the event's most important pages to assure you don't have to go digging if you need to direct someone to something specific.
More comprehensive information on creating an organizational document will be available in Organization Hacks upon completion.
Save this document natively on your computer or whatever device(s) you're using to organize, access and manage the event. You'll thank yourself later.
▌ 10. Post and schedule event prompts.
Create the post where you intend to reveal the prompt list! It should have the image, some basic information, a link to the directory, FAQ and guidelines, and then the prompts in text under a cut/readmore. Create multiple versions of this post to go up roughly once a week leading up to the event; these posts should use the same block of tags as the original, but have slightly different body text in order to avoid being flagged by often-buggy automated spam filters. Counting down the weeks (and eventually the days) leading up to the event is the best way to differentiate one post from the next.
If your fandom has a popular event calendar account, make sure to contact them to get your event added to the calendar, and tag the account if applicable in order to get your post(s) reblogged leading up to the event and increase your reach.
You should also schedule individual prompt posts at this time, set to go live each day of the event and tagged appropriately for each prompt. This allows you to fully commit to the event's tag structure, while also making sure that the individual prompt posts will go live around the same time every day of the event—even if you're indisposed.
▌ 11. GO TIME: RUN THE EVENT!
While there will probably be some work in the interim (answering questions and modifying the FAQ and tags are the most common), you're really just going to be in a holding pattern until the event starts.
If you've done all the organizational work, running the event itself shouldn't be particularly difficult, although it may be time consuming depending on the level of participation. Prompt fills should generally be queued rather than reblogged on sight, as this will not only assure that you don't flood the dashboard of anyone following the event account, but also allow you to double-check your tags before the post goes live on the main page. The last thing you want is for something intense to go up with no content warning!
Track the event tag and run regular searches to make sure that nobody has been missed. Double check that everyone is adding work to the AO3 collection on their own. Work on your own prompt fills in the interim, if you're participating as well as organizing.
Most importantly, this is the time to bask in the joy of a fandom community coming together around something you all love—that's the real reason that events like this exist, and presumably the whole reason you wanted to organize one in the first place. Try to enjoy yourself!
▌ 12. Conclude the event.
At the end of the event week term, make a post thanking everyone for their participation. It's recommended to continue to reblog posts and keep the AO3 collection open for submissions for one full week following the event in order for people who may have been waylaid by life to catch up if they so choose.
At the end of this straggler week, post a final thank you message, close the AO3 collection to new submissions, and take a nap! You deserve it!
▌ 12a. Prep to do it again next year! (OPTIONAL)
Depending on how things look when the dust settles, you may be one of the many people who decide that organizing a fan week event just isn't for them after all. This is fine! It's a lot of work, and it really isn't for everybody—but, well, you already did all the heavy lifting, didn't you?
If you followed this guide, you'll never have to fully organize this specific fan week again. You've got the guidelines, the FAQ, the tag structure. You know how to create, maintain, and close an AO3 collection. You know which sorts of prompts people liked and which ones they didn't, and you have a solid visual style that you're (hopefully) happy with.
In fact, all you really need to do to prep for next year is come up with a new set of prompts and update some tags...that doesn't sound so hard, does it?
Maybe that's the devil talking. You'll have to find out next year.