nasaworldwind / nasaworldwind.github.io Goto Github PK

This issue is an continuation of #80 (tasks for WW's public channels).

Read through Google Analytics' SEO starter guide and use this as a way to define further SEO tasks for WorldWind site.

What site generation options are available that can do the following:

1. Work within Travis-CI and on a local machine
2. Build static site and utilize Travis deploy functionality to GH Pages
3. Easy to use and pick up
4. Lots of formal and informal documentation/examples

Examples:
Jekyll, Hugo, Roots

Develop shortcode or other methodology to embed Web World Wind tutorials and examples in the site.

There are several components of the current "Get Started" page which will be ported to different pages of the new site.

Define the tasks and next steps needed for managing WorldWind's public channels:

• worldwind.arc.nasa.gov
• goworldwind.org
• webworldwind.org
• GitHub
• Forum

The new website structure should unify the three existing sites: worldwind.arc.nasa.go, goworldwind.org, and webworldwind.org. The content structure, presentation, and look needs to be common. Ensuring the underlying infrastructure of the site supports this goal will facilitate the porting of content from the different sites.

• Clear the current repository and stop automatic updates during new site development (#21)
• Establish site configuration and structure based on current site (#9)
• Create underlying html templates to ease site development and provide common display patterns (#10)
• Enable Travis, wait for Travis deployment until site is finalized (#12)

Synchronize the new Hugo site with any content in goworldwind.org and webworldwind.org not already included. Adapt the Hugo Java and Web sections as needed to include missing content or layout adjustments.

Extend the current NPM based content retrieval mechanisms to integrate into the static site generator.

The dynamic assets folder doesn't seem to be cloning to Ames, or it is referenced incorrectly by the site.

Applications need the capability to make text labels visible over the map background. Text outlines provide this capability and is usable with any combination of light/dark text and light/dark backgrounds.

Enhance text outline control in WebWorldWind and WorldWindAndroid by extending TextAttributes with the following properties:

• Outline enable bit
• Outline width
• Outline color

Spike task to find out what is involved with adopting Google Analytics.

• Take overview of entire Google Analytics Solutions site
• Try demos
• View capabilities/features
• Find out how to integrate

Establish a WebStorm project for the new Hugo based site.

Reported via email: The link " https://worldwind.arc.nasa.gov/?root=web" appears to be broken. Both IE and Firefox give error messages when clicking on the 'Web' button here:

Assess goals and objectives of proposed EO OpenScience presentation(s) and develop the software requirements needed to satisfy those goals.

Migrate the trial Bintray premium account in order to restore nasaworldwind as an OSS organization.

Transition the content from webworldwind.org to new site. Combine the overview and feature pages.

Transition the content from webworldwind.org to new site.

Create the pages for Home, About, and Contact

Configure Travis CI to deploy build and deploy pushes on the develop branch. Since this is a GitHub pages Organization/User site, use the built-in Travis CI GitHub pages deployment to publish to the master branch.

Spike task to determine how we will use elements of search engine optimization to build content and structure of website.

Questions:
-What words do users look for?
-What words do search engines look for?
-What are keywords to site?
-What social media platforms to use for outreach?
-Should site structure include "Blog" and/or "News and Events" page?
-What are common topics in the WorldWind forum?

Investigate: site content for keywords, community forum, optimal social media platforms, keywords for related content.

Spike limit: 1 day.

• How should content be structured?
• How can we improve on the current implementation?
• Can we harmonize the three projects and leverage common industry content structures (e.g. Overview, Download/Setup, Tutorials, Docs, Examples, Wikis???)

Transition the content from goworldwind.org to new site.

The new site will use a substantially different layout than the current one. There needs to be an orderly transition where the old site will stop updating our primary site (https://worldwind.arc.nasa.gov/), but still allow for development of the new static generator based site.

• Turn Off Travis Builds
• Remove Travis deploy configuration
• Determine if we want to eliminate the repo history when replacing site

Populate the static site with the content from goworldwind.org and webworldwind.org in preparation for transition from those sites.

This will consist of the following tasks:

• Port Java Overview and Features (#27)
• Port Web Overview and Features (#28)
• Port Java Developer Guide, Tutorials, and Examples (#29)
• Port Web Developer Guide, Tutorials, and Examples ( #30)
• Synchronize content and structure with the existing WordPress sites (#52)

Candidate sections:

• Overview

  • Purpose
    • Vision/Scope
  • Features
    • GeoPackage
    • Integrated GeoWebCache
    • GDAL Formats

• Developer

  • Architecture/Design
    • Module descriptions
    • UML diagrams
  • How to build
    • Maven
    • Github

• User

  • Documentation
    • Export GeoPackage
    • WorldWind Preview
    • Out-of-the-box settings
    • Common Issues/FAQ, e.g., CORS
  • How to add features
  • How to install/configure
    • Standalone/Jetty
    • Tomcat
    • Memory allocation
    • JAI
  • How to interface with clients

Please join Dave Collins & Patrick Hogan, presenting virtually from the AMES research center in California, who will discuss the latest advances to NASA’s WorldWind, a powerful open-source virtual globe SDK for development of web & mobile applications. The WorldWind team will touch on the recent developments to Web WorldWind, its associated Server Kit, WorldWind Java, and WorldWind Android as well as the adoption and use of the WorldWind SDK by various U.S. Gov’t sponsors.

September 8 at 1130 Eastern.

Add missing links to site and adjust links to WorldWind examples so that they open up in a new tab.

Prepare the Apache server at worldwind.arc.nasa.gov for the transition to the new Hugo based site. Apache is configured with a complex set of aliases in order to link to content historically published under worldwind.arc.nasa.gov.

Contents of /var/www/html

/agrosphere
/alaska
/assets/java/...
/assets/web/api-doc
/kml-samples
/milstd2525c
/NASAWorldWind.github.io
/quakehunter
/SARApp
/spacebirds
/springfield
/standalonedata
/temp
/videos
/worldweather

Apache configuration

DocumentRoot /var/www/html/NASAWorldWind.github.io
Redirect "/java/index.html" "/"
RedirectMatch "^/java$" "/"
RedirectMatch "^/java/$" "/"
Alias "/alaska" "/var/www/html/alaska/"
Alias "/java/apps/SARApp" "/var/www/html/SARApp/"
Alias "/java/apps/springfield" "/var/www/html/springfield"
Alias "/java" "/var/www/html/assets/java/"
Alias "/kml-samples" "/var/www/html/kml-samples/"
Alias "/milstd2525c" "/var/www/html/milstd2525c/"
Alias "/quakehunter" "/var/www/html/quakehunter/"
Alias "/spacebirds" "/var/www/html/spacebirds/"
Alias "/agrosphere" "/var/www/html/agrosphere/"
Alias "/temp" "/var/www/html/temp/"
Alias "/videos" "/var/www/html/videos/"
Alias "/worldweather" "/var/www/html/worldweather/"
Alias "/web" "/var/www/html/assets/web/"
Alias "/standalonedata" "/var/www/html/standalonedata/"

Review and validate all links in the new Hugo based site

Adjust the layout and images used by the new Hugo based site in preparation for deployment.

• Develop new method for embedding Web World Wind examples (#31)
• WorldWindServerKit website section (#34)
  • enhancements to Web, Android tutorials

Add refinements to the site for aesthetics.

Port the content from the current website implementation to the new site.

The organization should allow for unity between the three projects. To that end, I think the following project pages should be available for each project

• Overview (includes features)
• Get Started (includes Download and Setup)
• Developer Guide
• Tutorials
• Examples (can be links to other projects or applications)
• Docs

Porting the current content will consist of the following steps:

• Common Pages (#24)
• Android "Get Started" (#25)
• Android Developer Guide, Tutorials, and Examples (#26)

Mock up a small sample of the website to get a better understanding of what a full implementation would require. Check Travis and GitHub Pages integration.

The publication of daily builds to the repository has increased its size enormously. Most of the commits contain only date changes on a number of javadoc files. Removing the near duplicate files could significantly decrease the size of the repository without compromising the salient history.

In coordination with @pdavidc and @RandolphKim deploy the static assets of the current website (primarily all docs and webstarts in the asset directory) to hosting at Ames. The files will then be removed from the repository and the repository re-initialized to reduce size.

• Host static documentation/webstart/etc assets at Ames (specifically, everything from the java and web-api roots in the asset folder)
• Remove static assets from website files and check all links and items still resolve

Once the above tasks are complete the repository size can be reduced by re-initializing the repo. Steps:

• Ensure final site and functionality are the latest in the directory structure
• Remove/merge all branches from GitHub except master and develop
• Move the .git folder to a backup location
• Init the repository
• Checkout a 'develop' branch
• Add all the files present
• Make the initial commit
• Set the remote origin to GitHub
• git push --force

Implement the site generator, and required directory/file structure to meet the needs of #9. This would be the common site initialization, configuration, and setup provided by the site generator.

Complete the migration from the Oracle Jet based site to the new Hugo based site, which includes content from the Oracle Jet site, content from goworldwind.org, and content from webworldwind.org.

• Validate links (#56)
• Ensure content is contained in Hugo static resources (#61)
• Per-project API documentation links (#57)
• Update README to reflect latest design and structure (#65)
• Layout and image adjustments (#58)
• WebStorm project (#59)
• Hugo site link adjustments (#77)
• Prepare Apache for transition to new Hugo based site (#73)
• Travis CI deployment from develop branch (#12)

Establish per-project API documentation links in the new Hugo based site.

The structure of the site, particularly the front matter and template variables, have changed considerably since project inception. The README file needs to be updated to reflect the latest design of the site.

Make sure all content (images, etc.) is contained within the repository.

Add a curated table of contents to the Android Tutorials page. It is difficult to assess the contents of this page due to its size. Also, it can be difficult locate a tutorial on specific subject matter if you don't know its name. A concise, categorized list of it's contents with internal page links would improve the utility of this page.

Restore the Travis CI configurations used by NASA WorldWind projects to the default notification scheme. The original goal of notifying everyone on every build is now unnecessary, as GitHub protected branches and mandatory pull requests ensure that only successful builds make it into the develop and master branches. Removing our custom Travis CI notification blocks has two benefits:.travis.yml is simpler and noisy build notifications stop.

• Restore WebWorldWind (NASAWorldWind/WebWorldWind#162)
• Restore WorldWindAndroid (NASAWorldWind/WorldWindAndroid#123)
• Restore WorldWindJava (NASAWorldWind/WorldWindJava#113)
• Restore WorldWindServerKit (NASAWorldWind/WorldWindServerKit#73)
• Revoke Travis CI builds permission to post at team mailing list, and restore default Google Groups permissions

Port the developer guide, tutorial, and example content from the current website to the new website.

1. Describe interns' role in working with WW.
2. Identify apps to add (current, last year, year before that?)
3. Add description of apps and their url/github links

Add functionality to automatically update the external library hosting version information of the World Wind projects. Utilize Travis, our CI environment, to query the API's of the services which host our compiled libraries and update the website contents daily.

The initial focus will be Java Maven based projects. A daily cron job running on the develop branch of this website will run a script which will query the APIs, update files, and then push the latest to the master branch using the Travis GitHub Pages deploy functionality.

• Implement and test an extensible API query and website update script
• Remove daily build javadocs publishing from WWJ
• Remove daily build javadocs publishing from WWA
• Remove release javadocs publishing to this site from WWJ
• Remove release javadocs publishing to this site from WWA
• Coordinate WWSK documentation publishing with @emxsys
• Add Bintray API query for latest WWA version and javadocs
• Add website update based on query results and latest javadocs
• Add invocation of update via Travis
• Update non-dynamic asset links to point to static hosting at Ames
• Remove asset directory and contents

Develop the presentation(s) to be presented at the EO Open Science conference in September.

Create a mockup of the WorldWind websites that revises and redesigns the current content.

Prototype the current landing page and webworldwind.org to test usability and to better understand what full implementation will require. The prototypes will be built using Hugo as the site generator.

Redirect existing non-NASA WorldWind domains used for WorldWind help websites to worldwind.arc.nasa.gov.

Existing domains

Transfer ownership of these domains. Establish domain-only hosting for at least one year.

• goworldwind.org
• webworldwind.org
• worldwindserver.net

New domains

Establish domain-only hosting for at least one year.

• worldwind.io
• goworldwind.com
• webworldwind.com

Establish hosted per-project API documentation on each project's gh-pages branch. Push an initial static site containing API docs from the develop branch. Configure Travis CI to automatically build and push API docs on each push to develop.

• Initial WebWorldWind API docs (NASAWorldWind/WebWorldWind#165)
• Initial WorldWindAndroid API docs (NASAWorldWind/WorldWindAndroid#125)
• Initial WorldWindJava API docs (NASAWorldWind/WorldWindJava#116)
• Evaluate need for WorldWindServerKit hosted docs(NASAWorldWind/WorldWindServerKit#80)

Transition the content from goworldwind.org to new site. Combine the overview and feature pages.