Skip to content

Commit d2cb8e3

Browse files
authored
Rewrite guides for login, connecting projects, sync, & enabling checking (#52)
1 parent b56f3e4 commit d2cb8e3

File tree

12 files changed

+29
-80
lines changed

12 files changed

+29
-80
lines changed

docs/1201536679.png

-122 KB
Binary file not shown.

docs/1421415415.png

-10.5 KB
Binary file not shown.

docs/1628956354.png

-46.8 KB
Binary file not shown.

docs/210173750.png

-31.9 KB
Binary file not shown.

docs/2112594915.png

-121 KB
Binary file not shown.

docs/268421786.png

-35 KB
Binary file not shown.

docs/440460267.png

-56.9 KB
Binary file not shown.

docs/672841105.png

-132 KB
Binary file not shown.

docs/Community-Checking/enable-community-checking.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,10 @@ sidebar_position: 0
44
slug: /enable-community-checking
55
---
66

7-
To use Scripture Forge community checking, you need to first log in to Scripture Forge using your Paratext credentials and connect your project. Once your project is connected, navigate to Settings and scroll down to the Community Checking section. Make sure the "Enable Community Checking" checkbox is ticked as shown in the screenshot below.
7+
To set up community checking in Scripture Forge, [log in with Paratext](log-in). You must be an admin of the project to set up community checking.
8+
9+
If the project hasn't been connected to Scripture Forge yet, [connect the project](connect-paratext-project) and keep the **Enable Community Checking** checkbox ticked.
10+
11+
If the project has already been connected, you can enable community checking on the **Settings** page. In the **Community checking** section of the settings page, tick the **Enable Community Checking** checkbox as shown in the screenshot below.
812

913
![](./settings_community_checking.png)

docs/connect-paratext-project.md

Lines changed: 4 additions & 65 deletions
Original file line numberDiff line numberDiff line change
@@ -4,73 +4,12 @@ sidebar_position: 1
44
slug: /connect-paratext-project
55
---
66

7-
import ReactPlayer from "react-player";
7+
Before you can access a Paratext project in Scripture Forge, it needs to be connected to Scripture Forge. Connecting a project creates a copy of the Paratext project in Scripture Forge that can be [synced with Paratext](syncing-with-paratext).
88

9-
## Introduction {#6222bdf3db3a44b4bf01a9cc6ffdaa80}
9+
<!-- The following paragraph is an EXACT copy of one of the paragraphs on the /syncing-with-paratext page and should be kept in sync with it. Both pages have the need to explain the relationship between Paratext and Scripture Forge projects, and having them identical means translators only have to translate it once. -->
1010

11-
:::tip
12-
13-
Paratext projects only need to be connected once within Scripture Forge.
14-
15-
:::
16-
17-
After a Paratext project is connected to Scripture Forge, every user that is a member of the project in Paratext (under User Permissions) will be able to open the project in Scripture Forge.
18-
19-
20-
To be able to open a project in Scripture Forge, a user just needs to [log in to Scripture Forge with their Paratext account information](/log-in).
21-
22-
<div class="player-wrapper"><ReactPlayer controls url="https://youtu.be/exEJxc19Zm4" /></div>
23-
24-
25-
## How to Connect a Paratext Project to Scripture Forge {#a71dfc268ebb43a0b19c0ab7018f92b4}
26-
27-
1. If you have **never connected** a project to Scripture Forge:
28-
1. Click the Connect project button:
29-
30-
![](./268421786.png)
31-
32-
2. If you have already connected a project to Scripture Forge, follow these instructions to connect any additional projects:
33-
34-
To view the list of projects you have access to in Paratext, click on the Scripture Forge icon on the top left of the screen.
35-
36-
![](./2112594915.png)
37-
38-
39-
Alternatively, you can also click on your profile icon on the top right of the screen and from the drop-down menu click “My Projects.”
40-
41-
42-
![](./1201536679.png)
43-
44-
45-
From the displayed list, you shall be able to Open projects if they are already connected. You can also join a project or click on “Connect” to connect a project for the first time in Scripture Forge.
11+
In Paratext, each member of the project has a copy of the project on their own computer, and Send/Receive is used to share changes with other members. When a project is connected to Scripture Forge, all members of the project in Scripture Forge work on a single copy of the project, so any change made by one member is immediately seen by another member, if both members are online. These changes will be sent to the Paratext project when a sync is done in Scripture Forge, and any changes made in Paratext will be synced to the Scripture Forge project.
4612

13+
To connect a Paratext project in Scripture Forge, [log in with Paratext](log-in). When you log in, the **My projects** page will load. If you are on a different page in Scripture Forge you can get to the **My projects** page by clicking the Scripture Forge logo in the top-left corner of the page. The **My projects** page lists all projects you are a member of in Paratext, including those that are connected to Scripture Forge, and those that are not yet connected. If a project has already been connected and you are a member of the Paratext project, you can join the Scripture Forge project by clicking **Join**. If the project hasn't been connected yet, and you are an admin of the project, click **Connect**. Only admins can connect a project on this page.
4714

4815
![](./my_projects.png)
49-
50-
51-
After clicking on “Connect” you will be asked to select your Project Source. From the available drop-down list, select the source you wish to use for your project.
52-
53-
54-
![](./1628956354.png)
55-
56-
Optional: Enable translation suggestions (#1 below)
57-
58-
![](./440460267.png)
59-
60-
Optional: Enable Community Checking (#2 above)
61-
62-
When you are ready, click Connect:
63-
64-
![](./210173750.png)
65-
66-
Wait for Scripture Forge to connect the Paratext project:
67-
68-
![](./1421415415.png)
69-
70-
Scripture Forge may take a while to connect your project. The green progress bar will stop moving when your project is fully connected:
71-
72-
![](./672841105.png)
73-
74-
75-
Note: You may be able to work in Scripture Forge before it is fully connected.
76-

0 commit comments

Comments
 (0)