Added R-Shiny to the Front-End Development secion.

[0exbot]

Pull request from @grabear.

• title: R-Shiny
• head: Front-End Development
• desc: Web Framework built with R.
• url: https://github.com/grabear/awesome-rshiny
• stars: 674
• size: 289
• extra: +
• updated: 2022-06-22 21:17
• created: 2017-09-27 22:24
• pull: Added R-Shiny to the Front-End Development secion. sindresorhus/awesome#1069

https://github.com/grabear/awesome-rshiny

This awesome list is a compilation of useful R-Shiny resources. R-shiny has been available for several years now, and has evolved into a highly useful package for Data Scientists who are not necessarily familiar with web development. It gives these scientist an opportunity to create great web application for their publications and affiliated institutions. Accepting this link into the Front End Development section will bring more awareness to the inherit usefulness of Shiny as a web framework.

By submitting this pull request I confirm I've read and complied with the below requirements.

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

• I have read and understood the contribution guidelines and the instructions for creating a list.
• This pull request has a descriptive title.
  For example, Add Name of List, not Update readme.md or Add awesome list.
• The entry in the Awesome list should:
  • Include a short description about the project/theme of the list. It should not describe the list itself.
    Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
  • Be added at the bottom of the appropriate category.
• The list I'm submitting complies with these requirements:
  • Has been around for at least 30 days.
    That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  • It's the result of hard work and the best I could possibly produce.
  • Non-generated Markdown file in a GitHub repo.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
  • The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
  • Not a duplicate.
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Includes a project logo/illustration whenever possible.
    • Either fullwidth or placed at the top-right of the readme. (Example)
    • The image should link to the project website or any relevant website.
    • The image should be high-DPI. Set it to maximum half the width of the original image.
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Includes the Awesome badge.
    • Should be placed on the right side of the readme heading.
    • Should link back to this list.
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
    • Should only have one level of sub-lists, preferably none.
  • Has an appropriate license.
    • That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
    • If you use a license badge, it should be SVG, not PNG.
  • Has contribution guidelines.
    • The file should be named contributing.md. Casing is up to you.
  • Has consistent formatting and proper spelling/grammar.
    • The link and description are separated by a dash.
      Example: - [AVA](…) - JavaScript test runner.
    • The description starts with an uppercase character and ends with a period.
    • Drop all the A / An prefixes in the descriptions.
    • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
  • Doesn't include a Travis badge.
    You can still use Travis for list linting, but the badge has no value in the readme.
• Go to the top and read it again.

[0exbot]

@-grabear on 2017-09-27 22:27 says: grabear/awesome-rshiny#9

[0exbot]

@-sindresorhus on 2017-10-21 18:50 says: Please read the guidelines more closely. Multiple points not followed from it. Try going through the list point for point and check that you follow it. :)

[0exbot]

@-ucg8j on 2017-10-27 09:26 says: Hi @-sindresorhus a number of changes have been made over the last couple of weeks, many to address the awesome guidelines. Would you be able to take another look at this PR and advise on any points we're still not meeting?

[0exbot]

@-sindresorhus on 2018-07-28 18:19 says: Hey, sorry for the lack of response, please see sindresorhus/awesome#1363.

[0exbot]

@-sindresorhus on 2018-09-18 19:16 says: @-grabear ⬆️

[0exbot]

@-grabear on 2018-09-19 04:46 says: @-sindresorus I will try to lint this myself tomorrow and make some changes. Been busy! :)

[0exbot]

@-sindresorhus on 2019-02-26 05:24 says: Closing for lack of activity. The repo also has not been updated since mid last year.

[0exbot]

@-DanailMinchev on 2018-08-14 21:50 says: This line is not needed, please remove it

[0exbot]

@-DanailMinchev on 2018-08-14 21:53 says: As per rules in https://github.com/sindresorhus/awesome/blob/master/pull_request_template.md#requirements-for-your-pull-request you should add the entry in the end of the category, so you need to add it after Hyperapp

[0exbot]

@-DanailMinchev on 2018-08-14 22:01 says: also, you should add #readme in the end of the link and make sure it is linked proprly

[0exbot]

@-DanailMinchev on 2018-08-14 22:06 says: No need to specify the section name in your PR title, please rename it from Added R-Shiny to the Front-End Development secion. to Add R-Shiny

[0exbot]

@-DanailMinchev on 2018-08-14 22:06 says: please also rebase your PR as it has conflicts currently