<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE document PUBLIC "-//CNX//DTD CNXML 0.5 plus MathML//EN" "http://cnx.rice.edu/cnxml/0.5/DTD/cnxml_mathml.dtd">
<document xmlns="http://cnx.rice.edu/cnxml" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" id="m10510">
  
  <name>Training Module 1</name>
  <metadata>
  <md:version>2.7</md:version>
  <md:created>2002/02/15</md:created>
  <md:revised>2002/04/10</md:revised>
  <md:authorlist>
      <md:author id="jago">
      <md:firstname>Adan</md:firstname>
      
      <md:surname>Galvan</md:surname>
      <md:email>jago@rice.edu</md:email>
    </md:author>
  </md:authorlist>

  <md:maintainerlist>
    <md:maintainer id="jago">
      <md:firstname>Adan</md:firstname>
      
      <md:surname>Galvan</md:surname>
      <md:email>jago@rice.edu</md:email>
    </md:maintainer>
  </md:maintainerlist>
  
  

  <md:abstract>(Blank Abstract)</md:abstract>
</metadata>

  <content>
    <section id="sec1">
      <name>Introduction</name>
      
      <para id="para1">
	Welcome to the Connexions project!  As an employee of the
	Connexions project, we expect you to work diligently to create
	high quality modules.  By following the correct procedures and
	memorizing some of the basics, you too can become a Connexions
	expert!  <note type="note">This tutorial is only for employees
	of the connexions project. All non-employees should see the
	<cnxn document="m10307" strength="9">author-interface
	tutorial</cnxn>.</note>
      </para>
    </section>

    <section id="sec2">
      <name>Getting Started - The Basics</name>
      <para id="para2">
	So you've gotten all your paper work filled out with the help
	of our trusty project coordinator and are wondering what's
	next.  What is necessary to begin your new job as a CNXML
	editor?  Below are a few things that will be absolutely
	required for you to begin programming and to begin fulfilling
	your duties as a Connexions employee.
      </para>
      
      <section id="sec3">
	<name>Accounts</name>

	<section id="sec4">
	  <name>Connexions Account</name>
	  <para id="paraf3">
	    There are a couple of accounts that you'll need in order
	    to begin working as a Connexions employee.  The first
	    thing that you will need is an account for the
	    <term>Connexions web-based Student/Author/Instructor
	    interface</term>.  This can be obtained by contacting the
	    system architect. Come into the Connexions office to speak
	    with him about setting up your <term>Connexions
	    account</term>.  Your username will probably be your usual
	    owlnet account (unless otherwise specified).  You will be
	    provided with your password, which only you will know.
	    The system architect will not know your password, but he
	    will be able to provide you with it should you happen to
	    forget it.  This password will provide you access to the
	    interface which is located at <link src="http://cnx.rice.edu">http://cnx.rice.edu</link> This
	    step should take no more than five minutes.
	  </para>

	  <para id="mountainpara">
	    You will also need an account for the <cnxn target="mountain" strength="9">mountainbunker.org</cnxn> site.
	This password will be different but the username will remain
	the same. You can change this password from the <cnxn target="editmyinfo" strength="9">edit my info</cnxn> section
	of the mountainbunker site.  More information on your password
	can be obtained from the system architect or the project
	coordinator.</para>

	</section>
	
	<section id="sec5">
	  <name>ECE Account</name>
	  <para id="para4">
	    The second account you will receive upon completion of your
	    paperwork with the project coordinator is your
	    <term>ECE account</term>.  This account will use the same
	    username and password as that of your owlnet account.
	    Once you have completed your paperwork this account will
	    take about a day to be activated.  Once this account is
	    activated you can access any computer in the connexions
	    office as well as those in the electrical engineering
	    department.  This will make it convenient for you as an
	    employee, since you will now have the option to:
	    <list id="list1" type="bulleted">
	      <item>Work from your room</item>
	      <item>Work in any Owlnet Lab</item>
	      <item>Work in any electrical engineering department
		computing lab</item>
	      <item>Work in the Connexions Office</item>
	      <item>Work anywhere you want (even if you don't have
		access to the internet)</item>
	    </list>
	    Unfortunately, the last option will allow you to author
	    modules, but not submit them into the repository (more on
	    this later).
	  </para>
	</section>
      </section>

      <section id="sec5a">
	<name>Required Software</name>
	
	<para id="para5">
	  There are a couple of required installs that you will have
	  to make in order to begin now that you have access into the
	  system.</para>
	
	<section id="sec6">
	  <name>Mozilla</name>
	  <para id="para7">
	    Mozilla is an open source web browser that allows users to
	    view pages encoded with mathML.  This is advantageous to the
	    Connexions project since modules are often very mathML
	    intensive.  Mozilla is not the only web browser that
	    supports mathML, but is it the best.  Mozilla is
	    available in all of the owlnet and ECE labs.  Simply type
	    <code>mozilla</code> at the command prompt to get
	    Mozilla started.  There are at least two other sources for
	    Mozilla.
	    <list id="list2">
	      <item><link src="http://www.mozilla.org">mozilla.org</link>
	      </item>
	      <item><link src="http://cnx.rice.edu/learner/quick_start">student
		  quick start page</link></item>
	    </list>
	    If you download Mozilla from the mozilla web page, be sure
	    to get the build that is mathML enabled.  If you obtain
	    Mozilla from the quick start page, follow the steps and in
	    no time you will have Mozilla installed.
	  </para>
	</section>
	<section id="sec7">
	  <name>Connexions Roadmap</name>
	  <para id="para8">
	    If you were a student in a course that is part
	    of the Connexions, then you probably have seen the
	    <term>Connexions roadmap</term>.  This 'roadmap' is what
	    allows students to easily and quickly navigate modules for
	    their respective courses.  As an employee, you will need
	    the roadmap to:
	    <list id="list3">
	      <item>View existing courses</item>
	      <item>Create and view new courses</item>
	      <item>View the cnxml and mathML tutorials</item>
	    </list>
	    The roadmap can be found at the <link src="http://cnx.rice.edu/learner/quick_start">student quick
	 start page</link>. Simply follow the simple steps to install
	 the roadmap with Mozilla.  To learn more about the roadmap
	 view the <cnxn document="m10338" strength="9"> roadmap
	 tutorial</cnxn>.
	  </para>
	</section>

      </section>
    </section>

    <section id="admin">
      <name>Administrative Information</name>

      <para id="para13">
	There are a couple of items that need to be addressed before you begin
	authoring your modules. These items will be discussed below.
      </para>
      
      <section id="mountain">
	<name>Mountainbunker</name>
	<para id="paramountain">

	  One of internet sites that you will be visiting frequently
	  is <link src="http://mountainbunker.org">mountainbunker.org</link>. This
	  site has many useful links and resources for you to use as a
	  connexions employee. Let's begin discussing some of the
	  great information you will find on mountainbunker.
	</para>

	<section id="mount1">
	  <name>Site Navigation</name>

	  <para id="sitenav">
	    On the left hand side of the page you will find a
	    navigation bar. This will allow you to quickly navigate
	    the site. The options in the navigator bar are
	    <list id="navlist">
	      <item><cnxn target="home" strength="9">Home</cnxn></item>
	      <item><cnxn target="mytasks" strength="9">My Tasks</cnxn></item>
	      <item><cnxn target="timesheet" strength="9">Timesheet</cnxn></item>
	      <item><cnxn target="preports" strength="9">Progress Report</cnxn></item>
	      <item><cnxn target="announcements" strength="9">Announcements</cnxn></item>
	      <item><cnxn target="teamminutes" strength="9">Team Minutes</cnxn></item>
	      <item><cnxn target="editmyinfo" strength="9">Edit my info</cnxn></item>
	      <item><cnxn target="submitbug" strength="9">Submit a bug</cnxn></item>
	      <item><cnxn target="logout" strength="9">Log
		  Out</cnxn></item>
	    </list>
	  </para>
	  
	  <section id="home">
	    <name>Home</name>
	    <para id="homepara">
	      The  home page is the default page that loads after you log
	      into mountainbunker.  Use this link if you wish to return
	      directly back to the homepage. <note type="note">Use the
		mountainbunker password that you set up with the system
		administrator in order to first log into the system.</note>

	    </para>
