Research has proven effective, need help deciding on something.

yea, but should it be so narrow as "html"? or should I have volume 1 - markup languages, volume 2 - scripting languages, volume 3 - cascading style sheets, volume 4 - hypertext preprocessor, volume 5 - rapid application development, etc. OR do you think html will be a sufficient size in itself? I don't want to write a book in this particular series that's less than 50 pages for example. I want them to be individually between 80 and 200 pages. Do you think html can fill at a minimum 80 pages itself?

yes i do, if you give some examples on your pages, make a section for the reader to try some scripts out, that way as well as reading about and learnign about them, they will also be able to practice...

yea. I think I might provide a website address in the book for users to go to. The website will be one page and it will have an html editor for them to try things out. By them clicking submit after trying their own combination of codes and tags it'll show them what the code will do and look like. Although, I'm not yet sure how to create an html editor for users of a website to submit and see what it'll do. I'm sure this is possible, just not sure how yet.

William...

I'm sure you've probably seen books (the entire book is black & white) except for a couple pages in the middle usually with pictures and illustrations are colored pages. Is it possible to do this with lulu so that you don't have the manufacturing costs of the entire book being color?

I think u can download html editors, try google for that, im not sure but anything is possible on the net..I sent you an email from your site.

what if I make volume 1 an introduction book introducing the different types of languages and a brief rundown. This will let people decide exactly what kind of language they really want to learn guiding them to the appropriate book. The introduction book can be less than 80 pages if necessary. Although from what I'm reading, I might have to make 1,000 volumes 10,000 pages long each LOL. I went to a "list of markup languages" in wikipedia, then typed the xml (one language) and it pulled up a list of about 200 sub languages.

like a reference book? good idea, that way they can get the info they really want, some readers might be familiar with some aspects of coding but not all, good idea.

Above I said 50% off any book the first three months its released but... if you prove to be invaluable to the creation of the book (help with research, etc.) I'll list you in the book as an aknowledgement and give you one for the price it costs to manufacture and ship (meaning I'm not losing money, but I'm not making money either) and it'll be cheap.

I'll also be selling the book as a download. ANY Yola user can get one for 90% off within the first three months of its release. Expect this to be around December to March. Since I'm making volumes instead of one big book, it'll take me less time to release my first book.

lol i was kidding about the 70% u know if u need any help u can count on me mate.. good luck with this exciting venture..

When this book is written, I'll probably know more about html than I'll know what to do with! LOL!

There's four main purposes for making this kind of book

• To teach others about computer languages
  
• To learn about computer languages myself
  
• To make money - hopefully it'll successfully sell
  
• And the ultimate goal - to Attempt to become a Best Seller
  

The question though. The most important question.

Most books do not source where their information came from. Research papers do, websites do a lot of the time, stuff like that does, not usually books. How can I transform what I research and learn so it doesn't have to be sourced? Should I "learn" the stuff, then use my own knowledge to write the book or should I just reorganize and reword everything and you won't be able to find where it came from because technically it didn't come from anywhere besides my own knowledge from previous teachings

I'm thinking... after I get my books written on the most popular languages... html, php, css, etc. I'm going to write a book on web design... using the languages taught in previous volumes to create a successful website and provide them with as many resources as possible for creating different websites. Although, I believe you need permission to list companies like Yola, sitelevel, etc. in a book.

u should make the book a dummies guide, that way people like me can learn from step by step instead of trying to figure out your own experience,I just asked a few moments ago about putting images together, smithy kindly gave me a code, it didnt work, he also never explained WERE I link the images from? I was lucky I was able to work it out myself, but there are people who would be stumped with that, just getting a code and not explaining it in detial, so your book should be so easy to use a kid would be able to use html., now can u maybe help re my images??

William...

is your gray*****98@hotmal.com the current email?

no, the one I sent you from your WEBPAGE....

If I decide to write an introduction book I need a title...

