Skip to content

TheRealDeLorian/TempleGo

BranchesTags

Repository files navigation

Final Project Proposal

  1. Elevator pitch: Temple attendance tracker. It's like a journal for members of the Church of Jesus Christ of Latter-day Saints to keep track of the temples they've attended.
  2. Dorian Cottle is the only contributor
  3. Features (rough list):
    • Track which temples you've been to and when
    • Upload selfies and keep journal entries of your visits
    • Set goals for temple attendance and receive reminders
  4. Things I'll need to learn:
    • How to allow users to "download" the site like MySnow does
    • Browser notifications for web apps like this
    • How to ask for the user's location in React

Goals by Week

Nov 6

Projected

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them

Rubric status on this date

Points Section Requirement
2/20 General Professional, organized and smooth experience
2/30 Scope is 2-3 times larger than directory
0/5 Experience All experiences mobile-friendly
0/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
0/5 Technology Client-side state stores (e.g., TanStack Query or Context)
0/5 Technology Toasts / global notifications or alerts
0/5 Technology Error handling (both on API requests and render errors)
3/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
0/5 Technology 10+ pages or views
3/5 Technology CI/CD pipeline
3/5 Technology Tests run in pipeline, pipeline aborts if they fail
3/5 Technology Linting in pipeline
0/9 Technology 3+ generic form input components
0/12 Technology 4+ generic layout components
2/10 Technology Authentication and user account support
0/5 Technology Authorized pages and public pages
23/146 Total

Actual

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them

Rubric status on this date

Points Section Requirement
2/20 General Professional, organized and smooth experience
2/30 Scope is 2-3 times larger than directory
0/5 Experience All experiences mobile-friendly
0/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
0/5 Technology Client-side state stores (e.g., TanStack Query or Context)
0/5 Technology Toasts / global notifications or alerts
0/5 Technology Error handling (both on API requests and render errors)
3/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
0/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
5/5 Technology Tests run in pipeline, pipeline aborts if they fail
3/5 Technology Linting in pipeline
0/9 Technology 3+ generic form input components
0/12 Technology 4+ generic layout components
2/10 Technology Authentication and user account support
0/5 Technology Authorized pages and public pages
23/146 Total

Nov 9

Projected

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them

Rubric status on this date

Points Section Requirement
5/20 General Professional, organized and smooth experience
7/30 Scope is 2-3 times larger than directory
0/5 Experience All experiences mobile-friendly
0/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
0/5 Technology Client-side state stores (e.g., TanStack Query or Context)
0/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
5/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
2/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
5/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
3/9 Technology 3+ generic form input components
3/12 Technology 4+ generic layout components
10/10 Technology Authentication and user account support
5/5 Technology Authorized pages and public pages
65/146 Total

Actual

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them

Rubric status on this date

Points Section Requirement
2/20 General Professional, organized and smooth experience
2/30 Scope is 2-3 times larger than directory
0/5 Experience All experiences mobile-friendly
0/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
0/5 Technology Client-side state stores (e.g., TanStack Query or Context)
0/5 Technology Toasts / global notifications or alerts
0/5 Technology Error handling (both on API requests and render errors)
0/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
1/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
0/5 Technology Tests run in pipeline, pipeline aborts if they fail
0/5 Technology Linting in pipeline
0/9 Technology 3+ generic form input components
0/12 Technology 4+ generic layout components
6/10 Technology Authentication and user account support
0/5 Technology Authorized pages and public pages
21/146 Total

Nov 13

Expected

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them
  • neat, professional styling

Rubric status on this date

Points Section Requirement
12/20 General Professional, organized and smooth experience
11/30 Scope is 2-3 times larger than directory
0/5 Experience All experiences mobile-friendly
0/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
0/5 Technology Client-side state stores (e.g., TanStack Query or Context)
0/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
5/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
4/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
5/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
6/9 Technology 3+ generic form input components
6/12 Technology 4+ generic layout components
10/10 Technology Authentication and user account support
5/5 Technology Authorized pages and public pages
84/146 Total