<!--    
	    <figure id='homefig'>
	      <media type='image/png' src='homepage.png'/>
	      <caption>Screen shot of moutainbunker.org</caption>
	    </figure>
	-->
	  </section>
	  <section id="mytasks">
	    <name>My Tasks</name>
	    <para id="mytaskspara">
	      In order to get problems solved quickly, it is often
	      best to assign certain tasks or bugs to specific
	      connexions workers.  Additionally, you may occasionally
	      wish to assign yourself to a certain task.  The My
	      Tasks link has three different things for you to do.

	      <list id="listtasks">
		<item>Search for tasks.</item>
		<item>View tasks assigned to you specifically.</item>
		<item>View tasks assigned to your teams.</item>
	      </list>
	      Each task has the following labels:

	      <list id="tasklist">
		<item>ID-id number to identify the task.</item>
		<item>Date-date of submission.</item>
		<item>Type-type of task.</item>
		<item>Priority-priority of task</item>
		<item>Description-description of the task.</item>
		<item>Submitted by-name and email of person who
		  submitted the task.</item>
		
	      </list>

	      <note type="note">These labels will have to be filled in
	      when submitting a new task.</note>
	      
	    </para>
<!--	    <figure id='mytasksfig'>
	      <media type='image/png' src='mytasks2.png'/>
	      <caption>Image of my tasks page.</caption>
	    </figure>
