New website

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
61 messages Options
1234
Reply | Threaded
Open this post in threaded view
|

Re: Website update

Alex Krolick
On Nov 2 2016, at 5:12 pm, John W. Eaton <[hidden email]> wrote: 

On 11/02/2016 12:32 PM, Oliver Heimlich wrote:


>
>
> On 01.11.2016 02:10, siko1056 wrote:
>> [2]: https://www.gnu.org/software/octave/new/
>
> Nice, some minor remarks:
>
> 1. Without JavaScript, the margin between the menu bar and the content
> is wrong (too small / negative).
>
> 2. Without JavaScript, the menu is invisible on my phone.

Is javascript necessary now? If we can't eliminate it, can we minimize

its use and try to make it so basic things still work even if it is
disabled?


The site is 99% static with links doing most of the work. JS is only used to trigger the dropdown on mobile. On desktop everything should work. I think if you do "request desktop site" on a mobile browser you can browse without Javascript.

> 3. I would not put a link to Matlab on the website.

Agree.


Noted

jwe


The SVG images are a good idea. If anyone wants to do something even fancier as a demo plot, or has any stylistic comments on the axes labels, etc,. suggestions welcome.

--
Alex
Reply | Threaded
Open this post in threaded view
|

Re: Website update

siko1056
Another version:

https://www.gnu.org/software/octave/new/

The Matlab-Link is removed.

Pantxo wrote
Mike Miller-4 wrote
Pantxo wrote
Another minor remark: the plots on the front page all use the Courier font
which looks ... old. Maybe using a modern sans serif font would make them
look more up to date.
Yes, the color schemes are also out of date now. All plots should be
redone using 4.2 and a consistent sans serif font.
Using svg format for the web page would also be a good point:
* it is scalable
* it is the only format that has the grid line transparency right

I tried to reproduce the current website images using qt (it was gunplot right?). I attached the svg images produced using the current dev version of gl2ps [1] (simpleplot.svg, sombrero.svg).

[1] previous versions use the "baseline-shift" attribute for text vertical alignment, which is not supported by firefox and librsvg at least.
The images I didn't do myself, anyway I updated to your versions and added a newer screenshot of 4.2.

Alex Krolick wrote
John W. Eaton wrote
Oliver Heimlich wrote
Nice, some minor remarks:  

1. Without JavaScript, the margin between the menu bar and the content is wrong (too small / negative).  

2. Without JavaScript, the menu is invisible on my phone.
Is javascript necessary now? If we can't eliminate it, can we minimize  
its use and try to make it so basic things still work even if it is  
disabled?
The site is 99% static with links doing most of the work. JS is only used to
trigger the dropdown on mobile. On desktop everything should work. I think if
you do "request desktop site" on a mobile browser you can browse without
Javascript.
I don' t have a solution yet. But found this one https://stackoverflow.com/questions/30714316/make-zurb-foundation-5-top-bar-menu-work-without-javascript-nested-mobile.

Any Ideas?

Best,
Kai
Reply | Threaded
Open this post in threaded view
|

Re: Website update

Alex Krolick

That's a fine solution - we can add a noscript tag with the nav links. Same with the download tabs.


On Thu, Nov 3, 2016, 7:38 AM siko1056 <[hidden email]> wrote:
Another version:

https://www.gnu.org/software/octave/new/

The Matlab-Link is removed.


Pantxo wrote
>
> Mike Miller-4 wrote
>>
>> Pantxo wrote
>>> Another minor remark: the plots on the front page all use the Courier
>>> font
>>> which looks ... old. Maybe using a modern sans serif font would make
>>> them
>>> look more up to date.
>> Yes, the color schemes are also out of date now. All plots should be
>> redone using 4.2 and a consistent sans serif font.
> Using svg format for the web page would also be a good point:
> * it is scalable
> * it is the only format that has the grid line transparency right
>
> I tried to reproduce the current website images using qt (it was gunplot
> right?). I attached the svg images produced using the current dev version
> of gl2ps [1] (
> simpleplot.svg
> <http://octave.1599824.n4.nabble.com/file/n4680475/simpleplot.svg>
> ,
> sombrero.svg
> <http://octave.1599824.n4.nabble.com/file/n4680475/sombrero.svg>
> ).
>
> [1] previous versions use the "baseline-shift" attribute for text vertical
> alignment, which is not supported by firefox and librsvg at least.

The images I didn't do myself, anyway I updated to your versions and added a
newer screenshot of 4.2.


Alex Krolick wrote
>
> John W. Eaton wrote
>>
>> Oliver Heimlich wrote
>>> Nice, some minor remarks:
>>>
>>> 1. Without JavaScript, the margin between the menu bar and the content
>>> is wrong (too small / negative).
>>>
>>> 2. Without JavaScript, the menu is invisible on my phone.
>> Is javascript necessary now? If we can't eliminate it, can we minimize
>> its use and try to make it so basic things still work even if it is
>> disabled?
> The site is 99% static with links doing most of the work. JS is only used
> to
> trigger the dropdown on mobile. On desktop everything should work. I think
> if
> you do "request desktop site" on a mobile browser you can browse without
> Javascript.

I don' t have a solution yet. But found this one
https://stackoverflow.com/questions/30714316/make-zurb-foundation-5-top-bar-menu-work-without-javascript-nested-mobile.

Any Ideas?

Best,
Kai



--
View this message in context: http://octave.1599824.n4.nabble.com/New-website-tp4674179p4680486.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.

Reply | Threaded
Open this post in threaded view
|

Re: Website update

siko1056
In reply to this post by siko1056
Alex Krolick wrote
siko1056 wrote
Alex Krolick wrote
John W. Eaton wrote
Oliver Heimlich wrote
Nice, some minor remarks:  

1. Without JavaScript, the margin between the menu bar and the content is wrong (too small / negative).  

2. Without JavaScript, the menu is invisible on my phone.
Is javascript necessary now? If we can't eliminate it, can we minimize  
its use and try to make it so basic things still work even if it is  
disabled?
The site is 99% static with links doing most of the work. JS is only used to
trigger the dropdown on mobile. On desktop everything should work. I think if
you do "request desktop site" on a mobile browser you can browse without
Javascript.
I don' t have a solution yet. But found this one https://stackoverflow.com/questions/30714316/make-zurb-foundation-5-top-bar-menu-work-without-javascript-nested-mobile.
That's a fine solution - we can add a noscript tag with the nav links. Same with the download tabs.
Another final version accessible without Javascript:

https://www.gnu.org/software/octave/new/

Kai.
Reply | Threaded
Open this post in threaded view
|

Re: Website update

Sebastian Schöps
siko1056 wrote
Another final version accessible without Javascript:

https://www.gnu.org/software/octave/new/

Kai.
Works perfectly and looks nice (tested on macOS on iOS with Safari and Firefox). The color gradient in the SVG is less beautiful than in the previous pixel image but I think we should not mind.

Sebastian
Reply | Threaded
Open this post in threaded view
|

Re: Website update

Alex Krolick
On Nov 4 2016, at 6:18 am, Sebastian Schöps <[hidden email]> wrote: 

siko1056 wrote
> Another final version accessible without Javascript:
>
> https://www.gnu.org/software/octave/new/
>
> Kai.

Works perfectly and looks nice (tested on macOS on iOS with Safari and
Firefox). The color gradient in the SVG is less beautiful than in the
previous pixel image but I think we should not mind.

Sebastian

--
View this message in context: http://octave.1599824.n4.nabble.com/New-website-tp4674179p4680496.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.


Looks good on Chrome on Android and works without JS. Nice!

-- Alex 
Reply | Threaded
Open this post in threaded view
|

Re: Website update

Mike Miller-4
On Fri, Nov 04, 2016 at 17:25:22 +0000, Alex Krolick wrote:
> Looks good on Chrome on Android and works without JS. Nice!

There is something strange with the layout on my system (Firefox on
Debian). The <footer> <section> has a top padding that overlaps the last
line of the paragraph before it. This is most notable on the Donate and
Get Involved pages, where the links at the very end of the paragraph are
almost unclickable, I need to hover over the very top of the characters.

--
mike

Reply | Threaded
Open this post in threaded view
|

Re: Website update

Mike Miller-4
In reply to this post by siko1056
On Fri, Nov 04, 2016 at 02:18:01 -0700, siko1056 wrote:
> Another final version accessible without Javascript:
>
> https://www.gnu.org/software/octave/new/

I see that the Google font css is downloaded from googleapis.com even if
I have the "PT Sans" font locally installed on my computer. Can we paste
the css rules for the font substitution directly into either app.css or
a new css file hosted on gnu.org?

We had this discussion with the css changes to the user manual back in
June and fixed the font declarations so they are all done locally and
will prefer locally installed fonts to downloading any external
resources.

I've also tested the site with w3m (text-only browser) and it's mostly
pretty good. The biggest failure there is the section about how to
install Octave on the main page and on the Download page. The different
platforms appear as a bulleted list, followed by four paragraphs about
each platform with no indication of which paragraph goes under which
heading.

--
mike

Reply | Threaded
Open this post in threaded view
|

Re: Website update

Oliver Heimlich
On 04.11.2016 19:26, Mike Miller wrote:

> On Fri, Nov 04, 2016 at 02:18:01 -0700, siko1056 wrote:
>> Another final version accessible without Javascript:
>>
>> https://www.gnu.org/software/octave/new/
>
> I see that the Google font css is downloaded from googleapis.com even if
> I have the "PT Sans" font locally installed on my computer. Can we paste
> the css rules for the font substitution directly into either app.css or
> a new css file hosted on gnu.org?
>
> We had this discussion with the css changes to the user manual back in
> June and fixed the font declarations so they are all done locally and
> will prefer locally installed fonts to downloading any external
> resources.

As far as I can see we can mirror the css file [1] on gnu.org. There
already are “local” font definitions in the file, which will prevent
downloading the fonts from Google.

One problem is that [1] will deliver different content depending on your
browser (e. g. woff2 for Firefox, woff for IE).

Alternatively, we could use the font library and deliver true type
fonts. Therefore we have to copy the “local” definitions into [2].

Oliver

[1] https://fonts.googleapis.com/css?family=PT+Sans:400,700
[2] https://fontlibrary.org/face/pt-sans

Reply | Threaded
Open this post in threaded view
|

Re: Website update

siko1056
In reply to this post by Mike Miller-4
Mike Miller-4 wrote
There is something strange with the layout on my system (Firefox on
Debian). The <footer> <section> has a top padding that overlaps the last
line of the paragraph before it. This is most notable on the Donate and
Get Involved pages, where the links at the very end of the paragraph are
almost unclickable, I need to hover over the very top of the characters.

--
mike
Mike, I'm afraid, I cannot reproduce the behavior, with or without JS. Can you attach a screenshot?

Kai.

 
Reply | Threaded
Open this post in threaded view
|

Re: Website update

siko1056
In reply to this post by Oliver Heimlich
Oliver Heimlich wrote
On 04.11.2016 19:26, Mike Miller wrote:
> On Fri, Nov 04, 2016 at 02:18:01 -0700, siko1056 wrote:
>> Another final version accessible without Javascript:
>>
>> https://www.gnu.org/software/octave/new/
>
> I see that the Google font css is downloaded from googleapis.com even if
> I have the "PT Sans" font locally installed on my computer. Can we paste
> the css rules for the font substitution directly into either app.css or
> a new css file hosted on gnu.org?
>
> We had this discussion with the css changes to the user manual back in
> June and fixed the font declarations so they are all done locally and
> will prefer locally installed fonts to downloading any external
> resources.

As far as I can see we can mirror the css file [1] on gnu.org. There
already are “local” font definitions in the file, which will prevent
downloading the fonts from Google.

One problem is that [1] will deliver different content depending on your
browser (e. g. woff2 for Firefox, woff for IE).

Alternatively, we could use the font library and deliver true type
fonts. Therefore we have to copy the “local” definitions into [2].

Oliver

[1] https://fonts.googleapis.com/css?family=PT+Sans:400,700
[2] https://fontlibrary.org/face/pt-sans
Mike, Oliver,

Is the required portion within this file https://www.gnu.org/software/octave/doc/interpreter/octave.css ? If yes, can someone of you take the time to make a small diff-patch with http://hg.octave.org/web-octave/file/tip/css/app.css and send it to me by mail, I take care for the rest?

Thanks,
Kai.
Reply | Threaded
Open this post in threaded view
|

Re: Website update

Mike Miller-4
In reply to this post by siko1056
On Mon, Nov 07, 2016 at 05:07:31 -0800, siko1056 wrote:

> Mike Miller-4 wrote
> > There is something strange with the layout on my system (Firefox on
> > Debian). The
> > <footer>
> >  
> > <section>
> >  has a top padding that overlaps the last
> > line of the paragraph before it. This is most notable on the Donate and
> > Get Involved pages, where the links at the very end of the paragraph are
> > almost unclickable, I need to hover over the very top of the characters.
> >
> > --
> > mike
>
> Mike, I'm afraid, I cannot reproduce the behavior, with or without JS. Can
> you attach a screenshot?
Absolutely.

Looking at the Donate page, the first image shows that the pointer is
not able to click the bitcoin hyperlink (pointer1.png).

The second image shows that the Support header is highlighted when
double clicking at this location (pointer2.png).

The third image shows that if the pointer is moved to the very top of
the hyperlink, it can be clicked (pointer3.png).

The fourth image shows the Firefox box model debug tool, showing that
the footer area overlaps with the end of the last paragraph of the page
contents (box.png).

Does that help?

--
mike

pointer1.png (31K) Download Attachment
pointer2.png (31K) Download Attachment
pointer3.png (31K) Download Attachment
box.png (29K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Website update

siko1056
Mike Miller-4 wrote
On Mon, Nov 07, 2016 at 05:07:31 -0800, siko1056 wrote:
> Mike Miller-4 wrote
> > There is something strange with the layout on my system (Firefox on
> > Debian). The
> > <footer>
> >  
> > <section>
> >  has a top padding that overlaps the last
> > line of the paragraph before it. This is most notable on the Donate and
> > Get Involved pages, where the links at the very end of the paragraph are
> > almost unclickable, I need to hover over the very top of the characters.
>
> Mike, I'm afraid, I cannot reproduce the behavior, with or without JS. Can
> you attach a screenshot?

Absolutely.

Looking at the Donate page, the first image shows that the pointer is
not able to click the bitcoin hyperlink (pointer1.png).

The second image shows that the Support header is highlighted when
double clicking at this location (pointer2.png).

The third image shows that if the pointer is moved to the very top of
the hyperlink, it can be clicked (pointer3.png).

The fourth image shows the Firefox box model debug tool, showing that
the footer area overlaps with the end of the last paragraph of the page
contents (box.png).

Does that help?
Thank you Mike, now I got the problem, and yes, I had this problem as well. I didn't try the very last part of the bottom most content links ^^ It should be solved by now.

Kai.
Reply | Threaded
Open this post in threaded view
|

Re: Website update

siko1056
jwe,

I think Octave 4.2 is released by "2016-11-14 10:22". May I upload the new website at octave.org with the corresponding announcement?

Best,
Kai
Reply | Threaded
Open this post in threaded view
|

Re: Website update

John W. Eaton
Administrator
On 11/15/2016 02:24 AM, siko1056 wrote:

> I think Octave 4.2 is released by "2016-11-14 10:22". May I upload the new
> website at octave.org with the corresponding announcement?

Yes, I think it is OK to update the website now.

Thanks,

jwe


Reply | Threaded
Open this post in threaded view
|

Re: Website update

John W. Eaton
Administrator
In reply to this post by siko1056
On 11/15/2016 02:24 AM, siko1056 wrote:

> I think Octave 4.2 is released by "2016-11-14 10:22". May I upload the new
> website at octave.org with the corresponding announcement?

I will post an announcement for 4.2 to the mailing lists soon, probably
later today.

Could you also provide instructions for how to update the web site?

Thanks,

jwe




Reply | Threaded
Open this post in threaded view
|

Re: Website update

siko1056
John W. Eaton wrote
Could you also provide instructions for how to update the web site?
They are available from https://www.gnu.org/software/octave/README.md

Best,
Kai.
Reply | Threaded
Open this post in threaded view
|

Re: Website update

Sebastian Schöps
Thanks to Kai and Alex (and who else contributed). The result is great!

Sebastian
Reply | Threaded
Open this post in threaded view
|

Re: Website update

siko1056
Sebastian Schöps wrote
Thanks to Kai and Alex (and who else contributed). The result is great!
Thanks =) The documentation is also updated and the website points to it by now using the usual URLs.