Actual

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them
Points Section Requirement
2/20 General Professional, organized and smooth experience
2/30 Scope is 2-3 times larger than directory
0/5 Experience All experiences mobile-friendly
0/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
0/5 Technology Client-side state stores (e.g., TanStack Query or Context)
0/5 Technology Toasts / global notifications or alerts
0/5 Technology Error handling (both on API requests and render errors)
2/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
1/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
0/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
0/9 Technology 3+ generic form input components
0/12 Technology 4+ generic layout components
6/10 Technology Authentication and user account support
0/5 Technology Authorized pages and public pages
21/146 Total

Nov 16

Expected

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them
  • neat, professional styling

Rubric status on this date

Points Section Requirement
12/20 General Professional, organized and smooth experience
11/30 Scope is 2-3 times larger than directory
3/5 Experience All experiences mobile-friendly
2/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
0/5 Technology Client-side state stores (e.g., TanStack Query or Context)
3/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
5/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
4/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
5/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
9/9 Technology 3+ generic form input components
9/12 Technology 4+ generic layout components
10/10 Technology Authentication and user account support
5/5 Technology Authorized pages and public pages
98/146 Total

Actual

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them

Rubric status on this date

Points Section Requirement
3/20 General Professional, organized and smooth experience
2/30 Scope is 2-3 times larger than directory
0/5 Experience All experiences mobile-friendly
0/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
5/5 Technology Client-side state stores (e.g., TanStack Query or Context)
3/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
2/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
1/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
0/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
0/9 Technology 3+ generic form input components
0/12 Technology 4+ generic layout components
6/10 Technology Authentication and user account support
0/5 Technology Authorized pages and public pages
42/146 Total

Nov 20

Expected

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them
  • neat, professional styling

Rubric status on this date

Points Section Requirement
17/20 General Professional, organized and smooth experience
11/30 Scope is 2-3 times larger than directory
3/5 Experience All experiences mobile-friendly
2/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
0/5 Technology Client-side state stores (e.g., TanStack Query or Context)
5/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
5/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
4/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
5/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
9/9 Technology 3+ generic form input components
12/12 Technology 4+ generic layout components
10/10 Technology Authentication and user account support
5/5 Technology Authorized pages and public pages
108/146 Total

Actual

Feature checklist

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them

Rubric Status:

Points Section Requirement
5/20 General Professional, organized and smooth experience
3/30 Scope is 2-3 times larger than directory
1/5 Experience All experiences mobile-friendly
0/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
5/5 Technology Client-side state stores (e.g., TanStack Query or Context)
3/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
2/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
1/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
0/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
0/9 Technology 3+ generic form input components
0/12 Technology 4+ generic layout components
6/10 Technology Authentication and user account support
0/5 Technology Authorized pages and public pages
45/146 Total

Nov 23

Expected

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them
  • neat, professional styling
  • functional map that gets your location to know which temple you're visiting and sends a notification (like BeReal)

Rubric status on this date

Points Section Requirement
17/20 General Professional, organized and smooth experience
15/30 Scope is 2-3 times larger than directory
4/5 Experience All experiences mobile-friendly
4/5 Experience 3 instances where elements reorder on smaller screens
3/5 Technology Use local storage
2/5 Technology Client-side state stores (e.g., TanStack Query or Context)
5/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
5/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
4/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
5/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
9/9 Technology 3+ generic form input components
12/12 Technology 4+ generic layout components
10/10 Technology Authentication and user account support
5/5 Technology Authorized pages and public pages
120/146 Total

Actual

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them
Points Section Requirement
6/20 General Professional, organized and smooth experience
3/30 Scope is 2-3 times larger than directory
2/5 Experience All experiences mobile-friendly
2/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
5/5 Technology Client-side state stores (e.g., TanStack Query or Context)
3/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
2/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
1/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
0/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
0/9 Technology 3+ generic form input components
0/12 Technology 4+ generic layout components
6/10 Technology Authentication and user account support
0/5 Technology Authorized pages and public pages
45/146 Total

