pangeo-data / pangeo-data.github.io

#Clean Blog by Start Bootstrap - Jekyll Version

The official Jekyll version of the Clean Blog theme by Start Bootstrap.

###View Live Demo →

Before You Begin

In the _config.yml file, the base URL is set to /startbootstrap-clean-blog-jekyll which is this themes gh-pages preview. It's recommended that you remove the base URL before working with this theme locally!

It should look like this: baseurl: ""

What's Included

A full Jekyll environment is included with this theme. If you have Jekyll installed, simply run jekyll serve in your command line and preview the build in your browser. You can use jekyll serve --watch to watch for changes in the source files as well.

A Grunt environment is also included. There are a number of tasks it performs like minification of the JavaScript, compiling of the LESS files, adding banners to apply the MIT license, and watching for changes. Run the grunt default task by entering grunt into your command line which will build the files. You can use grunt watch if you are working on the JavaScript or the LESS.

You can run jekyll serve --watch and grunt watch at the same time to watch for changes and then build them all at once.

Support

Visit Clean Blog's template overview page on Start Bootstrap at http://startbootstrap.com/template-overviews/clean-blog/ and leave a comment, email [email protected], or open an issue here on GitHub for support.

pangeo-data.github.io's Issues

Initial website content

@pangeo-data/pangeo-dev -

I've thrown up a very bare bones pangeo-data website and copied in some initial content. The website is live here: https://pangeo-data.github.io/

I'm going to post a few issues that cover:

• Artwork
• Design of a page to show packages in pangeo-data
• Design of a page to show papers that use xarray/pangeo-data
• Design of a page with a gallery of talks and presentations using xarray/pangeo-data

pangeo-data publications website page

We need a page that we can use to point to publications that have used pangeo packages or xarray.

I'm somewhat partial to using an automated / yaml approach similar to what I use in my personal website (web, github). This would provide a relatively easy way to standardize formatting.

I'm open to ideas on how to organize the page [by subject area (atmos, ocean, etc), by software or science, one big list, etc.]

pangeo-data packages website page

We need a page that highlights the various packages related / included in pangeo.

Title is wrong

The title now shows up as "motivation" rather than "Pangeo Data". This did not happen in my local jekyll build!

add design documents to packages page

For now, I think it would be good to embed or link to our design documents on the website. I would like to get input from the broader community on them.

What is the best way to do this? The hackpads actually have very little flexibility in terms of permissions. We don't want them to just be editable by the entire world.

One option would be to translate them to markdown, put them into a repo (maybe the website repo itself, maybe the individual project repos, idk) and seek input as github issues or pull requests.

How should we handle this?

blog post for xarray 0.10.0 release

@jhamman, any interest in using this blog as a platform to explain all of the hard work and exciting new features that are going into the new xarray release?

Replace stock images in website

We need some geoscientific artwork for the website.

Any need/interest on the design docs?

Hi all,

I'm working on a project closely related to some of the needs mentioned in this vector calculus design doc. I know some of this is several years old, so can anyone share an update on where this stands? If it's a solved problem, can you send links to solid libraries? If not, what are the biggest needs?

Thanks!

• Alex

Can't access design documents

I just tried clicking through the menu to access the design documents, and couldn't get anywhere - the link is always to the current page. I tried a few different browsers, but none of them behaved as expected.