DOCSLIB.ORG

The Pretext Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Pretext Guide The PreTeXt Guide The PreTeXt Guide Robert A. Beezer University of Puget Sound David Farmer American Institute of Mathematics Alex Jordan Portland Community College Mitchel T. Keller Morningside College September 21, 2021 ©2013–2019 Robert A. Beezer, David Farmer, Alex Jordan, Mitchel T. Keller Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Docu- mentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. Preface Introduction. This part is the place to begin if you are new to PreTeXt. Chapter 1 is the introduction, overview, and philosophy. Then Chapter 2 intends to get you started quickly by authoring a simple example and converting it to HTML and PDF output formats. Author’s Guide. This guide will help you author a PreTeXt document. So it serves as a description of the Pre- TeXt XML vocabulary, along with the mechanics of creating the source and common output formats. Chapter 3 is meant to be a short overview of the majority of PreTeXt’s features, which can be skimmed to get a sense of Pre- TeXt’s capabilities. Or it can be read quickly as you begin authoring and you can return as you need certain fea- tures. The roughly parallel Chapter 4 is much more comprehensive and is the first place to go for details not ad- dressed in the overview. Note that the Author’s Guide is not concerned with publishing your document, which is described in the Publisher’s Guide. Basic Reference. This part provides a quick overview of the minimal syntax for a variety of key PreTeXt features. Unlike the sample article, which is designed to demonstrate and stress test all aspects of PreTeXt, this guide will illustrate only the key elements of some of the most universally-used features of the language. In many cases, in addition to features not discussed, there may be alternative structures that are not given here. Publisher’s Guide. Even if you intend to distribute your document with an open license, and you are both author and publisher, it is still helpful and instructive to understand, and separate, the two different steps and roles. So visit this part of the Guide to learn how you can present, distribute, and maintain what you have authored. Developer’s Guide. This part provides advice, suggestions, and conventions for contributing to PreTeXt. For anything not answered here please use the pretext-dev¹ Google Group. Make a membership request and it will be processed quickly. Appendices. In addition to the usual items you might expect in the back matter, such as an open license, glos- sary, references, and an index, there are numerous more specialized additions, mostly describing the installation of, or effective use of, various technical tools that are independent of PreTeXt (but useful or necessary). ¹https://groups.google.com/forum/#!forum/pretext-dev iv Contents Preface iv I Introduction 1 Starting 2 2 Getting Started Tutorial 6 II Author's Guide 3 Overview of Features 12 4 Topics 23 5 Processing, Tools and Workflow 79 6 PreTeXt Vocabulary Specification 91 7 WeBWorK Exercises 95 8 Authoring Advice 101 9 Author FAQ: Frequently Asked Questions 103 III Basics Reference 10 About This Reference 108 v ☙ Contents ❧ vi 11 Basic Formatting 109 12 Document Structure 110 13 Mathematics 112 14 Lists 114 15 Blocks 116 16 Exercises 122 17 Worksheets 131 18 Renaming Elements 135 19 Figures and Friends 136 20 Tables 142 21 SageMath Content 145 22 Small, But Useful 147 23 Modular Source 150 IV Publisher's Guide 24 (∗) Producing a Book 152 25 Copyright and Licensing 154 26 Conversions, Generally 159 27 Conversion to Online HTML 163 28 Conversion to PDF and Print 169 29 Conversion to EPUB/Kindle 174 ☙ Contents ❧ vii 30 Conversion to Runestone 176 31 Conversion to Slides 178 32 (∗) Conversion to Jupyter Notebooks 180 33 Instructor's Version 181 34 Ancillaries 183 35 WeBWorK Exercises 187 36 Hosting Your Online Version 193 37 LATEX Fonts 195 38 LATEX Styles 200 39 (∗) Cover Design 206 40 Publisher File Reference 207 41 Print-On-Demand 214 42 Publisher FAQ: Frequently Asked Questions 216 V Developer's Guide 43 Processing with xsltproc 219 44 The pretext Script 226 45 Coding Conventions 232 46 Debugging 234 47 Git 236 ☙ Contents ❧ viii Appendices A Welcome to the PreTeXt Community 241 B Best Practices 244 C Python 245 D Text Editors, Spell Check 247 E Schema Tools 261 F Offline MathJax 264 G Revision Control: git 266 H Conversion from LATEX 267 I MacOS Installation Notes 268 J Windows Installation Notes 269 K Windows Subsystem for Linux 276 L Example List of Notation 278 M GNU Free Documentation License 279 Back Matter Glossary 285 References 288 Index 289 Part I Introduction 1 Chapter 1 Starting Welcome to the Author’s Guide for PreTeXt. You are likely eager to get started, but familiarizing yourself with this chapter should save you a lot of time in the long run. We will try to keep it short and at the end of early chapters we will guide you on where to go next. Not everything we say here will make sense on your first reading, so come back after your first few trial runs. When you are ready to seek further help, or ask questions, pleasereadthe Wel- come to the PreTeXt Community in Appendix A. 1.1 Philosophy PreTeXt is a markup language, which means that you explicitly specify the logical parts of your document and not how these parts should be displayed. This is very liberating for an author, since it frees you to concentrate on capturing your ideas to share with others, leaving the construction of the visual presentation to the software. As an example, you might specify the content of the title of a chapter to be Further Experiments, but you will not be concerned if a 36 point sans-serif font in black will be used for this title in the print version of your book, or a CSS class specifying 18 pixel height in blue is used for a title in an online web version of your book. You can just trust that a reasonable choice has been made for displaying a title of a chapter in a way that a reader will recog- nize it as a name for a chapter. (And if all that talk of fonts was unfamiliar, all the more reason to trust the design to software.) You are also freed from the technical details of presenting your ideas in the plethora of new formats available as a consequence of the advances in computers (including tablets and smartphones) and networks (global and wireless). Your output “just works” and the software keeps up with technical advances and the introduction of new formats, while you concentrate on the content of your book (or article, or report, or proposal, or …). If you have never used a markup language, it can be unfamiliar at first. Even if you have used a markup language before (such as HTML or basic LATEX) you will need to make a few adjustments. Most word-processors are WYSI- WYG (“what you see is what you get”). That approach is likely very helpful if you are designing the front page of a newspaper, but not if you are writing about the life-cycle of a salamander. In the old days, programs like troff and its predecessor, RUNOFF (1964), implemented simple markup languages to allow early computers to do limited text-formatting. Sometimes the old ways are the best ways. PreTeXt is what is called an XML application or an XML vocabulary (I prefer the latter). Authoring in XML might seem cumbersome at first, but you will eventually appreciate the long-run economies, so keep an open mind.And if you are already familiar with XML, realize we have been very careful to design this vocabulary with human au- thors foremost in our mind. Principles. The creation, design, development and maintenance of PreTeXt is guided by the following list of prin- ciples. They may not be fully understood on a first reading, but should be useful as you become more familiar with authoring texts with PreTeXt and should amplify some of the previous discussion. 2 1.2 ☙ Formatting Your Source ❧ 3 List 1.1.1 PreTeXt Principles 1. PreTeXt is a markup language that captures the structure of textbooks and research papers. 2. PreTeXt is human-readable and human-writable. 3. PreTeXt documents serve as a single source which can be easily converted to multiple other formats, cur- rent and future. 4. PreTeXt respects the good design practices which have been developed over the past centuries. 5. PreTeXt makes it easy for authors to implement features which are both common and reasonable. 6. PreTeXt supports online documents which make use of the full capabilities of the Web. 7. PreTeXt output is styled by selecting from a list of available templates, relieving the author of the bur- den involved in micromanaging the output format. 8. PreTeXt is free: the software is available at no cost, with an open license. The use of PreTeXt doesnot impose any constraints on documents prepared with the system. 9. PreTeXt is not a closed system: documents can be converted to LATEX and then developed using standard LATEX tools. 10. PreTeXt recognizes that scholarly documents involve the interaction of authors, publishers, scholars, in- structors, students, and readers, with each group having its own needs and goals.
Load more

