ropensci / roweb

:no_entry: [DEPRECATED] Active at https://github.com/ropensci/roweb2

⚠

This is old repo for rOpenSci's website. To contribute to the site please visit our new repo roweb2 and add your contributions there. If you wish to access the old site (locked on October 26, 2017) visit legacy.ropensci.org

⚠

License

For more information see the LICENSE file. © rOpenSci 2014

roweb's Issues

Add PT localization folks to community list

Diogo and Thiago

Fix the subscibe form in the footer

@sckott made it work but the css is now broken. Need to fix that. Once that's set, the footer navbar is done and we can edit after moving that to a separate file.

Easy and minor things to take care of

• Add Gauges code
• Add chat widget

But both have to wait till we template (or just add to index.html for now since that's the file we'll use to extract the template info) otherwise we'd copy and paste a bunch

Contact form

Does not have a target yet. Wufoo forms doesn't work so nicely when using our own. So this will require some work.

Logos page is missing the logos

About page

Few things to finish off in the about page.

• Get missing thumbnails
• Clean up css for the list
• Can someone link to the references in the intro text?

Then this page is done for now.

Tutorial sidebar

Hi @sckott
Wondering if we should stick to a few standard headings on the sidebar for now and make it more complicated (automatically generated from page headers) later. Or, we manually do the sidebar, but the code is still run (so we'll know if it breaks). b) shouldn't be super hard since we only have so many packages.

e.g.

Installation (can also include api keys, github install)
Usage
Support
License
Bugs

Making templates

I messed up the blog_layout.html but will let someone else take a look shortly.
Now working on:

• post.html
• page.html
• tutorial.html

Add metadata tags to post page

A bit early atm, since we have not done templating yet. But if someone wants to add that as a .txt file to the root, I'll just add it the posts template once we slice it up.

Blog post ideas

Posts to do:

Post covering some common use cases for using curl options with our packages. E.eg.

• timeout Setting a timeout via httr::timeout() or timeout.ms curl option via RCurl
• verbose Print detailed info on the curl call
• add headers via httr::add_headers for content-type, accept, etc.
• authenticate via httr::authenticate
• cookies via httr::set_cookies , maybe not
• use proxy ? via httr::use_proxy
• tell folks about RCurl::listCurlOptions() for finding curl options, give website for more info
• others?

moved from https://github.com/karthik/ropensci_web/issues/87

RNeXML or EML post

Moved from https://github.com/karthik/ropensci_web/issues/84

Growth of data sets

DONE

Moved from https://github.com/karthik/ropensci_web/issues/82

Post on Travis

A few people have asked us about our Travis integration. I wrote something internally for Carl, and to a couple of people. David Springgate just asked. So it might be worth writing a post.

It would be in the spirit of us being a larger community resource for scientific sw development.

Moved from https://github.com/karthik/ropensci_web/issues/70

text mining and taxize

Engineer from EOL suggested (and some of my additions):

Demonstrate a workflow where a user takes a pdf, website, etc., and

• submits to scrapenames() to extract names
• run names through resolution service to clean them
• get classifications for all names
• make
  • taxonomy based tree, or
  • something else...

Moved from https://github.com/karthik/ropensci_web/issues/61

Add geonames to packages page

We just brought in geonames from Barry Rowlingson (booya!) to our suite. We should add that to the list (with rMaps). Will check with him on updating docs, adding travis, rOpenSci footer, etc and update those soon. He's also stoked on collaborating wtih us on the spatial tools suite. More on that soon.

Reorganizing

Once we are done with this round of edits, it might be worth moving things around a bit to match the old URLs as much as possible.

packages.html → packages/index.html
community.html → community/index.html
anti-harrasment.html → community/anti-harrasment.html
events.html → community/events.html

Idea: We could make a folder called docs/ and move miscellanous documents in there.
e.g.

logos.html → docs/logos.html
and whatever else.

Autoforward from old rgbif tutorial link to new one

ropensci/rgbif#91

have http://ropensci.org/tutorials/rgbif_tutorial_newapi.html autoforward to http://ropensci.org/tutorials/rgbif_tutorial.html

Exclude portuguese posts from Tags archive page

@cboettig Maybe you can easily figure this out.

I have almost everything done for the localization for the portuguese posts, except I can't figure out how to exclude portuguese posts. It was easy with the archive by date page b/c I could use an if/else statement like

{% if post.categories contains 'pt' %}
       <do nothing>
  {% else if %}
       <generate entries for page>
  {% endif %}
{% endfor %}

But the tags page is a little more complicated.

See code on the pt branch: https://github.com/karthik/roweb/tree/pt

Related links

I added a page for related links.

We can use this to link to other interesting projects, and also acknowledge that Tal douche and get him off our back.

Update taxize vignette

Only on 2.x on vignette, but cran at v3

Main tagline

Main tagline reads:

Transforming science through open data

I tried to find a good background image, perhaps a network diagram showing connections. But the subway analogy works well. We're not yet connecting really disparate data but various streams at the logical connection points.

Perhaps the following words should appear in that tag line:

dots, connection, ...

Things to do on the blog page

Once the posts template is complete, we need to add:

• tags (at the bottom)
• pagination (also at the bottom)
• A blog toc page.

rWBClimate tutorial

Someone requested a tutorial. Was there ever one for this package?

Video tutorials?

@sckott made one for taxize at some point. We could link to it from the main page (see under documentation). But, we can either follow through, or not mention it if we're not going to do it at all. Thoughts?

@sckott If you can update the link on the main page to the YT video, that would be great for now.

Website todos in May

I'm afk from the 10th to 17th but will be back afterwards. Here is a rough plan of things I'd like to get done on the website in May.

Major

1. Finish a first iteration of the three themes (things you can do with our packages). Starting with the mapping and spatial tools, then the data tools, finally a page on the reproducibility tools.
2. Finish a tutorial page for all the remaining packages
3. Fix the sidebar on the tutorials page. This is a design issue and I'll see if I can work on making it read headings from the markdown and autogenerate. I'll also make it float all over the page.
4. Explore possibilities of OpenCPU widgets so people can try out code inline.

Minor

1. Finish out events page. I have a plan to do this, including a form where people can request a larger event (since we are not doing smaller workshops anymore)

Approximate milestone

June 1.

Minor things before I forget

In the community page:

• In the fragment (rOpenSci is entirely a community effort) link the word community effort to http://karthik.github.io/roweb/community.html#community

Will add more as I think through.

Move important issues

Since we settled on this as the primary website repo, would be good to move relevant issues (especially blog post ideas) over here.

Front page

@sckott @cboettig
Can you read over the front page and give it a 👍 or a 👎 ?

Especially the text. Some questions:

• Do we really have 10+ million records collectively or did it exaggerate too much?
• Does that opening paragraph look ok? It's the same as before, so could use a rewrite.

Remove the word tutorials in the tutorials page

List gender in packages page

Add GitHub to social logos in footer

As per @cboettig's suggestion. Waiting on devs to update the font scheme. This is a note to self so I don't forget.

Issue with Taxize tutorial

> temp <- gnr_resolve(names = c("Helianthos annus", "Homo saapiens"))
> temp[, -c(1, 4)]
Error in temp[, -c(1, 4)] : incorrect number of dimensions
> temp
$results
    submitted_name                matched_name data_source_title score
1 Helianthos annus        Helianthus annuus L. Catalogue of Life  0.75
2 Helianthos annus         Helianthus annus L.               EOL  0.75
3 Helianthos annus            Helianthus annus               EOL  0.75
4 Helianthos annus            Helianthus annus     uBio NameBank  0.75
5    Homo saapiens Homo sapiens Linnaeus, 1758 Catalogue of Life  0.75

$preferred
NULL

Need to use temp$results since the data structure has changed.

> temp <- gnr_resolve(names = c("Helianthos annus", "Homo saapiens"))
> temp$results[, -c(1, 4)]
                 matched_name data_source_title
1        Helianthus annuus L. Catalogue of Life
2         Helianthus annus L.               EOL
3            Helianthus annus               EOL
4            Helianthus annus     uBio NameBank
5 Homo sapiens Linnaeus, 1758 Catalogue of Life
> 

Starting templating

Not touching any of the pages yet but going to spend the next 30 minutes making the _includes folder so I can pull out the following:

• header
• navbar
• footer
• javascript
• analytics
• disqus

and a template for page (blog posts) and page (all other pages)

Minor issue

Feeds.ecology is missing on new site. Might need it for ecobloggers. @sckott

Bug

The round overlays for the core/advisors and community is broken in Safari. It wasn't an issue back in 0abdf8f but it is now. Not deploying till I figure out what got messed up since then.

😢

Localization dropdown hangs over blog title on mobile

Prevents someone from clicking on the Portuguese button... woops

Write the community page

It's a placeholder now. But emphasize the following points:

a) This is a community effort. We welcome suggestions, contributions (as collaborators, pull requests).
b) People can either bring their package to us, or pitch an idea and develop it with our help
c) Host events for us. Some notes on that.

