Proposal: Turn components in examples into reusable components about dayzed

[mkartchner994]

I like the idea, but I am wondering if this would be better served as the goal of a different project that uses the Dayzed component under the hood. I am concerned that if we add the different Datepicker components, the Dayzed component's upgrade path would become tightly coupled with the other Datepickers making it more difficult to add new ideas to Dayzed when they come up.

I think Dayzed could be useful for more than just Datepickers. For example, It could also be used to create a custom google calendar like layout which doesn't deal with selecting specific dates, but showing events on those days instead.

Thoughts?

[donysukardi]

You bring up a really good point. We could definitely maintain the components as a separate project.

Do you mind if I create a new library out of #25 then?
Any suggestion for the package name? dayzed-pickers?

[mkartchner994]

Yes, if you would like to create the new lib that would be great! dayzed-pickers sounds good to me 👍