|
This Page has been suggested for deletion |
|
Several reasons may lead to a page being suggested for deletion, the most common being: 1. the content of the page is not appropriate, or just irrelevant to MusicBrainz, 2. the page duplicates (or has been entirely superseded) by another one, 3. the page no longer has a purpose (possibly following the introduction of a new server feature) or is entirely bit-rotted while not being of interest enough to be kept as History |
|
Pages marked as deleted won't usually be deleted immediately though, so, if you think the page either should be preserved as History or still serves a purpose and should just be kept, you may discuss this with the editor who marked it as such in order to expose your reasons and reach an agreement. |
|
If you're a newcomer who just stumbled here, chances are high that this page is not relevant for you either way, and you may rather head for the main documentation. |
ProposedMenu
Status: This Page is out of date. This was the second attempt to restructure the SiteMenuArrangement. There will probably not be a third one in this mindset, i.e. to design a new stie structure from ground up. Instead with WikiDocs the SiteMenu will probably evolve in a "bottom up" manner. Still, there might still be some valuable ideas in here. In a way this is a CandidateForDeletion, but should probably be kept until WikiDocs have settled down. --DonRedman
More than one year later. Maybe it's time now to DeletedPage? -- dmppanda 2007-04-01 16:20:46
Don, where are we with that now? -- dmppanda 2008-02-14 17:39:35
This page lists a proposed SiteMenuArrangement because we had several complaints, that the Site Menu was messy and overpopulated.
Here, the second number refers to what line it is in the CurrentMenu. In some cases there may be 2 or more numbers, indicating that pages need to be combined. I've tried to do this only where it is obviously beneficial. There are a couple new pages that would need to be made as well, which I have really worked to keep to a bare minimum (usually needing only a blurb and links, or made with material already present somewhere, that just needs to be moved to the new page). Comment follow in itialics, to clarify and explain, or just notes of ideas.
I added some comments in the listing (indented) and some general discussion at the bottom. --DonRedman
1 Home [1]
2 About [2/3] intro
4 The People [5] The tech Gods
4.1 Top Data Contributors [6/7]
4.2 Top Editors [6/7]
4.3 Top Voters [6/7]
:::::: Do you really want to have submenus for this? Currently the Top *s are listed at the bottom of the menu (which is a goo Idea I think). IMO this makes them obsolete here. --DonRedman
5 History [4] history of MB
6 Future [8] future of MB
7 Related Projects [15] (projects that use MB)
8 Social Contract [14]
9 Docs [135] this can have links to all the subpages here, no need for the subpages themselves
11 News [20]
12 Latest News [21]
13 In the Press [22]
14 Updates [NEW: make a page for this, blurb stating what each of these things are, with links] each subpage only needs it's main page, folk can follow the links there, they don't need yet another subpage for each date.
15 Tagger [26]
16 Server [30]
17 Client [36]
18 TunePimp [39]
:::::: I had expected 15--18 under Products not under News. E.g. the "TunePimp" page under products will always list the current version and the latest news (changes...). Why would you want extra news-pages for each product? --DonRedman
20 Products[42] Tagger and CD Look Up, latest versions--- with a link to the page with older versions. (that page can be complete, with the ave. users stuff (tagger, CD tool) as well as 'developers tools' (the Client lib, Tunepimp, etc..)
22 How to use Tagger[44] Intro
23 Quick start [NEW: grab from http://www.musicbrainz.org/tagger/intro.html]
24 Tutorial[47]
25 FAQ[48]
27 Search/Browse [65/69] keep search, advanced search, and google.. lose the browsing, contributing, login etc... (change the 'help' in advanced to 'what is this?') Add the off site search engines 'search links' here
28 Browse Artists[67]
29 Browse Releases[68]
31 Edit the Data [71*] about Style guide link high on this page, along with FAQ (add a bar to be present on all data altering pages, with the style guides and FAQ right at hand? possibly popping up into their own window, so one doesn't lose track of the edit they were on?)
32 Add data [109/110/111/112] (a thank you blurb, something about the importance of adding data, but doing it correctly too) then the links to add artist, add release, add VA release, and FreeDB import
33 Edit data[73] Suggestions page here (keep the links here, they don't need separate sub pages in the menu)
34 Vote on data [93/94/95/100/101] links to 'vote on new' 'vote on my subscribed' 'advanced data search' 'jump to ID
35 My history [96/97/98/99/100] page with link to all the data about my add/edit/votes.. no need to subpage each of these
37 Contribute[12] We are good... give us money.... if you are poor, get richer people to give us money!!
39 Sponsors[10]
40 Finances[11]
43 Development[34] this is good place for the 'help wanted' page (currently under 'about') (not a tech here, this section may need close review... tried to get everything logical, but without really knowing what connects to what, i could have lost something somewhere)
45 Introduction[118]
46 Project Status[119]
47 CVS Access[120]
48 CVS Modules[121]
49 CVS Viewer[122]
50 TODO[123]
51 Rob's TODO[125]
52 Johan's TODO[126]
53 Dave's TODO[127]
54 Metadata 2.1[128] Introduction (looks like everything is all on one page here, and rather long, so i split things up according to the table of contents, the separate pages 'mm' and 'mq' i have sub paged, but they might be better off as a link on the page they are sub to)
55 General Protocol Definition[128]
56 MusicBrainz Metadata Namespace[128]
* 57 mm[130]
58 MusicBrainz Query Namespace[128]
* 59 mq[131]
60 MusicBrainz Extended Metadata Namespace[128]
61 Developers Products [NEW: blurb about developing]
62 TRM Generator[51]
63 Client / SDK[52] intro (with link to Docs (HOWTO) and to the Developers Downloads
64 TunePimp / SDK [56] intro (with link to it's specific Docs (as well as main Doc listing?) and to the Developers Downloads
65 Server / Data [60] intro (with link to it's specific Docs (as well as main Doc listing?) and to the Developers Downloads
66 White Papers[23]
67 Non-Profit[24]
68 Licensing[25]
:::::: Don't need these either, their links are on 'White Papers' --jinxie
69 Licenses[13]
70 Logos[18]
72 Help/Contact[133]
73 FAQ[134] (get links to ALL the FAQ pages and the Style guide at the top of this page, currently they are lost in text)
74 Known Bugs[153]
75 Report a Bug[154]
76 Contact Us[151]
77 Mailing Lists[152]
79 Wiki[156]
80 Site Map [NEW: so a person doesn't have to click through each step of the menu to see what all is available] (saves bandwidth, LOL) (or maybe just link to the wiki finished product? Then they could see everything, if not link to it.)
Discussion
I believe third-level elements are a bad thing in a site-menu. If the corresponding second-level element is a good description of all the stuff grouped under it, then the user will feel he/she is still there. Adding a third-level is often more confusing than helpful.
The names of the first-level elements are very important. This is the first thing people see, thus the names must be clear and informative categories.
Home, About, Docs, News, Products, Search/Browse, Edit, Development, Help/Contact, Wiki and Site Map are generic elements and good names for first-level elements.
But History, Related Projects and Social Contract are not. These should be part of About IMHO.
I totally agree
that was a case of missing *'s. (fixed that)
(How to use) the Tagger is part of the Products (but might still be improtant enought to leave it on first-level).
I put it on the first level, because I remember hunting all over for how using the Tagger actually works, before I decided to download and try it.
Contribute is a difficult element. I would love to have Add new Data as a part of "contribute to MusicBrainz" but I believe that Edit the Data is the better name, where people who do not know MusicBrainz instantly have an idea, of what this section is about.
I agree with those third level items Don noted in the main body. Not sure why I felt they needed their own pages, but it was late, thats my only excuse. (am i allowed to go kill off some of the comments i had for some pages??? lol)
Line 54 Metadata 2.1 I'm really not sure why I wanted to break up that way, the original is fine.
Line 66 White Papers Doesn't need the submenu items separate. The links to both are on the heading page.
--jinxie