Initial Release (#1)

* initial commit
* adding changelog
* fixing action submission
* 1.0.0
* adding deploy workflow
* removing old README
* adding code of conduct
* adding contribution guidelines
* updating README

Author: dillonredding

.github/workflows/deploy.yaml

@@ -0,0 +1,18 @@
+# Deploys to Heroku when a release is created
+
+name: Deploy to Heroku
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  publish-npm:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+          registry-url: https://registry.npmjs.org/
+      - run: git push heroku master

.gitignore

@@ -0,0 +1,23 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.js
+
+# testing
+/coverage
+
+# production
+/build
+
+# misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

CHANGELOG.md

@@ -0,0 +1,38 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog][kac], and this project adheres to
+[Semantic Versioning][semver].
+
+[kac]: https://keepachangelog.com/en/1.0.0
+[semver]: https://semver.org/spec/v2.0.0.html
+
+## Unreleased
+
+### Added
+
+- Error response reporting
+- Non-Siren response handling
+- Tags for actions' `method` and `type`
+- Configuration options
+  - Siren client headers
+  - Title casing property names
+- Display original JSON source (in addition to current state)
+
+### Changed
+
+- Center location input control
+- Update location input control value to show current location
+
+## 1.0.0
+
+### Added
+
+- Fetch entry point URL
+- Display an (embedded) entity
+  - Render the `title` as the header, the `class` elements as tags, and panels
+    for the `actions`, `links`, and `entities`
+  - JSON representation of the entity
+- Follow (embedded) links
+- Submit actions

CODE_OF_CONDUCT.md

@@ -0,0 +1,79 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and our
+community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and
+expression, level of experience, education, socio-economic status, nationality,
+personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <[email protected]>.
+All complaints will be reviewed and investigated and will result in a response
+that is deemed necessary and appropriate to the circumstances. The project team
+is obligated to maintain confidentiality with regard to the reporter of an
+incident. Further details of specific enforcement policies may be posted
+separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+[version 1.4][v1.4]
+
+[homepage]: https://www.contributor-covenant.org
+[v1.4]: https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+For answers to common questions about this code of conduct, see the [FAQ].
+
+[faq]: https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,79 @@
+# Contribution Guidelines
+
+Thank you for taking the time and consideration to contribute to [Siren.js]!
+
+[siren.js]: https://github.com/siren-js
+
+This document outlines our guidelines for contributing to this repository, which
+is part of the Siren.js project. Following these guidelines helps communicate
+that you respect the time of the developers managing and developing this open
+source project. In return, they should reciprocate that respect in addressing
+your issue, assessing changes, and helping you finalize your pull requests.
+Check out the [Code of Conduct](CODE_OF_CONDUCT.md) to learn about our core
+values and norms.
+
+If you have feedback or questions, your contribution has been sitting for a
+while, you need help, or would like to talk through a contribution, feel free to
+join the [Google Group][gg]!
+
+[gg]: https://groups.google.com/g/sirenjs
+
+> First time contributing to open source? You can learn how from this _free_
+> video series: [How to Contribute to an Open Source Project on GitHub][course].
+
+[course]: https://kcd.im/pull-request
+
+## Bugs and Feature Requests
+
+If you find a bug or would like to request a new feature, be sure to check out
+the current list of [issues]. If you can't find anything, feel free to
+[create a new one][create-issue].
+
+[issues]: https://github.com/siren-js/api-browser/issues
+[create-issue]: https://github.com/siren-js/api-browser/issues/new
+
+## Pull Requests
+
+If you'd like to contribute a change, follow these steps:
+
+1. Fork the repository.
+1. Clone your fork.
+1. Create a branch.
+1. Make and commit your changes (see [Development](#development)).
+   - Be sure to update the [changelog](CHANGELOG.md).
+   - If you're making code changes, be sure to write tests!
+1. Push your changes to your fork.
+1. If your build is passing, create a pull request.
+1. Wait for a review and make changes as requested.
+1. Get merged!
+
+## Development
+
+Setup is simple. `cd` into the project directory and run `npm install`. Now
+you're ready to code!
+
+In the project directory, you can run the following commands
+
+- `npm start` - Runs the app in the development mode. Open
+  <http://localhost:3000> to view it in the browser. The page will reload if you
+  make edits. You will also see any lint errors in the console.
+- `npm test` - Launches the test runner in the interactive watch mode. See the
+  section about [running tests][testing] for more information.
+- `npm run build` - Builds the app for production to the `build` folder. It
+  correctly bundles React in production mode and optimizes the build for the
+  best performance.
+
+  The build is minified and the filenames include the hashes. Your app is ready
+  to be deployed!
+  
+  See the section about [deployment] for more information.
+
+[testing]: https://facebook.github.io/create-react-app/docs/running-tests
+[deployment]: https://facebook.github.io/create-react-app/docs/deployment
+
+This project uses [SemVer](https://semver.org/). When making code changes, be
+sure to increment the version accordingly with the
+[`npm version` command][npm-version]. We recommend using the
+`--no-git-tag-version` option to avoid potential issues.
+
+[npm-version]: https://docs.npmjs.com/cli/v7/commands/npm-version

README.md

@@ -1,2 +1,13 @@
-# api-browser
-Siren API browser that uses Siren.js
+# Siren.js API Browser
+
+Siren API browser implemented with [Siren.js client][client], [React], and
+[Bulma].
+
+[client]: https://github.com/siren-js/client
+[bulma]: https://bulma.io/documentation
+[react]: https://reactjs.org
+
+## Contributing
+
+If you would like to contribute anything from a bug report to a code change, see
+our [contribution guidelines](CONTRIBUTING.md).