Help me build a better site for Redline Smalltalk

gistfile1.txt

Hi,

I'm working on making the experience with redline.st much better. To do that, I need your input. 
If you could either comment on this gist with your answers to the questions below or drop me 
an email at sean@monkeysnatchbanana.com, I'd really appreciate it.

* When you arrive at the website for a programming language that you don't currently use 
  what do you immediately want to know? What are the questions you wanted answered before 
  you do any digging through the site?

* After you've gotten the initial information, what additional information do you want to be 
  easy to find?

* What information that normally appears on most programming language websites do 
  you think is undervalued and not given enough prominence? 

* What information that normally appears on most programming language websites do you 
  find doesn't provide much value?

* Anything else you would care to share that isn't addressed above?

Hello,

I like the way the ruby on rails website has been organised (okay not a language, but a platform). They have four big icons with titles: "get excited" (screencasts and elevator pitch), "get started" (getting started quickly), "get better" (improvers and more detailed reference material), "get involved" (material for contacting the community)

I think screencasts are more useful with Smalltalk than most other languages given that it's such an interactive environment. It's easy to write very wordy explanations of what to do when you just need to see it.

As redline matures, I would love to see the website developed in redline + preferred web framework (e.g., seaside, iliad).