All Esprit projects, actions, working groups and networks are
to maintain a Web home page with the following minimum contents:
A short project description providing an overview of the project, the partners, the objectives and the expected results. A suggested
A more detailed project description in the form of presentation slides. These slides should ideally be produced with commonly used software (such as PowerPoint®) and a
made available for the convenience of your audience.
Many projects will wish to move beyond this and develop more substantial Web server-based resources. In this case your project's home page should have links to all the computer-based artifacts created under the project contract. These would typically include:
the programme of work (technical annex) for the project
published papers and book chapters
dissertations and theses
software and data sets
images, animations and video clips
interactive demonstrations, simulations
talks, speeches and lectures
progress reports and the final report.
You might also consider linking your pages to any maintained by members of your consortium.
All Web documents are created in HTML (Hypertext Markup Language). There are three ways of creating HTML documents:
convert an existing document - text-conversion tools are widely available
produce directly in HTML via a tool/editor for use with a word-processing package
work directly on "raw" HTML.
You may find that you need to use all these methods depending on the availability of existing documents and the type of material included. Most developers of Web resources find that the use of an HTML tool alongside a mainstream word-processing package is the most efficient method. There are also a number of validation tools available to help you check the syntax of the documents you have created. See the
below for links to some useful pages.
Users access the Web via a variety of computers and using many different browsers, though varieties of Mosaicâ¢ and Netscapeâ¢ are most common at present. The same document will appear differently when viewed on each type of platform. Remember to allow for mono as well as colour screens and for access methods ranging from dedicated ISDN lines to slow dial-up modems.
For the above reason, use large graphics sparingly. Small
can greatly enliven a page.
Retain high levels of screen design for the home page and for other key screens which present a project image.
Structure new documents in small chunks and rework existing text documents on this basis.
Ensure top-level or "front" documents are short, with any essential larger documents in the background.
Give all documents meaningful titles.
For maximum compatability between PC and UNIX systems, limit file and directory names to 8 characters, with up to 3 characters for filename extensions. By default, .htm for PCs and .html for UNIX systems are used as the filename extensions for HTML documents.
How documents are designed and produced is a major issue, but how they are managed will be of equal importance in projects making substantial use of the Web. Recognising and resourcing this needs to be a clearly defined task with an appropriate allocation of time and budget. You should consider:
deciding who has ownership of the documents: author, organisation, project?
ensuring that there is collective project responsibility for the Web resources
giving one partner or individual overall responsibility for managing the Web site
providing opportunities for recording accesses, feedback and comments from users
maintaining alternative ways of distributing the documents, as the Web is more heavily used and accessible in some countries and sectors rather than others
ensuring that there is an agreed procedure for monitoring, updating, reviewing, reporting and dealing with faults and responding to users
agreeing a procedure for deleting and updating documents.
Notice: These links point to servers that, unless specifically indicated, are not under the European Commission's control. Please read the
The World-Wide Web Consortium,
, maintains a
advice for authors, webmasters and system administrators
of Web-related frequently asked questions (with answers!)
maintained by Thomas Boutell
covers, amongst many other topics, authoring and server maintenance.
covers skills-levels from the complete beginner to the experienced Web author, and for a quick, no-nonsense tutorial on the fundamentals of HTML, see the National Center for Supercomputing Applications'
Beginners Guide to HTML
. Once you've mastered the basics, check out
Composing Good HTML
by Eric Tilton.
Ken Jenks maintains pages covering
formats for WWW documents
and the variety of viewers available.
Andrew King answers the question: "
What makes a
great Web site?
Thalia's guide for
contains many useful links to other sites and offers an enquiry service.
Text can be greatly enhanced using
, and Yahoo maintain
a list of collections, libraries and archives.
Yahoo also list
various multimedia resources
Webmasters need a policy on handling WWW software agents -
wanderers and spiders
Some thoughts on
producing finely crafted
maintained by Patrick J. Lynch of the Yale Center for Advanced Instructional Media.
The first version of this document was based on section 5.5 of "A Guide to Project Style and Documentation" produced in July 1995 for DG XIII-C3 of the European Commission (
for Education and Training) by Cambridge Learning Systems Ltd (fax +44-1223-311-787), and drew on part 3 of "
Research Priorities for the World-Wide Web
", the Report of the NSF Workshop sponsored by the Information, Robotics and Intelligent Systems Division held in Arlington, VA on 31 October 1994. Thanks to the following for ideas, data and feedback: Anne O'Brien, Antoine Cavaciuti, Marc Fresko, Nick Cook, Pete Jones, Peter Wintlev-Jensen, Santiago Garrido and Tony Gore.
The sites listed in this document, unless specifically indicated, are not under the control of the European Commission. For this reason, the Commission can make no representation concerning such sites to you; nor does the fact that the Commission has provided this listing serve as an endorsement or warranty by the Commission of any organisation or individual either maintaining or providing content for any of the sites listed, or of any services advertised through the medium of such a site. The Commission has not tested any software found on these sites and is not in a position to make any representation regarding the quality, safety or suitability of any software found on them or retrievable from them.