How to post stories on BC...

Printer-friendly version

This is a frequently asked question and I thought I would put this up and let everyone who wants to take a crack at answering it.

Hugs,
Erin

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Loaded question!!!

I'm sure we all have our own way "that works"...

Me - the whole thing is a PROCESS. LOL

Me, I write my story using MS Word. I tend to archive work in process copies on googledocs. I've been known to share these (read only) to my editors though not all read them in this state.

Once I get a draft to the point I like it, I send it (serially - one at a time) to my editors (depends on what it is - who / how many editors). I send out the MS Word version, with "track changes" turned on.

When I get it back, I review the ENTIRE document - not just the areas where they made suggestions and/or asked comments. In some cases, I send feedback to the editor - explaining things... Some times those explanations end up in the story, sometimes not. Sometimes I send it off to the editor a 2nd time. I've been known to start over with reviewers too - when a later reviewer's comment/suggestion caused a significant change to the story.

Once I've got the STORY how I want it - formatted in MS word...

I open a Notepad ++ window (typically copied from an older post - but not always). I hand code the html to make the browsed page look like I want it to (mostly like the MS Word doc, but not always. I also decide on the "tease" section here.

Once that's all done, I finally come to BCTS and click that "Create Content" link.

I fill in the title, find my name in the list of authors (Note, the first time one posts, one needs to get set up as an Author by Erin/her team.) I set categories that represent the story and I copy/paste the hand crafted HTML into the box provided.

Hitting that Preview button - most of the time - shows me I did all the formatting correctly. But at least 1/3 of the time I have to go and fix things..

TO fix things - I fix my Notepad++ copy, and then paste it into BCTS (always that way). {Sorry Site managers - this has caused your changes to my stuff to get lost on more than one occasion... I don't mind tossing out their changes - most of the time - as the story is MINE. [yes - occasionally the managers go in and "fix" wording and the like.] And, by working in this way - I maintain control over my prose.)

I always re-preview before hitting that final post button... And, even then. After that post, I check how things show up in the site. (A missing </em> at the end may not show up in preview, but it does strange things to the site! Worse are failures to include a </table>, etc.)

The second to last step, assuming the post is part of a larger story is I add it to the cover page (outline).

The final step, for me is continuous... I check for comments. Okay. I like them.

Hope this is what you were looking for.
Anne

Erin's picture

Nice System

You can save a couple of menus by picking ++Fiction from the top of the page instead of going to Create Content. :)

Hugs,
Erin

= Give everyone the benefit of the doubt because certainty is a fragile thing that can be shattered by one overlooked fact.

= Give everyone the benefit of the doubt because certainty is a fragile thing that can be shattered by one overlooked fact.

Posting stories on BCTS

I am perhaps the most ignorant Author when it comes to posting stories, but I seem to have developed a simple work-around that may seem disingenuous to many but it does seem to work.

I write in MS Word 2010 for now because it is what I have and I like some of the features. Some people I know use some really complicated features on it and other word processors and I applaud them but for me I need KISS.

So, when I start a story, I don't bother with any extra formating other than I turn on the paragraph markers and make sure that there is one of those little "P" thingies between each paragraph, line of dialogue and any other place in the text where a space would make things clearer. To separate time periods, I simply use a line of "tilde" (~) characters, nothing too complicated.

So after I cut and paste it from my word document to the input place on BCTS, then I go back and center the title, my name and a few other things. It all seems to work out jolly good.

~~~~~~~~~~~~~~~~~~~~~~

As far as the particulars about BCTS, it does seem rather straight forward, and I like it, but it did take me quite a lot of time to finally feel comfortable because I generally find computers to be a bit frightening and inscrutable at times.

But for the new, and the few like me, here is my understanding of the process:

I go to "Create content", "fiction", and then wend my way through all the menu selections. Most of my stories are either "General Audience" or "Mature" as I don't seem to write explicit stories any more, if ever.

The word count, I get from the little counter in Word that tells me.

Then, once I have made my way through, all that, I press the Preview and then Submit buttons, and magically it all appears there on the screen before my wide eyes.

There is a little menu along the top of the box where my precious text is displayed, so I go there and make the title and things bold, and center them, and then press Submit I think.

I know that my method is inglorious and simple but I like it.

Much peace

Gwendolyn

Erin's picture

Drawing lines

If you use repeated characters to draw lines, don't use more than twelve or so, you will mess up the formatting on some mobile phones if you do.

You can also use the <hr> tag:


It's the mini-editor button that looks like two hyphens.

Hugs,
Erin

= Give everyone the benefit of the doubt because certainty is a fragile thing that can be shattered by one overlooked fact.

= Give everyone the benefit of the doubt because certainty is a fragile thing that can be shattered by one overlooked fact.

The HR Tag

And be aware when using the HR tag that those readers who copy and save stories for later reading (as many BC readers do) will find that the decorative lines drawn by HR tags are invisible when copied from most browser displays*, so if they're used to create scene breaks or for other semantic purposes, the ‘break’ will disappear.

Scene One


Scene Two
-o~O~o-
Scene Three


Scene Four

When copied and pasted, the above ‘divisions’ will look like this:

Scene One
Scene Two
-o~O~o-
Scene Three
Scene Four

The HR tag is not really a semantic element, although it's easy to start arguments by taking one position or another, but it's interesting in that -- unlike images -- HR tags don't allow an ALT="Description" tag to handle situations in which the underlying ‘picture’ is not displayed, as they are not when using copy and paste, or when the text is being read aloud by non-specialist browsers.

Cheers,

Puddin'

A tender heart is an asset to an editor: it helps us be ruthless in a tactful way.
--- The Chicago Manual of Style

* Notable exceptions are JAWS and other special-purpose browsers designed for the visually-disabled.

-

Cheers,

Puddin'

A tender heart is an asset to an editor: it helps us be ruthless in a tactful way.
--- The Chicago Manual of Style

Thank you, I will do that.

Sorry, I did not know that I would mess things up. I will do as you ask.

G

Andrea Lena DiMaggio's picture

I think I can answer this...

...after some of my stories have been around for a while on a less-attended website that shall remain unnamed, I gather them up and place them carefully in a raised bed covered in rich soil and surrounded by a pen of pressure-treated wood. After a while, I gather them back up along with the soil and the detritus of my poems and songs and strew them amid my tomato and zucchini plants as fertilizer. That's how I compost stories on BC, right?

<
Dio vi benedica tutti
Con grande amore e di affetto
Andrea Lena
Crying is all right in its own way while it lasts. But you have to stop sooner or later,
and then you still have to decide what to do. ― C.S. Lewis
Love, Andrea Lena

ROFL

OMG lol thats perfect well done.

I like kiss

Keep It Simple Stupid = kiss a really good phrase.

I write on whatever is handy. Notepad, word, text editor (its a palm program)Even paper though my penmanship totally sucks. No joke even my printing is hard for people to read.

Look through it once fix stuff I know is wrong, such as captial i some grammer and punctuation.

Then I click on Add a story here and work on it some more. Not always though since I may be falling asleep. Ill "save" it on the sight. I get feedback on what is wrong or how. Sometimes I can't understand what they heck they mean.

I even have a very old working typewriter from the 1950's. Ribbon is getting a little worn.

My stories right now are early ones I make plenty of mistakes in them but learn a bit here and there.

It does shock me at how much work people put into their stories.

I am using my gaming system at moment to do everything. Hence I will NOT load microsloft office onto it thank you very much, I have another comp that needs cleaning for that.

mittfh's picture

How mine were done...

For the short works, I generally compose them in Notepad (it the idea hits at work - usually during a particularly quiet helpdesk session) or GEdit (if I'm at home), save them as text files then copy / paste into the edit window.

The header I copy / paste into the file from a previous story then tweak to suit.

For my Retcons, I used a word processor (Google Docs) because I wanted to use different text colours and occasionally alignments - not to mention the header box. I naively thought I could export to HTML, remove the surplus bits then paste.

May I suggest: Don't Try This At Home.

I haven't yet found a word processor that generates nice, decent, clean HTML. They all have their faults, but one shared amongst pretty much all I've encountered (including Google Docs) is that they like to preserve the exact layout you've used, and respecify the layout for every single paragraph rather than setting a default style at the beginning. So export to HTML, open up in a text editor, find / replace with blanks all the redundant styles, replace any style declarations at the top with inline styles, then run through Tidy. Rinse and repeat until you've finally got a workable HTML doc. Top and tail it, save, paste into the edit box, preview, scan through and do any last minute fixup, then post.

Having said that, after I'd done the first one, I didn't create a header table then in the main document used a dummy separator, so when I got to the fixup stage, I could just insert / tweak the final version of the one used for the first one.

As I said, Don't Try This At Home (unless you enjoy the challenge!)

 

Find me on Google+ | Examine EAFOAB Resources

There are 10 kinds of people in the world - those who understand binary and those who don't...
Find me on Google+ | Examine EAFOAB Resources

There are 10 kinds of people in the world - those who understand binary and those who don't...

I generally write in the

I generally write in the built-in editor in my Dana Wireless (AlphaWord). When I synch with the desktop, they wind up as RTF files.

I generally take the RTF files and load them into OpenOffice and save as HTML. Then I open that with TextEdit and remove most of the HTML crap. I also reformat the lines as OO tends to set line lengths weird for HTML. It's mostly the paragraph tags I remove.

I open the story creation window on BC and upload a saved template file to get the titles and stuff right. Then I paste the pseudo-HTML into the right spot.

After a quick preview, to make sure it looks ok, I save it and there we are.

I sometimes create stories on the PC directly in an HTML editor (that's mostly for my site, though).

Brooke brooke at shadowgard dot com
http://www.shadowgard.com/~brooke/
Girls will be boys, and boys will be girls
It's a mixed up, muddled up, shook up world
"Lola", the Kinks

I get

Bonzi >^^< to do it.

Angharad

Angharad

Nick B's picture

Bonzi's work

Clever.

You have a pause at the end of your clause, where Bonzi has claws at the end of his paws

Jessica
I don't just look it, I'm totally off my rocker

Thank you, Erin,

ALISON

But IF I were a writer I would put a stamp on it and put it in the mail box.
Isn't that how you post something?:)

ALISON

How I post

I use a text editor similiar to the Notepad that comes with Windows.
(Notepad itself would do in a pinch.)

To format text, I type the HTML codes. There aren't many needed:

<b>bold</b>
<i>italic</i>

For an extra blank line, I put one these on a line by itself:
&nbsp;
 

And if I want a rule to divide sections:
&nbsp;
<hr>
&nbsp;
 


 

Then I hit Ctrl-A to highlight the whole thing, Ctrl-C to cut and then Ctrl-P to paste it into the form.

Good points,

So far I have entered two stories, and have made mistakes on both. I'll go down the list of my goofs and stuff I learned. A lot has already been said, I'm just putting it in one place.

I use Word 97. It is what I'm comfortable with, it is what I will use. I use copy and past, it works well inputting the body of the text. Any formatting is stripped off . I highlight my entire story (Ctrl-A works better), Ctrl-C, and Ctrl-V.

Before you enter the story, Please have someone edit it and proofread it! This is a rookie mistake, I did it. My second story came out much better with the help, and I learned a bit besides.

Do take the time to write a synopsis. It is worth it. Use the <!--break-> as described in the instructions given before entering the story. The number of reads will go up if you do.

HTML is going to be needed, for formatting, to make the story look clean. A good resource for a reference is:
http://www.w3schools.com/TAGS/ref_symbols.asp

It has much more, and I am going to go through the more common ones now. You will be able to get up and going with these immediately.
<i>itallics</i>   is itallics
<b>bold</b>    is bold

&nbsp; is a non breaking space. The software removes extra spaces, this allows you to force a extra space in a sentance if when you need to.

It also inserts a line if you do this by itself:
&nbsp;

This will insert a break line, something I do occasionally:
<hr align="center" width="90%" />

It looks like this:


 

In my second story I did this, it looked better to me.

-----------------------------------

It was wonderful. We both had fun.

 


 

It was the first of many dates.

-----------------------------------
Here is the code I used.

It was wonderful. We both had fun.

&nbsp;
<hr align="center" width="90%" />
&nbsp;

It was the first of many dates.

-----------------------------------
 

If I sound like a expert I'm not, I'm just fresh from my screw ups. I'll bookmark this for myself for later use.

 
This is important (at least it was to me)!

If your story is a solo, be sure to click the completed box at the bottom of the entry. This is important, your story will be offered on the Random Solos, and will hang later on the Recent Solos list. If you do not do this you are missing out on some really cool features on Big Closet, and cheating yourself of readers.

actually.....

You should NOT use < b > and < i >! They are deprecated, you should instead use < strong > and < em > (the second being short for emphasis, being known as the emphasis tag). Strong makes text on the screen appear bold, but it also gets read properly by readers and things to respond to them appropriately, either by stating that it's strong, or by changing inflection, or whatever. This is an accessibility thing. Emphasis is treated as italics, but also has the added benefit of being properly interpreted by accessibility software.

It's unpredictable at best how accessibility software will respond to the deprecated tags. Some ignore them, some treat < b > as an alias to < strong > and < i > to < em >. Still others treat them entirely differently.

We don't really have this concern for this site as much, perhaps, but if you want to use the same "source" for exporting to things like epub etc, use of deprecated tags can also prove detrimental.

In short, just use < strong > for bold, and < em > for italics.

Abigail Drew.

OK

What is depreciated? I used what I'm used to. Lord knows I'm still learning, must be I'm still breathing.

I just wrote another new author pointing this thread out. Truth, with Word I use it's formatting, but as I mentioned it is stripped out when uploading here.

I use firefox 3, do other browsers treat these HTML tags differently? Thanks for the heads up.

deprecated

Is tech speak for a tag, command, or function that is no longer officially supported and therefore might have unpredictable behavior. Deprecated is not QUITE unsupported, but it's essentially on its last legs, and by the next iteration of the language/program it will be likely to be removed. It's encouraged to avoid its use once something becomes deprecated and to switch to what it officially supported in any new work, that way, by the time the next version rolls around and it's completely removed you don't end up with surprises.

In current times, with digital technology being such a moving target as it is, the "deprecated" meaning has shifted a bit from the official definition and now, it's basically the same as saying unsupported without actually admitting it.

As I mentioned, in this particular case, accessibility software and software to convert to e-reader formats will be the most unpredictable when it comes to interpretation of the bold and italic tags, since they are both "newer" while (almost? not certain of Google's Chrome - I think chrome also comes from webkit, which comes from khtml, which comes from... yeah...) all of today's browsers are built on code bases originally written with the predecessors to HTML (Hypertext Markup Language) in mind, so they've mostly just built new versions of markup code around the existing functions, over, and over, again. And we're now on version 5 of HTML... So yeah, we don't really have to worry how browsers will behave in DISPLAY of bold and italic, but we do have to be concerned about how their accessibility add-ons might react... Or if we want to convert to an e-reader format, or... whatever other newfangled things the kids these days come up with next ;P

Abigail Drew.

The REASON they're....

The REASON they're depreciated (or so I was told) is that the "reading assistant" devices for those who are visually impaired do not treat the <b> and <i> the same way they treat <strong> and <em> markups (The former being ignored and the later impacting the reading).

Annette

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Syndicate content