Tidy up for rebranding

.github/config.yml

@@ -1,14 +0,0 @@
-# Configuration for request-info - https://github.com/behaviorbot/request-info
-
-# *Required* Comment to reply with
-requestInfoReplyComment: >
-  We would appreciate it if you could provide us with some more information about this issue/PR!
-
-# *OPTIONAL* default titles to check against for lack of descriptiveness
-# MUST BE ALL LOWERCASE
-requestInfoDefaultTitles:
-  - update readme.md
-  - updates
-
-# *OPTIONAL* Label to be added to Issues and Pull Requests with insufficient information given
-requestInfoLabelToAdd: needs-more-info

.github/lock.yml

@@ -1,35 +0,0 @@
-# Configuration for Lock Threads - https://github.com/dessant/lock-threads
-
-# Number of days of inactivity before a closed issue or pull request is locked
-daysUntilLock: 60
-
-# Skip issues and pull requests created before a given timestamp. Timestamp must
-# follow ISO 8601 (`YYYY-MM-DD`). Set to `false` to disable
-skipCreatedBefore: false
-
-# Issues and pull requests with these labels will be ignored. Set to `[]` to disable
-exemptLabels: []
-
-# Label to add before locking, such as `outdated`. Set to `false` to disable
-lockLabel: false
-
-# Comment to post before locking. Set to `false` to disable
-lockComment: false
-
-# Assign `resolved` as the reason for locking. Set to `false` to disable
-setLockReason: true
-
-# Limit to only `issues` or `pulls`
-# only: issues
-
-# Optionally, specify configuration settings just for `issues` or `pulls`
-# issues:
-#   exemptLabels:
-#     - help-wanted
-#   lockLabel: outdated
-
-# pulls:
-#   daysUntilLock: 30
-
-# Repository to extend settings from
-# _extends: repo

.github/stale.yml

@@ -1,18 +0,0 @@
-# Number of days of inactivity before an issue becomes stale
-daysUntilStale: 21
-# Number of days of inactivity before a stale issue is closed
-daysUntilClose: 7
-# Issues with these labels will never be considered stale
-exemptLabels:
-  - not-stale
-  - pinned
-  - security
-# Label to use when marking an issue as stale
-staleLabel: false
-# Comment to post when marking an issue as stale. Set to `false` to disable
-markComment: >
-  This issue has been automatically marked as stale because it has not had
-  recent activity. It will be closed if no further activity occurs. Thank you
-  for your contributions.
-# Comment to post when closing a stale issue. Set to `false` to disable
-closeComment: false

CONTRIBUTING.md

@@ -2,16 +2,6 @@
 
 **30 seconds of code** is powered by the community, so feel free to contribute in any way you can to help us!
 
-## Tools
-
-Before you begin contributing, you should install the integration-tools globally on your machine:
-
-```sh
-npm install -g @30-seconds/integration-tools
-```
-
-This will allow you to use our customized tools for all of our content repositories.
-
 ## How you can help
 
 - Submit pull requests with new snippets (see guidelines below) or snippet updates (tags, descriptions, explanations, typos, examples, code improvements).
@@ -23,30 +13,28 @@ Breaking any of these rules will result in your pull request being closed. Pleas
 
 - **Always be polite and respectful to others** and try to follow the advice of the moderators/collaborators/owners.
 - **Only modify snippet files**, never modify the generated files in the `blog_data` directory, except for the `blog_authors.json` file.
-- **Use the integration tools commands** to generate new snippets, ensuring they have the correct name and are in the correct location.
+- **Use the snippet template** to create new snippets, ensure they have the correct name and are in the correct location.
 - **Follow snippet format exactly**, otherwise your snippets will not be recognized correctly by the tools responsible for publishing them on the website. This includes such things as spacing and empty lines - if you accidentally make a mistake, consult the repository's [snippet template](snippet-template.md).
 - **Snippets should solve real-world problems**, no matter how simple and should be abstract enough to be applied to different scenarios.
 
 ## Snippet creation
 
-After installing the integration tools, you can run the following command:
+In order to create a new snippet, you should follow the steps below:
 
-```sh
+- Crate a copy of the [snippet template](snippet-template.md) in the `blog_posts` directory.
-create-new-snippet <my-snippet-name>
+- Change the name of the newly created file to the name of your snippet.
-```
+- Edit the file, adding your snippet based on the guidelines.
-
-Replace `<my-snippet-name>` with the name of the snippet you are adding. 
 
 ## Snippet guidelines
 
 - Snippets must have all their frontmatter sections (title, tags etc.) filled.
 - Snippet filenames must roughly correspond to the snippet title and be in `kebab-case`.
