Difference between revisions of "Website:Issues"

From Camino Wiki
Jump to navigation Jump to search
(→‎Smokey's issues and typos found: stuff i've fixed in my local copies)
(→‎Smokey's issues and typos found: style guide issues, initial idea)
Line 46: Line 46:
  
 
===Smokey's issues and typos found===
 
===Smokey's issues and typos found===
*Typos and other errors found (who will fix? '''Answer''': I will fix them in their respective Camino09Website pages. --Sakurina):
+
*Typos and other errors found:
 
** <strike>[http://www.caminobrowser.org/support/sup_faq.html#troub_java Support FAQ] mis-identifies JEP in the Java FAQ (should be "Java '''Embedding''' Plugin")</strike>
 
** <strike>[http://www.caminobrowser.org/support/sup_faq.html#troub_java Support FAQ] mis-identifies JEP in the Java FAQ (should be "Java '''Embedding''' Plugin")</strike>
 
** <strike>[http://www.caminobrowser.org/support/sup_faq.html#gen_savedinfo Support FAQ] is missing a "'''~'''" in the path in the "Where are my bookmarks" FAQ (should be "'''~'''/Library/Application Support/Camino")</strike>
 
** <strike>[http://www.caminobrowser.org/support/sup_faq.html#gen_savedinfo Support FAQ] is missing a "'''~'''" in the path in the "Where are my bookmarks" FAQ (should be "'''~'''/Library/Application Support/Camino")</strike>
Line 60: Line 60:
 
*** <s>"Report a Camino bug" should point to https://bugzilla.mozilla.org/enter_bug.cgi?format=guided&product=Camino (helper form) by default; experienced users who give good reports can figure out how to use the short form, and this gets us more useful info from everyone else.</s>
 
*** <s>"Report a Camino bug" should point to https://bugzilla.mozilla.org/enter_bug.cgi?format=guided&product=Camino (helper form) by default; experienced users who give good reports can figure out how to use the short form, and this gets us more useful info from everyone else.</s>
 
*** <s>"Report a Mozilla bug" points to an invalid product; should use https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Application%20Suite&format=guided (or https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&format=guided if it's intended for Core bugs) or be removed altogether.</s>
 
*** <s>"Report a Mozilla bug" points to an invalid product; should use https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Application%20Suite&format=guided (or https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&format=guided if it's intended for Core bugs) or be removed altogether.</s>
 +
* cb.o needs an "Editorial" style guide (how words are spelled, capitalized, US vs. European comma placement, how elements of the GUI are named, etc.)
 +
** drop-down
 +
** preference pane vs. preference panel ?
 +
** Navigating menus and prefpanes (step-by-step order?)

Revision as of 01:14, 19 January 2006

Please report all issues with the current Camino website below:

Sam's todo list

  • n.cb.o - Doc pages migration
  • Bug 292780 - Create /download/releases Page Listing Releases
  • Bug 292777 - Release notes page needs a download link
  • Bug 293093 - Main Page needs list of support languages
  • The sidebar look/style needs an update. (Design by Jasper, CSS by Sam/Wevah)
  • Register ce.o domain - Pending DNS
  • Bug 300111 - Enhance the Camino Bugzilla FAQ page
  • Remove incorrect line from 09a1 release notes: "Command + Up & Down now works the same as Page Up & Down."

Jasper's todo list

  • Create l10n header graphic
  • I should create some extra different sized badges.
  • Add the download links for latest release and multi lang on the features page.
  • Write new text for the features section.
    • The animation text need a look and tweaks.
    • Use the sidebar for a feature list.
  • Create new graphics for the features section.
    • Work myself trough the list of features. Keep it simple and clean.
  • n.cb.o - Access keys for navigation (use u for underline)
  • Create l10n graphic for development pages (similar to download icon on main page)

Wevah's todo list

  • n.cb.o - Migrate Development pages
  • Bug 300179 - Fix Search Customization Instructions

Graeme's todo list

  • Create /start/ page with it's own style and browser-detection PHP.
  • Migrate content from current site to new site.
  • Link in Jaspers l10n header graphic.
  • l10n plugin.
    • Seems to be some issues with the access privileges to the plugin.
    • Ability to add languages through preferences tab.
    • Content updates should mark localized text as requiring updates.
    • Ability to make minor edits which don't require updates to the localized text.
    • Specifying the language code in meta tag.
    • Image localization -
      Any ideas anyone?
    • Localization of other miscellaneous strings - i.e. Browser Warning
  • Highlight for the active Development & Support sidebar links.
  • Update plugins for the newer version of txp.
  • Design CSS version of support/docs pages.

Smokey's issues and typos found

  • Typos and other errors found:
  • cb.o needs an "Editorial" style guide (how words are spelled, capitalized, US vs. European comma placement, how elements of the GUI are named, etc.)
    • drop-down
    • preference pane vs. preference panel ?
    • Navigating menus and prefpanes (step-by-step order?)