Skip to content

spike: Explore the use-cases for previews #234

Closed

Description

@ahuseyn

We need to document the common use-cases for the previews, so we can understand the potential user flows and see how the plugin behaves in those cases. The other benefits of use-cases:

  • Detect the bugs in early stage
  • Create documentation/tutorials for specific cases
  • Have better E2E tests

NOTE: The GitHub issues of Faustjs, related to previews are a good resource to see the current bottlenecks and potential use-cases.

Activity

  1. self-assigned this
    on May 28, 2025
  2. moved this from 🆕 Backlog to 🏗 In progress in Headless OSSon May 28, 2025
  3. ahuseyn commented on May 29, 2025

    @ahuseyn
    ContributorAuthor

    Based on FE environment

    Based on API

    Content types and statuses

    Other cases

    Showing fresh content

    Previews should show fresh content each time - ie: wpengine/faustjs#1933, wpengine/faustjs#1436

    Here's how this flow works:

    1. Create a new page and publish it
    2. Make some change but don't save and then hit the Preview button.
    3. Make another change and click preview again. Do you see the latest changes?

    These are the ones I've found. @colinmurphy if you have more in your mind, please add them as well 🙂

  4. moved this from 🏗 In progress to 👀 In review in Headless OSSon May 29, 2025
  5. moved this from 👀 In review to ✅ Closed in Headless OSSon Jun 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

[Area] PreviewsIssues for the HWP Previews plugin

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions