Pocket program - Revision history

Susanphilbrook: /* What to include? */

2025-08-28T19:27:46Z

What to include?

← Older revision		Revision as of 12:27, 28 August 2025
Line 16:		Line 16:
	*'''QR Codes''': Not a requirement, but people have found it useful to have QR codes for things like the digital program book, pocket program, a restaurant guide, and Minicon Discord channel.		*'''QR Codes''': Not a requirement, but people have found it useful to have QR codes for things like the digital program book, pocket program, a restaurant guide, and Minicon Discord channel.
	*'''MnStf Logo''': Branding!		*'''MnStf Logo''': Branding!
	*'''Credits''': Please credit any artwork included in the Pocket Program, and all publications.		*'''Credits''': Please credit any artwork included in the Pocket Program, and all publications. Below is an example.

	''~~A note from Rachel Kronick: The blimp~~ and the ~~sword (located in~~ the ~~"Images" wiki) are pieces of art I created. I licensed them~~ Creative Commons ~~Attribution Share-~~Alike~~; that means that you may use them, but you must credit me when you do so~~.''		''Artwork at <locations> by <artist name here>. All contents ©2025 by the Minnesota Science Fiction Society and
			the respective creators. This work may be redistributed under the Creative Commons Attribution
			NoncommercialShare Alike License (creativecommons.org/licenses/byncsa/3.0/us/)''

Susanphilbrook at 19:20, 28 August 2025

2025-08-28T19:20:04Z

← Older revision		Revision as of 12:20, 28 August 2025
Line 64:		Line 64:
	Suggestions from Rachel: There isn't a totally satisfactory solution to this. What I've recently been doing is to have one column in the main grid for "events going on in other places and time", often labeled "Elseplace" or something equally silly, and another whole mini-grid with the non-block items in their own schedules. This means that, for example, the movie room (often called Cinema Obscura as of late) and the official gaming schedule have had their own sections. I like to give times in both the utmost left and the utmost right columns (that is, repeated left and right), with a color scheme that highly contrasts with the rest of the schedule. This makes the schedule easier to read, I find (see M50).		Suggestions from Rachel: There isn't a totally satisfactory solution to this. What I've recently been doing is to have one column in the main grid for "events going on in other places and time", often labeled "Elseplace" or something equally silly, and another whole mini-grid with the non-block items in their own schedules. This means that, for example, the movie room (often called Cinema Obscura as of late) and the official gaming schedule have had their own sections. I like to give times in both the utmost left and the utmost right columns (that is, repeated left and right), with a color scheme that highly contrasts with the rest of the schedule. This makes the schedule easier to read, I find (see M50).

	===~~=The~~ Maps====		===Maps===

	''More to be added here''		''More to be added here''

Susanphilbrook: /* Time Blocks on the Grid */

2025-08-28T18:57:44Z

Time Blocks on the Grid

← Older revision		Revision as of 11:57, 28 August 2025
Line 56:		Line 56:
	The Programming head has very helpfully made most of the time blocks consistent. That is, ''most'' programming items start and end at the same times. This makes the Pocket Programmer's life much easier, and makes it easier for con members read the schedule. There have been other cons where the Pocket Program was such a mess of different times and locations that the 'grid' was more of a maze. Recently, Minicon has settled on hour-long blocks, with half-hour breaks in between. Most other cons do it this way too.		The Programming head has very helpfully made most of the time blocks consistent. That is, ''most'' programming items start and end at the same times. This makes the Pocket Programmer's life much easier, and makes it easier for con members read the schedule. There have been other cons where the Pocket Program was such a mess of different times and locations that the 'grid' was more of a maze. Recently, Minicon has settled on hour-long blocks, with half-hour breaks in between. Most other cons do it this way too.

	NOTE: When "Programming Season" begins, make your life (and everyone else's) easier by notifying all departments with schedules ~~to be listed on the grid,~~ to use the standard time format (i.e. half-hour increments at :00 or :30)		NOTE: When "Programming Season" begins, make your life (and everyone else's) easier by notifying all departments with schedules to use the standard time format (i.e. half-hour increments at :00 or :30)

	The trick, of course, is that some items can't fit precisely into the overall time blocks. Sometimes movies are odd times, and therefore don't fit easily into the main blocks. Most of the gaming schedule doesn't easily fit, etc. What to do?		The trick, of course, is that some items can't fit precisely into the overall time blocks. Sometimes movies are odd times, and therefore don't fit easily into the main blocks. Most of the gaming schedule doesn't easily fit, etc. What to do?