-- Snippet types must be one of the following: `story`, `list` or `question`.
 - Snippet titles must be short enough and correspond to the type of the snippet. Titles for each type must follow the format of previous snippets (e.g. `The trickiest thing about X` for a story, `X things that are awesome` for a list, `How do I do X in Y?` for a question).
-- Snippet types must be one of the following: `story`, `list` or `question`. 
+- Snippet types must be one of the following: `story`, `list`, `tip`, `cheatsheet` or `question`.
 - Snippet tags must be comma-separated. You are allowed to specify a single language tag (e.g. `react` or `javascript`), preferably as the first tag.
+- Snippets must have their `firstSeen` dates formatted using [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601).
 - Snippet authors must be comma-separated and should be added in JSON format as seen in `blog_data/blog_authors.json`.
-- Snippet covers must be added inside the `blog_images` directory and have the exact same name as the snippet filename. Snippet covers must be Unsplash images of appropriate theme and content and must be credited accordingly at the end of the snippet.
+- Snippet covers must be added inside the `blog_images` directory and have the exact same name as the snippet filename. Snippet covers must be Unsplash images of appropriate theme and content and their links must be provided as part of the PR, so that they can be added to the appropriate collection.
 - Snippet excerpts must be a very short description of the snippet's content, up to 180 characters in length. The excerpt must contain some of the main keywords and a general intro to the snippet, as it will be used for social sharing and previewing the snippet itself.
 - Snippets that are of the `list` type must be written as such, check previously submitted snippets for more details.
 - Snippet code and examples must be enclosed in appropriate, language-tagged blocks, be short and use modern techniques and features. Also make sure to test your code before submitting. Always use soft tabs (2 spaces), never hard tabs.

README.md

@@ -1,25 +1,25 @@
 [![Logo](/logo.png)](https://30secondsofcode.org/blog/p/1)
 
-# 30 seconds blog
+# 30 seconds of code
 
-> The official 30-seconds blog
+> Code articles for all your development needs
 
-* Visit [our website](https://30secondsofcode.org) to view our snippet collection and blog.
+* Visit [our website](https://30secondsofcode.org) to view our snippet and article collections.
-* Use the [Search page](https://30secondsofcode.org/search) to find snippets and blog posts that suit your needs. You can search by pretty much anything. Just start typing a term and see what comes up.
+* Use the [Search page](https://30secondsofcode.org/search) to find snippets and articles that suit your needs. You can search by pretty much anything. Just start typing a term and see what comes up.
-* Browse the [Blog](https://30secondsofcode.org/blog/p/1) to see all the blog posts we have published.
+* Browse the [Articles collection](https://30secondsofcode.org/articles/p/1) to see all the articles we have published.
-* Click on each blog post card to view the whole blog post.
+* Click on each article card to view the whole article.
 * If you like the project, give it a star. It means a lot to the people maintaining it.
 
 ## Want to contribute?
 
 * If you want to help us improve, take a minute to read the [Contribution Guidelines](/CONTRIBUTING.md) first.
-* Use the [Blog Post Template](/snippet-template.md) to add new blog posts to the collection.
+* Use the [Article Template](/snippet-template.md) to add new articles to the collection.
-* If you find a problem with a specific blog post, please [open an issue](https://github.com/30-seconds/30-seconds-blog/issues/new).
+* If you find a problem with a specific article, please [open an issue](https://github.com/30-seconds/30-seconds-blog/issues/new).
 * If you find a problem with the website, please [report it in the web repository](https://github.com/30-seconds/30-seconds-web/issues/new).
 
-## Credits & Sponsors
+## Credits
 
-* This repository is maintained by the [30-seconds organization on GitHub](https://github.com/30-seconds).
+* This repository is maintained by the [30 seconds of code organization on GitHub](https://github.com/30-seconds).
 * All snippets are licensed under the CC0-1.0 License, unless explicitly stated otherwise.
-* Logos, names and trademarks are not to be used without the explicit consent of the maintainers or owners of the 30 seconds GitHub organization.
+* Logos, names and trademarks are not to be used without the explicit consent of the owners of the 30 seconds of code GitHub organization.
-* Our website is powered by [Netlify](https://www.netlify.com/), [Gatsby](https://www.gatsbyjs.org/), [Travis CI](https://travis-ci.com/) & [GitHub](https://github.com/).
+* Our website is powered by [Netlify](https://www.netlify.com/), [Next.js](https://nextjs.org/) & [GitHub](https://github.com/).

snippet-template.md

@@ -6,7 +6,6 @@ authors: chalarangelo
 cover: blog_images/my-image.jpg
 excerpt: A short summary of your story up to 180 characters long.
 firstSeen: 2021-06-13T05:00:00-04:00
-lastUpdated: 2021-06-13T05:00:00-04:00
 ---
 
 Write your blog post here.