-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
portico: Add script to auto-generate message screenshots /for/research. #30061
Conversation
Hello @zulip/server-misc members, this pull request was labeled with the "area: portico" label, so you may want to check it out! |
Overall, this looks great; posted a few comments but I'm generally in favor of merging this sort of thing and then doing iterative refinements on top of it. |
I updated to clean up the messages added in the
Should the data for the message conversation ( |
}, | ||
{ | ||
"sender": "Zoe Davis", | ||
"content": "@**everyone** Video call is happening now! [Click to join video call](#)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's change [Click to join video call] -> [Join video call.], since we changed the default text the button inserts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated!
Let's make the times more realistic, so that it doesn't look like all the messages were sent at the same time. I think the times in the screenshots that are currently on the website are fine, but I'm not super picky. |
"Today" is generally good for the date, and thanks for updating the global time. But let's make the storyline be that the call gets scheduled the day before, and then the "happening now" message is sent at the time that the call was scheduled for. |
@terpimost Could you please share images we should use for avatars for these conversations? |
Yeah, let's have it live in this directory; it's good to have all the source materials in one place. |
We can probably not block on finalizing the content of the |
This commit relocates all the scripts in the tools directory which are used for auto-generating screenshots to the new tools/screenshots directory to avoid cluttering the tools/ root.
This commit adds the "forged_timestamp" parameter to the "internal_prep_stream_message" method of "actions/message_send". This is a preparatory commit, that can be used for sending messages at a forged time in scripts for generating screenshots of messages.
Previously, we manually generated screenshots on /for/research and other landing pages, which makes them difficult to maintain. This PR adds a script - generate-user-messages-screenshot, which expects the path of the filename containing the thread conversation and path where screenshot needs to be generated, and generates screenshot at the mentioned location. Fixes zulip#30016
This commit utilizes the script added for auto-generating screenshots of message threads to generate screenshots for the "/for/recovery" page. This commit adds the message data for generating the screenshots.
@alya addressed reviews:
And updated screenshots accordingly. |
Addressed reviews:
changed the location of the
Removed
Updated |
Works for me! |
Merged, thanks @roanster007! |
A few follow-up requests:
|
Please skip /for/business for now; I need to do some content work there. |
I'll work over next few days. |
Previously, we manually generated screenshots on /for/research and other landing pages, which makes them difficult to maintain.
This PR adds a script - generate-user-messages-screenshot, which expects the path of the filename containing the thread conversation and path where screenshot needs to be generated, and generates screenshot at the mentioned location.
Fixes #30016
Testing:
./tools/screenshots/generate-user-messages-screenshot --thread tools/screenshots/interactive_messaging.json
Screenshots and screen captures:
Self-review checklist
(variable names, code reuse, readability, etc.).
Communicate decisions, questions, and potential concerns.
Individual commits are ready for review (see commit discipline).
Completed manual review and testing of the following: