From anna at phplist.com Fri Oct 7 03:27:57 2016 From: anna at phplist.com (Anna Morris) Date: Fri, 7 Oct 2016 11:27:57 +0100 Subject: [FM Discuss] new front page for FM In-Reply-To: <57EE6125.9070701@flossmanuals.net> References: <57EE3D1F.8000407@flossmanuals.net> <76688c3c-0c06-2bf5-8f32-139a109de4f6@phplist.com> <57EE5A12.2030409@flossmanuals.net> <7b7e09e0-d909-989d-0b1d-84ef88cd2899@phplist.com> <57EE6125.9070701@flossmanuals.net> Message-ID: On 30/09/16 13:57, mick wrote: > > On 30/09/16 13:43, Anna Morris wrote: >> ok, I will do the second option :) I also refer to the publication >> system for the manual itself, which has not been officially published yet >> >> >> ax > I see :) > > Where abouts is the working version now? So the manual is at www.phplist.org/manual and the editable version is here: http://write.flossmanuals.net/phplist/_edit/ We have documentation sprint this weekend and so I need to make sure this manual is ready for editing. If I press publish now, what will happen? Does it make a version number? I am keen that the manual as it is now is seen as version 1 and we take a move now to a new version where new chapters and changes will be added > > Thanks > Mick > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net From mick at flossmanuals.net Fri Oct 7 07:54:19 2016 From: mick at flossmanuals.net (Mick) Date: Fri, 7 Oct 2016 15:54:19 +0100 Subject: [FM Discuss] new front page for FM In-Reply-To: References: <57EE3D1F.8000407@flossmanuals.net> <76688c3c-0c06-2bf5-8f32-139a109de4f6@phplist.com> <57EE5A12.2030409@flossmanuals.net> <7b7e09e0-d909-989d-0b1d-84ef88cd2899@phplist.com> <57EE6125.9070701@flossmanuals.net> Message-ID: > So the manual is at www.phplist.org/manual > > and the editable version is here: > http://write.flossmanuals.net/phplist/_edit/ > > We have documentation sprint this weekend and so I need to make sure > this manual is ready for editing. If I press publish now, what will > happen? Does it make a version number? I am keen that the manual as it > is now is seen as version 1 and we take a move now to a new version > where new chapters and changes will be added > We'll probably have to hack this a little with the restrictions that we have with Booktype 1.6's limited versioning. I'm ccing Daniel and Aco so they can fact check this. You are working on a live version at http://write.flossmanuals.net/phplist - Going to publish will allow you to output your different pdf and epub versions and you can run your script to generate your pages at phplist.org >From what I can work out it doesn't seem possible to really hide a book on 1.6. So the best thing to do when you are ready to publish this say "version Oct2016" and want a new space to keep working on your next version is to clone your original to a new book with a new title which shows it's a work in progress. Say "phplist-draft2" When you have cloned it, it's worth making a new major version, so that a record of your original stays. And then you can edit away till you are ready to publish that. And when you are we can delete the one currently at phplist - and rename phplist-draft2 - to take it's place. A bit hacky I know but Booktype 2 I think has proper versioning. Thanks Mick From mick at flossmanuals.net Fri Oct 7 08:34:01 2016 From: mick at flossmanuals.net (Mick) Date: Fri, 7 Oct 2016 16:34:01 +0100 Subject: [FM Discuss] new front page for FM In-Reply-To: References: <57EE3D1F.8000407@flossmanuals.net> <76688c3c-0c06-2bf5-8f32-139a109de4f6@phplist.com> <57EE5A12.2030409@flossmanuals.net> <7b7e09e0-d909-989d-0b1d-84ef88cd2899@phplist.com> <57EE6125.9070701@flossmanuals.net> Message-ID: <02f54e76-de1f-bc68-2999-d25d6880f740@flossmanuals.net> Ps. Let me know if that makes sense. If not I can do the cloning for you. Just give me a ring and I'll get it sorted as I may be away from email for a bit this weekend. Mick On 07/10/16 15:54, Mick wrote: >> So the manual is at www.phplist.org/manual >> >> and the editable version is here: >> http://write.flossmanuals.net/phplist/_edit/ >> >> We have documentation sprint this weekend and so I need to make sure >> this manual is ready for editing. If I press publish now, what will >> happen? Does it make a version number? I am keen that the manual as it >> is now is seen as version 1 and we take a move now to a new version >> where new chapters and changes will be added >> > We'll probably have to hack this a little with the restrictions that we > have with Booktype 1.6's limited versioning. > > I'm ccing Daniel and Aco so they can fact check this. > > You are working on a live version at > http://write.flossmanuals.net/phplist - > Going to publish will allow you to output your different pdf and epub > versions and you can run your script to generate your pages at phplist.org > > From what I can work out it doesn't seem possible to really hide a book > on 1.6. > > So the best thing to do when you are ready to publish this say "version > Oct2016" and want a new space to keep working on your next version is to > clone your original to a new book with a new title which shows it's a > work in progress. Say "phplist-draft2" > > When you have cloned it, it's worth making a new major version, so that > a record of your original stays. > > And then you can edit away till you are ready to publish that. And when > you are we can delete the one currently at phplist - and rename > phplist-draft2 - to take it's place. > > A bit hacky I know but Booktype 2 I think has proper versioning. > > Thanks > Mick > > > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net From tomi at flossmanuals.net Fri Oct 7 11:35:44 2016 From: tomi at flossmanuals.net (Tomi Toivio) Date: Fri, 7 Oct 2016 21:35:44 +0300 Subject: [FM Discuss] new front page for FM In-Reply-To: <57EE3D1F.8000407@flossmanuals.net> References: <57EE3D1F.8000407@flossmanuals.net> Message-ID: So separate language sites would still be needed, just for the pdf and epub files? What about just linking to Objavi: http://objavi.booktype.pro/data/books/audacityopas-en-2016.10.07-20.25.53.pdf and http://objavi.booktype.pro/data/books/audacityopas-en-2016.10.07-20.25.53.pdf And there are a few manuals which are only available in Finnish, so would the Splash page be multilingual? 2016-09-30 13:23 GMT+03:00 mick : > Hi there, > > I've been talking about this on the FM admin but I want to cast the net > a bit wider. > > I've been doing some work on a simple FM splash page to link to manuals > in the new repository. > > It's a work in progress here > http://splash.flossmanuals.net/ > and on gitlab here - https://gitlab.com/mickfuzz/fm_en_splash > > I'm looking for help to finish the adding the text details and creating > images for the books too and advice on the following. > > This is especially true if you are linked to a manual. What should the > short description, keywords and image be? > > This page introduces a way of filtering manuals by broad category, and > beyond Video, Graphics and Audio, I'm not sure how to best categorise > the other manuals in a very simple way so that there is only a handful > of options. Any advice would be great! I'm thinking of resorting to big > catch alls like "Internet", or "Communication". > > Just email back to the list with offers of help. > > many thanks > Mick > > Thanks > Mick > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mick at flossmanuals.net Sun Oct 9 04:53:39 2016 From: mick at flossmanuals.net (Mick) Date: Sun, 9 Oct 2016 12:53:39 +0100 Subject: [FM Discuss] new front page for FM In-Reply-To: References: <57EE3D1F.8000407@flossmanuals.net> Message-ID: <5d986446-ea6f-fc07-1211-36110631d85c@flossmanuals.net> Hi there, I'm doing some work on this for the next couple of hours so if anyone has a spare 30-60 mins you could really help out. I'll be in irc.freenode.net #flossmanuals Tomi, When you mean sites, I think that it would be good to have different pages showing when people go to either http://fi.flossmanuals.net and http://en.flossmanuals.net But I think they could easily share the same codebase and hosting. Linking to objavi isn't optimal as that server is sometimes down and it seems a bit heavy handed to use it to generate files each time someone downloads it. Tomi, why not have a look at the code and have a go at creating data files for the finnish manuals as let's see what we can come up with together. I don't think this will be a bit job. In fact this could be the perfect solution for fi.flossmanuals.net. Thanks Mick On 07/10/16 19:35, Tomi Toivio wrote: > So separate language sites would still be needed, just for the pdf and > epub files? > > What about just linking to Objavi: > http://objavi.booktype.pro/data/books/audacityopas-en-2016.10.07-20.25.53.pdf > and http://objavi.booktype.pro/data/books/audacityopas-en-2016.10.07-20.25.53.pdf > > And there are a few manuals which are only available in Finnish, so > would the Splash page be multilingual? > > 2016-09-30 13:23 GMT+03:00 mick >: > > Hi there, > > I've been talking about this on the FM admin but I want to cast > the net > a bit wider. > > I've been doing some work on a simple FM splash page to link to > manuals > in the new repository. > > It's a work in progress here > http://splash.flossmanuals.net/ > and on gitlab here - https://gitlab.com/mickfuzz/fm_en_splash > > > I'm looking for help to finish the adding the text details and > creating > images for the books too and advice on the following. > > This is especially true if you are linked to a manual. What should the > short description, keywords and image be? > > This page introduces a way of filtering manuals by broad category, and > beyond Video, Graphics and Audio, I'm not sure how to best categorise > the other manuals in a very simple way so that there is only a handful > of options. Any advice would be great! I'm thinking of resorting > to big > catch alls like "Internet", or "Communication". > > Just email back to the list with offers of help. > > many thanks > Mick > > Thanks > Mick > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net > > > > > > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomi at flossmanuals.net Thu Oct 13 08:40:43 2016 From: tomi at flossmanuals.net (Tomi Toivio) Date: Thu, 13 Oct 2016 18:40:43 +0300 Subject: [FM Discuss] new front page for FM In-Reply-To: <5d986446-ea6f-fc07-1211-36110631d85c@flossmanuals.net> References: <57EE3D1F.8000407@flossmanuals.net> <5d986446-ea6f-fc07-1211-36110631d85c@flossmanuals.net> Message-ID: I added some of the Finnish book details here: https://gitlab.com/TomiToivio/fm_en_splash/blob/master/data/book_details.json Errm... How to proceed with this? 2016-10-09 14:53 GMT+03:00 Mick : > Hi there, > > I'm doing some work on this for the next couple of hours so if anyone has > a spare 30-60 mins you could really help out. > > I'll be in irc.freenode.net #flossmanuals > > Tomi, When you mean sites, I think that it would be good to have different > pages showing when people go to either http://fi.flossmanuals.net and > http://en.flossmanuals.net > But I think they could easily share the same codebase and hosting. > > Linking to objavi isn't optimal as that server is sometimes down and it > seems a bit heavy handed to use it to generate files each time someone > downloads it. > > Tomi, why not have a look at the code and have a go at creating data files > for the finnish manuals as let's see what we can come up with together. I > don't think this will be a bit job. In fact this could be the perfect > solution for fi.flossmanuals.net. > > Thanks > Mick > > > On 07/10/16 19:35, Tomi Toivio wrote: > > So separate language sites would still be needed, just for the pdf and > epub files? > > What about just linking to Objavi: http://objavi.booktype.pro/ > data/books/audacityopas-en-2016.10.07-20.25.53.pdf and > http://objavi.booktype.pro/data/books/audacityopas- > en-2016.10.07-20.25.53.pdf > > And there are a few manuals which are only available in Finnish, so would > the Splash page be multilingual? > > 2016-09-30 13:23 GMT+03:00 mick : > >> Hi there, >> >> I've been talking about this on the FM admin but I want to cast the net >> a bit wider. >> >> I've been doing some work on a simple FM splash page to link to manuals >> in the new repository. >> >> It's a work in progress here >> http://splash.flossmanuals.net/ >> and on gitlab here - https://gitlab.com/mickfuzz/fm_en_splash >> >> I'm looking for help to finish the adding the text details and creating >> images for the books too and advice on the following. >> >> This is especially true if you are linked to a manual. What should the >> short description, keywords and image be? >> >> This page introduces a way of filtering manuals by broad category, and >> beyond Video, Graphics and Audio, I'm not sure how to best categorise >> the other manuals in a very simple way so that there is only a handful >> of options. Any advice would be great! I'm thinking of resorting to big >> catch alls like "Internet", or "Communication". >> >> Just email back to the list with offers of help. >> >> many thanks >> Mick >> >> Thanks >> Mick >> _______________________________________________ >> Discuss mailing list >> Discuss at lists.flossmanuals.net >> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net >> > > > > _______________________________________________ > Discuss mailing listDiscuss at lists.flossmanuals.nethttp://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net > > > > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mick at flossmanuals.net Mon Oct 17 02:48:17 2016 From: mick at flossmanuals.net (Mick) Date: Mon, 17 Oct 2016 10:48:17 +0100 Subject: [FM Discuss] new front page for FM In-Reply-To: References: <57EE3D1F.8000407@flossmanuals.net> <5d986446-ea6f-fc07-1211-36110631d85c@flossmanuals.net> Message-ID: Hi there, That's great. I'll merge in your changes. I think the best way to proceed is to get the English focus page up and community tested. And then work out the best way to get a localised "fi" version running as well. That would involve you also creating translated short text descriptions. nice one Mick On 13/10/16 16:40, Tomi Toivio wrote: > I added some of the Finnish book details > here: https://gitlab.com/TomiToivio/fm_en_splash/blob/master/data/book_details.json > > > Errm... How to proceed with this? > > 2016-10-09 14:53 GMT+03:00 Mick >: > > Hi there, > > I'm doing some work on this for the next couple of hours so if > anyone has a spare 30-60 mins you could really help out. > > I'll be in irc.freenode.net #flossmanuals > > Tomi, When you mean sites, I think that it would be good to have > different pages showing when people go to either > http://fi.flossmanuals.net and http://en.flossmanuals.net > > But I think they could easily share the same codebase and hosting. > > Linking to objavi isn't optimal as that server is sometimes down > and it seems a bit heavy handed to use it to generate files each > time someone downloads it. > > Tomi, why not have a look at the code and have a go at creating > data files for the finnish manuals as let's see what we can come > up with together. I don't think this will be a bit job. In fact > this could be the perfect solution for fi.flossmanuals.net > . > > Thanks > Mick > > > On 07/10/16 19:35, Tomi Toivio wrote: >> So separate language sites would still be needed, just for the >> pdf and epub files? >> >> What about just linking to Objavi: >> http://objavi.booktype.pro/data/books/audacityopas-en-2016.10.07-20.25.53.pdf >> >> and http://objavi.booktype.pro/data/books/audacityopas-en-2016.10.07-20.25.53.pdf >> >> >> And there are a few manuals which are only available in Finnish, >> so would the Splash page be multilingual? >> >> 2016-09-30 13:23 GMT+03:00 mick > >: >> >> Hi there, >> >> I've been talking about this on the FM admin but I want to >> cast the net >> a bit wider. >> >> I've been doing some work on a simple FM splash page to link >> to manuals >> in the new repository. >> >> It's a work in progress here >> http://splash.flossmanuals.net/ >> and on gitlab here - https://gitlab.com/mickfuzz/fm_en_splash >> >> >> I'm looking for help to finish the adding the text details >> and creating >> images for the books too and advice on the following. >> >> This is especially true if you are linked to a manual. What >> should the >> short description, keywords and image be? >> >> This page introduces a way of filtering manuals by broad >> category, and >> beyond Video, Graphics and Audio, I'm not sure how to best >> categorise >> the other manuals in a very simple way so that there is only >> a handful >> of options. Any advice would be great! I'm thinking of >> resorting to big >> catch alls like "Internet", or "Communication". >> >> Just email back to the list with offers of help. >> >> many thanks >> Mick >> >> Thanks >> Mick >> _______________________________________________ >> Discuss mailing list >> Discuss at lists.flossmanuals.net >> >> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net >> >> >> >> >> >> _______________________________________________ >> Discuss mailing list >> Discuss at lists.flossmanuals.net >> >> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net >> > _______________________________________________ Discuss mailing > list Discuss at lists.flossmanuals.net > > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net > > > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From mick at flossmanuals.net Sat Oct 22 03:53:09 2016 From: mick at flossmanuals.net (Mick) Date: Sat, 22 Oct 2016 11:53:09 +0100 Subject: [FM Discuss] new front page for FM In-Reply-To: References: <57EE3D1F.8000407@flossmanuals.net> <5d986446-ea6f-fc07-1211-36110631d85c@flossmanuals.net> Message-ID: Hi there, I've added your updates to the site Tomi If anyone has some ideas about how to best do a Finnish page please do chip in. What we are looking to do is to duplicate the work done but translate it to Finnish, and get http://fi.flossmanuals.net to point to this duplication. I'm not sure if this is best done via forking the code or trying to do simple localisation. Thanks Mick On 13/10/16 16:40, Tomi Toivio wrote: > I added some of the Finnish book details > here: https://gitlab.com/TomiToivio/fm_en_splash/blob/master/data/book_details.json > > > Errm... How to proceed with this? > > 2016-10-09 14:53 GMT+03:00 Mick >: > > Hi there, > > I'm doing some work on this for the next couple of hours so if > anyone has a spare 30-60 mins you could really help out. > > I'll be in irc.freenode.net #flossmanuals > > Tomi, When you mean sites, I think that it would be good to have > different pages showing when people go to either > http://fi.flossmanuals.net and http://en.flossmanuals.net > > But I think they could easily share the same codebase and hosting. > > Linking to objavi isn't optimal as that server is sometimes down > and it seems a bit heavy handed to use it to generate files each > time someone downloads it. > > Tomi, why not have a look at the code and have a go at creating > data files for the finnish manuals as let's see what we can come > up with together. I don't think this will be a bit job. In fact > this could be the perfect solution for fi.flossmanuals.net > . > > Thanks > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mick at flossmanuals.net Sun Oct 30 11:27:01 2016 From: mick at flossmanuals.net (Mick) Date: Sun, 30 Oct 2016 18:27:01 +0000 Subject: [FM Discuss] Testing new front page Message-ID: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> Hi there, I'm testing the new front page at http://en.flossmanuals.net/ It would be great to get some feedback and bug reports here if anyone has the time. https://gitlab.com/mickfuzz/fm_en_splash/issues The old site is here http://www.flossmanuals.net One specific thing I need help with is redirects. for example: http://en.flossmanuals.net/turtle-art and http://en.flossmanuals.net/turtle-art/getting-started redirect ok but http://en.flossmanuals.net/turtle-art/ or http://en.flossmanuals.net/turtle-art/getting-started/ don't The rule I'm using is RewriteRule (.*)$ http://write.flossmanuals.net/$1/ [R=301,L] This is probably really easy but I'm clueless on regex Thanks Mick From epirat07 at gmail.com Sun Oct 30 11:50:30 2016 From: epirat07 at gmail.com (Marvin Scholz) Date: Sun, 30 Oct 2016 19:50:30 +0100 Subject: [FM Discuss] Testing new front page In-Reply-To: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> Message-ID: On 30 Oct 2016, at 19:27, Mick wrote: > Hi there, > > I'm testing the new front page at > http://en.flossmanuals.net/ I can't see anything different compared to http://www.flossmanuals.net > > It would be great to get some feedback and bug reports here if anyone > has the time. > > https://gitlab.com/mickfuzz/fm_en_splash/issues > > The old site is here > http://www.flossmanuals.net > > One specific thing I need help with is redirects. > > for example: > > http://en.flossmanuals.net/turtle-art and > > http://en.flossmanuals.net/turtle-art/getting-started > > redirect ok > > but http://en.flossmanuals.net/turtle-art/ > > or http://en.flossmanuals.net/turtle-art/getting-started/ don't > > The rule I'm using is > RewriteRule (.*)$ http://write.flossmanuals.net/$1/ [R=301,L] > > This is probably really easy but I'm clueless on regex > > Thanks > > Mick > > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net From mick at flossmanuals.net Sun Oct 30 12:13:22 2016 From: mick at flossmanuals.net (Mick) Date: Sun, 30 Oct 2016 19:13:22 +0000 Subject: [FM Discuss] Testing new front page In-Reply-To: References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> Message-ID: <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> On 30/10/16 18:50, Marvin Scholz wrote: >> > Hi there, >> > >> > I'm testing the new front page at >> > http://en.flossmanuals.net/ > I can't see anything different compared to http://www.flossmanuals.net > Hmm this could be a DNS propagation thing. Hang 10 and then try. should be 149.20.3.4 not 213.108.108.17 Thanks Mick -------------- next part -------------- An HTML attachment was scrubbed... URL: From epirat07 at gmail.com Sun Oct 30 12:24:46 2016 From: epirat07 at gmail.com (Marvin Scholz) Date: Sun, 30 Oct 2016 20:24:46 +0100 Subject: [FM Discuss] Testing new front page In-Reply-To: <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> Message-ID: On 30 Oct 2016, at 20:13, Mick wrote: > On 30/10/16 18:50, Marvin Scholz wrote: >>>> Hi there, >>>> >>>> I'm testing the new front page at >>>> http://en.flossmanuals.net/ >> I can't see anything different compared to >> http://www.flossmanuals.net >> > Hmm this could be a DNS propagation thing. > Hang 10 and then try. > > should be 149.20.3.4 > not 213.108.108.17 Now I get a "Internal Server Error" for the http://en.flossmanuals.net/ domain (the other one still works fine) > > Thanks > Mick > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net From epirat07 at gmail.com Mon Oct 31 03:41:18 2016 From: epirat07 at gmail.com (Marvin Scholz) Date: Mon, 31 Oct 2016 11:41:18 +0100 Subject: [FM Discuss] Testing new front page In-Reply-To: <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> Message-ID: <0F1F5FC5-245E-457A-B49B-D9C73DEC3435@gmail.com> It is a great improvement over the old page, still here is a list with some minor things I noticed that could be improved, in my opinion: - The different colors of the tabs are confusing, especially the white ones: https://i.imgur.com/B9lARA2.png - It would (maybe) look better if all the boxes for the books had the same height, not sure though. - The tag label backgrounds could be a bit lighter, currently it's quite a dark gray with black text which could be a bit hard to read for some people - The tabs in the boxed have the same problem as the top tabs, especially the white tab looks weird. But overall it looks very nice, great work! On 30 Oct 2016, at 20:13, Mick wrote: > On 30/10/16 18:50, Marvin Scholz wrote: >>>> Hi there, >>>> >>>> I'm testing the new front page at >>>> http://en.flossmanuals.net/ >> I can't see anything different compared to >> http://www.flossmanuals.net >> > Hmm this could be a DNS propagation thing. > Hang 10 and then try. > > should be 149.20.3.4 > not 213.108.108.17 > > Thanks > Mick > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From mick at flossmanuals.net Mon Oct 31 04:18:07 2016 From: mick at flossmanuals.net (Mick) Date: Mon, 31 Oct 2016 11:18:07 +0000 Subject: [FM Discuss] Testing new front page In-Reply-To: <0F1F5FC5-245E-457A-B49B-D9C73DEC3435@gmail.com> References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> <0F1F5FC5-245E-457A-B49B-D9C73DEC3435@gmail.com> Message-ID: <47bd26ed-35b4-468a-e574-443a59faa99e@flossmanuals.net> Great thanks Marvin That's good feedback. I think I'll be able to do those things. I'll wait to see if there's more feedback and add it to the page here https://gitlab.com/mickfuzz/fm_en_splash/issues Thanks Mick On 31/10/16 10:41, Marvin Scholz wrote: > It is a great improvement over the old page, still here is a list with > some minor things I noticed that could be improved, in my opinion: > - The different colors of the tabs are confusing, especially the white > ones: https://i.imgur.com/B9lARA2.png > - It would (maybe) look better if all the boxes for the books had the > same height, not sure though. > - The tag label backgrounds could be a bit lighter, currently it's > quite a dark gray with black text which could > be a bit hard to read for some people > - The tabs in the boxed have the same problem as the top tabs, > especially the white tab looks weird. > But overall it looks very nice, great work! > On 30 Oct 2016, at 20:13, Mick wrote: > > > > On 30/10/16 18:50, Marvin Scholz wrote: >>> > Hi there, >>> > >>> > I'm testing the new front page at >>> > http://en.flossmanuals.net/ >> I can't see anything different compared to http://www.flossmanuals.net >> > Hmm this could be a DNS propagation thing. > Hang 10 and then try. > > should be 149.20.3.4 > not 213.108.108.17 > > Thanks > Mick > > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net > > > > _______________________________________________ > Discuss mailing list > Discuss at lists.flossmanuals.net > http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From mick at flossmanuals.net Mon Oct 31 05:19:27 2016 From: mick at flossmanuals.net (Mick) Date: Mon, 31 Oct 2016 12:19:27 +0000 Subject: [FM Discuss] FLOSS Manuals invites you to BarnCamp 2017, UK In-Reply-To: <0F1F5FC5-245E-457A-B49B-D9C73DEC3435@gmail.com> References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> <0F1F5FC5-245E-457A-B49B-D9C73DEC3435@gmail.com> Message-ID: Hi there, If you haven't been before BarnCamp is a great event in UK that FLOSS Manuals is involved with organising. It is a rural, playful hack event that has it's roots in DIY / tactical media movement and associated Free Software advocacy. All things FLOSS related are welcome, especially those connected with creativity, coding and campaigning. Mike, Charlie and Nor have done some seriously advanced party work in preparing a sign up site. Check it out and sign yourselves up to next year's event at: https://www.barncamp.org.uk/ I said I would make a special effort to invite practitioners who have thing of interest to kids, so please do get in touch with me if you have any questions about what to expect. Thanks Mick From gpittman at iglou.com Mon Oct 31 06:48:08 2016 From: gpittman at iglou.com (Gregory Pittman) Date: Mon, 31 Oct 2016 09:48:08 -0400 Subject: [FM Discuss] Testing new front page In-Reply-To: <47bd26ed-35b4-468a-e574-443a59faa99e@flossmanuals.net> References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> <0F1F5FC5-245E-457A-B49B-D9C73DEC3435@gmail.com> <47bd26ed-35b4-468a-e574-443a59faa99e@flossmanuals.net> Message-ID: <04b13c6d-7a06-584c-5448-834cd86284fb@iglou.com> On 10/31/2016 07:18 AM, Mick wrote: > Great thanks Marvin > > That's good feedback. I think I'll be able to do those things. > > I'll wait to see if there's more feedback and add it to the page here > https://gitlab.com/mickfuzz/fm_en_splash/issues > I'm not having any luck registering for gitlab. Edward Tufte has done a series of books on design, starting with "The Visual Display of Quantitative Information". This first book mostly focuses on showing information in graph or graph-like forms, with a theme that when you do this, you should make sure that the information you want to show is not visually swamped by non-information, particularly considering the way that the eye is attracted and distracted by colors, bold black lines and bars, and so on. He also addresses computer displays, and complains of the tendency for designers to often splash the screen with pretty, multicolored areas, as if the goal is to show a rainbow-like effect on the screen. I think the new design suffers from this to a great extent. The eyes are drawn to the bold orange areas, where there is no useful information. In contrast, the areas which denote the various manuals look bland and uninteresting by comparison, except perhaps for the various project logos. I would echo the problem with the tabs at the top, and personally as a general rule I think it's good to avoid white text on a colored background, due to legibility issues. This is especially true with the white-on-orange tabs. Furthermore, you unintentionally set values to the individual tabs, since some colors attract the eye more than others. I guess that perhaps there is so much orange to provide continuity with prior schemes, or maybe orange is the flossmanuals team color? Judicious use of the orange could still provide this continuity. A scheme that Tufte promotes, when it is necessary to have a lot of information on a page or screen is to use grayscale in areas where you which to create borders, define areas, and to be more clear, you can use shades of gray to show more detail within those areas. Once you do that, the use of colors in areas where there is important information stand out much more and in fact your eye will be drawn to where you want it to go. In general, try to use black text where there is information that needs to be read. Even a dark gray is less legible than black. For example, look how the UpStage logo pops out at you, compared to if it were some shade of gray. Greg From gpittman at iglou.com Mon Oct 31 06:50:54 2016 From: gpittman at iglou.com (Gregory Pittman) Date: Mon, 31 Oct 2016 09:50:54 -0400 Subject: [FM Discuss] Testing new front page In-Reply-To: <04b13c6d-7a06-584c-5448-834cd86284fb@iglou.com> References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> <0F1F5FC5-245E-457A-B49B-D9C73DEC3435@gmail.com> <47bd26ed-35b4-468a-e574-443a59faa99e@flossmanuals.net> <04b13c6d-7a06-584c-5448-834cd86284fb@iglou.com> Message-ID: <3c1a75ed-15ec-5346-c5a7-a024c9d58f0e@iglou.com> On 10/31/2016 09:48 AM, Gregory Pittman wrote: > On 10/31/2016 07:18 AM, Mick wrote: >> Great thanks Marvin >> >> That's good feedback. I think I'll be able to do those things. >> >> I'll wait to see if there's more feedback and add it to the page here >> https://gitlab.com/mickfuzz/fm_en_splash/issues >> > > I'm not having any luck registering for gitlab. > I was finally able to get registered, so I copied the text to a new issue. Greg From mick at flossmanuals.net Mon Oct 31 09:48:05 2016 From: mick at flossmanuals.net (Mick) Date: Mon, 31 Oct 2016 16:48:05 +0000 Subject: [FM Discuss] Testing new front page In-Reply-To: References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> Message-ID: <956dd3a4-bfd2-30a6-2c5e-22a0828b7dd0@flossmanuals.net> The below seems sorted now with trial and error. Mick for example: > > > > http://en.flossmanuals.net/turtle-art and > > > > http://en.flossmanuals.net/turtle-art/getting-started > > > > redirect ok > > > > but http://en.flossmanuals.net/turtle-art/ > > > > or http://en.flossmanuals.net/turtle-art/getting-started/ don't > > > > The rule I'm using is > > RewriteRule (.*)$ http://write.flossmanuals.net/$1/ [R=301,L] > > > > This is probably really easy but I'm clueless on regex > > From mick at flossmanuals.net Mon Oct 31 11:44:08 2016 From: mick at flossmanuals.net (Mick) Date: Mon, 31 Oct 2016 18:44:08 +0000 Subject: [FM Discuss] Testing new front page In-Reply-To: <04b13c6d-7a06-584c-5448-834cd86284fb@iglou.com> References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> <0F1F5FC5-245E-457A-B49B-D9C73DEC3435@gmail.com> <47bd26ed-35b4-468a-e574-443a59faa99e@flossmanuals.net> <04b13c6d-7a06-584c-5448-834cd86284fb@iglou.com> Message-ID: <0ef15074-6c32-5547-2e2e-e874352bb4b8@flossmanuals.net> Hi Greg, This seems like sound advice. I'm wondering would you be able to make some alterations in the css to reflect the kinds of colour changes you would like to see? It would be good to see them side by side to check the effects. nice one Mick On 31/10/16 13:48, Gregory Pittman wrote: > Edward Tufte has done a series of books on design, starting with "The > Visual Display of Quantitative Information". This first book mostly > focuses on showing information in graph or graph-like forms, with a > theme that when you do this, you should make sure that the information > you want to show is not visually swamped by non-information, > particularly considering the way that the eye is attracted and > distracted by colors, bold black lines and bars, and so on. > He also addresses computer displays, and complains of the tendency for > designers to often splash the screen with pretty, multicolored areas, as > if the goal is to show a rainbow-like effect on the screen. > > I think the new design suffers from this to a great extent. The eyes are > drawn to the bold orange areas, where there is no useful information. In > contrast, the areas which denote the various manuals look bland and > uninteresting by comparison, except perhaps for the various project logos. > I would echo the problem with the tabs at the top, and personally as a > general rule I think it's good to avoid white text on a colored > background, due to legibility issues. This is especially true with the > white-on-orange tabs. Furthermore, you unintentionally set values to the > individual tabs, since some colors attract the eye more than others. I > guess that perhaps there is so much orange to provide continuity with > prior schemes, or maybe orange is the flossmanuals team color? Judicious > use of the orange could still provide this continuity. > > A scheme that Tufte promotes, when it is necessary to have a lot of > information on a page or screen is to use grayscale in areas where you > which to create borders, define areas, and to be more clear, you can use > shades of gray to show more detail within those areas. Once you do that, > the use of colors in areas where there is important information stand > out much more and in fact your eye will be drawn to where you want it to > go. In general, try to use black text where there is information that > needs to be read. Even a dark gray is less legible than black. For > example, look how the UpStage logo pops out at you, compared to if it > were some shade of gray. > > Greg From gpittman at iglou.com Mon Oct 31 14:02:59 2016 From: gpittman at iglou.com (Gregory Pittman) Date: Mon, 31 Oct 2016 17:02:59 -0400 Subject: [FM Discuss] Testing new front page In-Reply-To: <0ef15074-6c32-5547-2e2e-e874352bb4b8@flossmanuals.net> References: <4a8ce5db-01f7-eebd-95af-212f3cbf2b68@flossmanuals.net> <2278bab9-f150-a827-2c6d-2262ccdca261@flossmanuals.net> <0F1F5FC5-245E-457A-B49B-D9C73DEC3435@gmail.com> <47bd26ed-35b4-468a-e574-443a59faa99e@flossmanuals.net> <04b13c6d-7a06-584c-5448-834cd86284fb@iglou.com> <0ef15074-6c32-5547-2e2e-e874352bb4b8@flossmanuals.net> Message-ID: <4d9524bd-3d50-97a0-975c-d94da060272c@iglou.com> On 10/31/2016 02:44 PM, Mick wrote: > Hi Greg, > > This seems like sound advice. > > I'm wondering would you be able to make some alterations in the css to > reflect the kinds of colour changes you would like to see? > > It would be good to see them side by side to check the effects. > Here are a few I've tried; maybe you can see if this seems a useful direction to go. In the CSS file fmfr.css I made these changes: body { background-color:#555555; } .bgorange { background-color:#999999; } .cwhite { color:black; } .cwhite:hover { color:#333333; } (just enough change in the hover color to indicate that's what you're doing.) ---and a bit farther down: .bprint { background-color:aliceblue; border-color:darkgrey; color:black; } .bachat { background-color:#31B0D5; border-color:#31B0D5; color:black; } .blire { background-color:#ff7f00; border-color:#ff7f00; color:black; } I can't say that this is the only way to go, but what these do is keep the periphery of the page from screaming at my eyes, and puts the various text areas in the title and buttons in black. Greg