Skip to Login Skip to Content Skip to Secondary Navigation

Web Hosting

Process Required to Publish an Organizational Web Site:

1. Identify and appoint organization's web site manager.
2. Prepare html files and graphics to be used.
3. Read through, Student Affairs Web Server Policy, Accessing Your Files Via FTP, Updating Your Web Site, and Student Affairs Web Server Disclaimer
4. Complete the Student Organizations FTP Request Form by login in to your
On-line Orgs Account to acquire the FTP Account.


UCSB Student Affairs Web Server Policies and Procedures

The UCSB Student Affairs Web Server is a repository of information for and about departments within the Division of Student Affairs and student organizations. The purpose of the server is to provide departments within the Division of Student Affairs and student organizations with a place for publishing information on the World Wide Web.

All Student Affairs departments and registered student organizations may have accounts on the server, and will have the privilege of directly publishing and updating information on the server. The content of all documents published must be consistent with federal and state laws and University policy.

Each department and student organization may designate staff and/or currently enrolled students to publish information on the server. All designated persons must be authorized by the departmental head and/or organization president and in the case of students, an expiration date must be established. After which the student will no longer have access to the server. Currently, personal webpages which promote/describe and individual and his or her accomplishments will not be permitted, and if found, will be removed from the server. No person having access to the server may alter or delete files which are not located within their department's or organization's directory.

Departments and student organizations are responsible for the accuracy and appropriateness of the content of any document(s) published. Anyone with concern about the information included on the Student Affairs Web Server is encouraged to communicate that concern in writing to the Student Affairs Web Server administrator.

Consistent with the purposes for which the University has established the Student Affairs Web Server, the server administrator may take the initiative for suggesting documents to be included on the server. Such initiative may be taken to offer balance, inclusiveness, consistency, and general serviceability of the Student Affairs Web Server database.

All publishers are expected to adhere to and keep updated on the standards recommended for publishing on the Student Affairs Web Server.

Because the format of information on the Student Affairs Web Server provides no distinction between editorial and other content, commercial advertising will not be permitted.

The right to change these policies at any time is reserved.


Page Guidelines

Any registered student organization at University of California at Santa Barbara may be included in UCSB Student Affairs Home Page under Student Organizations. Each student organization will be given access to a home page in which they can provide vital information about their organization when the organization leader has completed a request to the Campus Activities Center for a home page. This request must be signed by the student organization president, the faculty advisor, and the Office of Student Life Advisor. Suggested items to cover on the home page are:

1. Name
2. Type
3. Purpose statement ( 1 or 2 sentences, 25 words maximum)
4. Criteria for membership (if any)
5. President's Name
6. President' local address
7. President's local telephone number
8. Advisor's Name
9. Advisor's campus mail address
10. Advisor's campus telephone number
11. Regular meeting time(s), day(s)
12. Regular meeting place
13. Cost of membership (if any)
14. Scheduled special events/activities (registered through Office of Student Life)

Inclusion in the UCSB Student Affairs home page is a privilege granted contingent upon the organization complying all University Policies and Regulations as outlined in the University of California, Santa Barbara Campus Regulations Applying to Campus Activities, Organizations, and Students. Student Affairs reserves the right to remove any student organization from the home page if Student Affairs and Office of Student Life deem this action in the best interest of the institution. Any grievances may be addressed through the Office of Student Life.

Process Required to Publish an Organizational Web Site:

1. Identify and appoint organization's web site manager.
2. Prepare html files and graphics to be used.
3. Read through, Student Affairs Web Server Policy, Accessing Your Files Via FTP, Updating Your Web Site, and Student Affairs Web Server Disclaimer
4. Complete the Student Organizations FTP Account Online Request Form
5. Have the organization's faculty advisor approve the request.
6. Submit request to the Office of Student Life for approval.
7. Upon approval, bring the form to Student Information Systems located at 1205 SAASB or 893-4606 to acquire the FTP Account.


How to Structure your Web site.

Your Web site Address is:

o index.html
o page1.htm
o page2.htm
o page3.htm
+ images.gif
+ photo.jpg
+ Sub photos 2.0
+ Sub photos 2.1
Sub photos 2.2.0
# photo.jpg
# photo.gif
CSS [optional]
+ stylesheet.css
+ index.html
+ page1.htm


Publishing Guidelines

Web publishers at UCSB Student Affairs are responsible for the content of the pages they publish and are expected to abide by the highest standards of quality and responsibility. Additionally, all publishers should comply with established publishing policies.
Concentrate on original work

Readers are looking for information on your college, department, or organization. The most valuable contribution you can make to your readers is to publish original work. Collections of pointers to the work of others, while a service that can be valuable, is not a substitute for publishing your own documents and materials.
Take advantage of the work of others

Cooperation and coordination are two prevailing principles among Web publishers on this campus and throughout the world. Rather than duplicating the work of others, take advantage of it. Incorporate links to the work of others into your own pages, when appropriate. Reducing redundancy lets you concentrate on original offerings.
Review your pages

Publishing in the Web is just that - publishing. And just like paper publishing, your Web pages should follow the normal procedures of proper review and approval before you publish them.
Preview your pages