http://octave.org/doc/interpreter/ == https://www.gnu.org/software/octave/doc/v4.2.0/
http://octave.org/octave.pdf == https://www.gnu.org/software/octave/doc/octave-4.2.0.pdf

Kai.
Reply | Threaded
Open this post in threaded view
|

Re: Website update

John W. Eaton
Administrator
In reply to this post by siko1056
On 11/15/2016 03:10 PM, siko1056 wrote:
> John W. Eaton wrote
>> Could you also provide instructions for how to update the web site?
>
> They are available from https://www.gnu.org/software/octave/README.md

Thanks.

I was looking to update the community news page and noticed that it is
now automatically generated from some other source (I'm still not sure
exactly where, as I don't completely follow the dependencies yet).

In the README.md file, I see

   The Octave News are currently very widespread
   (and **individually maintained!**) at:
   - https://www.gnu.org/software/octave/ (excerpt for the start page)
   - https://www.gnu.org/software/octave/news.html (some archive)
   - https://www.gnu.org/software/octave/community-news.html (excerpt
for the
     Octave GUI)
   - https://www.gnu.org/software/octave/fixes-4.0.x.html (here are many
more
     to come!)
   - http://wiki.octave.org/GNU_Octave_Wiki#News (some excerpt, anyone
can edit)

I agree that it is usually undesirable to have multiple independently
maintained sources for the same information.

However, I wouldn't really count the news item on the wiki, at least as
it currently exists, since it simply mentions the release.  Probably the
wiki news item should just point to the NEWS page on the web site.

Also, I would like to maintain the community news page separately from
the  other news.  It is really only intended to be displayed in the GUI.
  There don't need to be any other links to it and it may be used to
pass along information to users that doesn't belong on the NEWS page of
the web site.

For the GUI to display the community-news.html file, the serial number
in the header must be incremented (yes, I probably should have made a
note of that in the .in file).  As far as I can tell, that hasn't
happened for the current release, so people who have existing
installations of Octave probably haven't seen the release announcement.

To fix that, I modified the file _layouts/community-news.html and
executed the jekyll build command and it seems to have updated the
_site/community-news.html file.  Then I updated the CVS directory and
compared my newly generated _site/community-news.html file with the one
in the CVS archive.  There were more differences than just the serial
number (see the attached diffs.txt file).  Why is that happening?  Is it
a difference in the version of tools?  I'm using a Debian system and it
looks like I have Jekyll version 3.1.6+dfsg-3.

Even though updating the web site is just a single command, maybe it
would make sense to have a Makefile for that?  Also, to deploy the web
site requires a lot more complicated stuff that could probably go in a
Makefile rule.  At least for me, it's much more obvious to look in a
Makefile for rules about building something than to search for a list of
commands to copy and paste to execute.  Maybe we could even ignore the
fact that we have to use CVS if we used a Makefile rule to do the deploy
step.  It could checkout to a temporary directory, update the files,
commit changes, and delete the temporary directory.

jwe


diffs.txt (3K) Download Attachment
1234