Matthew Thomas wrote:

> Firstly, it will break site users' memories for where particular pages
> are located navigation-wise, only for them to be broken again later when
> the long-term site debogosification project goes live.

> Secondly, since the proposed temporary categories don't (seem to) map
> entirely onto existing pages on mozila.org, they will result in the
> creation of more temporary URLs that will probably rot later.

As far as I understand it, the short-term changes are mainly a clean-up of
the menu to contain only links to the really important pages, and fix these
pages to fit it that new structure. It shouldn't make any pages go away,
but make the existing information more accessible and not confuse users
with 27 items in a menu.

This may even be a good point _for_ having a sitemap: those people who know
the old navigational structure can find the new location with a single
click.

> And thirdly, there will be a risk of complacency -- of thinking that the
> temporary recategorization is `good enough', and that future
> debogosification is not necessary.

Ok. But we are all aware of the need to really do a general overhaul,
aren't we?

> > You don't mention documentation in your proposal.
> > Where would it go?
>
> It wouldn't, since `Documentation' is a meaningless category
> <http://groups.google.com/groups?q=x&seld=950494232&ic=1>.

What I meant is where would the current content from the "docs" page go?
You had a "Developer Info" link, and now you have a "Developer Center", so
I assume they would go there.

> > And since the pages for the for most of the items
> > you mention don't fit your description in their
> > current form, may I ask you to draft a proposal
> > for each of them?
> >...
>
> No -- because you were there, participating in the thread, when I
> already did that. :-P
> http://groups.google.com/groups?th=a399aa07ae3bd621&seld=947624252&ic=1

Your proposal is great, but what I wanted to say is that there is a big
difference between a jpg and working html pages. And for a short-term
project, the above mentioned reuse of existing pages seems more
appropriate. But if you already had html pages ready, this would of course
be an even better short-term fix. I'm not demanding that you to create
these html pages now, I'm just saying that it makes sense to fix the menu
_now_ and create new pages (or rewrite the complete website) afterwards.

Andreas


Reply via email to