[Proposal] Profile Interface

[ctsstc]

[WIP] Let me sleep on this, wake up, and realize the bad choices I've made.

We should aim to have a standard between profiles for anyone who would like to implement one.

Questions

• Should users enter this into a JSON file?
  • I don't think we can have type handling if we do that.
  • Should profiles be static singletons?
• Would we want a top level/primary SocialProfile?
  • Maybe require it to be a meetup profile?
    • The proposal below doesn't account for that, nor work for that example.

interface Profile {
	name: string;
	alias?: string;
	avatar: string;
	socialProfiles: SocialProfile[];
}

interface SocialProfile {
	network: SocialNetwork;
	handle: string;
}

enum SocialNetwork {
	Github,
	Twitter,
	Email,
	...
}

Additional Stories

There are additional stories that should be created if we decide to move forward with this. Please reference this issue if you create them.

• Profile link generator - should be able to take a SocialProfile and create a link from it -- assuming that they're composed of a standard base URL and the handle.

[paularmstrong]

Alternative from slack discussion: we could pull profiles from the Meetup API and rotate them based on recent attendees.