Change title to "Secure Tunnel for Local Testing". The documentation draft for this updated behavior can be found here. https://docs.google.com/document/d/1sZzciut0QwU_ver_Xx-_VoaYQRZ1zVZ9x8X7t1ywhYY/edit?usp=sharing

Remove these browser bullet points. However, add a section underneath that includes them plus iOS and Android for UFG integrated users.

This screenshot will need to be updated with the new tunnel changes. TBD - should be available this coming week. Additionally, we should add a link to the new local-testing documentation.

Need a screenshot to show Chrome only for non-UFG integration users. Users that either do not have Eyes integration or Eyes without UFG. This same screenshot can be used to show UFG integrated users.

Need a screenshot to show Chrome only for non-UFG integration users. Users that either do not have Eyes integration or Eyes without UFG. This same screenshot can be used to show UFG integrated users.

This screenshot needs to be updated with the latest UI.

Add a note here stating the screenshots displayed are accounts that have Eyes + UFG integration enabled. Otherwise , only Chrome would be shown.

We should make a note here that the screenshots displayed are for accounts with Eyes & UFG integration enabled. Otherwise, only Chrome browsers and screen sizes would be displayed.

New screenshot is needed to show only Chrome for non-UFG users. This screenshot can be used to show users that have an Eyes + UFG integration enabled.

Lets remove this bullet point.

Can you see this, Emma?

add: "or https://help.figma.com/hc/en-us/articles/4410793238167-Restrict-or-prevent-guest-access <hyperlinked> "Restricted guest access"

Actually, I think it will fit better as the last item in the Getting Started section. Under "Design and Implementation History" and above the next section "Administration.

Bold and underline

Add a bolded NOTE above this. "Centra will only accept invites that are sent with "CAN VIEW" permissions only. Permissions sent as "CAN EDIT" will be ignored. If you mistakenly sent an invite with editor permissions, you can change the permission to "can view" and then select "Resend invite"."

I will send you a screenshot to add to this note.

Can you make this BOLD and Underlined. It needs to be more obvious as users are sending editor permissions.

Add: "project public "Anyone with the link" and ..."

Add: "is private "Only people invited to this file" ...

Perhaps a better name would be "Getting Started". WDYT?

Hi Michael - we need to add bubbles for the comments indicator. e.g. (8) can mean there are 8 open comments or opened issues. Also need to add a bubble for "has implementation" icon. The icon is bolded when an implementation exists. Can we also add a different image as the "Has implementation" toggle switch is misaligned in this screenshot.

Need to remove Jira from here.

Actually, NEW means it's a new project. It will instead display an updated label if a new image is added to the project. We also need to change the text in the bubble below to reflect this too.

Didn't we have a bullet point list of what the labels mean? e.g. Updated on a frame can mean two things. Either the design or implementation was updated. The updated label on the project will appear whenever there is an update on any frame in the project.

Also, is the text in the bubbles placeholder text? Only say that because they are kind of obvious so wasn't sure if you meant to add more to it. Maybe you can add the difference on updated inside one of the frame updated bubbles?

Finally, can you add a bubble for the filesystem icon?

Can we rename this to "Learning Center" as that is what it's referred to in the tooltip in the app.

Lets move this above "Keyboard shortcuts".

We should add more details on approving and rejecting. e.g why/when someone will want to use these buttons. Also, that the approve/reject labels are reset whenever either a new design or implementation image is added.

Hi Michael - this topic should be moved outside of "Adding a project". Perhaps the next topic after and above "Updating a Filesystem project"

Please remove this one for now. It was disabled in Centra.

Lets move this below the "Adding Implementation Images" topic.

Need another sentence or paragraph explaining the difference between comments and issues. Let me know if you want me to provide this for you. Thanks.

Can we move this under "Adding a Figma Project". Also after that put "Synchronizing Figma Projects" so these are grouped together.

add at the end. "by using @".

Actually, this is slightly different than how it works. Lets change the text to: Click on an comment and respond to team members by tagging them using @. The users tagged will receive an email notification of your comments.

Change to: After installing the Chrome extension, click the extension icon to capture a screenshot of your website to your clipboard. Additional settings can be found in the browsers context menu by right-clicking on the page and selecting Applitools Centra Screenshot Capture . The capture options are as follow:

For consistency sake, can we add a screenshot of a design without an existing implementation image? That will then make the following bullet points make sense.

We need to make this it's own section that can I can link to from the Centra design viewer. e.g. "Use our Chrome extension to capture screenshot. Learn more". The "Learn more" will link to this content.

Additionally, we need bullet points to cover these topics.

Screenshot capture options - Screenshot options are in the context menu by right-clicking on the webpage. - Available options: - [Default] Full-page screenshot (Captures the entire page). - Viewport screenshot (Captures the viewable area on the page). - [Default] Stitch with CSS (Captures screenshot using CSS transition and removes duplication of fixed position elements. i.e sticky headers/footers). - Stitch with scroll (Captures screenshot using standard Javascript scrolling).

