I know. Your content is already organized. It's not random word salad jumbled together. You thought it through, and put things in order. This step involves finding places to insert visual cues for your readers. Places where you start a new topic, for example, or where you introduce a new idea.

So, the first thing to do with your content is look for these natural breaks in the text--places where you could insert a headline. Headlines will break up your text and make it easier to read. In fact, it's a good idea to strive for headline breaks at least every screenful of text--about every 300 words or so. Of course, the size of a single screen depends on things you can't control, things like the user's screen size or typeface choices, but 300 words is a pretty good estimate.

I've called them headlines, but they could also be bullet points. Sometimes in visual media bullet points are better than text, just because they are more visual. Whatever you call them, they are natural breaks in the text.

You'll noticed that we've used the dropnote links as our headlines, and that clicking on them reveals about a page of text. They're kind of like turning a page in a book. We'll talk about the WritingML for doing that in the layout section.

That's a LOT more breaks than you'd expect to see in printed media. That's because, for a variety of reasons, screens filled with text are more fatiguing to read than printed media. We'll discuss this more in a bit. For now, it's important to identify and mark these breaks.

Headlines are visual cue for the reader, but they work that way for the author, too.

Once you've got the headlines, a different organizational structure might occur to you. The headlines give an overview of the content--like the struts in a wall or the piers holding up a bridge.

Also, as the author, you'll know that some of the headlines are more important than others. The most important headlines are like chapters in a textbook or novel--they are natural breaking points in the stream of ideas, and point to larger divisions in the content.

Organizing your headlines means finding the major and minor break points. You might have a major break point with three sub-headlines.

Suppose your content is inviting people to enter an online writing contest. There are lots of these on WDC. Perusing them shows typical headlines are:



There are likely subheadings under each heading. For example, is this for prose, poetry, or both? Suppose you have a particular interest in poems using anapestic tentrameter. Some people--like me!--might not know that is, so a definition would be a subheading under the "what to enter" heading. Is there a minimum or maximum length? Does it have to be new for this contest?

The Rules could have many headings or bullets. These involve contest deadlines, whether or not adult content is permitted, lenght of entries, whether items or book entries are acceptable, and so on.

You get the idea.

What's that? And why break everything up, anyway?

Those are good questions. Hemingway didn't stop every hundred words or so with a bullet point in The Sun Also Rises. Even textbooks have long stretches of unbroken prose. So what gives? Why this emphasis on breaks?

At first glance, it looks like there's not much difference between a page on Writing.Com--or anywhere on the web--and a page in a book. There are words in a row that make up sentences. The sentences make up paragraphs, which make up pages, and so on.

It turns out, there is a difference. In the first place, those words in a row are in longer rows on screens than in books. Longer rows are more fatiguing to read. For one thing, it's easier to lose your place. That's why newspapers use narrow columns. Years of practical experience--now verified by research--has led to the standard page sizes for books. Those standards have shorter line lengths than the typical web page. This is true even on Writing.Com, where the content for member pages is restricted to the middle of the screen. On my desktop, that gives a line-length over twice as a long as a hard cover book and three times as along as a paperback.

Scrolling a screen is also different than turning a page. Turning a page is tactile. You don't have to peer at the page to be sure that you don't turn too many or too few. Scrolling keeps your eyes nailed to the screen, watching to get it just right. That's why readers for e-books have page-turning buttons instead of scroll bars. As we said above, clicking on the headlines on this page is like turning the page in a book.

This gives rise to an important conclusion

The first step in implementing this rule is identifying headlines that are spaced no more than one screenful of text apart. In practice, this means there should be no more than 300-400 words between headlines.

The emphasis on breaks is to give the readers a break and to make your pages both more visually appealing and less tiring to read. The headlines help the reader identify the important concepts, and let them know something new is coming. Web pages are mixed media in the sense that they are both visual and textual. Different content will have a different mix of visual and textual elements, but the web provides both a challenge and an opportunity for authors.

The organization of your content lets you decide what the layout should be. That's the next topic!

Creating a user page on Writing.Com isn't the same as creating a web page. Our user pages certainly reside on web pages, since they (almost) always have the same navigational blocks on the left, right, and top as every other page on Writing.Com. The single exception is user web pages hosted by Writing.Com, but that's a separate topic. What we're interested in here that big middle segment and helping your readers navigate that part of the content--the part we create.

It's one thing if we are publishing fiction or a poem--after all, that's what this space is designed for, and the Writing.Com editor gives tools for formatting text. It's relatively straightforward to insert italics or to center a title, for example. Fiction doesn't usually need much more than this. Indeed, unusual formatting or layout can distract from fictional world of the story. We do NOT recommend using headlines or other formatting that pulls the reader out of the here-and-now of the fictional world.

Still, some elements of layout are common in fiction. Layout means formatting your text to facilitate reading, understanding, and navigating the content. For fiction, you probably don't need much more than the occassional bit of italics, or perhaps an extra line feed to mark a jump in time. Articles, though, are different.

Articles engage the reader in ways unlike fiction. Our goal in fiction is to induce the fictional dream in the readers, in which they become the author's collaborator in imagining the fictional world. In an article, though, we are engaging the reader on an intellectual level, to persuade, or inform, or teach. Articles are where headlines are helpful.

Writing.Com newsletters are an example of where headlines appear. For example, see "For Authors Newsletter (July 26, 2023)" . You'll also notice that example also uses color and boldface to emphasize important ideas in addition to headlines.

When you write an article, blog, or newsletter, you can use layout to facilitate the readers' interactions with your content.

Again, there's nothing fancy here. We're just using the standard layout tools provided by the Writing.Com editor, along with the Single Screen Rule from the first section. That's enough for almost all pages on Writing.Com.

However, a few pages on Writing.Com are more complex than simple newsletters or blogs. This one, for example, has multiple sub-pages, kind of like the chapters in a book. These longer, more complex pages, are the main subject of the remainder of our discussion.

We've been using headlines, too, as you've doubtless noticed. The way we've been using them employs one of the layout tools that the owners of Writing.Com have provided. Layout includes things like inserting italics or boldface in your copy. Layout means formatting your copy so that it's more readable. When you're writing a longer article for a screen, that means implementing the Single Screen Rule.

We've already mentioned formatting italics by typing {i} formatting italics{/i} in the editor to get italicized type. The layout tool we've been using is like that. It employs something called a dropnote. Here's the syntax



The result is YOUR HEADLINE in blue, underlined text--a link. When the reader clicks on the link, it expands to show the material in green, your content, i.e., the material between the end of the initial {dropnote:"HEADLINE"} tag and the start of final {/dropnote} closing tag . The code we used for the dropnote that you clicked above was

We ended the entire section with {/dropnote}-see below.

Back toi the syntax: the text hiighlighted in green is the content you want to fit on one screen. Two important notes:

Now you know almost all the secrets that make this page--or set of pages--work.

We're done with this section, so this is where we close by typing {/dropnote}

Have you ever wanted to put a table on a Writing.Com page? You can! See!

Chapter	Item	Words	Total so far
1	2192539	2216	2216
2	2192789	2255	4471
3	2192901	2769	7240
4	2192975	2295	9535
5	2193046	2511	12046

This one keeps track of chapters in one of our in-progress books. It gives the chapter number, the item number that contains the chapter, the word count for that chapter, and the words so far. We're kind of obessive about these kinds of details. Anyway, this is an example of a table in a Writing.Com page. The good news it's not hard to do!

It's kind of convoluted, since it involves working through Excel and Word, but it's not hard.

First, create and format your table in Excel. Highlight your table and copy it to your paste buffer with <CONTROL> C.