Nov 26

Expected

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them
  • neat, professional styling
  • functional map that gets your location to know which temple you're visiting and sends a notification (like BeReal)

Rubric status on this date

Points Section Requirement
20/20 General Professional, organized and smooth experience
18/30 Scope is 2-3 times larger than directory
5/5 Experience All experiences mobile-friendly
5/5 Experience 3 instances where elements reorder on smaller screens
4/5 Technology Use local storage
3/5 Technology Client-side state stores (e.g., TanStack Query or Context)
5/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
5/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
4/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
5/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
9/9 Technology 3+ generic form input components
12/12 Technology 4+ generic layout components
10/10 Technology Authentication and user account support
5/5 Technology Authorized pages and public pages
130/146 Total

Actual

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them
Points Section Requirement
6/20 General Professional, organized and smooth experience
3/30 Scope is 2-3 times larger than directory
2/5 Experience All experiences mobile-friendly
2/5 Experience 3 instances where elements reorder on smaller screens
0/5 Technology Use local storage
5/5 Technology Client-side state stores (e.g., TanStack Query or Context)
3/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
2/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
3/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
0/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
0/9 Technology 3+ generic form input components
0/12 Technology 4+ generic layout components
6/10 Technology Authentication and user account support
0/5 Technology Authorized pages and public pages
52/146 Total

Dec 4

Expected

Feature checklist on this date

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them
  • neat, professional styling
  • functional map that gets your location to know which temple you're visiting and sends a notification (like BeReal)

Rubric status on this date

Points Section Requirement
20/20 General Professional, organized and smooth experience
30/30 Scope is 2-3 times larger than directory
5/5 Experience All experiences mobile-friendly
5/5 Experience 3 instances where elements reorder on smaller screens
5/5 Technology Use local storage
5/5 Technology Client-side state stores (e.g., TanStack Query or Context)
5/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
5/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
5/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
5/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
9/9 Technology 3+ generic form input components
12/12 Technology 4+ generic layout components
10/10 Technology Authentication and user account support
5/5 Technology Authorized pages and public pages
146/146 Total

Actual

  • Users can create an account
  • Users can log in
  • Site is accessible from a duckdns subdomain
  • Users are brought to an error page if something goes wrong
  • Data is retrieved from the database when you visit the site
  • Data is displayed on the site after retrieval
  • Home page displays all temples
  • Logged in users can select temples they've been to and it saves progress to their account
  • Users can log a temple visit including uploading photos and write a journal entry about the experience and that data is there when they come back.
  • Settings page with location toggling, notifications toggling, Set your default temple
  • "temple encyclopedia" Page with a list of temples and facts about them
Points Section Requirement
6/20 General Professional, organized and smooth experience
5/30 Scope is 2-3 times larger than directory
2/5 Experience All experiences mobile-friendly
2/5 Experience 3 instances where elements reorder on smaller screens
5/5 Technology Use local storage
5/5 Technology Client-side state stores (e.g., TanStack Query or Context)
3/5 Technology Toasts / global notifications or alerts
5/5 Technology Error handling (both on API requests and render errors)
2/5 Technology Network calls that read and write data
5/5 Technology Developer type helping (TypeScript)
3/5 Technology 10+ pages or views
5/5 Technology CI/CD pipeline
0/5 Technology Tests run in pipeline, pipeline aborts if they fail
5/5 Technology Linting in pipeline
0/9 Technology 3+ generic form input components
0/12 Technology 4+ generic layout components
10/10 Technology Authentication and user account support
0/5 Technology Authorized pages and public pages
63/146 Total

Priorities:

  • Tests (run them in pipeline and abort on fail)
  • authorized pages
  • form input components
  • generic layout components
  • CRUD (remember to include error handling on all api requests)
  • more local storage

About

No description, website, or topics provided.

Resources

Readme
Activity

Stars

1 star

Watchers

1 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

 
 
 

Contributors

Languages