-->

	  </section>

	  <section id="timesheet">
	    <name>Timesheet</name>
	    
	    <para id="timesheetpara">
	      When you click on the Timesheet link you will be taken
	      to a page which consists of a simple timesheet applet.
	      You are not required to use this applet, but it is very
	      useful. Simply record the number of hours you worked for
	      a specific day in the boxes labeled M-F.  Hit the
	      <code>save</code> button to store the hours
	      worked.  Record the number of hours worked throughout
	      the week and save yourself the trouble of having to
	      remember when you worked later.  Hit the
	      <code>clear</code> button in order to begin
	      recording hours for a new week.</para> 
<!--
	    <figure id='timefig'>
	      <media type='image/png' src='timesheet.png'/>
	      <caption>Image of timesheet page.</caption>
	    </figure>
-->
	  </section>

	  <section id="preports">
	    <name>Progress Reports</name>

	    <para id="preportspara">
	      For administrative purposes, we require that every employee of
	      connexions submit a progress report indicating a few
	      things.
	      <list id="preportslist">
		<item>Work done in the previous week.</item>
		<item>Problems encountered during the previous week
		  and how you dealt with them.</item>
		<item>Future plans.</item>
	      </list>
	      <note type="note"> There is a sample progress report on
		<link src="http://mountainbunker.org">mountainbunker</link>.
	      </note>
	      <note type="warning">
		Progress reports are <emphasis>mandatory</emphasis>
		and failure to submit one each week will result in
		your time sheet not getting turned
		in. <foreign>i.e</foreign> You will not get
		paid!</note> The progress report page will show all
		the of the students and staff and the progress reports
		for the past ten weeks.  After that time any progress
		report can be viewed using the search at the bottom of
		the page.
	    </para>
