Projects

A project is one body of work, such as a marketing site, a checkout rebuild or a client’s app. Every thread belongs to exactly one project, and its replies stay with it. Separate projects keep feedback on different work in separate lists.

Owners, admins and collaborators can create projects. Reviewers can’t. The Free plan allows 3 projects across the whole organization. Paid plans have no limit.

Which project a thread goes to

Skyelight picks the project from where the pin was left:

• In the Chrome extension, the thread goes to the project selected in the side panel header. You can pick a project there or create one. A new tab starts on the last project you used in that workspace.
• Through the review badge, the thread goes to the project that owns the site’s address. Each preview address belongs to one project, so a reviewer pinning on acme-git-main.vercel.app doesn’t have to choose. See Preview URLs.

How threads are grouped by page

Inside a project, Skyelight groups threads by page. You don’t create pages. Skyelight works them out from each thread’s address, by site and path:

• Path segments that look like ids are treated as one page, so /orders/123 and /orders/456 appear together.
• A leading www. is ignored, so www.acme.com/pricing and acme.com/pricing are the same page.
• Each Google Doc, Sheet or Slides file counts as its own site.

The project view lists threads from every page, and you can filter it to one page.

What a project connects to

Each project has its own connections. You can link the repository its code lives in, send its threads to a Linear project, post them to a Slack channel, and list the preview addresses where reviewers can pin with the review badge.