FoafProjectHomepageNotes
From FOAF
Contents |
[edit] Foaf Project Beta Website Issues Page
current status: open
[edit] Missing Content!!! (Most Important Issue -- site cannot go live w/out the following)
Note: Be sure to also fill in the "related articles" at the bottom, even if, for now, they need to point to external resources
[edit] You
* Intro Article - edit. * FAQ - Edit (for stable version) * Internationalization - what languages are available? Outside resources? What to link these to? * Join - Edit, update.
[edit] The World
* Directories - Write * tools - Write
[edit] Us
* events/meetings - pg doesn't exist * About - Write * Trust - Write * Friends of foaf - Write
[edit] Them
* Intro page - Write
[edit] Weblog
[edit] We must have something in every section for the software to work right
* You - This article should be deleted and resubmitted by danbri (who wrote it) with the code parts fixed. http://www.foaf-project.org/~nicole/danbri-test/weblog/index.php?p=8 * The World - Write * The Web - Deal with comment spam issues. * Them - Write * Us - Should the article about Blindless be here?
[edit] Old list of Missing Content (to integrate)
* foafInternational - summary of multilingual resources avail. * Faq cleanup - http://rdfweb.org/topic/FAQ * ShortFAQ aims to be a cleaned up version of the FAQ for inclusion with the website. Probably best to have a "This didn't answer your question? Type it here, and send it to our mailing list!" at the bottom as well. * How to get your foaf file noticed. * http://www.livejournal.com/users/crschmidt/263380.html -- draft. * Aggregators page - Including what to call aggregators so that regular users will know what it means. Maybe "directories"? Yellow pages... * About the foaf project - http://www.xml.com/pub/a/2004/02/04/foaf.html is there now, but we need something that can be pulled inside the foaf project domain. * file:///c:/Documents%20and%20Settings/Nicole%20Sullivan/My%20Documents/My%20Webs/foaf/us/history.html - edit. * Weblog - Them article * Weblog - The World article
[edit] To Do's
* content and links checked by someone familiar with the foaf community * one article in each of the content areas of the weblog. The only one which has nothing is the world. But "them" needs to have the article on spam put in its category and the filler article I put in the "you" section needs editing. Also, all the filler entries like "Hello world!" and "First Post" need to be deleted. * A note added to the search page explaining why foaf-project.org searches won't return many results yet. * fix CSS for comments page of weblog. The text boxes look squished together and the comments headings are indented strangely. * fix CSS for paragraphs, add top and bottom margin. * fix CSS for navigation, a:active is a funny burnt orange color. * fix CSS for visited links. The gray color isn't obvious enough, but I don't like having no change. Will look into darker blues and greens. dashed underlining looked dumb. * make weblog posts automatically belong to upper categories. i.e. if article "blindless" is in "stories" under the "us" category it should also belong to "us". * make all the categories show up on the blog, why can we see only general and news? * accessibility checks, can we make AAA? Also, add a site information page which explains the accessibility features.
[edit] Testing
[edit] Browsers it looks OK under (please add browsers to this list):
* IE6 - Windows * Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 * Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 * lynx * IE55SP2_NT - FOUC, but otherwise good * IE501SP2_NT * IE3_NT - All of the content none of the style, add hr tags to delineate the sections
[edit] Browsers it does NOT look ok under (please add browsers to this list):
* IE401_NT - I think my testing copy of IE4.01 might be off. I haven't found a site that looks normal on it, even ones that did before my last reinstall. Can someone recheck this browser for me?
[edit] Notes:
* http://rdfweb.org/pipermail/foafsite-webmasters/2004-September/000021.html nicole's todo list- an email to webmasters about to-do's before the launch
[edit] Notes from the IRC meeting:
The Agenda for the Meeting: http://rdfweb.org/pipermail/rdfweb-dev/2004-October/013816.html, and the IRC log: http://www.ilrt.bris.ac.uk/discovery/chatlogs/rdfig/2004-10-13.html
* mortenf - h1 (foaf project) to be linked, dan suggested making the entire upper area a link done: In IE it is the entire upper area, in Firefox it is the text boxes and icon. Can't seem to get it to be exactly the same. * jibberjim - found the font rather small, CSS setting that's below 80 is just too small to read - probably better on this screen, but I just couldn't read it. fixed: larger now * mortenf - in firefox, it seems the vertical "line" splitting foaf and project seems to move a bit when navigating around. Response: This is related to scroll bar/no scroll bar from page to page. * Talliesin I disagree with the alt text "Blue, yellow, red, and ____ smileys - foaf logo" that seems more of a description than an alternative. You could go with dan's suggestion of having the whole top section link, and then have the logo's alt be "" fixed: changed to "foaf logo - back to welcome page" * gk - It's not obvious the FOAF logo links to the home page fixed: better alt text should show in the tool tip. * gk - I think the home page could do with a few words about what FOAF is about. Any suggestions where this kind of text can be found? We may want to keep that on the developer page (the web) vs the user site (you) so that the info can be tailored to the specific user group * bengee - FOUC, http://www.bluerobot.com/web/css/fouc.asp Flash of Unstyled Content fixed: added link element to print css * reto - For accessibility I think the navigation should be at bottom with a hidden link to it at top. Response: I think we will do the opposite and offer a hidden link at the top to both the main navigation, secondary navigation, and content. * Talliesin - Speaking of the logo, having a section about the logo would be nice I think (and could also serve as a longdesc in places where the logo is used). Do you want to write it? Or maybe know where there is something already written? We plan to add a site information page which covers access features, details of navigation, etc. This could fit nicely there. * reto - I'd like to see "web" renamed and merged with "welcome", to much clicking to get the spec. Talliesin - Could we reuse the web submenu on the welcome page - to fulfil reto's request? Response: Since this is a user site we don't want them getting confused / wrapped up in developer resources. The welcome page is an attempt to balance the needs of two quite diverse groups of ppl who could be looking for foaf info * Talliesin - move to rss 1.0 rather than (or maybe as well as) 2.0) DANBRI? * bengee - A short explanation of the sections on the welcome page could be helpful. done. * reto - I'm wondering if a planet-foaf woudn't be better than a blog, aggregating only foaf-spefic blogs. If foaf-particpator would have all their foaf-specific rss-feeds I wouldn't know when to use the project blog. Define the purpose of each piece of the foaf world. Response: It is on the agenda to move the planet-foaf site into the look and feel of the main site. We just don't want to delay going live --longer than we have already anyway :) * iand - I offered for danbri to host the foaflet icons DANBRI? * Capt Solo - click those nice thumbnails and get somewhere, mortenf - hopes the thumbnails will be scutter-driven at some point... * Why are only some of the categories showing in the weblog?
[edit] FAQ:
Q: Will wiki also be styled in similar fashion?
A: The wiki will be simillar but pared down, more developer less fuss. It will be based the offsite page, http://beta.foaf-project.org/offSite.html.
Q: what about translations?
A: There will be an international foaf section that includes translations. Probably not before the initial launch, but shortly afterward.
Q: Are the index.html URIs an artefact of working with files rather than a webserver? Will we lose them in the the final cut?
A: How to keep the pages organized is still under discussion. It will likely depend on the system used for maintaining these pages.
Q: And can the blog have RSS1.0 instead of RSS2.0 so that it'll be RDF?
A:
Q: Do we have a launch date?
A: 1 November. Unfortunately we are not going to make the Nov 1 deadline, we still need a fair bit of content written and some RSI issues kept me from my computer last week. Expect to be working steadily until 15 November.
* have pointers to rdfweb-dev email, IRC chatlog, weblog etc. pages where the issue was originally raised - if only I knew how to find these things?!?! * briefly summarise the problem, oportunity, confusion etc. * link to test cases, examples etc where possible * have an issue owner (who has acknowledged this role in some archived forum)
When an issue is resolved or its status w.r.t. the FOAF spec changes, that changed state of affairs should be documented somewhere less transient than the wiki. See IssueTracker for more notes on issue management conventions.
CategoryOrganizationalPage