<!--	    
	    <figure id='progressfig'>
	      <media type='image/png' src='progress.png'/>
	      <caption>Image of progress report page.</caption>
	    </figure>  -->
	  </section>

	  <section id="announcements">
	    <name>Announcements</name>

	    <para id="announementspara">
	      Any changes or announcements for the mountainbunker site
	      will be posted here.  Announcements are shown by date by
	      default. There is also an option to view the
	      announcements by team.  Simply click on <code>show
	      by team</code>.  Each announcement will contain:

	      <list id="announcelist">
		<item>team <note type="note">Only for team
		announcement view.</note></item> <item>date
		posted</item> <item>announcement summary</item>
		<item>announcement author</item> <item>announcement
		text</item>
	      </list>
	      Check back here often to keep up with all the important
	      news regarding mountainbunker.

	    </para>
<!--
	    <figure id='announfig'>
	      <media type='image/png' src='announcements.png'/>
	      <caption>Image of announcement page.</caption>
	    </figure>
-->
	  </section>

	  <section id="teamminutes">
	    <name>Team Minutes</name>

	    <para id="teamminutespara">
	      During team meetings it is important to take minutes,
	      since it is often difficult to get everyone to attend at
	      once.  You can check here to see if your team/teams met
	      and what transpired during the meeting.  Each entry here
	      represents a different meeting.  There are three things
	      that you can do from this page.
	      <list id="minuteslist">
		<item>Submit new minutes</item>
		<item>View current minutes (from your teams)</item>
	        <item>View current minutes (from other teams)</item>
	      </list>
	      Submitting new minutes is self-explanatory and can be
	      easily done by clicking on the submit new minutes link.
	    </para>
<!--
	    <figure id='minutesfig'>
	      <media type='image/png' src='minutes.png'/>
	      <caption>Image of the team minutes page.</caption>
	    </figure> -->
	  </section>

	  <section id="editmyinfo">
	    <name>Edit My Info</name>
	    <para id="editpara">
	      The edit my info link will take you to the page which
	      will allow you to:
	      <list id="editlist">
		<item>change your password</item>
		<item>edit you name</item>
		<item>edit your email address</item>
		<item>choose whether or not to receive weekly email
		  reminders for your progress report</item>
	      </list>
	      Simply fill in the fields and click on <code>update
		user</code> to change your info.  The
		<code>reset</code> button reverts your info
		back to its original format.<note type="note">Your
		info will not be updated if you do not hit
		<code>update info</code>.</note></para>

	    <figure id="editfig">
	      <media type="image/png" src="editmyinfo.png"/>
	      <caption>Screen-shot of edit my info page.</caption>
	    </figure>

	  </section>

	  <section id="submitbug">
	    <name>Submit Bug</name>

	    <para id="submitpara">
	      By clicking on <code>submit bug</code> you will
	      be able to submit a bug about any trouble you are having
	      with any software developed or maintained by Connexions.
	      This includes:

	      <list id="submitlist">
		<item>Author Interface</item>
		<item>Roadmap</item>
		<item>Mountainbunker</item>
		<item>Risa</item>
	      </list>

	      and many other specific bug types (eg. browser
	      funkiness, bad hyperlink, <foreign>etc.</foreign>).
	      <note type="note">It is very important for you to submit
	      bugs that you find! We will all benefit from finding and
	      dealing with these bugs.</note>
	    </para>
	  </section>

	  <section id="logout">
	    <name>Log Out</name>

	    <para id="logpara">
	      Once you are done visiting the site, click the
		<code>log out</code> link to log out of the
		system.
	    </para>

	  </section>
	</section>

	<section id="documen">
	  <name>Documentation</name>

	  <para id="documenpara">
	    The documentation section of the navigation bar will
	    allow you to visit pages with tons of information on many
	    subjects directly and indirectly related to Connexions.
	    <list id="documentools">
	      <item>
		<cnxn target="tools" strength="9">Tools</cnxn>
	      </item>
	      <item>
		<cnxn target="specs" strength="9">Specs</cnxn>
	      </item>
	      <item>
		<cnxn target="tutorials" strength="9">Tutorials</cnxn>
	      </item>
	      <item>
		<cnxn target="links" strength="9">Links</cnxn>
	      </item>
	      <item>
		<cnxn target="wikis" strength="9">Wikis</cnxn>
	      </item>
	      <item>
		<cnxn target="files" strength="9">Files</cnxn>
	      </item>
	    </list>
	    Each of the links in the documents section will contain
	    lists that are similar to the image below.

	  </para>