Valley oak use case

Idea for themes

We could link each of the three circles in the bigpic section to a page each that looks like this.

Big splash image (using a class that mimics the main header on index page).

Then some powerful use cases below.

Thoughts?

Package names should link to tutorials

Right now there is only a link to the tutorials in the footer because the goal is to link all package names in the packages table to the respective tutorial page. Since we have 5 tutorials now, we should link those up.

For a newbie, clicking on a package name and ending up on a GitHub repo is a bad thing.

List missing pages from old repo for redirects

I just added a redirect from ropensci.org/codevs → ropensci.org/community, since we listed the old page in the proposal (and we can't edit the text anymore). If there are other big ones that exist in the new site but under a new name, let me know and I'll add the redirects.

Safari bug #2

The blog index breaks once you go to page 2 and beyond. The css is again off. Not going to deploy till Monday since I am out of bandwidth tonight.

Package descriptions

http://new.ropensci.org/packages/

Still read poorly. If anyone feels like killing time, please update to something more interesting.

Do we need a related packages page?

Or should we link to @sckott's excellent task view? Seems like work to maintain two sets.

Packages page

As @cboettig pointed out, it's not great to have just a long list. I'm thinking maybe a small paragraph of text saying, here are some key packages, and themes we cover. If you're new, this would be a good place to start. Otherwise see the exhaustive list below.

What other information can we include in the table? I agree that on CRAN is not particularly useful. Besides package name and description, anything else needs to go on there? We have a field for whether or not an API key is required but again not sure if that's really useful to know at this list stage.
Maybe just package name, version(?) and description. A link to the github repo since that will always exist regardless of cran?

Need help

Hi @cboettig @sckott

Looks like the site is more or less there and ready to build. Jekyll is failing all over now. Can you help?

Once we get the blog posts and tutorials to work, then we can fix things up and get to launch. There are no pending issues besides Jekyll related ones.

Running list of minor issues

Major

• The tutorials link on the bottom goes to the tutorial template. We either remove the link, or just link that to the packages page? We'll need to write at least one tutorial linking from package name to see how it works.

- [ ] Old Disqus comments are not showing up Will fix after it's live. Might fix itself.

Minor

• Fix thumbnails now for core and advisors. Hmm
• Events page is blank
• Resources page is blank

Add link to SO on resources page

Since we now have many questions.
http://stackoverflow.com/questions/tagged/ropensci

Safari bug 3

Collapsed menu does not work on sub folders in mobile safari.

Reorganize use-case page

Right now the page is a wall of ecology (not even larger biology) use cases with one general one (mapping) hidden in the middle. This could really turn away new visitors on first glance when they first visit the page for use case ideas.

I think the best way to address this will be to addd subfolders or categories. Ecology, Text mining, Mapping to begin with and nest them underneath. That way people interested in one area can dig deeper while others can see all the various possibilities without being scared away at first glance.

Implement affix.js to tutorial sidebar

Done...

I've previewed the site for the last few hours and caught most broken links, typos and issues I can find. Feels ready to deploy. So unless anyone has issues, going to push this live and tweet it out tomorrow at 9am.

Latest build: http://new.ropensci.org/

Please post any issues, fix things, or tell me to hold off. Hoping to write hackathon post and push that out tomorrow too (with a cross post to Mozilla Science).

Add instructions for getting api key in rnoaa tutorial

Fix code modal

Here: http://new.ropensci.org/blog/2013/06/19/usgs-app/

Inline code block would be better.