feat: rework entire repository to push notion-toolbox in new direction

- Alfred and bitbar tools are removed (for now) as things get reworked.
- Stripped the server of functionality that was for the tailored weekly
  template.
- Added a notice about the weekly template at top of the repo (pointing
  to a previous revision of the repo).
- The server tool no longer is there to support the idea of the weekly
  template. Instead, things are more flexible in terms of what you can
  do with the server (i.e., specifying CRUD actions for specified
  blocks/collections. The server now expects a Notion-Token in the
  header so it can perform operations using the provided token.
- Switched the notion-py dependency back to jamalex's version.
- The shared/notionscripts was reworked to be more simple in terms of
  what it does

Author: kevinjalbert

.gitignore

@@ -1,7 +1,3 @@
-##### CUSTOM #####
-alfred/data/config.json
-alfred/data/tags.json
-
 ##### PYTHON #####
 # Byte-compiled / optimized / DLL files
 __pycache__/

README.md

@@ -8,22 +8,23 @@
   </a>
 </p>
 
-This is a collection of [Notion](https://www.notion.so/) tools that work in tandem together. All of these tools take advantage of a [specific weekly/daily template](https://kevinjalbert.com/my-weekly-notion-setup/) that integrates with various tools and solutions present in this repository.
+> NOTE: If you are interested in the Notion tooling around the [Notion Weekly Template](https://kevinjalbert.com/my-weekly-notion-setup/) from [kevinjalbert.com](https://kevinjalbert.com/) then you should look at the historic [snapshot of the repository](https://github.com/kevinjalbert/notion-toolbox/tree/63d8bf16670b44ec355132d5f251e0728fc5cd78). This project no longer uses the tailored template, and instead is moving in a more flexible direction.
+
+This is a collection of [Notion](https://www.notion.so/) tools that work in tandem together.
 
 ## Tools
 
 The following tools are available. Each tool has a README file present in its corresponding sub-directory.
 
-- [Alfred](alfred/) workflow
-  - Enables a handful of ways to interact with the template using shortcuts
-- [BitBar](bitbar/) plugin
-  - Displays the current task in your menubar (with quick access to the Notion page)
 - [Server](server/) application
-  - Enables an online (and backgrounded) interface to interact with the template
+  - Provides a REST API to perform CRUD operations with blocks and collections
   - Useful to connect with webhooks (e.g., IFTTT)
-  - Opens integrations with Google Assistant
+  - Opens integrations with Google Assistant, iOS Shortcuts, and Android Tasker
+
 
-## History
+## History of this Repository
+<details>
+<summary>Toggle to read about this...</summary>
 
 For a good part of 2019, I focused heavily on my [Notion[Referral]](https://www.notion.so/?r=6b8d609eb50943419db4d87c67fa558e) setup. I personally feel that this was time well invested, akin to a craftsman refining his tools.
 
@@ -32,17 +33,8 @@ For a good part of 2019, I focused heavily on my [Notion[Referral]](https://www.
 - I created a server web application called [`notion-heroku`](https://github.com/kevinjalbert/notion-heroku) that interacts with [IFTTT](https://ifttt.com/) and Google Assistant ([blog post](https://kevinjalbert.com/integrating-notion-with-google-assistant/)).
 - I created a shared repository called [`notion-scripts`](https://github.com/kevinjalbert/notion-scripts) to further help the development of my tooling for Notion ([blog post](https://kevinjalbert.com/introducing-notion-scripts/)).
 
-I recently made the decision to consolidate all my Notion related projects into a single repository. The goal is to increase cohesion to allow the tools to better interact with each other. It also puts everything in one place instead of spreading it out over multiple repositories. This approach does increase the size of the repository and the deployment/usage complexity for certain tools, but overall I feel that this decision will result in an easier way to use and develop with the Notion tools found there.
-
-### The Great Merge
-
-The great merge happened on December 27, 2019. On GitHub, `notion-heroku` and `notion-scripts` were merged into `alfred-notion`. I decided for `alfred-notion` to be the main repository as it had the most _stars_ on GitHub and was the longest-tenured repository I have for Notion tools. I did rename the repository to [`notion-toolbox`](https://github.com/kevinjalbert/notion-toolbox) to better represent the mission and contents of this project. Fortunately, GitHub automatically handles the redirects from `alfred-notion` to `notion-toolbox`.
-
-I was able to retain the commit history of each project by following the approach mentioned in this article on _[How to merge two or multiple git repositories into one](https://medium.com/altcampus/how-to-merge-two-or-multiple-git-repositories-into-one-9f8a5209913f)_. This approach worked flawlessly for me, and was rather straightforward. The only thing I had to do was move each project's contents into subdirectories.
-
-As for the merged repositories, I archived them following my approach listed in _[Archive Unused Repositories](https://kevinjalbert.com/archive-unused-repositories/)_ that I blogged about last year.
-
-The only issue that I've hit right now is the _server_ (formerly `notion-heroku`) [expects certain files in the root directory to be deployable to Heroku](https://devcenter.heroku.com/articles/procfile#procfile-naming-and-location). I've temporarily restructured the repository so that it works, but it isn't ideal as the tool itself is bleeding outside of its sub-directory. A better solution will be found in the future.
+I consolidated all my Notion related projects into this repository ([`notion-toolbox`](https://github.com/kevinjalbert/notion-toolbox)), to increase the cohesion and interactions between the tools. Over time I've slowly pivoted away from the Notion template I put together, and this has led to a revamp of what I want notion-toolbox to do. The new vision is to allow for greater flexibility and to be more generic.
+</details>
 
 ## Author