Susanphilbrook: /* The Grid */

2025-08-28T18:56:07Z

The Grid

← Older revision		Revision as of 11:56, 28 August 2025
Line 47:		Line 47:
	and the Pocket Program, there may be times where book has already been printed, and perhaps some scheduling changes have occurred. It's annoying, but not the end of the world.		and the Pocket Program, there may be times where book has already been printed, and perhaps some scheduling changes have occurred. It's annoying, but not the end of the world.
	Printing of the Pocket Program doesn't happen until the week of the convention, so last minute changes to the Grid or Maps can happen there.		Printing of the Pocket Program doesn't happen until the week of the convention, so last minute changes to the Grid or Maps can happen there.

			[https://docs.google.com/spreadsheets/d/1yz9u3nWsFwogkh-AAFbdKCg8J94LYGDFfP5T-coTWs8/edit?gid=1938267234#gid=1938267234 Here] is an example of the Programming Grid created in Google Sheets for the Minicon 58 Pocket Program. Should you be saddled with creating a grid, feel free to save a copy of this and use it as a template. It fits on 11x17 perfectly and is readable.

	''A note from Rachel Kronick: When Minicon is three or four days (like M50), I've recently set the grid page in landscape orientation, with the various rooms as columns and the timeline as rows.''		''A note from Rachel Kronick: When Minicon is three or four days (like M50), I've recently set the grid page in landscape orientation, with the various rooms as columns and the timeline as rows.''

	[https://docs.google.com/spreadsheets/d/1yz9u3nWsFwogkh-AAFbdKCg8J94LYGDFfP5T-coTWs8/edit?gid=1938267234#gid=1938267234 Here] is an example of the Programming Grid created in Google Sheets for the Minicon 58 Pocket Program.

	===Time Blocks on the Grid===		===Time Blocks on the Grid===

Susanphilbrook: /* What to include? */

2025-08-28T18:50:42Z

What to include?

← Older revision		Revision as of 11:50, 28 August 2025
Line 15:		Line 15:
	*'''Bozo Bus Info''': Adding a note to check the Bozo Bus Tribune (the at-con newsletter) to learn about or contribute schedule changes, surprise programming, and other notifications.		*'''Bozo Bus Info''': Adding a note to check the Bozo Bus Tribune (the at-con newsletter) to learn about or contribute schedule changes, surprise programming, and other notifications.
	*'''QR Codes''': Not a requirement, but people have found it useful to have QR codes for things like the digital program book, pocket program, a restaurant guide, and Minicon Discord channel.		*'''QR Codes''': Not a requirement, but people have found it useful to have QR codes for things like the digital program book, pocket program, a restaurant guide, and Minicon Discord channel.
	*'''Credits''': Please credit any artwork included in the Pocket Program. ''A note from Rachel Kronick: The blimp and the sword are pieces of art I created. I licensed them Creative Commons Attribution Share-Alike; that means that you may use them, but you must credit me when you do so.'' ~~Hi-res images are available in the ''Images'' section of this Wiki.~~		*'''MnStf Logo''': Branding!
			*'''Credits''': Please credit any artwork included in the Pocket Program, and all publications.

			''A note from Rachel Kronick: The blimp and the sword (located in the "Images" wiki) are pieces of art I created. I licensed them Creative Commons Attribution Share-Alike; that means that you may use them, but you must credit me when you do so.''


	Examples of other things we have previously included (optional):		Examples of other things we have previously included (optional):
Line 25:		Line 29:
	*'''Volunteer Information'''		*'''Volunteer Information'''
	*'''Fun Art''': GoH art is always the best, but filios and license free clip art is also acceptable.		*'''Fun Art''': GoH art is always the best, but filios and license free clip art is also acceptable.
	*'''Silliness''': For funsies~~. Who doesn't like a footnote? Footnotes are cool~~.		*'''Silliness''': For funsies.

	[https://mnstf.org/minicon/web-era-pub-index.php Here] is where you can view a history of Minicon publications.		[https://mnstf.org/minicon/web-era-pub-index.php Here] is where you can view a history of Minicon publications.


	==Layout==		==Layout==

Susanphilbrook at 04:17, 28 August 2025

2025-08-28T04:17:31Z

← Older revision		Revision as of 21:17, 27 August 2025
Line 1:		Line 1:
	''Edited/Updated by Susan, incorporating information provided by Rachel and others. (Aug. 2025)''		''Edited/Updated by Susan, incorporating information previously provided by Rachel and others. (Aug. 2025)''


Line 30:		Line 30:


	==~~Pocket Program~~ Layout==		==Layout==

	===Size===		===Size===

Susanphilbrook: /* The Maps */

2025-08-28T04:16:16Z

The Maps

← Older revision		Revision as of 21:16, 27 August 2025
Line 63:		Line 63:
	====The Maps====		====The Maps====

			''More to be added here''

	==Printing!==		==Printing!==

Susanphilbrook at 04:15, 28 August 2025

2025-08-28T04:15:24Z

← Older revision		Revision as of 21:15, 27 August 2025
Line 39:		Line 39:
	[https://mnstf.org/minicon58/m58_pocket_program.pdf Here] is an example of the most recent Minicon 58 Pocket Program.		[https://mnstf.org/minicon58/m58_pocket_program.pdf Here] is an example of the most recent Minicon 58 Pocket Program.

	===The Grid!===		===The Grid===

	This is arguably the most important piece of the Pocket Program, because while those of us in Publications do our best to provide accurate information across the Program Book		This is arguably the most important piece of the Pocket Program, because while those of us in Publications do our best to provide accurate information across the Program Book
Line 61:		Line 61:
	Suggestions from Rachel: There isn't a totally satisfactory solution to this. What I've recently been doing is to have one column in the main grid for "events going on in other places and time", often labeled "Elseplace" or something equally silly, and another whole mini-grid with the non-block items in their own schedules. This means that, for example, the movie room (often called Cinema Obscura as of late) and the official gaming schedule have had their own sections. I like to give times in both the utmost left and the utmost right columns (that is, repeated left and right), with a color scheme that highly contrasts with the rest of the schedule. This makes the schedule easier to read, I find (see M50).		Suggestions from Rachel: There isn't a totally satisfactory solution to this. What I've recently been doing is to have one column in the main grid for "events going on in other places and time", often labeled "Elseplace" or something equally silly, and another whole mini-grid with the non-block items in their own schedules. This means that, for example, the movie room (often called Cinema Obscura as of late) and the official gaming schedule have had their own sections. I like to give times in both the utmost left and the utmost right columns (that is, repeated left and right), with a color scheme that highly contrasts with the rest of the schedule. This makes the schedule easier to read, I find (see M50).

	===The Maps===		====The Maps====



	==Printing!==		==Printing!==

Susanphilbrook: /* Time Blocks on the Grid */

2025-08-28T04:14:42Z

Time Blocks on the Grid

← Older revision		Revision as of 21:14, 27 August 2025
Line 49:		Line 49:
	[https://docs.google.com/spreadsheets/d/1yz9u3nWsFwogkh-AAFbdKCg8J94LYGDFfP5T-coTWs8/edit?gid=1938267234#gid=1938267234 Here] is an example of the Programming Grid created in Google Sheets for the Minicon 58 Pocket Program.		[https://docs.google.com/spreadsheets/d/1yz9u3nWsFwogkh-AAFbdKCg8J94LYGDFfP5T-coTWs8/edit?gid=1938267234#gid=1938267234 Here] is an example of the Programming Grid created in Google Sheets for the Minicon 58 Pocket Program.

	==Time Blocks on the Grid==		===Time Blocks on the Grid===

	The Programming head has very helpfully made most of the time blocks consistent. That is, ''most'' programming items start and end at the same times. This makes the Pocket Programmer's life much easier, and makes it easier for con members read the schedule. There have been other cons where the Pocket Program was such a mess of different times and locations that the 'grid' was more of a maze. Recently, Minicon has settled on hour-long blocks, with half-hour breaks in between. Most other cons do it this way too.		The Programming head has very helpfully made most of the time blocks consistent. That is, ''most'' programming items start and end at the same times. This makes the Pocket Programmer's life much easier, and makes it easier for con members read the schedule. There have been other cons where the Pocket Program was such a mess of different times and locations that the 'grid' was more of a maze. Recently, Minicon has settled on hour-long blocks, with half-hour breaks in between. Most other cons do it this way too.

	~~The trick, of course, is that some items can't fit precisely into the overall time blocks. Notice in the example above that movies are sometimes two hours long~~, and ~~therefore don~~'~~t fit easily into~~ the ~~main blocks. Most of the gaming schedule doesn't easily fit~~, ~~and~~ the ~~Rumpus Room~~ (~~programming for kids and families) doesn't always fit the grid easily~~. ~~Many readings are only a~~ half-hour~~. What to do?~~		NOTE: When "Programming Season" begins, make your life (and everyone else's) easier by notifying all departments with schedules to be listed on the grid, to use the standard time format (i.e. half-hour increments at :00 or :30)

	Suggestions from Susan: I broke the times down in half-hour increments, and shade in the time blocks. If there's an item with a non-standard time (films, usually), I show the start time below the name (see M58). Like Rachel, I have a column for "Other" locations, for items that one-off events, like a gaming tournament in the game room, or a trivia in the bar, etc. I add the location under the Name of the event.		The trick, of course, is that some items can't fit precisely into the overall time blocks. Sometimes movies are odd times, and therefore don't fit easily into the main blocks. Most of the gaming schedule doesn't easily fit, etc. What to do?

			Suggestions from Susan: I broke the times down in half-hour increments, and shade in the time blocks. If there's an item with a non-standard time (films, usually), I show the start time below the name of the film (see M58). Like Rachel, I have a column for "Other" locations, for items that are one-off events, like a gaming tournament in the game room, or a trivia in the bar, etc. I add the location under the Name of the event.

	Suggestions from Rachel: There isn't a totally satisfactory solution to this. What I've recently been doing is to have one column in the main grid for "events going on in other places and time", often labeled "Elseplace" or something equally silly, and another whole mini-grid with the non-block items in their own schedules. This means that, for example, the movie room (often called Cinema Obscura as of late) and the official gaming schedule have had their own sections. I like to give times in both the utmost left and the utmost right columns (that is, repeated left and right), with a color scheme that highly contrasts with the rest of the schedule. This makes the schedule easier to read, I find (see M50).		Suggestions from Rachel: There isn't a totally satisfactory solution to this. What I've recently been doing is to have one column in the main grid for "events going on in other places and time", often labeled "Elseplace" or something equally silly, and another whole mini-grid with the non-block items in their own schedules. This means that, for example, the movie room (often called Cinema Obscura as of late) and the official gaming schedule have had their own sections. I like to give times in both the utmost left and the utmost right columns (that is, repeated left and right), with a color scheme that highly contrasts with the rest of the schedule. This makes the schedule easier to read, I find (see M50).

	===The Maps!===		===The Maps===



	==Printing!==		==Printing!==

Susanphilbrook at 03:41, 28 August 2025

2025-08-28T03:41:53Z

← Older revision		Revision as of 20:41, 27 August 2025
Line 26:		Line 26:
	*'''Fun Art''': GoH art is always the best, but filios and license free clip art is also acceptable.		*'''Fun Art''': GoH art is always the best, but filios and license free clip art is also acceptable.
	*'''Silliness''': For funsies. Who doesn't like a footnote? Footnotes are cool.		*'''Silliness''': For funsies. Who doesn't like a footnote? Footnotes are cool.


	~~[https://mnstf.org/minicon58/m58_pocket_program.pdf Here] is an example of the most recent Minicon 58 Pocket Program.~~



	[https://mnstf.org/minicon/web-era-pub-index.php Here] is where you can view a history of Minicon publications.		[https://mnstf.org/minicon/web-era-pub-index.php Here] is where you can view a history of Minicon publications.
Line 37:		Line 32:
	==Pocket Program Layout==		==Pocket Program Layout==

	*'''Size~~''':~~ Tabloid (11x17). Anything smaller gets to be too difficult to read.		===Size===
			Tabloid (11x17). Anything smaller gets to be too difficult to read. Smaller paper requires smaller type. Don't worry, people will also complain about the tabloid size paper, pointing out "this isn't pocket sized," but hey, they can fold it. If the paper was much smaller, the complaints about readability would be much louder.

	~~The past few years, I've mostly been doing the pocket program as a tabloid (11x17") document. This~~ has ~~allowed the type~~ to ~~be ''barely'' readable: generally 8pt URW Palladio in the main programming grid. Smaller paper requires smaller type. People complain about~~ the ~~tabloid size paper -- "this isn't pocket sized" -- but, hey~~, ~~they can fold it. If~~ the ~~paper was much smaller, I bet~~ the ~~complaints about readability would be much louder~~.		It has generally worked well to put the Grid vertically on one side, and the maps and information on the other side.

	~~Mostly, I've tried to stick to "programming grid on the front, maps and miscellaneous information on~~ the ~~back"~~.		[https://mnstf.org/minicon58/m58_pocket_program.pdf Here] is an example of the most recent Minicon 58 Pocket Program.

	~~===The Grid===~~

	~~This is arguably the most important function of the pocket program, especially because it can end up being a better version of the overall schedule than the program book can. (See "~~The ~~printing process", below, for more on this.) Laying the grid out can be a pain in the butt. Here is a copy of the M49 grid, for reference:~~		===The Grid!===

			This is arguably the most important piece of the Pocket Program, because while those of us in Publications do our best to provide accurate information across the Program Book
			and the Pocket Program, there may be times where book has already been printed, and perhaps some scheduling changes have occurred. It's annoying, but not the end of the world.
			Printing of the Pocket Program doesn't happen until the week of the convention, so last minute changes to the Grid or Maps can happen there.

	When Minicon is three or four days, I've recently set the grid page in landscape orientation, with the various rooms as columns and the timeline as rows. ~~(For M50, it looks like I~~'~~m going to have to put it in portrait orientation.)~~		''A note from Rachel Kronick: When Minicon is three or four days (like M50), I've recently set the grid page in landscape orientation, with the various rooms as columns and the timeline as rows.''

	[https://docs.google.com/spreadsheets/d/1yz9u3nWsFwogkh-AAFbdKCg8J94LYGDFfP5T-coTWs8/edit?gid=1938267234#gid=1938267234 Here] is an example of the Programming Grid created in Google Sheets for the Minicon 58 Pocket Program.		[https://docs.google.com/spreadsheets/d/1yz9u3nWsFwogkh-AAFbdKCg8J94LYGDFfP5T-coTWs8/edit?gid=1938267234#gid=1938267234 Here] is an example of the Programming Grid created in Google Sheets for the Minicon 58 Pocket Program.

	====Time ~~blocks: standard and non-standard==~~==		==Time Blocks on the Grid==

	~~Note that the programming~~ head has very helpfully made most of the time blocks consistent. That is, most programming items start and end at the same times. This makes the ~~pocket programmer~~'s life ~~a lot~~ easier, and makes it ~~much~~ easier for con members ~~to actually~~ read the schedule. ~~(I've seen~~ other cons where the ~~pocket program~~ was such a mess of different times and locations that the 'grid' was more of a maze~~, and it was almost easier to just read the full descriptions in their equivalent of the program book~~.) Recently, ~~we've~~ settled on hour-long blocks, with half-hour breaks in between~~: 10:00am–11:00, 11:30–12:30pm, 1:00–2:00, 2:30–3:30, 4:00–5:00, 5:30–6:30, 7:00–8:00, 8:30–9:30, 10:00–11:00~~. Most other ~~nearby~~ cons do it this way, too.		The Programming head has very helpfully made most of the time blocks consistent. That is, ''most'' programming items start and end at the same times. This makes the Pocket Programmer's life much easier, and makes it easier for con members read the schedule. There have been other cons where the Pocket Program was such a mess of different times and locations that the 'grid' was more of a maze. Recently, Minicon has settled on hour-long blocks, with half-hour breaks in between. Most other cons do it this way too.

	The trick, of course, is that some items can't fit precisely into the overall time blocks. Notice in the example above that movies are sometimes two hours long, and therefore don't fit easily into the main blocks. Most of the gaming schedule doesn't easily fit, and the Rumpus Room (programming for kids and families) doesn't always fit the grid easily. Many readings are only a half-hour. What to do?		The trick, of course, is that some items can't fit precisely into the overall time blocks. Notice in the example above that movies are sometimes two hours long, and therefore don't fit easily into the main blocks. Most of the gaming schedule doesn't easily fit, and the Rumpus Room (programming for kids and families) doesn't always fit the grid easily. Many readings are only a half-hour. What to do?

	~~There isn't a totally satisfactory solution to this. What~~ I~~'ve recently been doing is to have one column in~~ the ~~main grid for "events going on~~ in ~~other places~~ and time~~", often labeled "Elseplace" or something equally silly, and another whole mini-grid~~ with ~~the~~ non-~~block items in their own schedules. This means that~~, ~~for example~~, the ~~movie room~~ (~~often called Cinema Obscura as of late~~) ~~and the official gaming schedule~~ have ~~had their own sections. See the above illustration~~ for ~~an example of this.~~		Suggestions from Susan: I broke the times down in half-hour increments, and shade in the time blocks. If there's an item with a non-standard time (films, usually), I show the start time below the name (see M58). Like Rachel, I have a column for "Other" locations, for items that one-off events, like a gaming tournament in the game room, or a trivia in the bar, etc. I add the location under the Name of the event.

	I like ~~to give times~~ in ~~both~~ the ~~utmost left and~~ the ~~utmost right columns (that is~~, ~~repeated left and right), with a color scheme that highly contrasts with~~ the ~~rest~~ of the ~~schedule. This makes the schedule easier to read, I find~~.

	~~When there are items that don~~'t ~~start at the standard times, if~~ I'~~m going~~ to ~~put them~~ in the grid, ~~I always try to place them~~ in ~~an earlier slot rather than a later one~~. ~~For~~ example, ~~if Ms~~. ~~Smith is doing a reading from 6:30~~ to ~~7:00, I'll place it~~ in the ~~5:30–6:30 block rather than~~ the ~~7:00–8:00 block. My reasoning~~ is that ~~this way, if someone accidentally follows~~ the ~~main~~ schedule, ~~they'll end up early rather than missing the programming item entirely~~.		Suggestions from Rachel: There isn't a totally satisfactory solution to this. What I've recently been doing is to have one column in the main grid for "events going on in other places and time", often labeled "Elseplace" or something equally silly, and another whole mini-grid with the non-block items in their own schedules. This means that, for example, the movie room (often called Cinema Obscura as of late) and the official gaming schedule have had their own sections. I like to give times in both the utmost left and the utmost right columns (that is, repeated left and right), with a color scheme that highly contrasts with the rest of the schedule. This makes the schedule easier to read, I find (see M50).

	===The Maps===		===The Maps!===

	These could, to be honest, be printed smaller. But in recent years, there hasn't been enough information that needed to fit on this side, and the grid has needed to be full-on tabloid size. So I've ended up making the maps larger than they needed to be to fill space.

	~~[[ File:M49 pocket program 85x11 1z r2 for display on wiki 1b p2.png ]]~~

	==~~The printing process~~==		==Printing!==

	Because the pocket program is only a single sheet, printing it has a very short lead time (at least compared to the program book). This means that the pocket program can reflect changes made to the schedules, often a lot later than the program book can.		Because the pocket program is only a single sheet, printing it has a very short lead time (at least compared to the program book). This means that the pocket program can reflect changes made to the schedules, often a lot later than the program book can.