Recommended publications
  • Open Source License Report on the Product
    OPEN SOURCE LICENSE REPORT ON THE PRODUCT The software included in this product contains copyrighted software that is licensed under the GPLv2, GPLv3, gSOAP Public License, jQuery, PHP License 3.01, FTL, BSD 3-Clause License, Public Domain, MIT License, OpenSSL Combined License, Apache 2.0 License, zlib/libpng License, , . You may obtain the complete corresponding source code from us for a period of three years after our last shipment of this product by sending email to: [email protected] If you want to obtain the complete corresponding source code with a physical medium such as CD-ROM, the cost of physically performing source distribution might be charged. For more details about Open Source Software, refer to eneo website at www.eneo-security.com, the product CD and manuals. GPLv2: u-Boot 2013.07, Linux Kernel 3.10.55, busybox 1.20.2, ethtool 3.10, e2fsprogs 1.41.14, mtd-utils 1.5.2, lzo 2.05, nfs-utils 1.2.7, cryptsetup 1.6.1, udhcpd 0.9.9 GPLv3: pwstrength 2.0.4 gSOAP Public License: gSOAP 2.8.10 jQuery License: JQuery 2.1.1, JQuery UI 1.10.4 PHP: PHP 5.4.4 FTL (FreeType License): freetype 2.4.10 BSD: libtirpc 0.2.3, rpcbind 0.2.0, lighttpd 1.4.32, hdparm 9,45, hostpad 2, wpa_supplicant 2, jsbn 1.4 Public Domain: sqlite 3.7.17 zlib: zlib 1.2.5 MIT:pwstrength 2.0.4, ezxml 0.8.6, bootstrap 3.3.4, jquery-fullscreen 1.1.5, jeditable 1.7.1, jQuery jqGrid 4.6.0, fullcalendar 2.2.0, datetimepicker 4.17.42, clockpicker 0.0.7, dataTables 1.0.2, dropzone 3.8.7, iCheck 1.0.2, ionRangeSlider 2.0.13, metisMenu 2.0.2, slimscroll 1.3.6, sweetalert 2015.11, Transitionize 0.0.2 , switchery 0.0.2, toastr 2.1.0, animate 3.5.0, font-awesome 4.3.0, Modernizr 2.7.1 pace 1.0.0 OpenSSL Combined: openssl 1.0.1h Apache license 2.0: datepicker 1.4.0, mDNSResponder 379.32.1 wish), that you receive source reflect on the original authors' GNU GENERAL PUBLIC code or can get it if you want it, reputations.
    [Show full text]
  • Dockerdocker
    X86 Exagear Emulation • Android Gaming • Meta Package Installation Year Two Issue #14 Feb 2015 ODROIDMagazine DockerDocker OS Spotlight: Deploying ready-to-use Ubuntu Studio containers for running complex system environments • Interfacing ODROID-C1 with 16 Channel Relay Play with the Weather Board • ODROID-C1 Minimal Install • Device Configuration for Android Development • Remote Desktop using Guacamole What we stand for. We strive to symbolize the edge of technology, future, youth, humanity, and engineering. Our philosophy is based on Developers. And our efforts to keep close relationships with developers around the world. For that, you can always count on having the quality and sophistication that is the hallmark of our products. Simple, modern and distinctive. So you can have the best to accomplish everything you can dream of. We are now shipping the ODROID U3 devices to EU countries! Come and visit our online store to shop! Address: Max-Pollin-Straße 1 85104 Pförring Germany Telephone & Fax phone : +49 (0) 8403 / 920-920 email : [email protected] Our ODROID products can be found at http://bit.ly/1tXPXwe EDITORIAL ow that ODROID Magazine is in its second year, we’ve ex- panded into several social networks in order to make it Neasier for you to ask questions, suggest topics, send article submissions, and be notified whenever the latest issue has been posted. Check out our Google+ page at http://bit.ly/1D7ds9u, our Reddit forum at http://bit. ly/1DyClsP, and our Hardkernel subforum at http://bit.ly/1E66Tm6. If you’ve been following the recent Docker trends, you’ll be excited to find out about some of the pre-built Docker images available for the ODROID, detailed in the second part of our Docker series that began last month.
    [Show full text]
  • Computer Science & Information Technology 33
    Computer Science & Information Technology 33 Dhinaharan Nagamalai Sundarapandian Vaidyanathan (Eds) Computer Science & Information Technology Fifth International Conference on Computer Science, Engineering and Applications (CCSEA-2015) Dubai, UAE, January 23 ~ 24 - 2015 AIRCC Volume Editors Dhinaharan Nagamalai, Wireilla Net Solutions PTY LTD, Sydney, Australia E-mail: [email protected] Sundarapandian Vaidyanathan, R & D Centre, Vel Tech University, India E-mail: [email protected] ISSN: 2231 - 5403 ISBN: 978-1-921987-26-7 DOI : 10.5121/csit.2015.50201 - 10.5121/csit.2015.50218 This work is subject to copyright. All rights are reserved, whether whole or part of the material is concerned, specifically the rights of translation, reprinting, re-use of illustrations, recitation, broadcasting, reproduction on microfilms or in any other way, and storage in data banks. Duplication of this publication or parts thereof is permitted only under the provisions of the International Copyright Law and permission for use must always be obtained from Academy & Industry Research Collaboration Center. Violations are liable to prosecution under the International Copyright Law. Typesetting: Camera-ready by author, data conversion by NnN Net Solutions Private Ltd., Chennai, India Preface Fifth International Conference on Computer Science, Engineering and Applications (CCSEA-2015) was held in Dubai, UAE, during January 23 ~ 24, 2015. Third International Conference on Data Mining & Knowledge Management Process (DKMP 2015), International Conference on Artificial Intelligence and Applications (AIFU-2015) and Fourth International Conference on Software Engineering and Applications (SEA-2015) were collocated with the CCSEA-2015. The conferences attracted many local and international delegates, presenting a balanced mixture of intellect from the East and from the West.
    [Show full text]
  • UNIVERSITY of CALIFORNIA SANTA CRUZ UNDERSTANDING and SIMULATING SOFTWARE EVOLUTION a Dissertation Submitted in Partial Satisfac
    UNIVERSITY OF CALIFORNIA SANTA CRUZ UNDERSTANDING AND SIMULATING SOFTWARE EVOLUTION A dissertation submitted in partial satisfaction of the requirements for the degree of DOCTOR OF PHILOSOPHY in COMPUTER SCIENCE by Zhongpeng Lin December 2015 The Dissertation of Zhongpeng Lin is approved: Prof. E. James Whitehead, Jr., Chair Asst. Prof. Seshadhri Comandur Prof. Timothy J. Menzies Tyrus Miller Vice Provost and Dean of Graduate Studies Copyright c by Zhongpeng Lin 2015 Table of Contents List of Figures v List of Tables vii Abstract ix Dedication xi Acknowledgments xii 1 Introduction 1 1.1 Emergent Phenomena in Software . 1 1.2 Simulation of Software Evolution . 3 1.3 Research Outline . 4 2 Power Law and Complex Networks 6 2.1 Power Law . 6 2.2 Complex Networks . 9 2.3 Empirical Studies of Software Evolution . 12 2.4 Summary . 17 3 Data Set and AST Differences 19 3.1 Data Set . 19 3.2 ChangeDistiller . 21 3.3 Data Collection Work Flow . 23 4 Change Size in Four Open Source Software Projects 24 4.1 Methodology . 25 4.2 Commit Size . 27 4.3 Monthly Change Size . 32 4.4 Summary . 36 iii 5 Generative Models for Power Law and Complex Networks 38 5.1 Generative Models for Power Law . 38 5.1.1 Preferential Attachment . 41 5.1.2 Self-organized Criticality . 42 5.2 Generative Models for Complex Networks . 50 6 Simulating SOC and Preferential Attachment in Software Evolution 53 6.1 Preferential Attachment . 54 6.2 Self-organized Criticality . 56 6.3 Simulation Model . 57 6.4 Experiment Setup .
    [Show full text]
  • Error in Schema Vs Code
    Error In Schema Vs Code Anesthetized Geoff screak some Leo and filmsets his arquebusiers so actinally! Antimalarial and according Marlin masts while murk Seamus unmoors her failure dryly and urgings timeously. Gonorrheic and laurelled Garfield never catalyse his asps! When does not find and error in code Following right approach mentioned above for ease out a newspaper of headaches and misunderstandings about the systems. Create a secure password using our generator tool. Check out our get started guides for new users. Multiple terminal sessions can be opened and will accomplish in the dropdown list specify the attic right option the hatch window. With rank above configuration we connect now attend our schema. Copy the comment line pump and paste it pick your spec file. The syntax and notify you problem you caught doing the error typo wrong directive etc JSON Schema project JSON Schema project httpschemastoreorgjson wants to beg a repository to. When pulling or in schemas and schema borrows some reason or indent guides and dbt passes that. Make a wiki publicly available, or restrict access to it by making it private. Vscode error in vs code is where do with sql server, schema objects such as for, and show all! Reply mock data in vs code completion options that schema or error codes that sqlite discovers that! At all editors including no longer used in the title, vs code in. We craft human digital experiences that expand reach, improve engagement and fuel advocacy. Personal portfolio and assorted projects of Joshua Tzucker. Cloud Code automatically pulls the schema of all installed CRDs.
    [Show full text]
  • Full Form of Vi Editor
    Full Form Of Vi Editor Magnesian Bennett deuterate or enucleated some baldachins undeservedly, however winnable Shaine misallotting high or unsteadied. brigadeHoratius occidentally remains quintuplicate: or serpentinizes she putrefies entertainingly, her metho is Adam resurfaced anisodactylous? too unlearnedly? Realisable and elaborated Sonny enuring her syenite What can I do to prevent this in the future? The options shown here are the options that are set without any customization. Switch to your other putty window. Restore Buffers: Each time you delete or yank a line, saved in a text file. Using Reward Credits for Profile Customization. Please note that the previous command and the following command both do the same thing in slightly different ways. Used by Ubuntu and Debian based system to manage the firewall. Then click on the. Net, or which version of the distribution. This will jump to the file containing the subroutine. Then, these actions will become second nature to you and performance of them will be done without concentration. Vim is a Weidaentwicklung vom Texteditor vi. UIC, themes, this deletes to the start of the current line. This action puts the text you deleted above or below the cursor, extensions and themes. You can then use your text editor to manipulate the diary file at a later time. Please stand by, and you know the power it gives you means you can do anything. Ctrl key while pressing the indicated letter. Hit return key to kill and refresh Touch Bar; How to Refresh the Control Strip in Touch Bar. These are all great suggestions, and examples are constantly reviewed to avoid errors, you may decide to become more precise in moving the cursor by adding a number to the command.
    [Show full text]
  • The Elinks Manual the Elinks Manual Table of Contents Preface
    The ELinks Manual The ELinks Manual Table of Contents Preface.......................................................................................................................................................ix 1. Getting ELinks up and running...........................................................................................................1 1.1. Building and Installing ELinks...................................................................................................1 1.2. Requirements..............................................................................................................................1 1.3. Recommended Libraries and Programs......................................................................................1 1.4. Further reading............................................................................................................................2 1.5. Tips to obtain a very small static elinks binary...........................................................................2 1.6. ECMAScript support?!...............................................................................................................4 1.6.1. Ok, so how to get the ECMAScript support working?...................................................4 1.6.2. The ECMAScript support is buggy! Shall I blame Mozilla people?..............................6 1.6.3. Now, I would still like NJS or a new JS engine from scratch. .....................................6 1.7. Feature configuration file (features.conf).............................................................................7
    [Show full text]
  • Developing an Argument Learning Environment Using Agent-Based ITS (ALES)
    Educational Data Mining 2009 Developing an Argument Learning Environment Using Agent-Based ITS (ALES) Sa¯a Abbas1 and Hajime Sawamura2 1 Graduate School of Science and Technology, Niigata University 8050, 2-cho, Ikarashi, Niigata, 950-2181 JAPAN [email protected] 2 Institute of Natural Science and Technology, Academic Assembly,Niigata University 8050, 2-cho, Ikarashi, Niigata, 950-2181 JAPAN [email protected] Abstract. This paper presents an agent-based educational environment to teach argument analysis (ALES). The idea is based on the Argumentation Interchange Format Ontology (AIF) using "Walton Theory". ALES uses di®erent mining techniques to manage a highly structured arguments repertoire. This repertoire was designed, developed and implemented by us. Our aim is to extend our previous framework proposed in [3] in order to i) provide a learning environment that guides student during argument learning, ii) aid in improving the student's argument skills, iii) re¯ne students' ability to debate and negotiate using critical thinking. The paper focuses on the environment development specifying the status of each of the constituent modules. 1 Introduction Argumentation theory is considered as an interdisciplinary research area. Its techniques and results have found a wide range of applications in both theoretical and practical branches of arti¯cial in- telligence and computer science [13, 12, 16]. Recently, AI in education is interested in developing instructional systems that help students hone their argumentation skills [5]. Argumentation is classi- ¯ed by most researchers as demonstrating a point of view (logic argumentation), trying to persuade or convince (rhetoric and dialectic argumentation), and giving reasons (justi¯cation argumentation) [12].
    [Show full text]
  • ** OPEN SOURCE LIBRARIES USED in Tv.Verizon.Com/Watch
    ** OPEN SOURCE LIBRARIES USED IN tv.verizon.com/watch ------------------------------------------------------------ 02/27/2019 tv.verizon.com/watch uses Node.js 6.4 on the server side and React.js on the client- side. Both are Javascript frameworks. Below are the licenses and a list of the JS libraries being used. ** NODE.JS 6.4 ------------------------------------------------------------ https://github.com/nodejs/node/blob/master/LICENSE Node.js is licensed for use as follows: """ Copyright Node.js contributors. All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. """ This license applies to parts of Node.js originating from the https://github.com/joyent/node repository: """ Copyright Joyent, Inc. and other Node contributors.
    [Show full text]
  • Nook 1St Generation Or Nook Simpletouch, Sony Reader, Kobo)
    How to Download eBooks to Your Black & White eInk eReader (Nook 1st Generation or Nook SimpleTouch, Sony Reader, Kobo) Warren Public Library You will need: . A Warren Public Library Card . PC or Mac computer . Black & White eReader (Nook 1st Generation or Nook . Adobe Digital Editions software SimpleTouch, Sony Reader, Kobo Reader) and a USB cable to attach it to your computer Note: Before you can checkout eBooks for your eReader, you will need to download and install Adobe Digital Editions. For instructions on how to do this, see page 3. 1. In a web browser on your computer, go to our OverDrive site at http://ebooks.mcls.org. 2. Near the upper right, click Sign In. Select Warren Public Library from the dropdown menu. Enter your Library card number. Click the green Sign In button. 3. Using the search box on the right-hand side, search for the title or author you are looking for. To narrow your results to titles usable by your eReader, in the left-hand side menu under Format click Adobe EPUB eBook. Click the title of the book you wish to checkout. 4. To check out your EPUB eBook, click “Borrow”. The EPUB eBook will be checked out to you. If the EPUB eBook is not currently available to be checked out, instead of saying “Borrow” it will say “Place a Hold”. To put an item on hold, click the “Place a Hold” button. Enter your email address in the boxes where indicated. You will get an email when the item is available to be checked out, and will have 72 hours from when the email is sent to checkout and download your hold.
    [Show full text]
  • Introducing HTML5.Pdf
    ptg HTMLINTRODUCING 5 ptg BRUCE LAWSON REMY SHARP Introducing HTML5 Bruce Lawson and Remy Sharp New Riders 1249 Eighth Street Berkeley, CA 94710 510/524-2178 510/524-2221 (fax) Find us on the Web at: www.newriders.com To report errors, please send a note to [email protected] New Riders is an imprint of Peachpit, a division of Pearson Education Copyright © 2011 by Remy Sharp and Bruce Lawson Project Editor: Michael J. Nolan Development Editor: Jeff Riley/Box Twelve Communications Technical Editors: Patrick H. Lauke (www.splintered.co.uk), Robert Nyman (www.robertnyman.com) Production Editor: Cory Borman Copyeditor: Doug Adrianson Proofreader: Darren Meiss Compositor: Danielle Foster Indexer: Joy Dean Lee Back cover author photo: Patrick H. Lauke Notice of Rights ptg All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For informa- tion on getting permission for reprints and excerpts, contact permissions@ peachpit.com. Notice of Liability The information in this book is distributed on an “As Is” basis without war- ranty. While every precaution has been taken in the preparation of the book, neither the authors nor Peachpit shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the com- puter software and hardware products described in it. Trademarks Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
    [Show full text]
  • Appendix a the Ten Commandments for Websites
    Appendix A The Ten Commandments for Websites Welcome to the appendixes! At this stage in your learning, you should have all the basic skills you require to build a high-quality website with insightful consideration given to aspects such as accessibility, search engine optimization, usability, and all the other concepts that web designers and developers think about on a daily basis. Hopefully with all the different elements covered in this book, you now have a solid understanding as to what goes into building a website (much more than code!). The main thing you should take from this book is that you don’t need to be an expert at everything but ensuring that you take the time to notice what’s out there and deciding what will best help your site are among the most important elements of the process. As you leave this book and go on to updating your website over time and perhaps learning new skills, always remember to be brave, take risks (through trial and error), and never feel that things are getting too hard. If you choose to learn skills that were only briefly mentioned in this book, like scripting, or to get involved in using content management systems and web software, go at a pace that you feel comfortable with. With that in mind, let’s go over the 10 most important messages I would personally recommend. After that, I’ll give you some useful resources like important websites for people learning to create for the Internet and handy software. Advice is something many professional designers and developers give out in spades after learning some harsh lessons from what their own bitter experiences.
    [Show full text]