gs4f2wcln: Fit long text-only posts to the slide and add Read more and more/less for long post text on mobile
This commit is contained in:
@@ -81,6 +81,58 @@ export const FIXTURE_FEED_ITEMS: unknown[] = [
|
||||
mediaItems: [],
|
||||
},
|
||||
},
|
||||
{
|
||||
// Medium text-only post: too long for 31px, fits at 26px or 22px with no "Read more".
|
||||
type: "post",
|
||||
publishedAt: "2026-10-19T11:30:00Z",
|
||||
likesCount: 12,
|
||||
commentsCount: 0,
|
||||
post: {
|
||||
id: "p10",
|
||||
content: "The best advice I got as a new manager: your job is not to have the answers. It is to make sure the right question gets asked in the right room, by the person closest to the customer, early enough that the answer still changes what we build. Everything else, the rituals and the dashboards and the planning decks, exists to protect that one habit. When a meeting ends without a better question than it started with, it was a status update, and those can be an email.",
|
||||
author: author("a10", "Grace Whitfield"),
|
||||
mediaItems: [],
|
||||
},
|
||||
},
|
||||
{
|
||||
// Very long text-only post: does not fit at 19px, so it clamps and ends with "Read more".
|
||||
type: "post",
|
||||
publishedAt: "2026-10-19T11:10:00Z",
|
||||
likesCount: 87,
|
||||
commentsCount: 0,
|
||||
post: {
|
||||
id: "p11",
|
||||
content: "I spent ten years building products before I learned the most useful habit of all: write down what you expect to happen before you ship, then check it a month later.\n\nMost teams skip the first half. They launch, watch a dashboard for a week and call whatever they see a win. Without the written guess there is nothing to be wrong about, so nobody learns.\n\nHere is the routine we use now. Every change gets one sentence: who it is for, what they will do differently, and the number that will move if we are right. The sentence goes in the ticket, not in a slide.\n\nThirty days later the person who wrote it reads it out loud in the weekly review and says what actually happened. No blame, no speeches. Just the guess, the result and one line on why they differ.\n\nAfter a quarter you get something no analytics tool gives you: a record of how good your team is at predicting its own customers. Ours was humbling. We were right about a third of the time.\n\nThat number changed how we plan. We now run smaller bets, we talk to five customers before any big build, and we kill features faster when the guess was wrong.\n\nIf you try one thing this month, try the sentence. It takes two minutes and it will teach you more than the next roadmap offsite.",
|
||||
author: author("a11", "Daniel Moreau"),
|
||||
mediaItems: [],
|
||||
},
|
||||
},
|
||||
{
|
||||
// Photo post with a caption longer than three lines: "more" / "less".
|
||||
type: "post",
|
||||
publishedAt: "2026-10-19T10:50:00Z",
|
||||
likesCount: 64,
|
||||
commentsCount: 0,
|
||||
post: {
|
||||
id: "p12",
|
||||
content: "Notes from the panel on hiring a first sales lead, since a few people asked. Hire for the next eighteen months, not the next five years: the person who closes your first fifty customers is rarely the one who builds a team of twenty. Ask every candidate to walk you through a deal they lost and what they changed afterwards. Give them real numbers in the interview, including the bad ones, and watch how they react. Pay them on outcomes you can measure from day one, and write down what success looks like at thirty, sixty and ninety days. Last point: the founder keeps selling until the new lead has closed at least three deals alone. Handing over too early was the most common regret in the room.",
|
||||
author: author("a12", "Aiko Tanaka"),
|
||||
mediaItems: [{ mediaType: "image", imageUrl: placeholderImage(48, "Sales panel", 1080, 1350), order: 0 }],
|
||||
},
|
||||
},
|
||||
{
|
||||
// Video post with a long caption.
|
||||
type: "post",
|
||||
publishedAt: "2026-10-19T10:30:00Z",
|
||||
likesCount: 39,
|
||||
commentsCount: 0,
|
||||
post: {
|
||||
id: "p13",
|
||||
content: "Full recording of the Thursday session on pricing experiments. Chapters: why we test price at all, how to pick the first segment, the three-week test plan, what to tell existing customers, reading the results without fooling yourself, and the questions from the audience at the end. Slides and the spreadsheet template are linked in the comments. If you only have five minutes, skip to the part on reading results: that is where most teams get it wrong, and where we lost two months last year before we noticed.",
|
||||
author: author("a13", "Rafael Duarte"),
|
||||
mediaItems: [{ mediaType: "video", thumbnailUrl: placeholderImage(230, "Pricing session"), mp4Url: FIXTURE_LANDSCAPE_URL, videoDuration: 2, order: 0 }],
|
||||
},
|
||||
},
|
||||
{
|
||||
type: "post",
|
||||
publishedAt: "2026-10-19T10:15:00Z",
|
||||
|
||||
Reference in New Issue
Block a user