Re: UI

>>>>> "s" == sfritz  <[email protected]> writes:

  s> slashboxes:
  s> 	featured book
  s> 	quick links
  s> 	CPAN search
  s> 	Poll
  s> 	most popular books
  s> 	most recent books

  >>> no need for that if we have some headlines and short paragraphs, etc. 
  >>> i am not into busy pages like that.

  s> hm, I actually think having a right and left colum is standard anymore?

that stuff makes sense.


  s> I had been wondering about the cover pages thing,  does anyone know how 
  s> that works legally?

good question. i linked to the cover page and didn't copy it. that
should be ok IMO. we can ask legal types at o'reilly and other pubs that
we have connections to.

  s> Also can we get permission to use the camel in the logo?  If not I can 
  s> think of something else, but the camel is my favorite =p

that is easy. as we will be perl.org and not a business, we can get
permission from o'reilly as long as we acknowledge their camel trademark
on the page.

  s> couldn't it be alot simpler and just add a 'ignore reviewer'?

that would be adding that guy to your foe reviewer list.

  >>> book price searching? we could become an affiliate(s) with our cut 
  >>> going to perl.org or YAS. easy way to support the perl community.

  s> how does that work?

my old page does price searching and that isn't hard to do. mine is
b0rken somewhat as it does raw regex parsing of each site (it knows the
layouts and how to find the prices/discounts). the drawback is you have
to update the parse code (mine was simple and table driven) if the book
seller page alters its layout. as for affiliates, that is technically
easy. you join a vendor's affiliate program and they will give you a 15%
commission. you create links to their page for that book (by isbn) and
with your affiliate code. if someone clicks through that link and buys
the book, you get the commission. we would have to work with YAS to
figure out how to join for them and make sure they can take the money
and keep it non-profit, etc. we should talk to lenzo about this. i think
he would love it and it shouldn't be a major hassle.

we wouldn't search all book sites as most are not too perlish nor big
nor techie enough. i did amazon, B&N, bookpool, fatbrain IIRC. we could
add a few others.

some publishers now do E-books and we could become affiliates with them
too.


  >>> keys to telling if a perl book is good? schwern had a couple of neat
  >>> points he always checks for in the index. many perl books fail it. 
  >>> call this page, how to judge a perl book.
  >>>> This sounds like some static content we could simply link of the top 
  >>>> page. Maybe an 'essays' section where we'd put that.  It certainly 
  >>>> doesn't need to be dynamic since we're unlikely to get a lot of 
  >>>> submissions of that sort and we can review them on a case by case 
  >>>> basis.

  s> how do we get the right to post the index?

again, i never copied any pages from a book site. i always linked to
them which is fine AFAIK. now, how to make links to other sites look
good is an issue. i used frames which work but some hate. this is a web
UI/design issue.

  s> what were these points?  (I don't think I saw that thread)

don't remember them. i am sure we could get them and other points from
our readers/reviewers. it would be an interesting page to create.

uri

-- 
Uri Guttman  ------  [email protected]  -------- http://www.stemsystems.com
-- Stem is an Open Source Network Development Toolkit and Application Suite -
----- Stem and Perl Development, Systems Architecture, Design and Coding ----
Search or Offer Perl Jobs  ----------------------------  http://jobs.perl.org