Before you put your pages up for the world to see, take a look at them locally in your browser. This way you can make sure your pages look as you expect them to.
Announce your pages

To increase exposure to your pages, publishers are encouraged to send announcements of their important additions.
Keep pages up to date

Web publishing is not a one-time task. You should keep all pages up to date. In many ways, you will find updating Web pages quicker and more convenient than updating paper publications.
Design pages for ADA Compliance

Pages must be usable by those using screen readers. Therefore, do not create pages with graphic-only content or graphic-only navigation. All graphics must have alt tags. All graphic nativation bars and buttons must have text alternatives on the page. Avoid creating a second set of text-based pages. Instead, integrate graphics and text on the same page.
Keep pages browser independent

Design pages that are viewable in all major browsers, including Netscape, Explorer, and Lynx, a text-based browser used by the visually impaired.
Sign all pages

Place a standard signature at the bottom of all major pages. This signature should contain the date of last update, organization name, E-mail address for comments, a link to Web Central, and links to other appropriate pages.
Make the best use of your home page

Your home page is the most valuable portion of your Web collection. Do not waste home page space on introductory paragraphs of information that users will read only one time and subsequently ignore. History and introductory text are important and should be a part of every home page, but shrink it to a link labelled "Introduction" or "About."
Follow a simple and consistent design

Complex designs can confuse users, so keep it simple. Also, a consistent design will let your readers concentrate on content, without having to waste time figuring out how to maneuver your layout.
Use index.htm as name for primary HTML file

If the primary file is called index.asp, you need not specify it in URLs. For example, both of these links work, but the shorter one is more conventional and might be easier for others to remember and for you to type:

* Okay: /index.htm
* Better:

Organize files into subdirectories

A subdirectory is the same thing as a folder. Create subdirectories to organize your HTML files by topic. For example, you might have several subdirectories, including one each of the following: forms, graphics, a newsletter, etc.
Give users cross links

Users should be able to move from one major page to another without having to go back to your home page. Put cross links to all your major pages at the bottom of all major pages.
Don't create gratuitous graphics

Graphics are one reason for the interest in the Web by both publishers and readers. Definitely include graphics. The Web version of a document should contain the same graphics the printed version does. However, do not overuse graphics. Blinking text and other decorations are only distractions that get in the reader's way. Background colors and textures are strongly discouraged, because of additional download time. If you cannot avoid backgrounds, think very carefully about the colors and textures you choose and the effects of those colors and textures on the readiblility of the text.
Don't create dead end links

Readers can get discouraged from returning to your pages when those pages are filled with empty links with grand labels, such as Descriptions of All Classes.
Make hot text meaningful

A page of click here links do not help readers easily locate the information they want. See examples of alternatives below.(don't click the links they don't work)

* Bad: To learn to publish, click here.
* Good: To learn to publish, see Learning to Publish. (avoid this redundancy)
* Better: To publish in Web Central, see Learning to Publish.

* Bad: For information on HTML, click here
* Good: For information on HTML, see Learning HTML
* Better: See Learning HTML for more information.


Using FTP

This document describes the method(s) necessary to exchange files through FTP. You must know the username and password for the account you plan to access.

If you have trouble accessing your account send email to
Accessing your files through FTP:

1. First your computer (Mac or FTP) must have internet access. This needs to be provided by a network to which your computer is connected, or to a dial-up internet provider(ie. AOL, Compuserve or local internet provider).

2. Next you must acquire FTP software:

* If you are running Windows 3.1, Windows 95 or Windows NT, you can use a program called WS_FTP LE, which can be downloaded through

* If you are using Macintosh, you may want to use Fetch.
To download it, go to

* Firefox FTP is a free, secure, cross-platform FTP client for Mac and PC

3. Connect to the Student Affairs Web Server through FTP.

Regardless of the FTP software you use, there are four things that must be specified before (or while) connecting.

1. You must supply the server address:

2. You must supply your provided FTP username.

3. You will need to supply the password for your account.
Note: The password is case sensitive where the username is not.

4. You will be put into your directory. If you are not, type cd\yourdirectory

4. Depending on your account type, you may need to change directories to access the desired files. Both WS_FTP LE and Fetch will allow you to double-check on the listed directory name to open it (in some few cases you may see directories that you cannot open). Once you see the files you wish to access you can basically either "GET" or "PUT." Most Mac and Windows based FTP software have graphical representations of the get and put commands.

Get - refers to transferring a file from the server to your machine.

Put - refers to transferring a file from your machine to the server.


UCSB Student Affairs Web Server Disclaimer

Notice: The UCSB Student Affairs Division provides these pages as a service. Only information that has been properly reviewed and cleared for dissemination will be published on the Student Affairs Web Server. Student Affairs departmental heads and student organization designees are responsible for reviewing, clearing, and maintaining information posted on official pages. The page Developer is ultimately responsible for page information. Information on the Student Affairs Web Server must be both accurate and current, and represent the University of California and the Student Affairs Division in a professional manner. The Student Affairs Web page Developers are responsible for following university policies and Local, State and Federal laws.

By using this service you acknowledge that the divisional webmaster has the right to audit your site for content, and may force changes at his discretion to enforce university policy and ensure that the all content is in the best interest of the division.