Difference between revisions of "DeveloperWiki:Branding Proposals"

From ArchWiki
Jump to: navigation, search
m (New page: = Introduction = This article is for discussing Arch Linux artwork and branding ideas. Feel free to add any suggestions or concerns. == Separate branding from upstream packages == Create ...)
 
(categorizing uncategorized page)
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Category:DeveloperWiki]]
 
= Introduction =
 
= Introduction =
This article is for discussing Arch Linux artwork and branding ideas. Feel free to add any suggestions or concerns.
+
This article is part of the [[DeveloperWiki]]. Feel free to add any suggestions or concerns.
  
== Separate branding from upstream packages ==
+
 
 +
= Separate branding from upstream packages =
 
Create a separate package of artwork for upstream packages, including:
 
Create a separate package of artwork for upstream packages, including:
  
Line 11: Line 13:
 
Include post-install notes informing the user where to find the theme and where to modify its preference.
 
Include post-install notes informing the user where to find the theme and where to modify its preference.
  
=== Pros: ===
+
==== Pros ====
 
* Upstream packages are delivered as-is
 
* Upstream packages are delivered as-is
 
* Users can choose whether to download Arch-branded content
 
* Users can choose whether to download Arch-branded content
  
=== Cons: ===
+
==== Cons ====
 
* Users will have to modify theme settings manually
 
* Users will have to modify theme settings manually
  
== Package Naming Scheme ==
+
 
 +
= Package Naming Scheme =
 
If artwork is separated from upstream packages, we should have a consistent naming scheme, for example:
 
If artwork is separated from upstream packages, we should have a consistent naming scheme, for example:
  
 +
* archlinux-artwork
 +
* archlinux-wallpaper
 
* archlinux-themes-gdm
 
* archlinux-themes-gdm
 
* archlinux-themes-kdm
 
* archlinux-themes-kdm
 
* archlinux-themes-slim
 
* archlinux-themes-slim
 
* archlinux-themes-xfce
 
* archlinux-themes-xfce
* archlinux-artwork-icons
 
* archlinux-artwork-logos
 
* archlinux-artwork-wallpapers
 
  
  
== Essential Artwork ==
+
= Essential Artwork =
 
Provide at least 1 style-neutral (minimalist) theme for the standard packages:
 
Provide at least 1 style-neutral (minimalist) theme for the standard packages:
  
=== Completed: ===
+
==== Completed ====
 
* Framebuffer logo
 
* Framebuffer logo
 
* SLiM
 
* SLiM
 
* Qingy
 
* Qingy
 
* Splashy
 
* Splashy
 
=== Pending: ===
 
 
 
* GDM
 
* GDM
 
* KDM
 
* KDM
 +
 +
==== Pending ====
 
* XDM
 
* XDM
 +
 +
= Other Resources =
 +
[[DeveloperWiki]]

Revision as of 01:22, 21 September 2011

Introduction

This article is part of the DeveloperWiki. Feel free to add any suggestions or concerns.


Separate branding from upstream packages

Create a separate package of artwork for upstream packages, including:

  • login themes
  • desktop environment additions (wallpapers, icons, etc.)
  • splash screens

Include post-install notes informing the user where to find the theme and where to modify its preference.

Pros

  • Upstream packages are delivered as-is
  • Users can choose whether to download Arch-branded content

Cons

  • Users will have to modify theme settings manually


Package Naming Scheme

If artwork is separated from upstream packages, we should have a consistent naming scheme, for example:

  • archlinux-artwork
  • archlinux-wallpaper
  • archlinux-themes-gdm
  • archlinux-themes-kdm
  • archlinux-themes-slim
  • archlinux-themes-xfce


Essential Artwork

Provide at least 1 style-neutral (minimalist) theme for the standard packages:

Completed

  • Framebuffer logo
  • SLiM
  • Qingy
  • Splashy
  • GDM
  • KDM

Pending

  • XDM

Other Resources

DeveloperWiki