Developers

• Welcome
• Register

• Developers Web
• Developers Web Home
• Changes
• Topics
• Index
• Search

• TWiki Webs
• Developers
• Know
• Main
• Sandbox
• TWiki

Pages with missing content:

• sitemap.html -- Removed; we're not there yet. -- JamesGallagher - 01 Jul 2004
• about/people.html: much work needed. Removed until improved -- JamesGallagher - 01 Jul 2004
• About: What we have there is pretty lame... Peter will write this.
• contact.html -- Done -- JamesGallagher - 07 May 2004
• Developers: This is about as useless as content can get... Updated; much better -- JamesGallagher - 01 Jul 2004

Actions once the pages are installed on OPeNDAP.org In progress...

• Add access stats!! -- JamesGallagher - 12 Jul 2004
• Find/Fix test.dods.org --> www.opendap.org Mostly done; the latex docs still contain some references to test.dods.org. The hlx and css files are correct now, so we need to re-generate the HTML -- JamesGallagher - 02 Jul 2004
• Setup ps/pdf files on some ftp site (ftp.opendap.org?): I created CNAMES for ftp.opendap and mail.opendap. They reference dcz.opendap. We should keep the ftp on Unidata for now.-- JamesGallagher - 02 Jul 2004
• Run nightly link checks: The check_link program is installed and I've run it once. We should not run it every night... -- JamesGallagher - 02 Jul 2004
• What are we going to do about the mail lists? What about searching the mail lists? Keep this at Unidata. -- JamesGallagher - 02 Jul 2004
• Maintain Unidata as ftp/http site for source and binaries? Yes, I think we should (JamesGallagher - 22 Apr 2004).

Other fixes to the latex docs

• Edits to the tex files:
  1. Change to PDF files (from PS and PDF) and set up something on opendap.org. Also change the pslink text. But, we must make sure to use ps2pdf and pdflatex to build those PDF files (pdflatex makes blank figures from \psfig). -- JamesGallagher - 01 Jul 2004
  2. Change dates to CVS dates.
  3. Look for test.dods.org and unidata.ucar.edu in URLs; replace with opendap.
• Organize the dtx/ins files in /latex and update the Makefile so it works. Make user all the needed files are in CVS and no generated files are.
• Uniform (grey/black arrows) navigation on the html The hlx files are fixed, we need to re-generate the docs. -- JamesGallagher - 02 Jul 2004
• check \xmlsym use; I can't get it to work: Ignore -- JamesGallagher - 02 Jul 2004
• There's some documentation we're not using (e.g., server/cat-html, server/freeform/ff-html). Why? At a minimum, add a note to the directory's README.
• We should look over the stuff in /archive/design and see what's usable. Move those into /design.

Notes:

• Run html 'tidy' on the files as we edit them. This cleans them up and finds some common syntax errors.
• Use the Validate link at the bottom of a page after editing.

Layout

(updated -- JamesGallagher - 16 Apr 2004)

• opendap_web_pages.png:
  

-- JamesGallagher - 24 Apr 2004

Issues to resolve...

• CSS issues
  1. Browsers -- Resolved: We won't try for complete backward compat.
  2. Masthead logo -- Resolved: New, scaled logo fits default.css exactly, requires no scaling by browser thus loads fast (and transmits more quickly).
  3. 'Submit' text -- Resolved, fixed css.

• Download:
  1. Design. Improve, look at curl, mozilla, ... -- Semi-resolved. Use current design (21 Apr 2004) but add more by-line text and improve 'product' pages.
  2. Where should we store the source/binary files? Suggestion: at Unidata, for time being. -- JamesGallagher - 27 Apr 2004

Management issues:

1. The OPeNDAP Web Site needs to be overhauled, using cascading style sheets (CSS). The current plan is to start with the Mozilla css. Done -- JamesGallagher - 09 Apr 2004.
2. The OPeNDAP Web Site needs to actively handle contributed software, in terms of solicitation, contribution collection, advertisement, and distribution (at least pointing to the source(s)). Partly Done (advert. and distribution) -- JamesGallagher - 09 Apr 2004.
3. Everything related to OPeNDAP should refer to opendap.org, not just in the reference (initial url), but in the dereferenced statement (resulting urls, mailing addresses, user lists, et c.) as well.
4. Paths to the appropriate documentation for a given purpose should be made clear. (See Documentation above.
5. Path to available software should be made clear.
6. All running software should be included clearly on the web site.
7. I think that the path to the data set list needs to be more prominent. PeterCornillon 4/16/04 -- Done (it's now linked directly from the front page) -- JamesGallagher - 27 Apr 2004

I've added the following list. We've planned on making the transition on 16 April. -- JamesGallagher - 09 Apr 2004 -- Note tranisition is now set for early May. -- JamesGallagher - 27 Apr 2004

• I propose that we use the bug database to track non-trivial changes to the web pages. An example of a trivial change is a spelling mistake. Numbers 3-6 above are non-trivial changes. Comments?
• Before we can address non-trivial changes, we must get the current pages functioning correctly. (I will work on this up to the 16th.) This means:
  1. Fixing broken links
  2. Adding new content where I/we started and left a note to continue later
  3. install a page at undata.ucar.edu/packages/dods that will refer browsers/people to the new pages. Yuan & Ethan agreed this is the way to go, with the possibility of looking at teh logs to see if people come into the pages at places other than the main page. If so, we'd put forwarding references there. Initially these references would be text. At some point (2 weeks and 6 months are the extremes) we'd replace the text with an HTTP referrer link. -- JamesGallagher - 27 Apr 2004