Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/codyogden/killedbygoogle
Part guillotine, part graveyard for Google's doomed apps, services, and hardware.
https://github.com/codyogden/killedbygoogle
front-end google hacktoberfest json open-data product react
Last synced: 2 days ago
JSON representation
Part guillotine, part graveyard for Google's doomed apps, services, and hardware.
- Host: GitHub
- URL: https://github.com/codyogden/killedbygoogle
- Owner: codyogden
- License: mit
- Created: 2018-09-16T00:52:08.000Z (about 6 years ago)
- Default Branch: main
- Last Pushed: 2024-08-14T14:29:46.000Z (4 months ago)
- Last Synced: 2024-10-29T15:34:44.107Z (about 1 month ago)
- Topics: front-end, google, hacktoberfest, json, open-data, product, react
- Language: TypeScript
- Homepage: https://killedbygoogle.com
- Size: 5.28 MB
- Stars: 2,487
- Watchers: 36
- Forks: 386
- Open Issues: 59
-
Metadata Files:
- Readme: README.md
- Changelog: newsletter.http
- Contributing: .github/CONTRIBUTING.md
- License: LICENSE
- Code of conduct: .github/CODE_OF_CONDUCT.md
Awesome Lists containing this project
- awesome - killedbygoogle - Part guillotine, part graveyard for Google's doomed products, services, devices, and brands. (JavaScript)
- awesome-list - killedbygoogle
- awesome-starred - codyogden/killedbygoogle - Part guillotine, part graveyard for Google's doomed apps, services, and hardware. (react)
README
Killed by Google
A tribute and log of beloved products and services killed by Google.
[](/LICENSE)
## Contribute
To add a product, gather the following information:
- Name of Product (`name`)
- Launch Date (`dateOpen`)
- Discontinued Date (`dateClose`)
- Description (`description`)
- Link (`link`) - Relevant link to the source.
- Type (`type`) - one of App, Service or Hardware
If you are not familiar with or do not want to use `git`, submit a [new issue](https://github.com/codyogden/killedbygoogle/issues/new?template=add-an-obituary.md) requesting the change. If you are already familiar with `git`, follow these steps:
1. If you haven't already, start by [forking](https://help.github.com/en/articles/fork-a-repo) this repository.
1. [Create a new branch](https://help.github.com/en/desktop/contributing-to-projects/creating-a-branch-for-your-work) in your fork. Name it using the product you want to add
1. Switch to that branch (should happen automatically if you've just created it) and open the `graveyard.json` file
1. Run `yarn && yarn kill` to start the product addition CLI. This will prompt you for the information and validate your entry as you go. It will write the product information into the `graveyard.json` file for you.
1. After the CLI, run `yarn test` to ensure that the `graveyard.json` is formatted properly and all values are valid.
1. Commit your work in git and [create a Pull Request (PR)](https://help.github.com/en/articles/creating-a-pull-request) using the newly created branch.
For code contributions outside of `graveyard.json`, check out the [Contributing Guide](.github/CONTRIBUTING.md).
### Editorial Guidelines
#### Description
The description should be a single sentence describing the product. It should begin with the products name. For example, "Google Reader was an RSS/Atom feed aggregator." It will be attached to a generated sentence like "Killed about 5 years ago, Google Reader was an RSS/Atom feed aggregator."
Please be respectful, only use past tense.
#### Link
Link should be a resource that mentions the discontinuation date and talks about the product. Links to Wikipedia or a news organization should be prioritized. **Please do not use Google Support articles, linking to the product's URL, the product's marketing URL, or other Google-provided links.** Google removes these links quickly after a service is ended.
#### Type
The type should be either `app`, `service`, or `hardware` as a string.