Difference between revisions of "WGO Redesign"

From GIMP Developer Wiki
Jump to: navigation, search
Line 27: Line 27:
 
This is already how the current site exists, though the implementation is a little clunky.
 
This is already how the current site exists, though the implementation is a little clunky.
  
 +
# Possibly having role-based permissions against different areas of a git repository (admin, presentation, content, tutorials, news, etc...) ([http://www.git-scm.com/book/en/v2/Git-Tools-Submodules git sub-modules] were mentioned as a way to manage this).
 
# The proposed idea is to separate WGO content into more user-friendly discrete pieces, such as individual [http://daringfireball.net/projects/markdown/ Markdown] text files.
 
# The proposed idea is to separate WGO content into more user-friendly discrete pieces, such as individual [http://daringfireball.net/projects/markdown/ Markdown] text files.
 
# These text files (+assets) would then be passed through a processor to be turned into static HTML assets.
 
# These text files (+assets) would then be passed through a processor to be turned into static HTML assets.
 
# These static HTML assets would then be served to users.
 
# These static HTML assets would then be served to users.
 +
 +
 +
 +
== Role based access (git submodules) ==
 +
 +
== Content ==
 +
 +
== Presentation ==

Revision as of 15:57, 2 April 2015

Why?

The email from Cristobal on the Gimp-web list recently prompted this further discussion. His summary of work and ideas were documented on this page.


Assumptions

  • We (the royal 'We') could benefit from having more content on WGO, in particular tutorials.
  • Lowering the barrier-to-entry can help entice users to generate new content.
  • A new facelift can't hurt from a PR standpoint.


Benefits

There are a few possible benefits from conducting a redesign now:

  • Better organization of content
If the content organization is approached as described below.
  • Modern Look
  • A chance to consider usability and ease of access for users (and to improve it)
  • Lowering the barrier to entry for new contributors/contributions.


Summary

From an architecture standpoint, the general idea is to separate content from presentation. This is already how the current site exists, though the implementation is a little clunky.

  1. Possibly having role-based permissions against different areas of a git repository (admin, presentation, content, tutorials, news, etc...) (git sub-modules were mentioned as a way to manage this).
  2. The proposed idea is to separate WGO content into more user-friendly discrete pieces, such as individual Markdown text files.
  3. These text files (+assets) would then be passed through a processor to be turned into static HTML assets.
  4. These static HTML assets would then be served to users.


Role based access (git submodules)

Content

Presentation