<!--
	  <figure id='specimage'>
	    <media type='image/png' src='spec.png'/>
	    <caption>Screenshot of specs page.</caption>
	  </figure>
-->
	  <section id="tools">
	    <name>Tools</name>
	    <para id="toolspara">
	      In the tools section you will find commands and hints
	      about tools that you will use when working for
	      connexions. You can submit a new tool by clicking on the
	      <code>Submit tool</code> link.  Each entry will
	      contain:

	      <list id="toolslist">
		<item>name</item>
		<item>date and submitter info</item>
		<item>description and use info</item>
	      </list>
	    </para>
	  </section>
	  
	  <section id="specs">
	    <name>Specs</name>
	    
	    <para id="specspara">
	      In the specs section you will find links to the
	      specifications you will need to refer to when working
	      for connexions. Certain specifications will be used
	      more than others.  These include:

	      <list id="speclist">
		<item>cnxml specification (currently 0.5)</item>
		<item>mathml specification (currently 2.0)</item>
		<item>qml specification</item>
	      </list>
	      
	      <note type="note">These specs are very important and
		will be required when composing modules!</note>

	    </para>
	  </section>
	  
	  <section id="tutorials">
	    <name>Tutorials</name>
	    
	    <para id="tutorialpara">
	      In the tutorial section you will find links to tutorials
	      on cnxml, mathml, qml, and other connexions related
	      languages.  The tutorial section will be updated as the
	      links become available.  For more information on the
	      tutorials see the <cnxn target="sec12" strength="9">Connexions Tutorial</cnxn> section.
	    </para>

	  </section>
	  
	  <section id="links">
	    <name>Links</name>
	    
	    <para id="paralinks">
	      In the links section you will find links that are
	      related to connexions. These sites may be helpful
	      when authoring modules.
	    </para>
	  </section>

	  <section id="wikis">
	    <name>Wikis</name>
	    
	    <para id="wikispara">
	      
	      In the wikis section you will find links to wikis
	      regarding many different subjects such as mathml, cnxml,
	      <foreign>etc.</foreign> The term wiki is discussed below.


	      <definition id="wiki">
		<term>wiki</term>
		<meaning>
		  A wiki is a kind of collaborative website. Pages
		  can be changed on the spot by clicking "Edit this
		  page", and certain conventions are followed to
		  simplify writing and linking. A wiki web usually
		  has a particular focus or subject orientation.
		</meaning>
	      </definition>
	      
	      Anyone interested may add comments on a subject that
	      they wish to collaborate on.  More info on wikis can
	      be found at the <link src="http://zwiki.org">Zwiki
		home page</link>.

	    </para>
<!--
	    <figure id='wikisfig'>
	      <media type='image/png' src='wikis2.png'/>
	      <caption>Screen-shot of the wikis page.
	      </caption>
	    </figure>
