|
| 1 | +--- |
| 2 | +title: Documentation |
| 3 | +description: How to use this site |
| 4 | +--- |
| 5 | + |
| 6 | +## Search for projects |
| 7 | + |
| 8 | +### Organization |
| 9 | + |
| 10 | +The projects are organized by the hosting platform, user name, and project name. |
| 11 | +The organization is hierarchical, so each section lists the available projects |
| 12 | +nested below it. Some concrete examples: |
| 13 | + |
| 14 | +* `/projects/` - Lists all workflowr projects available on workflowr.io |
| 15 | +* `/projects/github/` - Lists the workflowr projects hosted on [GitHub][] |
| 16 | +* `/projects/github/jdblischak/` - Lists the workflowr projects by [GitHub][] user [jdblischak][] |
| 17 | +* `/projects/github/jdblischak/fucci-seq` - Main page for workflowr project [fucci-seq][] |
| 18 | + |
| 19 | +[GitHub]: https://github.com/ |
| 20 | +[jdblischak]: https://github.com/jdblischak/ |
| 21 | +[fucci-seq]: https://github.com/jdblischak/fucci-seq |
| 22 | + |
| 23 | +### By topic |
| 24 | + |
| 25 | +Some users have added topics to categorize their workflowr projects. This makes |
| 26 | +it easier to find projects you are interested in. The most popular topics are |
| 27 | +listed on the home page, but you can view all available topics at |
| 28 | +[/topics/](/topics/). Clicking on a topic will take you to a page that lists all |
| 29 | +the projects labeled with this topic, e.g. [single-cell](/topics/single-cell/). |
| 30 | + |
| 31 | +### Search bar |
| 32 | + |
| 33 | +The navigation bar contains a search bar powered by [DuckDuckGo][]. When you use |
| 34 | +the search bar, you will be redirected to DuckDuckGo's website with the results |
| 35 | +of your query limited to workflowr.io. |
| 36 | + |
| 37 | +[DuckDuckGo]: https://duckduckgo.com/ |
| 38 | + |
| 39 | +## Add a project |
| 40 | + |
| 41 | +### Install GitHub App |
| 42 | + |
| 43 | +In order to add your workflowr project to workflowr.io, you need to install the |
| 44 | +[workflowr.io GitHub App][github-app] for the specific repositories that you |
| 45 | +want to share. This app only requests read-only access to a minimal set of |
| 46 | +information about your repository. In fact, it only accesses information that is |
| 47 | +available for all public repositories on GitHub. |
| 48 | + |
| 49 | +[github-app]: https://github.com/apps/workflowr-io |
| 50 | + |
| 51 | +### Edit description |
| 52 | + |
| 53 | +The description of your workflowr project is obtained from the Description section on GitHub. Whatever you type there will be reflected on workflowr.io. If your repository doesn't have a Description on GitHub, then workflowr.io creates the description using the following pattern: |
| 54 | + |
| 55 | +> The workflowr project \<project name\> by \<user name\> |
| 56 | +
|
| 57 | +### Add topics |
| 58 | + |
| 59 | +The topics assigned to workflowr projects on workflowr.io are obtained directly from the topics you assigned to your GitHub repository. We highly encourage you to add topics to make it easier for others to find your project both on workflowr.io and GitHub. |
| 60 | + |
| 61 | +* [GitHub Help: Classifying your repository with topics](https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/classifying-your-repository-with-topics) |
| 62 | + |
| 63 | +### Remove a project |
| 64 | + |
| 65 | +To remove one of your projects from workflowr.io, you can uninstall the |
| 66 | +[workflowr.io GitHub App][github-app] from the repository. |
| 67 | + |
| 68 | +There are two ways you can access the configuration for the GitHub App: |
| 69 | + |
| 70 | +* Go the the Settings for the repository and then navigate to the menu for Integrations |
| 71 | + |
| 72 | +* From your user home page, go to Settings and then navigate to Applications |
| 73 | + |
| 74 | +Regardless of which method you used, next click Configure for the workflowr.io |
| 75 | +GitHub App. You can choose to uninstall the app for one or more repositories by |
| 76 | +clicking on the X next to their name. To remove the app from your account (and |
| 77 | +thus any projects it was installed on), click the button at the very bottom to |
| 78 | +uninstall the app from your account. |
| 79 | + |
| 80 | +## About this site |
| 81 | + |
| 82 | +### Purpose |
| 83 | + |
| 84 | +The goal of the [workflowr][] R package is to make your data analysis projects |
| 85 | +more organized, reproducible, and shareable. The purpose of workflowr.io is to |
| 86 | +increase the discoverability of workflowr projects. Currently, most readers will |
| 87 | +find your workflowr website only if you directly send them the URL or if you |
| 88 | +include the URL in your published manuscript. By curating workflowr projects, |
| 89 | +workflowr.io makes it easier for other interested readers to find your |
| 90 | +reproducible results. In essence, it is promoting transparency and openness. |
| 91 | + |
| 92 | +[workflowr]: https://jdblischak.github.io/workflowr/ |
| 93 | + |
| 94 | +None of the workflowr projects are actually hosted on workflowr.io. Instead, it |
| 95 | +is a centralized directory of available projects to explore. The individual |
| 96 | +project pages provide links to the website and source Git repository. |
| 97 | + |
| 98 | +### Update frequency |
| 99 | + |
| 100 | +This site is updated every X hours. If you (un)install the GitHub app or make |
| 101 | +any changes to your project, please check back in a few hours to see the update |
| 102 | +take effect. |
| 103 | + |
| 104 | +### Technology |
| 105 | + |
| 106 | +This site was made possible by many different technologies. Highlighting a few |
| 107 | +of them: |
| 108 | + |
| 109 | +* [Bulma](https://bulma.io/) - CSS framework |
| 110 | +* [DuckDuckGo](https://duckduckgo.com/) - Search bar |
| 111 | +* [GitHub API](https://docs.github.com/v3/) - Obtain metadata on workflowr projects hosted on GitHub |
| 112 | +* [Hugo](https://gohugo.io/) - Static site generator |
| 113 | +* [Netlify][] - Deploy and host site |
| 114 | +* [R](https://www.r-project.org/) - Data management |
| 115 | + |
| 116 | +[Netlify]: https://www.netlify.com/ |
| 117 | + |
| 118 | +### Funding |
| 119 | + |
| 120 | +The [workflowr][] project is grateful for support from the [Moore |
| 121 | +Foundation][moore] and the University of Chicago][uchicago]. |
| 122 | + |
| 123 | +[moore]: https://www.moore.org/ |
| 124 | +[uchicago]: https://www.uchicago.edu/ |
| 125 | + |
| 126 | +### Privacy |
| 127 | + |
| 128 | +> **tl;dr** We don't collect any data on you. |
| 129 | +
|
| 130 | +#### For site visitors |
| 131 | + |
| 132 | +We don't collect any data on you. We don't store any cookies. In fact, there |
| 133 | +isn't even any JavaScript running on this site. |
| 134 | + |
| 135 | +If you use the search bar, you will be taken to duckduckgo.com. However, they |
| 136 | +are a [privacy-conscious company](https://duckduckgo.com/about), and they do not |
| 137 | +store your search queries or track you. |
| 138 | + |
| 139 | +The website is hosted on [Netlify][] servers. We have no reason to believe they |
| 140 | +collect any personal information from you. See their [Terms of Use |
| 141 | +Agreement][netlify-toc] for more details. |
| 142 | + |
| 143 | +[netlify-toc]: https://www.netlify.com/legal/terms-of-use/ |
| 144 | + |
| 145 | +#### For workflowr users |
| 146 | + |
| 147 | +The workflowr.io GitHub App only accesses publicly available data for your |
| 148 | +GitHub repository. In other words, any data displayed on workflowr.io is also |
| 149 | +easily accessible by browsing GitHub or querying publicly accessible endpoints |
| 150 | +of their API. |
| 151 | + |
| 152 | +## Miscellaneous |
| 153 | + |
| 154 | +### Getting started with workflowr |
| 155 | + |
| 156 | +To start using workflowr, the best place to start is to go through the [Getting |
| 157 | +started vignette][getting-started]. This will take you from zero to deploying a |
| 158 | +website. Once you are comfortable with the basics of the workflowr framework, |
| 159 | +you can read through the other [vignettes][]. For example, if you already have |
| 160 | +an existing project that you would like to migrate to use workflowr, read |
| 161 | +[Migrating an existing project to use workflowr][migrating]. |
| 162 | + |
| 163 | +[getting-started]: https://jdblischak.github.io/workflowr/articles/wflow-01-getting-started.html |
| 164 | +[vignettes]: https://jdblischak.github.io/workflowr/articles/index.html |
| 165 | +[migrating]: https://jdblischak.github.io/workflowr/articles/wflow-03-migrating.html |
| 166 | + |
| 167 | +### Support for GitLab |
| 168 | + |
| 169 | +Not yet. The initial launch of workflowr.io only supports GitHub because it is |
| 170 | +the most popular service for hosting workflowr projects. However, since |
| 171 | +workflowr also supports [hosting projects on GitLab][hosting-with-gitlab], we |
| 172 | +plan to add support for public repositories hosted on [GitLab][]. |
| 173 | + |
| 174 | +[GitLab]: https://about.gitlab.com/ |
| 175 | +[hosting-with-gitlab]: https://jdblischak.github.io/workflowr/articles/wflow-06-gitlab.html |
0 commit comments