website map verse 3

redesign website map verse 3

Raffaello was the author of verse 2 with some explicit help from 
Itchthyo in the “Dev's vault”.

verse 3 is the result of research, analysis, reversion. in part one, the 
map is described. in part two the changes from verse 2 are explained

in verse 2, our community was defined as developers and users. verse 3 
is an attempt to join the two groups.

verse 3 defines developers to include programmers, documenters, 
educators, marketers, promoters, even critics and feature requesters. 
users are anyone.

to define, for example, documenters, educators, marketers, and promoters 
as developers in addition to programmers is respectful and a result is 
increased communication.

the theory is that more developers is always better. if users and 
developers are exposed to the variety of development then they can 
easily transition from user to developer and developer to developer.

part one map specifics

    *

      the purpose of the map is to define all sections once in the most
      correct *structure*

    *

      all capitol words are the *definitive* suggested words to write at
      the website

    *

      each line is a section. indented lines are sub sections on the
      same page as the super section; either as the full sub section, a
      brief and a link to the sub section, or the link only

    *

      sections in the map list are *ordered* approximately for
      translation to site pages; high left to low right

with these specifics formalized we can effectively communicate to 
evaluate the site structure, semantics, and website page design.

in this phase

    *

      we must choose best words or phrases per section title and link

    *

      compose a list of sections and links in order to translate it to a
      site page

therefore, website map verse 3 is more than informed personal 
suggestions, also it is in phase to translate a map to a draft graphic 
of the site Project Lumiera.

in verse 3 some of the chosen words originate from verse 2. the change, 
addition, or neglect of any word is explained in part two.

part one, map description

SEARCH

PROJECT

NEWS

DOWNLOAD

ABOUT

ROADMAP

TICKER

SCREENSHOTS

CONTRIBUTE

CREDITS

CONTACT

COMMUNITY

USERS

DEVELOPERS

MERCHANTS

DONORS

DOCUMENTS

MANUALS

HOW TOS

DESIGN

SOURCE CODE

FOR THE PRESS

DEVELOPMENT

SUB PROJECTS

JOBS SMALL TO LARGE

NEXT MEETING AGENDA

PAST PROTOCOLS

SOURCE CODE

LINKS

UWIKI

NOBUG

PASTEBIN

CINELERRA

part two, changes are explained

compare verse 2 to part one verse 3

as you may have noticed in the map that I wrote, I favour concise short 
words and phrases that impose less on the page. for a designer that 
conciseness translates to limitless designs, especially where links are 
in rows or columns.

note of humour to Raffaella: this is only semantics. all to better the 
project, not break your heart...but if that is what you feel then the 
worst is definitely to come.

SEARCH abstracted from HOME only, search works in whole site

PROJECT

PUBLIC SECTION is changed to PROJECT. the chance is that Raffaello wrote 
the phrase to order the list rather than as a word to write at the site 
finally.

the word public, for open source projects is ambiguous in that context. 
unless the word public is written elsewhere to mean something that was 
published specially, then it has no greater relevance as everything at 
the site was published and is public.

HOME is negated as a section and all the sub sections are merged to 
PROJECT. the word home is typically only used as a solitary link to the 
most general part of a site. It has less versatility, almost none, than 
the word project in paragraphs.

THE PROJECT is negated as a section and all the sub sections are merged 
to PROJECT.

ESSENTIAL PRESENTATION is negated as a phrase. the chance is that 
Raffaella wrote the phrase to suggest a page style.

actually PROJECT HEARTBEAT is not that bad. though it was changed, the 
purpose was to state that other sites have varied equivalent concise 
words or phrases. some are:

TICKER http://mozilla.com <http://mozilla.com/>

LATEST COMMITS http://www.compiz.org/

ROADMAP is in verse 3, not for its explicit meaning, but for its 
pervasiveness in most other projects. The phrase is not my favourite, I 
can accept it, but while we are all here, is there any better alternatives?

PLAN or PROJECT PLAN

WEBSITE is negated as a section and all the sub sections are merged to 
DOCUMENTS - USER MANUALS

COMMUNITY

COMMUNITY is added as a section to order other sub sections that were 
added. On the page community, like any super section, is the full sub 
sections, briefs of sub sections and links to sub sections, or links 
only. uWiki can dynamically automate some data, statistics.

USERS is added as a section. user has a profile that features their art, 
products. encourage creative licenses. interlink users to user groups, 
what groups?

DEVS is changed from DEVELOPER'S VAULT to COMMUNITY - DEVELOPERS. 
developer has a profile that features their work in the project, jobs.

MERCHANTS is added as a section. merchant has a profile that features 
their merchandise. merchants have equality; single persons or large 
manufacturers.

for example,

in community archlinux (a linux distribution) there is a user who lives 
in Canada, Saskatchewan. he likes to craft wood and crafted some 
archlinux merchandise that he sold from the archlinux forums.