-->
	  </section>
	  
	  <section id="files">
	    <name>Files</name>
	    
	    <para id="filespara">
	      In the files section of the mountainbunker site, anyone
	      can deposit files so that other team members may easily
	      download them.  This was implemented so that the number
	      of large emails sent could be reduced.  Simply click on
	      the name of the team you are leaving the file for, and
	      follow the instructions to upload the file.
	    </para>

	    <figure id="filesfig">
	      <media type="image/png" src="files.png"/>
	      <caption>Screenshot of Files page.
	      </caption>
	    </figure>

	  </section>
	</section>
	
	<section id="calenders">
	  <name>Calendars</name>
	  <para id="calpara">
	    In the calendars section of the mountainbunker site, one
	    can view a calendar for the current and upcoming months.
	    The calendar will contain important events for different
	    connexions teams. With the correct permissions, one can
	    also add items to the calendar.  <note type="note">Contact
	    the system architect in order to gain access to the
	    calendar system.</note>
	  </para>
	</section>

	<section id="Forums">
	  <name>Forums</name>
	  <para id="forumspara">
	    In the forums section of the mountainbunker site, one
	    can leave messages for other members of connexions
	    teams.  This functions as an alternative mode of
	    communication. Simply click on the forum name to be
	    taken to the particular forum.  Each forum page gives
	    you the option to:

	    <list id="forumlist">
	      <item>Change View
		<list id="viewlist">
		  <item>Collapsed - hide all responses to
		    posts.</item>
		  <item>Expanded - show all messages and
		    replies.</item>
		</list>
	      </item>
	      <item>View posts by date.</item>
	      <item>Post new messages to the forum.</item>
	    </list>
	    
	    <note type="note">The forum section <emphasis>does
	      not</emphasis> require special permissions like calendar
	      sections.</note>
	  </para>
	</section>

	
	<section id="teampages">
	  <name>Teams</name><!-- shouldn't this say Teams like the
	  actual header on the page?-->
	  
	  <para id="teampara">
	    In the final section of the navigation bar one can see a
	    list of all the teams currently existing in the connexions
	    project (content, style, <foreign>etc.</foreign>).  <note type="note">These team links are very useful!</note> In
	    each team link there will be much of the vital information
	    that you will find by navigating through the
	    mountainbunker site, all in one convenient place.  The
	    team pages allow you to:

	    <list id="teamlist">
	      <item>Send a message to the mailing list for that
		particular team.
	      </item>
	      <item>View the current tasks for that particular
		team.</item>
	      <item>View the files that have been deposited for that
		particular team.</item>
	      <item>View any announcements that have been made for
		that particular team.</item>
	      <item>View the minutes from recent meetings for that
		particular team.</item>
	      <item>Send a message to any member of the particular
		team.</item>
	    </list>

	    This page should be the first place you visit upon
	    entering the mountainbunker site.
	  </para>
<!--
	  <figure id='teamfig'>
	    <media type='image/png' src='team.png'/>
	    <caption>Screenshot of the Connexions team page.</caption>
	  </figure>
-->
	</section>
      </section>
    </section>
    <section id="sec12">
      <name>Connexions Tutorials</name>
      
      <para id="para13_1">
	Now that you have mozilla and the roadmap installed
	it's time to begin authoring modules.   First, it is
	necessary to read through the following tutorials:

	<list id="listtut">
	  <item>
	    <cnxn document="m9002" strength="9">XML</cnxn>
	  </item>
	  <item><cnxn document="m9000" strength="9">cnxml</cnxn>
	  </item>
	  <item><cnxn document="m9008" strength="9">mathML</cnxn>
	  </item>
	</list>

	There are two methods for viewing these tutorials.  It is
	recommended that you use the <cnxn target="sec7" strength="9">roadmap</cnxn> to go through these tutorials,
	since this will make them easier to navigate. Links to these
	tutorials are also available on the mountainbunker.org site.
	<note type="note">It is mandatory that you go through these
	tutorials!  It is not easy to simply begin writing modules
	using the specifications references.</note>

      </para>
<!--
      <figure id='tutimage'>
	<media type='image/png' src='tutorials.png'/>
	<caption>Screen shot of the Tutorials menu of the
	  roadmap.</caption>
      </figure>
