https://github.com/doubleedesign/life-screen
Using the Microsoft Graph API, Node/Express, and React to bring my calendars together with other relevant information.
https://github.com/doubleedesign/life-screen
azure expressjs microsoft microsoft-graph-api nodejs reactjs typescript
Last synced: 8 months ago
JSON representation
Using the Microsoft Graph API, Node/Express, and React to bring my calendars together with other relevant information.
- Host: GitHub
- URL: https://github.com/doubleedesign/life-screen
- Owner: doubleedesign
- Created: 2022-11-11T23:34:04.000Z (over 3 years ago)
- Default Branch: master
- Last Pushed: 2024-12-28T04:57:42.000Z (about 1 year ago)
- Last Synced: 2025-06-06T12:05:14.266Z (10 months ago)
- Topics: azure, expressjs, microsoft, microsoft-graph-api, nodejs, reactjs, typescript
- Language: TypeScript
- Homepage:
- Size: 3.46 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Life Screen
Using the Microsoft Graph API, Node/Express, and a to-be-decided front-end stack to bring my calendars together (and other things eventually, e.g., weather forecast).
Some of the code is specific to my calendars, e.g., exclusions, renaming, categorisation, front-end styling; but this could all easily be adjusted for use by other individuals. So please feel free to fork the repo and have a go (insert standard disclaimer about no warranty etc etc).
---
## Server
1. Install dependencies:
```bash
npm install
```
2. [Set up or update integrations and their credentials](./docs/setup-integrations.md)
3. Run the server locally in dev mode:
```bash
cd server
```
```bash
npm run dev
```
4. [Test endpoints](./docs/testing-integrations.md) using Postman or similar.
---
## Front-end
To come.
---
## Previous iterations
### Version 1
This version was built when I was juggling a part-time primary job with a teaching job and studying, all of which were a mix of online and in-person. I note it here to showcase the original concept and usage.
The code for this is archived in the `archive/version-1` branch.
### Version 2
Version 2, which I started after starting my job at Atlassian, never really took off due to: general time constraints; UI redesign requirements (e.g., some teaching and study-related features not needed anymore or to be temporarily shelved) and plans; and the limitations on sharing my work calendar reducing the immediate usability.