Hello to all. I'm a member of this non-profit organization:
[1] http://www.hitagroup.org/
For several reasons, we need to move our web host and I got volunteered.
The person who created it is no longer available; we don't have FTP
access (at least for now); and I don't know ASP, only some HTML. So I
started to convert the pages to that format.
I started by saving an HTML version of the home page, and cleaning it
using NotePad2, a Notepad replacement with some simple display schemes
for HTML). Next I validated it at validator.w3.org. All the errors are
gone except one. My HTML version is available at this location for the
time being (most of the other pages are not loaded yet):
[2] http://www.marzolian.com/hitahome.html
There's going to be some more reorganization, but here is my first group
of questions.
1. On the original home page (No. 1), when viewed in IE, the navigation
buttons at the top are blue ovals, distributed across the whole page.
In Firefox they're truncated ovals and go only partway across. For my
HTML-only version (No. 2 above), the buttons are truncated whether I use
Internet Explorer or Firefox.
I want the buttons at the new site (written in HTML, and using any
browser) to look like the ovals at the original site (viewed in IE). How?
2. Why are there lines around some sections of the page, when viewed in
IE, and not in Firefox?
3. There are about 16 tables in this page. They display fine, but are
they necessary? Is it worth replacing them, and if so, with what?
4. Some of the other pages are like this one, but simpler. We want to
keep the top section (skyline and navigation buttons) the same on each
page. What's the best way to maintain the top section, edit it at a
single location and have the changes passed when visiting the other
pages? I want to avoid making the same changes 5 or 6 times.
5. The association doesn't have time for me to learn how to reproduce
the member database. So that part will be contracted out. Based on
recommendations from two people who were in a similar position, I plan
to hire a developer to use PHP and MySQL and duplicate the functionality
of this database.
A visitor should be able to search the database for a translator or
interpreter, each association member should be able to edit his/her own
information, and an administrator should be able to edit all
information. Most of the database will be public, but there are some
exceptions; for example, a visitor should not be able to see whether a
member has paid his/her annual membership fee, and some other minor points.
What else do I need to tell a developer, so that he can provide a good
estimate? We keep the member information in text and database format,
in addition to the web site.
6. Any other suggestions for places to ask these types of questions?
Steven