-->
    </section>

    <section id="sec9">
      <name>Author System</name> <para id="test">When developing
      modules for the <link src="http://cnx.rice.edu">Connexions</link> repository you will
      have multiple tools at your disposal. You will be working both
      with local and web based tools.  Although authoring modules is
      possible in any operating system, we recommend using <link src="http://www.linux.org">Unix/Linux</link>. This in
      conjunction with the <cnxn target="sec10" strength="9">author
      interface</cnxn> your <cnxn target="sec11" strength="9">local
      text editor</cnxn> will be the main tools used in the creation
      of your modules.  In this section I give a quick review of the
      tools mentioned.
      </para>


      <section id="sec10">
	<name>Author Interface</name>
	<para id="para9">
	  The <term>author interface</term> is an easy to use web
	  based system that allows authors to view and manipulate
	  modules.  So what can you do with the interface?

	  <list id="authorintlist">
	    <item>Manage/view workgroups.</item>
	    <item>Create new workgroups.</item>
	    <item>Edit/view modules.</item>
	    <item>Create new modules.</item>
	    <item>Edit metadata.</item>
	    <item>Upload/download files associated with modules.</item>
	    <item>Create PDF files from modules that can be
	      printed.</item>
	  </list>
	  The interface has been designed to make it easy for you to
	  carry out these various actions.  Once you have an account
	  it will be possible for you to enter the author interface
	  and begin manipulating modules.  To learn more about the
	  author interface, view the <cnxn document="m10307" strength="9">Author Interface Tutorial</cnxn>.
	</para>
      </section>
      <section id="sec11">
	<name>Authoring Module Content</name>

	<para id="para11">
	  Although the author interface does allow you to edit modules
	  directly online, for the most part you will not be using the
	  author interface to write/edit your modules. It is often
	  more convenient to use a local text editor to make
	  changes to the actual text of the module, since a browser
	  does not have the numerous options available for formatting
	  and editing that a good text editor does.<!-- Why -->
	  There are a couple of options when writing/editing modules:

	  <list id="editorlist">
	    <item>edit the modules online through the author
	      interface</item>
	    <item>download a copy of the module text to your local
	      machine and edit it using:
	      <list id="sublist1">
		<item><cnxn target="emacssec" strength="9">emacs</cnxn></item> 
		<item><cnxn target="otheredsec" strength="9">your favorite text
		editor</cnxn></item>
	      </list>
	    </item>
	  </list>
	</para>

	<section id="emacssec">
	  <name>Authoring with Emacs</name>
	  
	  <para id="emacspara">
	    Although one of the options is to edit the modules
	    directly through the author interface, this is not the
	    most efficient way to do so.  For the most part you will
	    not be using the author interface to write/edit your
	    modules, but instead are advised to use emacs to edit your
	    modules locally.  A <code>.emacs</code> file has
	    been created that allows users to quickly and easily edit
	    their modules.  With <cnxn document="m9004" strength="9">emacs sgml mode</cnxn> one can:

	    <list id="emacslist">
	      <item>ensure correct indenting (especially important for
	      mathML)</item> <item>quickly and easily insert
	      tags</item> <item>edit/manipulate the text as easily as
	      you would with any other text editor.</item>
	    </list>
	    <note type="Notice">For help on obtaining the
	      <code>.emacs</code> file and using it with emacs
	      ask your mentor or one of the connexions staff
	      members.</note> For more information on emacs see an
	      <link src="http://www.lib.uchicago.edu/keith/tcl-course/emacs-tutorial.html">emacs
	      tutorial</link>
	  </para>
<!--
	  <figure id='smgmlfig'>
	    <media type='image/png' src='sgml.png'/>
	    <caption>Screen shot of Emacs using SGML mode.</caption>
	  </figure>
	-->  
	</section>

	<section id="otheredsec">
	  <name>Authoring with Other Text Editors</name>

	  <para id="para12">
	    Using other text editors is allowed, and encouraged if emacs
	    is not available.  Use these editors as you normally would,
	    and save the file as a <code>.cnxml</code> file.
	    Again, it is not mandatory to use emacs and the emacs
	    connexions environment to edit your modules, but it is
	    preferable.</para>
	</section>
      </section>
    </section>
  </content>
  
  
</document>
