Posts by DavidONE (Page 1 of 2)

OK, as WWIII hasn't errupted yet , I'll try and clarify:

The main links should provide for what visitors want in order of use and priority, so I'd suggest main menu like so:

> FluxBB (with logo) | Home . About . Download . Forum . Wiki . Addons . Development . Contact

1. No one is going to be confused about what they will get from that menu with the Download link. It's completely intuitive. To suggest otherwise is silly. It could also provide links to the addons / extras and then do away with the 'Addons' link.
2. Forum should be up front and available - it's always going to be the primary method of communication for most people. It's a real nuisance to have to go hunting for it.
3. There's some confusion over terminology. I'm not an 'end user'. I (usually) install and customise and hand over to end users. So, 'User Documentation' is misleading. Also, by calling it what is - Wiki - lets me know that it is community-edited. That's a selling point for me. A project that encourages community participation is far preferable to one that tries to keep everything 'under control'.
4. Calling the extras / addons 'Resources' is simply too vague - just on the dictionary definition: *Something that one uses to achieve an objective*. It tells me nothing about what might be there. To repeat: it could be documentation, links to other sites, tutorials, recommended tools, etc. 'Addons' is much more descriptive and covers modifications, plugins, styles and language packs. Just because Mozilla use 'addons' for browser plugins does not mean other projects can't use it.
5. 'Contact' could hold IRC, international forums, etc. - and if you wanted to offer paid support later, it would go here.

Minor details to some, but I think important.

HTH.

EDIT - Also, international forums should be linked from the main forum.

1. "being worked on"? There's already one from the competition a while back - in use now as the favicon. Is that being dumped?
2. 'Download' is pretty obvious - what else would it be but FluxBB?!
3. 'Addons' perhaps? 'Resources' just tells the visitor nothing - it could be documentation, links to other sites, tutorials, etc. - 'mystery meat navigation'
4. A forum is possibly the most frequently clicked link on a project like this - I'd suggest that it should be available as a 'level 1' menu option
5. 'User Guide' suggests only end-user docs. Will it not contain info on installing, upgrading, template creation, plugin dev, core dev, roadmaps, etc.? Call it 'Wiki' or 'Documentation' and it's clear that it's more than just end-user stuff.

Connor and team,

All sounds good to me - good, pragmatic decisions. 

Also, very good to see you're encouraging involvement.  I'll try and give some time once I've cleared up my current project.

It's best not to speak in absolutes about SEO - what's true today may be false next week, and it's impossible to be certain what weighting is given to the hundreds of factors used to determine SERPs.  All we can do is follow Google guidelines and best practices, e.g. avoid duplicate content, provide unique and meaningful meta title + description.  Flux is already very good, and this little tweak would make it even better.

P.S.  I didn't receive notification of replies, hence delay in replying.

If by "at the moment" you mean the last 8 years, you'd be correct - but you don't, so you're not.

Try reading pretty much every article published by ALA over the last 8 years.  I have.  It was very enlightening.  Also, glancing at my book shelf, I'd recommend:

* User-Centred Web Design / Cato
* Eric Meyer on CSS
* Taking Your Talent to the Web / Zeldman

Once you've read all that, your opinion on web design will be <strike>a little better</strike> informed.

Their audience is really no more captive than FluxBB.  37s do not have a product monopoly.  If this decision were going to alienate large numbers of their users, they would not be doing it.

If 37s make a business or design decision, it's usually not a bad idea to look at it closely.  Investing a disproportionate amount of development time for a dying browser, at the expense of 'good stuff', isn't a good strategy.

Also, by dropping support for an obsolete browser gives a clear signal that the project is looking to the future.  And, of course, it doesn't prevent those who need it to cond. comment for IE6.

Persuasive argument.

And who are you?

1. 'flux' = 'flux capacitor' =
     Roads?  Where we're going we don't need roads! (possible copyright issues with Universal Studios)

2. Everything that you need and nothing that you don't

3. More conversation, less clutter

4. Less bloat, more banter

5. Flux's acronym =
     Fast. Light. User-friendly. eXtensible

The topic is in the browser address bar and the permalinks (which position the viewport to individual posts).  The forum is second to last in the breadcrumb.

Next.

permalink != breadcrumb

Leaving aside personal preference, W3C / WCAG provides a recommendation which should take precedence: http://www.w3.org/TR/WCAG20-TECHS/SCR24.html

I'm not a fan of the current method. 

I use Tab Mix Plus which allows me to force all links to open in current tab - it's then my choice to open links in new tabs.  The FluxBB implementation means that when I CTRL+click 'BBCode', for example, I don't get a new tab and the link opens in current tab.  Irritating.

I'd prefer:

function externalLinks() { 
 if (!document.getElementsByTagName) return; 
 var anchors = document.getElementsByTagName("a"); 
 for (var i=0; i<anchors.length; i++) { 
   var anchor = anchors[i]; 
   if (anchor.getAttribute("href") && 
       anchor.getAttribute("rel") == "external") 
     anchor.target = "_blank"; 
 } 
} 
window.onload = externalLinks;