Open ethanresnick opened 9 years ago
yelly is owning the calendar - the jank prototype i had made is here: https://github.com/grungerabbit/tech-nyu-site/tree/calendar/simple-cal/app
she has a much more refined version in progress. we can consider splitting calendar UI module off into its own repo? thoughts @oa495 ? I think when it's done, we should have Calendar as an include as part of https://github.com/TechAtNYU/universal-header - i can make an example to show you what i mean
I was thinking if the end goal can be a calendar that can just take like an API events response and build a calendar from it :) So we can use the same calendar on the nyusw.com site to be a calendar for our Startup week. We'd just give it the API response to be like /events/<startup-week-filter>
.
What do you think @grungerabbit? Is this too much for an MVP? We can build one and then abstract it later if @oa495 doesn't want to worry about the abstraction layer yet.
yeah of course - this is what i meant
https://jsfiddle.net/grungerabbit/p768vxt1/1/embedded/result/
click on that [cal] button in the right to see
Perfect @grungerabbit. I was reading this part:
"They were lost without the elfish church that composed their flat. If this was somewhat unclear, the literature would have us believe that an utmost lip is not but an alcohol."
Got really confused really fast. Yeah great idea! A really good solution :) Also very easy to update and manage on all of our sites.
How do you think this will look on our current main Tech@NYU site, though? Like if there's a universal header with the current design. There's two areas on the main site are the first part (that expands out), and the second part (which already has a header).
two areas on the main site
that's a really good question and i want to tackle the techatnyu.org integration after we
Gotcha! Awesome :) :100:
cc @grungerabbit