Known limitations - Saving an image to the system clipboard only works on HTTPS or local HTTP sites. - Users need to allow the extension to copy images to clipboard per domain they use it on.

To be consistent. We should use the same content for this in this section. https://devtst.applitools.com/docs-rvw-4/bestpractices

Can we make this a note block similar to the other notes (in yellow) to be consistent?

"is added to a team (Welcome email and Verify email are sent)"

We can remove this. Centra now has unsubscribe capabilities per team. We need to add a section for this on this page with screenshots. FYI - unsubscribing or disabling email notifications only stops the grouped email notifications for sending. Those emails include the first 4 bullet points. It does not include the notifications in the last 6 bullet points. Perhaps add a note about this.

Take a look at these Trello cards. Let me know if you have questions. Thanks.

https://trello.com/c/uNH6UuNY/284-unsubscribe-link-in-grouped-email-notifications https://trello.com/c/jkDorHsu/278-disable-enable-notifications

Let remove/hide this section for now. Don't delete it so we can add it again later.

can we add a note section after this stating: "Deleted users will be removed from the team and can no longer access the team. You can re-add these users again at any time or other team members can invite them with admin approval."

Lets add a note section after this. e.g. This option will be disabled or not displayed if you do not have admin permissions for the team you are viewing.

Remove for now.

We need to show comments in issues (after creation). It will be similar to Adding a comment but users should know this exists. e.g. 3. After creating an issue, you can open the issue again and tag team members you wish to collaborate with on this issue. <add screenshot>

Need to remove this part for now.

Lets remove/hide this section (Jira) for now as for EA and perhaps early GA will not have it. I don't want to delete it so what ever can be done to hide it for now would be best.

I don't think this section should be under Getting Started. Perhaps it would be better under the "Comparisons" section after "Adding a Project"

For early access, lets switch this to "all you need is to join our waitlist." waitlist should be hyperlinked to https://applitools.com/centra/

lowercase

change to "design"

We should be more agnostic as it might not always be the designer doing this.

change to "implementation"

Switch to "A team member uploads ..."

change to PNG

change to: "is able to accept your invitation. After that is completed, you will then be able to upload your Figma page.

"can view" permission to centra@applitools.com. Can you add a copy/paste button next to this for the user to copy it to their clipboard?

file

Add a note above. e.g. Note: Figma projects in Centra can only contain entities from Figma. Meaning you cannot mix and match both Figma designs and designs uploaded from your filesystem into the same project.

change to: "and the previous revision comments and issues are removed.

Can we add a screenshot for this?

Change to: "When syncing your project, previous design images can be viewed in the ..."

I'd move this below the image as it is a separate topic to project syncs.

change to: with comments and issues

This should be a section under "Updating a project". We should have two sections, one for "Filesystem" and one for "Figma".

A non-admin team member invites a user to the team. (Admin only).

separate

change to: "A project is updated with added or replaced design or implementation images".

change to: comment

We need to add more content to this section as to the meaning or why Approving or Rejecting is for. I'd also say this should be a separate topic and not under collaborating.

I will slack you a screenshot we should add to show users what to copy from Jira to add to this textfield.

Remove the format.

Is there a bullet point or number missing?

Lets not add the formatting here and below since it could be different for different Jira accounts.

change to: "Issues can be added to implementation images only." bold and underline only.

Add after the period: "The default option is "Unresolved".

change to: "previous comments and issues by opening the REVIEW HISTORY and viewing each revision.

change to: "all previous comments and issues will be removed."

an

Change to: "Or use our Chrome extension to capture screenshots of your web application." Add hyperlink with placeholder link for "our Chrome extension"

Can we add a screenshot for both? One with implementation and one without.

Make this a hyperlink with a temporarily placeholder link for now.

upcase to PNG

We need to specify this is only applicable to "Filesystem" projects and not Figma projects.

Do we show an example and explanation of a project that is updated?

change to: "is able to accept your invitation. After that is completed, you will then be able to upload your Figma page.

change to: "can view" permission to centra@applitools.com. Can you add a copy/paste button next to this for the user to copy it to their clipboard?

A little bit of a reversal in order. Invitations sent by non-admins (Editors, Viewer-only) will first be sent to an Admin to approve. After the admin approves the request, the invited users will receive a "Welcome" email including the person who originally invited them. Also, Admins who invite users the invited user will receive a Welcome email right away without the need for approval via the "Pending requests".

We might want to temporarily remove the hyperlink. Marketing is going to gatekeep who can signup so we don't want to expose these links publicly, and the same for the registration link.

We should put this under Administration. But provide a link on this page to direct the user to there.

Please center the text inside the images below. Teammembers should be two words (last image).