Next, open a new Word document. In the document, click on the PASTE options in the upper left hand corner of the home screen. Choose PASTE and select option that lets you keep source programming and link the contents. Presto! Your formatted spreadsheet is in your document. Save it to your hard disk with a name you can remember. (On most Windows systems, you can't do the next step from a virtual drive, so you have to save it to a physical disk.) Also, CLOSE the document in Word, since otherwise Windows will lock it and the next step won't work.

Now, on Writing.Com, click the option in the left-column to create a new item. There's a big blank spot at the top that says "Drag and drop your Word document here." So, with file explorer, find the document you just saved. Drag it with your mouse to the area on the Writing.Com screen. It takes a few moments for the system to process your file, then you get another choice: simple or complex HTML. Our goal here is to get a formatted table, so choose "Complex." Fill out the rest of the required elements when creating a new item (title, ratings, etc.), then save and view the document. You'll see your Excel spreadsheet displayed as a Writing.Com item. You can see the one we made this way by clicking here: "Import Excel Table Example" .

It's not perfect, but it produces a reasonable approximation. In our original table, the first row was two lines high, while all the subsequent rows were one line. The process produced a table with what appear to be rows of equal height with lots of extra white space. Not a big deal.

The downside is that you can't edit the resulting Writing.Com item directly. You have to edit your original Excel file, save it, OPEN and then CLOSE the Word document that contains the link to the spreadheet (to update the link). Finally, back at your Writing.Com version of the table, select Edit. This will give you an opportunity to drag and drop the new version in the window that opens, just like you did when you created your document.

Of course, this works for regular Word documents that just have ordinary Word formatting. In this case, though, you can choose to create a SIMPLE HTML document, rather than a complex one. This will give you a document with ordinary WritingML in it, and you can edit that.

How did I get the spreadsheet item, {item:2301751}, to display in this document? Well, that's a trick we'll talk more about in the next section: the insert tag. The document that contains the spreadsheet is "Import Excel Table Example" . In order to display it within another Wrighting.Com document--like this one--use the insert tag like so:

It turns out the insert tag is critical to the next section on navigation.

This isnt exactly layout, but it's useful to know. On the rare occassions when we want to include a table in a Writing.Com document, we have to re-learn how to do this, so it was a good investment of our time to memorialize this here.

The more you insert layout in your copy, the more likely you are to make a mistake. In fact, it's inevitable. Few things are more frustrating than tracking down exactly where you failed to close a {b} tag. It's even worse with dropnote tags, since it's inevitable that the close dropnote tag--the {/dropnote}--is a long ways from where you started it with the original {dropnote:"HEADLINE"} tag.

Best practices are things that people have discovered that help you recover from mistakes. In fact, a definition of a working program is one in which the mistake hasn't been found. Yet. The best praciice that's relevant here is commenting your copy.

But you're copy isn't like a Javascript program that no one except another geek will read. You copy is your content! You need to find an invisible way to insert your camments, a way that people who read your content will never see. Lucky for us, there is another helpful formatting tool that Writing.Com gives us: the {hide} and {/hide} commands. Everything between the start {hide} and stop {/hide} is invisible when the page is displayed.

For longer pages with multiple headlines--and hence multiple {dropnote} tags--it's helpful to have searchable markers for the headlines. That's where the {hide} command comes in.

For example, the layout we used for the above headline was:

The ### symbols we used aren't required; they just give something to search for that will probably only appear where we've used it to mark {dropnotes}. We've similarly marked the other {dropnote} tags in this document.

Everyone who writes code, whether its Javascript or WritingML, hates writing comments, usually with a white hot passion. That is, until they've made a mistake and can't find where it's at. That's still probably going to happen, but you'll be glad you put comments like this next to your {dropnote} tags.

Turst us.

This means designing for those who are differently abled. In particular, for those who use screen readers, graphical elements need to include meaningful text that these readers can access.

For dropnotes, screen readers will identify these as a link that can be clicked to reveal more content, and will read the headline you've typed into the dropnote.

You've probably already guessed that the major divisions of this site use dropnotes with an image providing the headline. Screen readers can't read the image, but they can read the title and short description you provided when you loaded the image to your Writing.com portfolio. Therefore, if you use images as navigational tools, you need to be sure that these fields are informative.

In fact, anyone can access these. Hover your cursor over an image on this page. After a moment, a little window will pop up that displays the title, the short description, and item number of the graphic. This is another way Writing.Com evidences good web design.

It's also the case that some users will find the default typeface on your page too small to read. As we've aged, we've discovered that the default typeface for pages is often too small for our weary eyes. We've even enlarged the type on one of our contest pages in response to a request from a user, usinsg the {size:4} and {/size} tags. However, this is generally not necessary. All browsers have the capacity to enlarge (or shrink) the contents (try <control>+). When using my laptop, I often do this while working on Writing.Com, since the dealut font in the editor is microscopic.

If your page uses music as an element, you should similarly attend to accessibility. It can be handy to use color as an element, for emphasis or to link navigational elements for example, but bear in mind that not all readers will report this.

In all cases, it's good practice to anticipate where possible the different ways users will experience your page.

{dropnote:"{image:2301288-50%}"} {/hide}

Actually, since we do this trick more than once, it's a technique.

Anyway, there's another WritingML bit that solves the problem. Its the insert tag. The context is

where ####### is the number of a static item. This only works with static items and webpages on Writing.Com. It does not work with other item types.

We've repeatedly used the insert tag on this page. We've used it precisely six times, to be exact. Each of the six little articles under the major headings are stored in separate static items. The main page has no content. It just has inserts to the desired static item. For example, this page is "Navigation Content" , inserted right after the {dropnote} tag and right before the corresponding {/dropnote}..

This is a good idea to use whenever you have a collection of articles. For this page, we've created a "design" folder in our portfolio, and put a separate "content" folder inside of it. All of the little articles are stored there as static items. The main page, the one your looking at, has no content. It just has the dropnotes for the images and insert commands. Here's what the main page looks like:
                                                           

                                                           

There are no nested dropnotes because the system processes the insert file, including the dropnotes, before it places the content. The main page doesn't "know" about the dropnotes in the content pages. Magic, no?

Note that we have centered the menu items by surrounding them all with a {center} and {/center} tag. This means that all of the intervening text will be centered, even the text in the inserted files. To avoid this, we have surrounded each {insert:########} tag with {left} and {/left} tags. This aligns the inserted content for each menu item on the left.

It's also good practice any time a site contains several long articles to split things up like this, using insert tags to place your static items inside the main container page.

That's a good question. After all, the resulting page is on a website, Writing.Com, which already has a full set of navigational tools. The problem is that theese don't point to your pages.

You have at least two ways to point people to your items. One is a text link, like {item:2301281}, which gives the link: "Ideas on Page Design" .

Another way is that you can set up your an image so that when someone clicks on it, it opens a new page on the iitem you name. For example, this image takes you to our contest when you click on it (but don't click on it here):

Okay, you clicked on it, didn't you? At least you found your way back. Clicking on it opened a new page and left this one open. That's not a good thing for a navigation tool. If we'd used this linking feature of images for menus, users would quickly wind up with dozens of pages open, one for each time they clicked on a menu item. That would be so annoying no one would likely ever come back.

Another way would be to surround images with {x-link} and {/x-link} code like so:

Which gives (don't click on this one etiher):

You clicked again, didn't you? At least this time it opened this page, but, this time it replaced the window we were in. We'd lose our place if we used this technique. (There's a way around this, but it involves doubling the number of buttons *and* doubling the number container files--a real mess to maintain.)

Having menus that look like a "normal" webpage might be nice, but it's not obvious how you would efficiently do it without creating an actual web page hosted by Writing.Com. But if you want to put navigational tools on a normal item on Writing.Com, using dropnotes are the way to go.

The keep it simple rule is usually good here. Using too many colors runs the risk of making your page look noisy.

Web pages often follow the three color rule: 60% primary color, 30% secondary color, and 10% accent color.

However, the background color is going to be your primary color, so if you apply this rule on your Writing.Com pages, you'll only have two colors. That can work, since you can use different tints shades , and tones of these colors for variety, but it's not a bad thing to add a fourth color.

For graphical elements, you might consider a modified three color rule: 60% main color, 30% secondary color, and 10% accent color., where the color choices apply to your graphical elements.

Your color palette is your choice of which basic colors you will use for the main, secondary, and accent colors. The color wheel is a useful tool in making these selections.



Most color wheels show twelve basic colors. This one shows various tints of these colors--the basic color is in the outer ring, and the inner rings mix that color progressively with shades of white, to get different tints. The second graphic shows the names of the twelve basic colors, starting with blue-green in the nine-o'clock position and proceeding counter-clockwise around the wheel. Shades mix the basic colors with black to obtain darker versions. Tones mix both white and black.

The palette for this set of pages is basically monocrhomatic: it uses different shades and tints of blue for the navigational elements. The artbrush background for the buttons is basic blue, the text is a darker shade of the same color, and the glow around the text is a lighter tint.

The text in the header graphic is similar, with the text itself the basic blue color, outlined in the darker shade of blue, and with a slightly darker tint for for the glow. The "brand" for this site is more colorful and not constrained by the palette, for variety.

When choosing your palette, it's important to consider contrast. In the case our choices for this site, we used a glow around the text to help set it off from the background, increasing the contrast. We might have made other choices for the secondary color though, that didn't require a glow. For example, if instead of blue we had chosen red. Then the "Palette" button would have looked like this, and no glow would have been needed:

We even thought about a rainbow text for this button, but decided to stick with the basic monotone scheme.


While we used a monochrome strategy for our palette, there are other possiblities.

Complementary palettes choose two colors from the opposite sides of the color wheel. These can be effective because they create both visual balance and tension, To avoid too much tension, it's best if one is the basic color and the other is one of the accent colors.

Analogous palettes choose colors from adjacent spokes on the color wheel. This makes the colors fit together in appealing ways and can result in beautiful designs. Attention to contrast via shade, tint, and tone can be important with these.

A triad palette choses three equally-spaced colors from the wheel. This should be used with caution, though, as it runs the risk of making your page look noisy.

This is where you can find graduate-level textbooks and is beyond the scope of this little set of ideas. Instead, we're going to list some common cultural associations with color from Stephaie Corrigan.  

Red: passion, power, love, danger, excitement
Blue: calm, trust, competence, peace, logic, reliability
Green: health, nature, abundance, prosperity
Yellow: happiness, optimism, creativity, friendliness
Orange: fun, freedom, warmth, comfort, playfulness
Purple: luxury, mystery, sophistication, loyalty, creativity
Pink: nurturing, gentleness, sincerity, warmth
Brown: nature, security, protection, support

 

Creative Commons CC-BY-NC License  

The buttons are sized at 400x60 px. Buttons are displayed here at half-size. There are similar sets, sized at 400x300 px, suitable for banners.

These are BLANK buttons--no text in them.

You will need third party software to add your text to these files.

There are at least two online services that do this for free.
        https://onlinepngtools.com/add-text-to-png
        https://products.aspose.app/drawing/en/text-on-image/png
The first of these is reliable and free, but the free version limits you to five uses a day. The second is free and unlimited, but I've had inconsistent results with it. The second is easier (when it works), and the first is more fully-featured.

You can also use Paint (installed on all Windows systems) to add labels, but I've found the above websites easier to use. With Paint, it's hard to place your text where you want it, and once you click on the frame, you can't change the text OR its position--you can only delete the text and start over. In our case, that's usually preceded by shouting our compliments about the helpful design of the program.

Of course, if you have access to Photoshop or Corel Draw, that's the way to go, but in that case you don't need these images.

The buttons are larger than you will probably want to use, but are sized so it's easier to insert text. Font size should be roughly half the height of the button. Once you've put your text on the button, you can use {image:####-NN%} in your document to scale them. Recommended scaling is 50%.

Here are a few pages we've designed using the techniques and ideas discussed here.

FORUM

Tales Shown, Not Told Discussion Forum  (18+) A short story contest with a focus on showing, not telling. #2295490 by Max Griffin 🏳️‍🌈

FORUM

Crosstimbers Review Forum  (18+) Free, honest, and in-depth reviews. #1848419 by Max Griffin 🏳️‍🌈

FORUM

23 Skidoo Contest  (E) 23 Skidoo Contest #2302607 by Max Griffin 🏳️‍🌈

we've created a sample template file for contests using some of the techniques in "Ideas on Page Design" . This sample template is fully customizable, and is complete with a set of buttons based on a short scan of those used in existing contests. The template is just a container file into which you can insert your own contest logo and information.

I've created a second set of more artistic-looking buttons with a brushstroke background and font, so there are now two versions of this. Here's what they look like:

STATIC

Contest Template Container  (E) Contest Template Container #2301609 by Max Griffin 🏳️‍🌈

STATIC

Generic Contest Container--Brush Theme  (E) Generic Contest Container--uses brushstroke background and font #2301639 by Max Griffin 🏳️‍🌈

These templates are based on the one used in

FORUM

Tales Shown, Not Told Discussion Forum  (18+) A short story contest with a focus on showing, not telling. #2295490 by Max Griffin 🏳️‍🌈

The template uses dropnotes as a navigational device. While you could just type your text for each button between the {dropnote} and {/dropnote} tags for that button, I recommned instead that you place that information in a static item. You can then use an {insert:#######} tag to insert the text into the template. This makes it easier to edit (and debug) the WritingML.

Note that {insert:#######} only works with static items and web pages. Also, the inserted text does not appear to "preserve spacing" no matter how you've set that option in your static items. Finally, while nested dropnotes are generally not permitted, if you use {insert:#######} with this template, the inserted static item may have dropnotes even though it is called from within a dropnote.

Feel free to use or modify this template as you see fit. If you use or modify it, please retain the copyright notice in the code below.

The code for each of these templates follows. To use it, copy it to your own file.

{hide}
############## CODING NOTES 8/6/2023 ##############
This file must be customized for your contest.
Where it says ### <CONTENT> goes on the next line ### you have two options.
use an {insert:#########} to insert the number of a static item that has the content
OR type the content directly into this file, starting on the "next line" as indicated.
We strongly recommend that you place your content in separate static items and use the first method.
The countdown information at the end must also be customized or can just be hidden if you don't want to use it.
Additional buttons are available:
{image:2301606-50%} RULES
{image:2301604-50%} PROMPT (singular)
{image:2301709-50%} RESOURCES
{image:2301598-50%} BENEFICIARIES
Buttons are scaled at 50% to fit three across the page. Buttons scaled to 80% fit two to a line.
If you want to use differently sized buttons, you will need to change both the scaling and the arrangement of the buttons.
These buttons are CENTERED. The text underneath each button will also be CENTERED unless you surround it with
{left} TEXT HERE {/left}
############## END CODING NOTES ##############
{/hide}
{center}{image:2301610} {hide} ### PUT YOUR HEADER HERE ### {/hide}{/center}

{c:green}{i}{b}{size:4}Place a short introduction to your contest here.{/size}{/b}{/i}{/c}
{center}
{dropnote:"{image:2301607-50%}"} {hide} ### The Basics go on the next line ### {/hide}
{left} BASICS TEXT HERE {/left}
{/dropnote}{dropnote:"{image:2301605-50%}"} {hide} ### Prompts go on the next line ### {/hide}
{left} PROMPTS TEXT HERE {/left}
{/dropnote}{dropnote:"{image:2301600-50%}"} {hide} ### Guidelines go on the next line ### {/hide}
{left} GUIDELINES TEXT HERE {/left}
{/dropnote}

{dropnote:"{image:2301603-50%}"} {hide} ### Prizes go on the next line ### {/hide}
{left} PRIZES TEXT HERE {/left}
{/dropnote}{dropnote:"{image:2301601-50%}"} {hide} ### How to Enter goes on the next line ### {/hide}
{left} HOW TO ENTER TEXT HERE {/left}
{/dropnote}{dropnote:"{image:2301608-50%}"} {hide} ### What to Enter goes on the next line ### {/hide}
{left} WHAT TO ENTER TEXT HERE {/left}
{/dropnote}

{dropnote:"{image:2301602-50%}"} {hide} ### Past Winners### {/hide}
{left} PAST WINNERS TEXT HERE {/left}
{/dropnote}{dropnote:"{image:2301599-50%}"} {hide} ### Donors ### {/hide}
{left} DONORS TEXT HERE {/left}
{/dropnote}{dropnote:"{image:2301597-50%}"} {hide} ### Judging ### {/hide}
{left} JUDGING TEXT HERE {/left}
{/dropnote}
{/center}
{hide}
############## COUNTDOWN NOTES ##############
CONTEST COUNTDOWN
CUSTOMIZE WITH INFORMATION APPROPRIATE FOR YOUR CONTEST.
AS WRITTEN THE COUNTDOWN DOES THE FOLLOWING
places a limit of TEN in entries
Gives a closing date of August 7, 2023
Specifies a countdown ending date of 8/7/2022 0800, i.e, 8AM WDC time, August 7, 2023
Note that the date appears TWICE, once in the text and a second time in the countdown function.
Currently shows seven entries, three open slots, both in text and in symbols
############## END COUNTDOWN NOTES ##############
{/hide}
{center}
{center}{b}{u}{s:30}{/u}{/b}{/center} {hide} ### draws a line 30 spaces long ### {/hide}
Contest open for entries until we receive ten stories or {b}8:00AM August 7, 2023{/b}, whichever happens first.
Assuming we don't close early, the contest closes in {b}{c:red}{code:countdown('8/7/2023 0800')}{/c}{/b}
{b}Seven {/b}entries so far. {b}Three {/b} positions available.
{e:X}{e:x}{e:x}{e:x}{e:x}{e:x}{e:x}{e:notepady}{e:notepady}{e:notepady}
{center}{b}{u}{s:30}{/u}{/b}{/center}
Questions or comments about the contest?
please contact {hide} ### Your name here ### {/hide}
{/center}
{center}{b}{u}{s:30}{/u}{/b}{/center}

NOTE: the Standard Generic Contest has centered menu items and inserts additional code to align the corresponding text to the left. The Brushstroke Generic Contest does NOT have centered buttons and so needs no additional alignment code. If you want centered buttons, change this code accordingly, using the Generic Contest as a guide.

{hide}
############## CODING NOTES 8/4/2024 ##############
This file must be customized for your contest.
Where it says ### <CONTENT> goes on the next line ### you have two options.
use an {insert:#########} to insert the number of a static item that has the content
OR type the content directly into this file, starting on the "next line" as indicated.
We strongly recommend that you place your content in separate static items and use the first method.
The countdown information at the end must also be customized or can just be hidden if you don't want to use it.
Additional buttons are available:
{image:2301606-50%} RULES
{image:2301604-50%} PROMPT (singular)
Buttons are scaled at 80% to fit two across the page.
If you want to use the differently sized buttons you will need to change both the scaling and the arrangement of the buttons.
############## END CODING NOTES ##############
{/hide}
{center}{image:2301610} {hide} ### PUT YOUR HEADER HERE ### {/hide}{/center}

{c:indigo}{i}{b}{size:4}Place a short introduction to your contest here.{/size}{/b}{/i}{/c}

{dropnote:"{image:2301637-80%}"} {hide} ### The Basics go on the next line ### {/hide}

{/dropnote}{dropnote:"{image:2301626-80%}"} {hide} ### Guidelines go on the next line ### {/hide}

{/dropnote}
{dropnote:"{image:2301635-80%}"} {hide} ### Prompts go on the next line ### {/hide}

{/dropnote}{dropnote:"{image:2301628-80%}"} {hide} ### Beneficiareis go on the next line ### {/hide}

{/dropnote}{dropnote:"{image:2301638-80%}"} {hide} ### What to Enter goes on the next line ### {/hide}
{/dropnote}{dropnote:"{image:2301629-80%}"} {hide} ### How to Enter goes on the next line ### {/hide}

{/dropnote}
{dropnote:"{image:2301633-80%}"} {hide} ### Prizes go on the next line ### {/hide}

{/dropnote}{dropnote:"{image:2301632-80%}"} {hide} ### Past Winners### {/hide}

{/dropnote}
{dropnote:"{image:2301706-80%}"} {hide} ### Donors ### {/hide}

{/dropnote}{dropnote:"{image:2301631-80%}"} {hide} ### Resources ### {/hide}

{/dropnote}


{hide}
############## COUNTDOWN NOTES ##############
CONTEST COUNTDOWN
CUSTOMIZE WITH INFORMATION APPROPRIATE FOR YOUR CONTEST.
AS WRITTEN THE COUNTDOWN DOES THE FOLLOWING
places a limit of TEN in entries
Gives a closing date of August 7, 2023
Specifies a countdown ending date of 8/7/2022 0800, i.e, 8AM WDC time, August 7, 2023
Note that the date appears TWICE, once in the text and a second time in the countdown function.
Currently shows seven entries, three open slots, both in text and in symbols
############## END COUNTDOWN NOTES ##############
{/hide}
{center}
{center}{b}{u}{s:30}{/u}{/b}{/center} {hide} ### draws a line 30 spaces long ### {/hide}
Contest open for entries until we receive ten stories or {b}8:00AM August 7, 2023{/b}, whichever happens first.
Assuming we don't close early, the contest closes in {b}{c:red}{code:countdown('8/7/2023 0800')}{/c}{/b}
{b}Seven {/b}entries so far. {b}Three {/b} positions available.
{e:X}{e:x}{e:x}{e:x}{e:x}{e:x}{e:x}{e:notepady}{e:notepady}{e:notepady}
{center}{b}{u}{s:30}{/u}{/b}{/center}
Questions or comments about the contest?
please contact {hide} ### Your name here ### {/hide}
{/center}
{center}{b}{u}{s:30}{/u}{/b}{/center}

WritingML is what is called a markup language. This means you enter snippets of code into your text which, when displayed, results in a formatted text. This is different from a WYSIWYG (what you see is what you get) editor like Word. The downside is that Word is better described as what you see is all you get. Word has lots of features, but you're pretty much stuck with what the wizards at Microsoft think you need.

Anyway, WritingML is a markup language, and you're probably familiar with using markup to format your documents. Even if you're not, you can rearrange the buttons in these template files. Below I've outlined hyper-detailed steps on how to do this. Please don't be offended by the detail, and please be aware that there are some reasons for it. In particular, dropnotes add an order of complexity to your markup. The more complex your markup, the nastier it is to find and correct mistakes. One reason for the detail is that we've had some experience with the ways things can go amiss when you want to rearrange the buttons. Based on this experience, we've suggested some extra steps, like first arranging the buttons so the appear in one column.

Anyway, with that prelude, there is one important step you need to do BEFORE attempting to rearrange the buttons.

Make a BACKUP of the file, so if something goes wrong you can recover. To make a backup, display the page you want to edit, and open it with the full screen editor. Select the contents, press <CONTROL> C to make a copy of the contents in your paste buffer. Now open a new, blank document with your word processor or notepad. In the new document, press <CONTROL> V, which will copy the contents of your paste buffer into this new file. If something goes wrong in editing your contest, you can simply reverse this process to replace the contents of your contest file with the contents from this backup.

You've got your backup done, right? No? Then do it now, before you read any further. It's inevitable something will go wrong and you'll be sorry you don't have a backup.

Ok, we'll trust that you've really and truly backed up your file, so here is how to rearrange the buttons.

Step 1. Write down the order in which you want the buttons to appear.
Step 2. Open your file with the full screen editor and look for all the places where you see {/dropnote}{dropnote:} together, one one line, with no linefeed or or space between them.
Step 3. Insert a linefeed (carriage return) between the {/dropnote} and the {dropnote:}

Step 4. The code for the buttons is now arranged in groups of three, with each group representing one button. This makes them easier to rearrange in your desired order.

STEP 5. Repeat this process until the groups-of-three are in the order you want.
STEP 6. Save the file and view it. You should see the buttons in the desired order in one long column.
Step 7. If the file displays the buttons correctly and in the proper order, you're ready to put groups of buttons a single line.

Step 8. If you're extra careful, save and display the file to be sure this step worked.
Step 9. Repeat steps 7 and 8 until the buttons are grouped and in the order you desire.