"The many different markup languages" and a sub-title (it'll show on the cover and title page)
"An introduction to languages such as html, XML, XHTML, GenCode, and more"

Or do you have better ideas?

And how can I organize the book?

• Table of Contents
  
• Introduction (to the book and what's included in the book not to each individual language)
  
• Preface (this is written by another person usually a good friend or someone partial into the topic) - if you write this, your name AND website will be listed at the end of the preface - if you want to write it for me, look at other books that include a preface and get some ideas or search preface (how to write a preface) on google.
  
• Different Types of Markup Languages with introduction paragraph
  
• Introduction to each markup language (part of the chapter different types of markup languages)
  

Should I make the book in a text book format with margins, definitions, questions, worksheets, etc.?

I would keep the introductory book simple mate, no point in getting potential readers stuck at this point, the way u described above is perfect and I would be happy to write your preface donald lol I am not the type of person who needs to get something in return id be happy to do it for u. I would design the book with margins and definitions but make it easy for the reader to look things up at ease, so many books these days are so difficult to understand it still elaves the reader clueless, be careful not to use too much jargon, use everyday language people like me can understand..

I don't know that I received your email. Maybe it was lost lol.

I checked
Webmaster@youcanneverbetoosmart.com
webmaster@youcanneverbetoosmart.info
youcanneverbetoosmart@rocketmail.com
youcanneverbetoosmart@yahoo.com
Wufoo Contact Us Form
Form Assembly Newsletter Form

None of them has your email.

From now on, can you use only one email so I don't get tangled lol...

webmaster@youcanneverbetoosmart.com - that's my most frequently checked ones, the others have a lot of junk mail.

If I make an 84 page book (the minimum page count using the cheapest paper) the book will cost $5.01 to manufacture.

If I make a smaller book at 32 pages (the minimum page count using the better paper) the book will cost $6.30 to manufacture.

It's more money for less than half the size of the book to use the better paper. This is a problem.

If I use the cheaper paper, then my book has to be 84 pages.
If I use the better paper, then my book will be more expensive than I want it to be. Nowadays, people just want to save money!

true, but if u sell it then u wont be worrying about the costs of manufacture, my advice, go for the BETTER paper, its quality.. I know u need to go thrifty but if the book sells and I am sure it will, then best going for the better paper option, I sent the email through the webmaster add, send me an email to hotmail, then I will reply to it and give u my proper email ad, right now going for dinner, see u later mate..

yea, but 32 pages is $6.30 - is this worth it? I mean, I guess quality is the most important. And that is still cheap. If I sell it for $12.60 (double the manufacture cost).. then my share is...

12.60
- 6.30
$6.30 profits (lulu I believe gets 20% of this)

$1.26 Lulu
$5.04 Me per book

Is this a good price or should I make it more?

The thing is... with quality comes higher prices. Will the buyers know it's better quality before they buy it? I think the cheaper a book is, the more sales it will get!?

Hi Donald,

You could maybe categorize then into would type of scripting they are. For example, HTML and Javascript would be client side scripting while php and asp are server side scripting, and so on.

Volume 1: Client Side Scripting
Volume 2: Server Side Scripting

You said one of the purposes of the book was, 'learn about computer languages myself...'. I would of thought you would need to know alot (experience and stuff) about what you are writing about, to write a book on it.

Just my thoughts,
Connor

that's a good suggestion... but I think it might be too broad. Go find a list of client side scripting and server side scripting. You'll probably find 500 different languages for each. And as for writing a book... 90% of books out there involve A LOT of research (stuff the author didn't know before he/she wrote the book). I know enough to provide the basis for research. Also, I have actually learned an extremely a lot about html to know if something doesn't sound right, at which point I can double check with multiple sources and say, ok, this needs to be changed or ten people say that this is right.

But your idea might be good, but I think I should make a "SERIES - then a volume set" - the SERIES could be client side scripting and server side scripting and each SERIES will have a volume such as language types (css, javascript, markup, etc.) OR volumes could be narrower than that (html, xml, etc.)

Want to see an excerpt of the book? Remember... it's only a rough draft...

http://sitebuilder.yola.com/sites/D7d...

I could do more with color, but then the book will have to be like 4 times the price (I know... crazy right?)

When publishing, gray is considered black and white, isn't it?

and an update...

An Excerpt from my book

donald thats the idea I was thinking of, its clean and easy to read, I know its a draft but its good, well done... the second link above this doesnt work..

that's weird cause when I first posted it and tested it, it worked, now it doesn't. But it confuses me that if its the wrong link how does connor know the right one? Anyways, the one connor posted works.

When I started making the page and I made a second page with margins, I accidentally made the mistake of making the second page with margins on the same side. And if you know a book, they go on different sides. The left page usually has margins on the left (outside of book) and the right page has margins on the right (also the outside of the book)... and this isn't an easy fix. I had to copy the left side of the page and post it in a one column page, copy the right side of the page and post it before the left side in the one column page, add columns and do all my borders all over again.

ok, check that link again, I replaced the screen shot... I've added a light gray background to the margin area. Tell me what you think. Gray does print in black and white copies right?

I think you get to select color or black and white don't you? All gray is is a mixture of black and white. I don't think gray is included as a color because when you have a printer with no color ink, it will still print the gray as is.

William...

I'm finding that this "introduction" book is going to have to include more information than I originally thought. So I had an idea...

I want each topic "HTML", "XML", etc. to only be one page long - since it is only an "introduction". So... I am thinking about putting the most important information in the body of the book and having each topic no more than one page - then include an appendix at the end to include more detailed information. However, it won't be so detailed as to take away from my other volumes. I won't include in this book specific information as to "how to" write an html code and design websites with them and stuff. Basically, only general information will go into this book. XML is particularly a large topic itself.

What do you think of the idea to add other information in as an appendix at the end of the book?

Its a brilliant idea mate, u do need to keep it compact but teasing enough to want the reader to buy the full volumes, and to learn to write the codes good one..

yea. When I write the volumes in full detail. It'll include the same information in this book under the introduction section, and then it'll have sections such as "World Wide Web Consortium (W3C) and HTML", "HTML releases and updates" "tags used in HTML" - describing all the tags and what they do. "Putting tags to use in HTML", "designing a webpage using HTML", etc. - as examples.

I'll also try to come up with lists and descriptions such as...

developers of HTML
products of HTML
web creators using HTML
programs using HTML

XML is going to be one long book... they have hundreds of XML-based languages which will need to be included.

now thats a GREAT idea, updates, very clever, and they will have to come to your website for them? very clever, donald answer my question I posted please, no one else is...ta