You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fill out event details (Usually comes from the #communications slack channel)
TITLE:
EF & CH: "Weekly Prayer Meeting" (Beginning Sunday, September 1, various times based on campus location)
COPY:
EF: "Join us for a time of weekly prayer beginning Sunday, September 1 from 8:45AM-9:15AM before our first 9:30AM worship service, on the 3rd floor of our East Falls campus (4200 Ridge Ave, Philadelphia). This will be an opportunity to come together as a church to pray for the renewal of our congregation and our city. Everyone is welcome! Contact [email protected] with any questions."
CH: Join us for a time of weekly prayer beginning Sunday, September 1 from 3:15PM-3:45PM before our 4:00PM worship service, in Room 110 at our Cherry Hill campus (5 Carnegie Plaza, Cherry Hill). This will be an opportunity to come together as a church to pray for the renewal of our congregation and South Jersey. Everyone is welcome! Contact [email protected] with any questions."
DUE DATE:
on website by 8/10, no registration link
ADDITIONAL CONTEXT:
Issue Creator Checklist
Fill out the relevant Title, Copy, Due Date, and Detail needs from
#communications channel into the description.
Ensure that the graphic from #communications or #graphics is attached.
On the GitHub Issues sidebar, set the "Project" to "Metro Support
Rotations"
Ping the assigned team member in the thread in the #digitech-github Slack
channel!
Assignee Checklist
Update event document in Sanity and deploy
After deploy is published, verify that event card is visible on homepage
tiles and /events (as applicable)
The text was updated successfully, but these errors were encountered:
Saw that this was missed, so I figured I'd pick it up. I made 2 separate event cards for now, but considering consolidating once I get the okay. Otherwise deployed and ready for review.
Fill out event details (Usually comes from the #communications slack channel)
TITLE:
EF & CH: "Weekly Prayer Meeting" (Beginning Sunday, September 1, various times based on campus location)
COPY:
EF: "Join us for a time of weekly prayer beginning Sunday, September 1 from 8:45AM-9:15AM before our first 9:30AM worship service, on the 3rd floor of our East Falls campus (4200 Ridge Ave, Philadelphia). This will be an opportunity to come together as a church to pray for the renewal of our congregation and our city. Everyone is welcome! Contact [email protected] with any questions."
CH: Join us for a time of weekly prayer beginning Sunday, September 1 from 3:15PM-3:45PM before our 4:00PM worship service, in Room 110 at our Cherry Hill campus (5 Carnegie Plaza, Cherry Hill). This will be an opportunity to come together as a church to pray for the renewal of our congregation and South Jersey. Everyone is welcome! Contact [email protected] with any questions."
DUE DATE:
on website by 8/10, no registration link
ADDITIONAL CONTEXT:
Issue Creator Checklist
Fill out the relevant Title, Copy, Due Date, and Detail needs from
#communications channel into the description.
Ensure that the graphic from #communications or #graphics is attached.
On the GitHub Issues sidebar, set the "Project" to "Metro Support
Rotations"
Ping the assigned team member in the thread in the #digitech-github Slack
channel!
Assignee Checklist
Update
event
document in Sanity and deployAfter deploy is published, verify that event card is visible on homepage
tiles and
/events
(as applicable)The text was updated successfully, but these errors were encountered: