Skip to content

Commit 811bdd4

Browse files
committed
Resolve #259 - Add extensions to getting started guide
1 parent 54363fb commit 811bdd4

1 file changed

Lines changed: 15 additions & 1 deletion

File tree

CSF.Screenplay.Docs/docs/index.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
# Get started with Screenplay
22

3-
To get started with Screenplay, the first step is to decide how you'd like to use it:
3+
## 1. Install Screenplay
4+
5+
The first step is to decide how you'd like to use it:
46

57
* [As a testing tool, with NUnit 3]
68
* [As a testing tool, with Reqnroll]
@@ -11,3 +13,15 @@ To get started with Screenplay, the first step is to decide how you'd like to us
1113
[As a testing tool, with Reqnroll]: gettingStarted/reqnroll/index.md
1214
[the retired SpecFlow]: https://reqnroll.net/news/2025/01/specflow-end-of-life-has-been-announced/
1315
[As a process automation library]: gettingStarted/nonTesting/index.md
16+
17+
## 2. Pick extensions
18+
19+
To get the most from Screenplay you should install one or more [extensions].
20+
These give Screenplay the capability to interact with and control other systems.
21+
22+
Here is [a list of the extensions which are authored alongside Screenplay's core].
23+
If you'd like, you are also encouraged to [write your own extension], adding new capabilities to Screenplay.
24+
25+
[extensions]: ../glossary/Extension.md
26+
[a list of the extensions which are authored alongside Screenplay's core]: extensions/index.md
27+
[write your own extension]: extendingScreenplay/index.md

0 commit comments

Comments
 (0)