“We’ve built this new tool.”
+“We understand the pain points you have with the existing workflow. To address X and Y, our proposed solutions are A and B.”
+“These restrictions have been in place since X, with the intention of preventing Y, and our data has shown that Z, so we’re making the decision to temporarily lower the restrictions.”
+“We’ve lowered these restrictions, and are excited to see a much larger proportion of the community using X!”
+“X has a new face, and we hope to see engagement from newcomers increase in the coming months.”
+“We’re excited to get your feedback on this new and improved version of X, which we hope addresses many of the longstanding concerns raised in prior posts over the years [potentially link to relevant posts that indicate community discontentment with a feature, etc.].”
+The public Style guide covers brand-wide grammar and mechanics. The guidance below is specific to Meta posts.
+“Comment spoilers have been updated.”
+“We updated comment spoilers to fix keyboard accessibility.”
+“We are moving toward improving user experience.”
+“This update adds spoiler support in comments.”
+“We are working on custom badges, which will allow you to have that extra special flair on your profile.”
+“Team X is starting work on a custom badges feature that will allow communities to award users for achievements that are underrepresented or exceptional across the network. You can work with your communities to define what custom badges make sense for each of them.”
+“We’re updating the version of the third-party markdown renderer we use in question & answer pages.”
+“We’re updating the version of the third-party markdown renderer (the software that converts Markdown to HTML) we use in question & answer pages.”
+“This week we’ll be finalizing work on a new-and-improved version of the tag synonyms page, which is planned for release next week.”
+“Starting next week, an alpha version of the tag synonyms page we’ve been working on will be made available for testing for users who’ve signed up for it. The current plan is to follow up with a beta version on DATE, which will be made available to all logged-in users.”
+“Starting next week, the new version of the tag synonyms page we’ve been working on will be made available to 10% of users. The page will be made available to the rest of the user base in 10% daily increments over the following weeks, assuming we don’t see a significant number of reports about the pages’ usage.”
+“Starting next week, we’ll be rolling out an experiment on the tag synonyms page. For two weeks we’ll monitor performance against the control group (which will be using the current version of the page). We’ll evaluate whether to graduate the feature depending on what we see in the data.”
+“Given the importance of Y, by DATE we are planning to roll out an addendum to our Terms of Usage that will accommodate scenario X.”
+“We’re working on an addendum to our Terms of Usage that will accommodate scenario X. This is an important addition because of Y. As per our current timeline, we plan to have the change deployed by DATE.”
+See Alt-text for how to write good alt-text, when to leave it blank, and how to add it.
+The public Style guide covers date and time formatting for product UI and copy, where times follow the user’s local time zone. The guidance below is specific to Meta posts and intentionally differs.
+The Internal communications abbreviation guidance in the public Style guide also applies when writing on Meta sites. Although Meta is a public channel, the same rule holds: abbreviations may be used for brevity only once the full name has been established in context (with the abbreviation in parentheses), and defaulting to full names is still preferred.
+For product and brand naming (Stack Overflow, Stack Internal, Stack Ads, etc.), see the public Naming guidelines. This page covers terms specific to community and Meta contexts. Source: Meta Stack Exchange.
+“We’re improving review queues, and expect to maximize workflow efficiency for users. We’ll keep an eye on impact for some time, in order to minimize disruption.”
+“To pay down some tech debt, we’re making improvements to the back-end architecture for review queues. This may affect user workflows in unpredictable ways, so we’ll be monitoring Meta for related reports in the coming 2 months.”
+“In order to bring the future into the platform by integrating AI solutions, we’re moving some cheese around. We expect you’ll see a variety of funky behavior, but we can always blame solar flares for that!”
+“We’re improving our search functionality by integrating AI components into it. We expect this may negatively affect some search results in the short term, but honestly any change to the current search functionality is likely a step up.”
+“We’ve realized how inefficient the question reopening system is after some internal analysis. Our findings show X, Y, and Z. We plan to address those problems by doing A, B, and C.”
+“You’ve told us several times about how inefficient the question reopening system is. We’ve finally devoted some time to fixing it, taking your past input as a key part of our problem definition phase.”
+“Oops! Work on feature Y was delayed due to unforeseen circumstances. We plan to deliver it as soon as possible, though, so you shouldn’t experience too much of a disruption.”
+“Our timeline for delivering feature Y has been delayed for roughly a month, in part due to incident X two weeks ago. We know this causes some inconvenience for a lot of our users, and are making this our top priority in the coming month. Our new deadline to deliver feature Y is DATE.”
+“We believe our Privacy Policy needs to change to reflect the new reality we’re facing as a company, in which partnerships like the one with Y become common.”
+“The Privacy Policy will be edited on DATE. This change will take place in order to accommodate some technical aspects of our partnership with Y, explained further down in this post.”
+“Thank you for your report. We’ve fixed the bug now.”
+“When we integrated with Z for better spam prevention last month, we failed to account for edge case X. I’ve now gone over the relevant code and done Y, to ensure edge cases like X won’t happen again. If you see the issue persist, please respond to this post.”
+{category.description}
{/each} diff --git a/packages/stacks-docs/src/routes/[category]/+page.svelte b/packages/stacks-docs/src/routes/[category]/+page.svelte index 46e81fcc61..0dce7b97e4 100644 --- a/packages/stacks-docs/src/routes/[category]/+page.svelte +++ b/packages/stacks-docs/src/routes/[category]/+page.svelte @@ -20,12 +20,12 @@ {#if subsection.externalUrl} -