Planning A Theme Wedding(repost)

1. This will be a how to book/manual on how to plan for a theme wedding. A theme wedding is one that has a specific, but unconventional theme such as western/country, Star Wars, Renaissance, etc. In a theme wedding, the wedding party usually wears costumes instead of the tuxedos and poofy dresses. 2. The eBook should be written in a warm, friendly style but still provide simple, step-by-step instructions. 3. The primary target audience is/are unmarried women who want to have a different and unconventional wedding. 4. The secondary target audience would be unmarried men who are going to be a groom for #3. 5. This book must include a few examples of themes (3 minimum) that other people either have used or have considered for their wedding. We prefer about 5 examples. One example must be a Western (i.e., Old American West about 100 to 130 years ago) theme. We prefer that another two theme examples would be Renaissance and Star Wars. 6. The typical wedding planning tools (e.g., schedules, list of types of people and professionals to contact, etc.). In addition, the planning schedule and list should include contacting a costume shop or other business that could supply and tailor costumes and supply the necessary props and decorations. 7. We can and will provide some material for this project, such as a description and details of our own Old West Theme wedding which would include the script (MS Word file) of the skit (bad guy objects to the weddin', several costumed people have words, US marshal groom shoots bad guy) during the ceremony, costume details, costume shop examples, list of props, digital photographs of our wedding, and any other relevant information. ## Deliverables 1) Document (eBook) written in English (AMERICAN/USA dialect) and be free of spelling errors and obvious (non-controversial) grammatical errors. We will allow some limited deviation from standard rules of grammar provided there is a good reason for doing so and the document still appears to be written by an educated person who knows how to write. 2) Complete eBook should be somewhere between 30 and 60 pages long including the table of contents, preface, introduction. and/or sources/resources pages with one inch margins. The optimum length of the eBook will probably be between 40 to 50 pages. This is a guideline, not a rule. 3) We prefer a common font such as Arial or Times New Roman with a size of 10 to 14 points. The size should be large enough to make it easy to read on a PC monitor and on paper, but not so large that it is annoying. Line spacing must make the text easy to read, which means either double spacing or 1/2 line space between lines of text. We will glady consider a professional writer's recommendations for both font size and line spacing. 4) We estimate that the total number of words would be between 5,000 and 7,500 words depending on the font size, margin size, prefered page length and considering that some pages will be mostly graphics, photographs, charts, tables, diagrams, or other material with few words. 5) We prefer that you write this eBook in active voice and avoid passive voice except where appropriate and necessary. 6) Graphics (pictures for examples) and hyperlinks must be an integral part of the document and be included as speparate files in one of the following formats: jpg, bmp, or gif. 7) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): PDF format file and a 2nd file in either MS Word or Rich Text Format (RTF). 8) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Windows PC (both file formats) and Apple Mac (PDF only). This is only a document and the file formats are listed in the Deliverables section.