My comment on white themes is that printing out parts of dark-themed websites on paper is not really workable. We can expect people to sometime (rarely though) print part of the documentation. (Besides, white themes are also better rendered when projected on a wall.) Regarding sphinx, I meant that we should probably go for the most adopted documentation system in the Python scientific community. Besides, I largely prefer your mockup to the current look of the web site. Cheers,
On Thursday, January 8, 2015 at 6:41:00 AM UTC-5, Gonzalo A. PEÑA CASTELLANOS wrote: > > Hi Sylvain > > Never too late :), glad you like the mockup... well not really a mockup > that was a screenshot from how the website is looking so far. > > Did not get your comment of white themes and sphinx and all that, could > you clarify please. > > *On another note,* > > Unfortunately I ran out of the time I had allocated to get the website > running for now, so I will put this on hold for at least a couple of weeks > (to a month or 2). > > Hopefully as soon as the github move is complete and some of the initial > headaches solved, then it would be a good time to proceed. > > I would like to ask your (anyone willing to share!) opinion on the > following issues: > > 1. Right now the Website in pelican is built using pure HTML (+ > bootstrap) for the pages not associated to the blog. The blogs are written > in markdown. The documentation of Spyder is in RST (restructured text). > Should we just stick to RST so blog and docs use just that? On the other > hand Markdown is easier and simpler to learn and used ia lot in wikis and > github comments as well. Also there are new projects like this one > http://www.mkdocs.org/ which look interesting, specially for us that > do not (yet?) handle API autodoc generation > 2. Right now there are several paths to take for the documentation > > > - Readthedocs -> works great, webhooks and all... but is offsite and > the look does not follow any of the website... but apparently used by > EVERYONE out there! > - Continue with the current docs and preprocess with sphinx. -> A > custom matching theme has to be adjusted and would allow for hosting > everything in one place... no webhooks > - Use the rst docs already written and adapt them slightly so no > sphinx specific directives are used, and generate the documenation > directly > in Pelican. > > Cheers > > On Monday, 5 January 2015 17:06:20 UTC+1, Sylvain Corlay wrote: >> >> Hi All, >> >> Sorry for coming so late in the conversation. This is great that you are >> tackling the problem of the web site and I really like your mock-up. I have >> a slight preference for white themes, because some people may want to print >> parts of the documentation, which is not possible with dark themes. >> Besides, most of the scientific stack uses sphinx for the documentation. >> >> Cheers, >> >> Sylvain >> >> On Friday, January 2, 2015 5:10:23 PM UTC-5, Adrian Klaver wrote: >>> >>> On 01/02/2015 02:09 PM, Gonzalo A. PEÑA CASTELLANOS wrote: >>> > A preview concept of the new website home page look and feel... >>> > >>> > < >>> https://lh4.googleusercontent.com/-JQ1Kj6maBYc/VKcW3mFmOmI/AAAAAAAC4OM/9BZYyJGJzr0/s1600/preview.png> >>> >>> >>> >>> Looks good. >>> > >>> > >>> > -- >>> > 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 >>> >>> >>> -- >>> Adrian Klaver >>> [email protected] >>> >> -- 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.
