Difference between revisions of "Website migration plan 2019"

From GRASS-Wiki
Jump to: navigation, search
(creating CMS migration plan 2018)
 
m
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This wiki is a first draft roadmap of priorities for the migration from CMSMS ([https://grass.osgeo.org/ grass.osgeo.org]) to Wordpress ([https://staging.grass.osgeo.org/ staging.grass.osgeo.org]).
+
This page is a first draft roadmap of priorities for the migration from our current CMSMS website ('''[https://grass.osgeo.org/ grass.osgeo.org]''') to <strike>Wordpress ([https://staging.grass.osgeo.org/ staging.grass.osgeo.org])</strike> a [https://gohugo.io/ Hugo]/git based solution.
  
== High priority ==
+
== Why a new Website ==
  
 +
First impressions is usually the influence that gives the biggest effect and our current CMSMS website is getting completely dated and non-attractive. Therefore, to '''redesign''' GRASS GIS website is of high priority for the project. Moreover, the current site is pretty hard to maintain and most of the work is done by one or two persons. This becomes a pretty heavy task in occasions. Most importantly, the old CMSMS template is not responsive, i.e., not mobile friendly, which prevents GRASS GIS users and especially potential new users to browse related contents on mobile. This is nowadays an important drawback as compared with other projects and proprietary options.
 +
 +
To enable more people to contribute and contents to be more discoverable and easy to browse, a complete redesign with different technology is planned. Particularly, we consider '''static website design''' through [https://gohugo.io/ HUGO] which has several assets over Sphinx, including more web design freedom and many responsive theme available to build on. Moreover, content can be written in '''Markdown''' which is much simpler than HTML. We plan to host the site on a '''git'''-flavored instance as well, so contributions are significantly eased as compared with the current CMSMS.
 +
 +
For these reasons, we believe it’s imperative to refresh our website in line with recent design trends, technological advancements and search engine algorithms. In this way, we are confident that more people will contribute to keep it alive with blog posts and examples as well as with maintenance. Moreover, GRASS GIS contents will be more discoverable for the newcomers, which we hope will then benefit the whole OSGeo community.
 +
 +
== Technology ==
 +
 +
* <strike>Wordpress ([https://staging.grass.osgeo.org/ staging.grass.osgeo.org])</strike>
 +
* a [https://gohugo.io/ Hugo]/git based solution
 +
 +
== Desired content ==
 +
* ...
 +
* ... your ideas here (but please check also below for existing content)
 +
 +
== Expected workload ==
 +
* Research and planing (gathering information about project, users, existing content, type of media...)
 +
* Solution design (creating wireframes, sitemaps and user workflows)
 +
* Solution setup (local Hugo install, templates and base layouts)
 +
* Web design (HTML and CSS to integrate the GRASS GIS branding)
 +
* Responsive adaptations (CSS media queries, possibly bites of JS)
 +
* Content writing (Bringing the default markdown files, with minimal content)
 +
* Testing (including common mobile browsers)
 +
* Corrections and fixes (iterations according to community feedbacks)
 +
 +
== Crowd funding campaign ==
 +
 +
* March 2019: https://grass.osgeo.org/news/83/15/New-crowd-funding-campaign/
 +
** You can contribute easily via our PayPal Money Pool: https://www.paypal.com/pools/c/86YKZiIEPV
 +
 +
== Design and implementation phase ==
 +
 +
* The GRASS PSC will work out details in the next weeks.
 +
 +
== Existing content - to be restructured ==
 +
 +
=== High priority ===
 +
 +
Legal:
 +
* https://grass.osgeo.org/home/imprint
 +
* https://grass.osgeo.org/home/copyright
 +
 +
The team:
 +
* https://grass.osgeo.org/home/about-us
 +
* https://grass.osgeo.org/home/contact-us
 +
 +
Software (see also "To be merged"):
 
* https://grass.osgeo.org/download
 
* https://grass.osgeo.org/download
 
* https://grass.osgeo.org/download/software
 
* https://grass.osgeo.org/download/software
 
* https://grass.osgeo.org/download/addons
 
* https://grass.osgeo.org/download/addons
 +
 +
Sample Data:
 
* https://grass.osgeo.org/download/sample-data
 
* https://grass.osgeo.org/download/sample-data
 +
 +
Docs:
 
* https://grass.osgeo.org/documentation
 
* https://grass.osgeo.org/documentation
 
* https://grass.osgeo.org/documentation/manuals
 
* https://grass.osgeo.org/documentation/manuals
 +
* https://grass.osgeo.org/documentation/tutorials
 +
 +
Use cases:
 
* https://grass.osgeo.org/documentation/applications
 
* https://grass.osgeo.org/documentation/applications
* https://grass.osgeo.org/documentation/tutorials
+
 
 +
Community:
 
* https://grass.osgeo.org/support
 
* https://grass.osgeo.org/support
 
* https://grass.osgeo.org/support/community
 
* https://grass.osgeo.org/support/community
 
* https://grass.osgeo.org/support/mailing-lists
 
* https://grass.osgeo.org/support/mailing-lists
 +
* https://grass.osgeo.org/get-involved
 +
* https://grass.osgeo.org/development/translations
 
* https://grass.osgeo.org/development
 
* https://grass.osgeo.org/development
* https://grass.osgeo.org/get-involved
 
  
=== To be joined ===
+
==== To be merged ====
  
These 3 should become only '''sponsonship'''
+
These 3 pages should become a single page '''sponsorship'''
  
 
* https://grass.osgeo.org/support/commercial-support
 
* https://grass.osgeo.org/support/commercial-support
Line 25: Line 81:
 
* https://grass.osgeo.org/donations
 
* https://grass.osgeo.org/donations
  
These should be all combined into '''download/software'''
+
These should be all combined into '''download/software''' (see also above)
  
 
* https://grass.osgeo.org/download/software/linux
 
* https://grass.osgeo.org/download/software/linux
Line 33: Line 89:
 
* https://grass.osgeo.org/download/software/sources
 
* https://grass.osgeo.org/download/software/sources
 
* https://grass.osgeo.org/download/software/docker-images
 
* https://grass.osgeo.org/download/software/docker-images
 
== Normal ==
 
 
* https://grass.osgeo.org/development/bug-tracking
 
* https://grass.osgeo.org/development/translations
 
* https://grass.osgeo.org/development/programmer-manual
 
* https://grass.osgeo.org/development/code-submission
 
 
=== To be joined ===
 
  
 
All these ''screenshots'' could be converted into a "Gallery", for example
 
All these ''screenshots'' could be converted into a "Gallery", for example
Line 55: Line 102:
 
* https://grass.osgeo.org/screenshots/cartography
 
* https://grass.osgeo.org/screenshots/cartography
  
== Low priority ==
+
=== Low priority ===
  
* https://grass.osgeo.org/home/history
 
* https://grass.osgeo.org/home/history/releases
 
* https://grass.osgeo.org/home/history/documents
 
* https://grass.osgeo.org/home/history/van-warren-notes
 
* https://grass.osgeo.org/home/press-releases
 
* https://grass.osgeo.org/home/imprint
 
* https://grass.osgeo.org/home/about-us
 
* https://grass.osgeo.org/home/contact-us
 
* https://grass.osgeo.org/home/copyright
 
* https://grass.osgeo.org/home/credits
 
 
* https://grass.osgeo.org/download/logos
 
* https://grass.osgeo.org/download/logos
* https://grass.osgeo.org/grass7
 
* https://grass.osgeo.org/documentation/search-engine
 
 
* https://grass.osgeo.org/documentation/books
 
* https://grass.osgeo.org/documentation/books
* https://grass.osgeo.org/development/compiling-grass-gis
 
 
* https://grass.osgeo.org/development/svn
 
* https://grass.osgeo.org/development/svn
* https://grass.osgeo.org/development/svn/svn-tags
+
* https://grass.osgeo.org/development/svn/svn-tags <<-- git will do that
 
* https://grass.osgeo.org/development/svn/svn-mailing-list
 
* https://grass.osgeo.org/development/svn/svn-mailing-list
  
== To be moved to wiki (?) ==
+
=== To be moved to trac dev wiki ===
 +
 
 +
* https://grass.osgeo.org/development/bug-tracking
 +
* https://grass.osgeo.org/development/programmer-manual
 +
* https://grass.osgeo.org/development/code-submission
 +
 
 +
=== To be moved to user wiki ===
  
 +
* https://grass.osgeo.org/home/press-releases
 
* https://grass.osgeo.org/documentation/general-overview
 
* https://grass.osgeo.org/documentation/general-overview
 
* https://grass.osgeo.org/documentation/first-time-users
 
* https://grass.osgeo.org/documentation/first-time-users
 +
* https://grass.osgeo.org/home/credits
 +
* https://grass.osgeo.org/home/history
 +
* https://grass.osgeo.org/home/history/releases
 +
* https://grass.osgeo.org/home/history/documents
 +
* https://grass.osgeo.org/home/history/van-warren-notes
  
== To be trashed ==
+
=== To be trashed ===
  
 
* <del>https://grass.osgeo.org/download/software/live-cdrom</del>
 
* <del>https://grass.osgeo.org/download/software/live-cdrom</del>
 +
* <del>https://grass.osgeo.org/documentation/search-engine</del>
 +
* <del>https://grass.osgeo.org/development/compiling-grass-gis</del>
 +
* <del>https://grass.osgeo.org/grass7</del>
 +
 +
[[Category: Website]]

Latest revision as of 04:09, 2 May 2019

This page is a first draft roadmap of priorities for the migration from our current CMSMS website (grass.osgeo.org) to Wordpress (staging.grass.osgeo.org) a Hugo/git based solution.

Why a new Website

First impressions is usually the influence that gives the biggest effect and our current CMSMS website is getting completely dated and non-attractive. Therefore, to redesign GRASS GIS website is of high priority for the project. Moreover, the current site is pretty hard to maintain and most of the work is done by one or two persons. This becomes a pretty heavy task in occasions. Most importantly, the old CMSMS template is not responsive, i.e., not mobile friendly, which prevents GRASS GIS users and especially potential new users to browse related contents on mobile. This is nowadays an important drawback as compared with other projects and proprietary options.

To enable more people to contribute and contents to be more discoverable and easy to browse, a complete redesign with different technology is planned. Particularly, we consider static website design through HUGO which has several assets over Sphinx, including more web design freedom and many responsive theme available to build on. Moreover, content can be written in Markdown which is much simpler than HTML. We plan to host the site on a git-flavored instance as well, so contributions are significantly eased as compared with the current CMSMS.

For these reasons, we believe it’s imperative to refresh our website in line with recent design trends, technological advancements and search engine algorithms. In this way, we are confident that more people will contribute to keep it alive with blog posts and examples as well as with maintenance. Moreover, GRASS GIS contents will be more discoverable for the newcomers, which we hope will then benefit the whole OSGeo community.

Technology

Desired content

  • ...
  • ... your ideas here (but please check also below for existing content)

Expected workload

  • Research and planing (gathering information about project, users, existing content, type of media...)
  • Solution design (creating wireframes, sitemaps and user workflows)
  • Solution setup (local Hugo install, templates and base layouts)
  • Web design (HTML and CSS to integrate the GRASS GIS branding)
  • Responsive adaptations (CSS media queries, possibly bites of JS)
  • Content writing (Bringing the default markdown files, with minimal content)
  • Testing (including common mobile browsers)
  • Corrections and fixes (iterations according to community feedbacks)

Crowd funding campaign

Design and implementation phase

  • The GRASS PSC will work out details in the next weeks.

Existing content - to be restructured

High priority

Legal:

The team:

Software (see also "To be merged"):

Sample Data:

Docs:

Use cases:

Community:

To be merged

These 3 pages should become a single page sponsorship

These should be all combined into download/software (see also above)

All these screenshots could be converted into a "Gallery", for example

Low priority

To be moved to trac dev wiki

To be moved to user wiki

To be trashed