Hi,

I agree with Gonzalo that pointing to some generic site is of no much help. Besides, I was the one who suggested him to use Pelican because we need something easy to build from simple sources, instead of something really beautiful (using templates and bootstrap themes) that afterwards be hard to update.

I like the design showcased by Gonzalo but I have some suggestions:

1. I'd like to see more content on the front page. For inspiration I can cite:

http://www.wolframalpha.com/pro/
https://enterprise.github.com/

Not all content has to be in the main page, but at least the more relevant features (Editor, Variable Explorer, etc) would be fine :-) Else the site seems too "naked" :-)

2. Above the banner I'd like to see something like there is in old site: the Spyder logo and some text about its usefulness.

3. As Anatoly mentioned eariler, perhaps using red for buttons would be a better match with Spyder logo. That's what I tried to with the old site.


I also agree with Gonzalo that the purpose of the new website should be to attract new users. For developers is that we are moving to Github. It would also be better for them to improve our docs.

Finally, I think using rst for the docs and markdown for the new site and blog is fine. I don't expect huge amounts of content coming to the blog, and markdown is easy enough for people to get used to it quite easily, while rst has its quirks.

Cheers,
Carlos

El 11/01/15 a las 13:33, Gonzalo A. PEÑA CASTELLANOS escribió:

@tectonik


First and foremost: I am not a website designer, I am a Civil Engineer

Second: If you see a design that you subjectively or objectively like then point me to it and then perhaps I can replicate it, otherwise the site will remain mostly as showcased. Pointing to a general site with stock designs serves me no purpose, if you have a clear idea of what you would like to see, then please point to it.

 I thought that scientific community makes
decisions for IDE mostly on objective criteria, such as features,
usability, openness and fitness for particular task (including price
and integration/extensibility) rather than web site design.

A lot of people tend to thinks academia is an objective and proactive environment... reality check it is not like that and whatever works on the outside world has its own twisted equivalent in academia.

Before developers, people are users, and users are attracted with nice looking things... website, interface etc...

--
You received this message because you are subscribed to the Google Groups "spyder" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
"spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.

Reply via email to