Hello, Arthur and others-- So, what has happened with this? I was quiet on this subject previously because I didn't have much to add, but I thought the proposed design was a big improvement.
I'm writing today because, if anyone is still working on updating the wiki, I have a feature request. Perhaps it's something I could implement--though I haven't studied the code at all. But I thought perhaps it was something that should be discussed a bit. My proposal is, simply, to include a *mandatory* "last-updated" field on every page. I'm getting increasingly frustrated (and BTW, this is by no means specific to Chicken Scheme--it's all over the flipping Internet) at seeing technical and news articles whose relevance to current reality cannot be determined because they are undated. I suppose the theory is that, since it's a wiki, everyone will pitch in to make sure the docs are always up to date. But it should be clear by now that that doesn't always happen. If everything had a date on it, then we would know to be skeptical of a 3-year-old document; or we could reasonably assume that a 1-year-old page is more likely correct than a 3-year-old one. And so on ... PS: regarding the menu font--why not have a fallback[s]? If visitors don't have Noto Sans, they may well have Ubuntu Sans; and if they're using some weird OS and have neither, I'm sure comparable fonts can be found for those other platforms? Or were you using @font-face? On Wed, Jan 8, 2014 at 5:43 PM, Arthur Maciel <[email protected]> wrote: > Dear chickeneers, I promised and I failed: this *is* the last email about > the wiki redesign (unless there is a major problem with it :) > > Following Thomas advice I changed default font to "sans-serif", leaving > "Noto Sans" only for the menu and h1, h2, h3, h4, h5 and h6. It is much more > readable to me now. > > https://dl.dropboxusercontent.com/u/621606/chicken-wiki.tar.gz > > Best wishes, > Arthur > > > > > 2014/1/4 Arthur Maciel <[email protected]> >> >> Thomas, with the feedback of Evan Hanson I realized that in order to set >> the #content top border correctly I have to set the #menu position to >> "relative". This brings back the problem of misalignment og the search box, >> which in my opinion is the worst of the problems (please take a look to Evan >> printscreens attached). >> >> Another try that looks good here is using CSS3 box-shadow. This way we >> have a more 'professional' look, menu and search box properly aligned and no >> border. >> >> https://dl.dropboxusercontent.com/u/621606/chicken-wiki.tar.gz >> >> What do you all think about this new version? I promisse this is the last >> one :) >> >> Best wishes, >> Arthur >> >> >> 2014/1/3 Arthur Maciel <[email protected]> >>> >>> Dear Thomas, thank you for your feedback! >>> >>> I gave up setting the #content border before because there wasn't a >>> solution that worked on all browsers - each one misaligned the border >>> contact between #menu and #container in its own way :) >>> >>> But I agree that no border is as bad as a misaligned border, so I put it >>> back. >>> >>> About the Open Sans... I changed to Noto Sans and I don't expect it to >>> work fine on your browser/OS/system, but using default fonts really look >>> "old style" to me. Maybe other opinions could help us to decide. >>> >>> I would appreciate another look on it if possible. >>> >>> https://dl.dropboxusercontent.com/u/621606/chicken-wiki.tar.gz >>> >>> A Happy New Year to all! >>> Arthur >>> >>> >>> 2013/12/30 Thomas Hintz <[email protected]> >>>> >>>> Arthur, >>>> >>>> On Tue, Dec 17, 2013 at 11:42 PM, Arthur Maciel <[email protected]> >>>> wrote: >>>> > Dear chickeneers, >>>> > >>>> > I messed up a bit with the wiki design and below is a link to a >>>> > sketch. >>>> > >>>> > https://dl.dropboxusercontent.com/u/621606/chicken-wiki.tar.gz >>>> >>>> Thanks Arthur! It looks great overall! >>>> >>>> Design by committee is not always a good idea so feel free to disagree >>>> but I have a few thoughts. >>>> >>>> I think the top of the #content div really should have a border like >>>> the rest of the box. It just doesn't lock your eyes in as well with it >>>> missing. Of course that won't be that easy to do but you could move >>>> the #menu div down a pixel with a higher z-index so it overlaps the >>>> #content box that has a top-border so it still looks right. >>>> >>>> I think the show/edit/history links could use a little more space >>>> between them. They are tricky to easily hit even on a mouse >>>> (non-touch) device. >>>> >>>> Not a huge deal but the open-sans font is fuzzy for me. I've attached >>>> an image of it. Unfortunately fonts are done so differently across >>>> browsers, OSes, and even individual monitors and settings that they >>>> are hard to get looking good on all systems. I think that the common >>>> fonts are often set to work well with most conditions so it may be >>>> better to just use one of them. Or maybe some of the new CSS3 >>>> attributes would help? Again, not a big deal. >>>> >>>> Any ways, looks really nice overall. And feel free to ignore my >>>> suggestions if you disagree. >>>> >>>> All the best, >>>> Thomas Hintz >>> >>> >> > > > _______________________________________________ > Chicken-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/chicken-users > _______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
