Hello! Thanks for reaching out.
I’d love some help on some high level building blocks that are used throughout the site that represent the following clusters of data:
-
An event
-
An identity
-
A grouping of activity
-
A stream of activity
At the core of Smoke Signal is an event and events have several required fields, but many optional fields. Every event has an AT-URI (which is the ATProtocol location that the event record can be found) and a name. Additionally, there is description text that is the general “body” of an event. Other optional fields include the start date/time, end date/time, the status (planned, scheduled, cancelled, etc.), the mode (in-person, virtual, or hybrid), locations, and links.
In this context, identities have 3 roles. They create events (event organizers), they RSVP to events (event attendees), and they provide feeds of events (event curators).
Event activity, either grouped or streams, represents lists of event and RSVP activity. There are a few things that are relevant here:
- Events are created and updated (“Nick created the event ‘Bowling’”)
- RSVPs are created and updated (“Boris is going to Nick’s event ‘Bowling’”)
For the most part, activity is time relevant, but some activity that occurs within a small period of time can be grouped (“Ted and Boris are going to Nick’s event ‘Bowling’”).
There are a bunch of interesting “quirks” that influence what data shows up where. For example, the “start time” of an event isn’t required, displaying a list of events by when they start won’t be inclusive.
What I’d really love is design input on how and where these elements can be used as they are repeated throughout the site. Beyond that, having a general style guide and color scheme would be great.
Currently I’m just using the bulma CSS toolkit and basic components with very minimal styling on top of what is provided.