Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.1-incubating
    • Component/s: website
    • Labels:
      None

      Description

      gasp, this will be a HUGE issue, but we really need to start working on:

        Activity

        Hide
        Sean Kelly added a comment -

        Just a quick note: at 1024×768, the information that a user would otherwise have to scroll to see is (a) the other half of the Incubator Disclaimer and (b) the site map—neither of which are terribly interesting.

        That's just on the home page.

        On all of the inner pages, I set up a slimmer blue banner, and 768 vertical resolution is enough to get you all the content and into the site map on the bottom on the majority of pages—without scrolling.

        Do we need to seriously cater to the 800×600 (l)users?

        Show
        Sean Kelly added a comment - Just a quick note: at 1024×768, the information that a user would otherwise have to scroll to see is (a) the other half of the Incubator Disclaimer and (b) the site map—neither of which are terribly interesting. That's just on the home page. On all of the inner pages, I set up a slimmer blue banner, and 768 vertical resolution is enough to get you all the content and into the site map on the bottom on the majority of pages—without scrolling. Do we need to seriously cater to the 800×600 (l)users?
        Hide
        Chris A. Mattmann added a comment -

        Hey Sean (H.): when you get a chance it would be good to see a mockup of what you're proposing so we could take a look. I do think the banner image and top content are huge, but I'm torn as to whether they are too huge or not. Anyhoo, check out this page: https://cwiki.apache.org/confluence/display/OODT/How+to+Publish+the+OODT+Web+Site to see how to mock up the site on your own. You could try messing with the CSS locally to see if you can make a demo of what you're thinking then post it on your people.a.o account so others can see...

        Show
        Chris A. Mattmann added a comment - Hey Sean (H.): when you get a chance it would be good to see a mockup of what you're proposing so we could take a look. I do think the banner image and top content are huge, but I'm torn as to whether they are too huge or not. Anyhoo, check out this page: https://cwiki.apache.org/confluence/display/OODT/How+to+Publish+the+OODT+Web+Site to see how to mock up the site on your own. You could try messing with the CSS locally to see if you can make a demo of what you're thinking then post it on your people.a.o account so others can see...
        Hide
        Sean Hardman added a comment -

        Love the site layout and the banner graphic. My only issue is that the banner and the header together are huge. Would it be possible to slim them down so more of the content is above the fold?

        Show
        Sean Hardman added a comment - Love the site layout and the banner graphic. My only issue is that the banner and the header together are huge. Would it be possible to slim them down so more of the content is above the fold?
        Hide
        Chris A. Mattmann added a comment -
        • I'm calling this done.

        I was able to successfully run through:

        https://cwiki.apache.org/confluence/display/OODT/How+to+Publish+the+OODT+Web+Site

        I set up a staging site to show the final product (which has already been SVN co'ed to people.a.o:/www/incubator.apache.org/oodt/):

        http://people.apache.org/~mattmann/apache-oodt-0.1-incubating-site/

        I committed a changelog entry for this in r981273.

        Frickin' awesome job, Sean!

        Show
        Chris A. Mattmann added a comment - I'm calling this done. I was able to successfully run through: https://cwiki.apache.org/confluence/display/OODT/How+to+Publish+the+OODT+Web+Site I set up a staging site to show the final product (which has already been SVN co'ed to people.a.o:/www/incubator.apache.org/oodt/): http://people.apache.org/~mattmann/apache-oodt-0.1-incubating-site/ I committed a changelog entry for this in r981273. Frickin' awesome job, Sean!
        Hide
        Chris A. Mattmann added a comment -

        Some interesting stats:

        a. to run mvn site:site on minotaur:

        [noformat]
        [INFO] ------------------------------------------------------------------------
        [INFO] BUILD SUCCESSFUL
        [INFO] ------------------------------------------------------------------------
        [INFO] Total time: 23 minutes 12 seconds
        [INFO] Finished at: Sun Aug 01 16:48:42 UTC 2010
        [INFO] Final Memory: 251M/802M
        [INFO] ------------------------------------------------------------------------
        [mattmann@minotaur]/home/mattmann/oodt-site/oodt(45):
        [noformat]

        b. to run OODT site publisher tests:

        [noformat]
        mattmann@minotaur]/home/mattmann/oodt-site(33): bin/test
        Running zope.testrunner.layer.UnitTests tests:
        Set up zope.testrunner.layer.UnitTests in 0.000 seconds.
        Running:

        Ran 23 tests with 0 failures and 0 errors in 0.358 seconds.
        Tearing down left over layers:
        Tear down zope.testrunner.layer.UnitTests in 0.000 seconds.
        [noformat]

        c. to run oodtsitepublish: ~1 min

        Show
        Chris A. Mattmann added a comment - Some interesting stats: a. to run mvn site:site on minotaur: [noformat] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 23 minutes 12 seconds [INFO] Finished at: Sun Aug 01 16:48:42 UTC 2010 [INFO] Final Memory: 251M/802M [INFO] ------------------------------------------------------------------------ [mattmann@minotaur] /home/mattmann/oodt-site/oodt(45): [noformat] b. to run OODT site publisher tests: [noformat] mattmann@minotaur]/home/mattmann/oodt-site(33): bin/test Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Running: Ran 23 tests with 0 failures and 0 errors in 0.358 seconds. Tearing down left over layers: Tear down zope.testrunner.layer.UnitTests in 0.000 seconds. [noformat] c. to run oodtsitepublish: ~1 min
        Hide
        Chris A. Mattmann added a comment -

        Sean, to me this is good enough to publish right now. There are some broken links that we can run a link checker on before releasing, but I would push this out to people.a.o:/www/incubator.apache.org/oodt...Big +1

        YOU RULE!

        Show
        Chris A. Mattmann added a comment - Sean, to me this is good enough to publish right now. There are some broken links that we can run a link checker on before releasing, but I would push this out to people.a.o:/www/incubator.apache.org/oodt...Big +1 YOU RULE!
        Hide
        Sean Kelly added a comment -

        Draft of the site available at http://216.146.47.22/oodt/

        Feedback appreciated.

        Show
        Sean Kelly added a comment - Draft of the site available at http://216.146.47.22/oodt/ Feedback appreciated.
        Hide
        Chris A. Mattmann added a comment -

        haha i bet! I knew it would be HUGE!

        Show
        Chris A. Mattmann added a comment - haha i bet! I knew it would be HUGE!
        Hide
        Sean Kelly added a comment -

        "this will be a HUGE issue" ... understatement of the year!

        I've been working this all week and still ongoing. This ... is ... freakin' ... huge. (Resist the straight line, folks!)

        Show
        Sean Kelly added a comment - "this will be a HUGE issue" ... understatement of the year! I've been working this all week and still ongoing. This ... is ... freakin' ... huge. (Resist the straight line, folks!)
        Hide
        Chris A. Mattmann added a comment -

        Hey Sean,

        Can you try assigning the issue to yourself now?

        If it works, I think we're in good shape...

        Cheers,
        Chris

        Show
        Chris A. Mattmann added a comment - Hey Sean, Can you try assigning the issue to yourself now? If it works, I think we're in good shape... Cheers, Chris
        Hide
        Sean Kelly added a comment -

        Great! Thanks for the links.

        And don't worry if infrastructure won't fix the perms—better we have it tracked at all! I don't mind working by proxy.

        Some day, this comment will look awesome.

        Show
        Sean Kelly added a comment - Great! Thanks for the links. And don't worry if infrastructure won't fix the perms—better we have it tracked at all! I don't mind working by proxy. Some day, this comment will look awesome .
        Hide
        Chris A. Mattmann added a comment -

        oh, forgot to include [1] and [2]. Here they are:

        [1] http://www.apache.org/images/feather.gif
        [2] http://www.apache.org/foundation/marks/pmcs.html

        Show
        Chris A. Mattmann added a comment - oh, forgot to include [1] and [2] . Here they are: [1] http://www.apache.org/images/feather.gif [2] http://www.apache.org/foundation/marks/pmcs.html
        Hide
        Chris A. Mattmann added a comment -

        LOL at your comment, Sean. +1 to your approach too. See here [1] for the typical Apache feather logo and this site [2] overall for look/feel guidelines. It seems I don't have enough karma to grant you permissions to assign issues to yourself. I've filed INFRA-2852 for this so hopefully infra@ takes care of it.

        Show
        Chris A. Mattmann added a comment - LOL at your comment, Sean. +1 to your approach too. See here [1] for the typical Apache feather logo and this site [2] overall for look/feel guidelines. It seems I don't have enough karma to grant you permissions to assign issues to yourself. I've filed INFRA-2852 for this so hopefully infra@ takes care of it.
        Hide
        Sean Kelly added a comment - - edited

        An approach for this would likely entail:

        1. Replacing the JPL-specific cruft from the oodt-core parent project with Apache-specific cruft
        2. Developing a script that finds each pom.xml and calls "mvn site"
        3. Assembles some connective boilerplate to link them all together
        4. Reserves a spot for the non-Java code
        5. Publish to http://svn.apache.org/repos/asf/incubator/oodt/site

        If someone could assign this to me, I'd be happy to get started!

        (The "Worklog" section says: "You don't have permission to work on this issue." Bummer.)

        EDIT: Argh. JIRA-old-version fail. Pretend those are numbered steps.

        Show
        Sean Kelly added a comment - - edited An approach for this would likely entail: Replacing the JPL-specific cruft from the oodt-core parent project with Apache-specific cruft Developing a script that finds each pom.xml and calls "mvn site" Assembles some connective boilerplate to link them all together Reserves a spot for the non-Java code Publish to http://svn.apache.org/repos/asf/incubator/oodt/site If someone could assign this to me, I'd be happy to get started! (The "Worklog" section says: "You don't have permission to work on this issue." Bummer.) EDIT: Argh. JIRA-old-version fail. Pretend those are numbered steps.
        Hide
        Chris A. Mattmann added a comment -
        • set component
        Show
        Chris A. Mattmann added a comment - set component

          People

          • Assignee:
            Sean Kelly
            Reporter:
            Chris A. Mattmann
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development