also there are large sites like t-shirts.com where anyone can create 
designs of shirt to sell.

the single person like the archlinux crafter would create their own 
merchant profile. a Lumiera administrator may have to create the 
t-shirts.com profile and link it to t-shirts.com.

the intent, ideally, is to have a directory of merchant profiles at the 
same page somewhere (a page may feature some merchandise elsewhere). 
merchant profiles have a consistent style that lists the merchandise and 
prices.

DONATE is changed from THE PROJECT to COMMUNITY - DONORS. donor has a 
profile that features their donation, anonymity is a choice. at the 
donors page, new donations are accepted and a there is a list of donors 
that is linked per profile.

interlink all community profiles.

If uWiki is distributed then Lumiera.org is not the only store of all 
profiles data, less server load. community is the most obvious data to 
distribute. what is other data to distribute?

DOCUMENTS

DOCUMENTS is added as a sub section to attempt a major reorder of the 
site map. documents from verse 2 PUBLIC SECTION and DEVELOPER'S VAULT 
were merged to the new generic section. the intended result is to 
transition the curious to user to developer.

PROJECT section continues to have links to priority documents of any 
type. DEVELOPMENT section continues to have links to developer documents.

the challenge of documenters to write documents that span types. On the 
page documents, the challenge to type documents may result in a unique, 
creative design that links documenter profiles to documents as a 
perspective of the project.

USER MANUAL is changed to MANUALS the cause of plurality is a merge of 
all sub sections from THE PROJECT - WEBSITE. also the section is 
generalized to include developer manuals.

HOW TOS is added as a sub section. though there is no current content 
for how tos, the section is suggested to order documents that explain 
how to create or produce specific results in Lumiera.

any author may write a how to. if a how to is written in wiki, it is 
indexed for search and styled consistently. to have this consistency 
implies a job for documenters when a how to is authored in some other 
format.

DESIGN DOCUMENTATION is changed from DEVELOPER'S VAULT to DOCUMENTS - 
DESIGN. the sub section in documents is to unify all parts of project 
design, that includes (note: developers refine to complete the list) 
process, workflow, GUI, PROC, BACKEND, PLUGIN, BUILDRONE, CONFIG LOADER, 
website.

though the section is essentially a link to DEVELOPMENT, there is added 
value to describe, on one page, how the project design is unified and 
link to the design per sub project at DEVELOPMENT - SUB PROJECTS.

CODE DOCUMENTATION is changed from DEVELOPER'S VAULT to DOCUMENTS - 
SOURCE CODE. like DOCUMENTS - DESIGN, the section SOURCE CODE is at 
least a unifier to source code per sub project at DEVELOPMENT - SUB 
PROJECTS.

PRESS is changed from THE PROJECT - PRESS to DOCUMENTS - FOR THE PRESS 
for syntactic reasons and order.

DEVELOPMENT

DEVELOPER'S VAULT is merged to DEVELOPMENT, I like the phrase 
'developer's vault' too – whatever the choice, we should design the site 
consistently.

HOME is negated as a section and all the sub sections are merged to 
DEVELOPMENT.

QUICK START or START UP NOTES or STARTING POINTS. in the section, there 
is currently no defined content. alternatively, if the content here is 
brief, place it high on the super page DEVELOPMENT with no section 
title, as an implicit introduction.

CODE DOCUMENTATION and DESIGN DOCUMENTATION are merged to SUB PROJECTS. 
sub projects include (note: developers refine to complete the list) 
process, workflow, GUI, PROC, BACKEND, PLUGIN, BUILDRONE, CONFIG LOADER, 
website. at each sub project page there is links to design and code 
documents.

TRAC REPORTS is changed to JOBS SMALL TO LARGE. better to write a 
general phrase for any person. we should minimize the work for new 
persons to learn minor details like what is 'trac'. alternatives ? small 
to large is in the phrase to attract the busy and the brave.

GITWEB is changed to SOURCE CODE for generality that includes various 
interfaces to the source code, doxygen, gitweb, direct address to git 
protocol. chance is there is no confusion with DOCUMENTS - SOURCE CODE, 
both pages should interlink.

USEFUL LINKS is changed to LINKS. some examples are UWIKI, NOBUG, 
PASTEBIN?, CINELERRA.

note that all super sections are pages also. to criticize this website 
map, these sections are the first parts to critic. try to imagine a 
design of each section page where you can find all the sub sections.

the intent of this phase is to design the map of pages that is 
informative, orderly, directive to all sub sections.

the next phase is to design the draft graphic interface. best is to 
initiate the next phase with a perfect map, that will require 
imagination to foresee any problems.

to conclude, the intent of this verse was to formalize a website map 
that is general and total.

_______________________________________________
Lumiera mailing list
Lumiera@...
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html