Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of resources #7

Open
tgerke opened this issue Jul 4, 2018 · 2 comments
Open

List of resources #7

tgerke opened this issue Jul 4, 2018 · 2 comments

Comments

@tgerke
Copy link
Member

tgerke commented Jul 4, 2018

I try (mostly unsuccessfully) to keep a running list of sites/blogposts/similar that have been crucial in completing certain tasks. I'm sure we all do the same. I was thinking about how we linked this site up through netlify with another domain: I'm sure there are amazing walkthroughs out there for doing this, so there would be no need to create a blog post. Almost selfishly though, I'd like to document how we did it, so it could be done again if necessary (even if said documentation is a link to someone else's). Could there be a space on this site for a list of resources which are searchable by keyword that we've used to complete things that would have otherwise been cumbersome?

@gadenbuie
Copy link
Member

@jhcreed said:

I always go through like 6 tutorials before I do something like this though so I think the more we have (no matter how basic it seems) the better

I agree too. Would the blog section work? We can post these kinds of posts under a consistent category, like Tutorial or Walkthrough, then there are category views: http://www.gerkelab.com/categories/r-development/

For increased visibility I can add category links to the header of the blog list at http://www.gerkelab.com/blog/ ... but we can wait until we have a bit more content for this step.

Adding search is a somewhat separate feature that I can pull out into it's own issue if we want that.

Blog posts are great for the "hey, I used this and here's how I made it work" kind of posts, and I'm all for having lots of these even if they're short. But if you're thinking of a more long-running document, we could do a package/resource list in the style of Awesome R that we can build into the website as a page rather than a post.

@tgerke
Copy link
Member Author

tgerke commented Jul 5, 2018

You make a good point re: there is no need to put a minimum length on blog posts. I do click a lot of blog links that seem cool, and then I just go "ugh, tl;dr." Perhaps putting things in quick blogs is good for now; if we see the need for a list later we can open a new issue and restructure as appropriate.

@gadenbuie gadenbuie mentioned this issue Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants