Open darcyclarke opened 7 years ago
my quick thoughts:
NODE_SCHOOL_LOCATION=toronto
?I think the first step would be to identify the current grunt work that is required when creating / updating events and write some hardcoded scripts that help with that (do we already have that?). Later on that can be converted into a CLI.
This is a quick draft of a CLI tool we should create, to help us more efficiently run events.
The Goal:
References:
Features:
API
Mentors
$ nsto
acronym for the namespace/npm package$ nsto create december
--date=29
sets a specific date for the event--name='Christmas Blowout!'
sets a specific name for the event--max=100
sets the maximum attendees for the event$ nsto update ...
$ nsto notify
Attendees
$ nsto register april --email=<email@domain.com>
Implementation Details
--email
isn't passed for registration$ nsto update june --name='Summer Time, Fun Times'
modifies the event in June 2016Future Ideas
$ nsto events
would return a list of the previous and upcoming events to query further