Skip to content

Commit 49e95bf

Browse files
committed
Improve next steps page
1 parent f6b2338 commit 49e95bf

2 files changed

Lines changed: 19 additions & 1 deletion

File tree

docs/setup/next_steps.mdx

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ title: Next steps
33
description: How to get started on your integration after configuring your project.
44
---
55

6+
import Button from "@site/src/Button";
7+
68
Now that you've gone through the [getting started guide](./index.mdx) and configured your project, you're ready to begin your integration.
79

810
The Redpoint EOS Online Framework offers multiple ways to integrate Epic Online Services into your project, from high-level components that you can drop into your project using blueprints, to low-level C++ APIs that provide you a high degree of control.
@@ -11,14 +13,26 @@ The Redpoint EOS Online Framework offers multiple ways to integrate Epic Online
1113

1214
Our [high-level framework components](../framework/index.mdx) are a great way to get started with Epic Online Services, especially if you're in the prototyping stage. **We recommend all new users to Epic Online Services start by using framework components.**
1315

16+
<Button
17+
type="success"
18+
href="../framework/"
19+
text="View framework component documentation"
20+
/>
21+
1422
## Using online subsystem APIs
1523

1624
If you're looking to do something not covered by the framework components, or the framework components aren't a great fit for your game, you can use the [online subsystem APIs](../ossv1/index.mdx) from blueprints or C++.
1725

26+
<Button href="../ossv1/" text="View online subsystem documentation" />
27+
1828
## Using modern C++
1929

2030
If you're a C++ developer and would prefer to use modern C++ APIs for accessing Epic Online Services, we provide [an improved C++ API](../systems/index.md) compared with the online subsystem APIs. The online subsystem APIs are constrained to the API design that Epic has put in place; our modern C++ APIs are much nicer to work with and more closely represent plugin and EOS features.
2131

32+
<Button href="../systems/" text="View modern C++ documentation" />
33+
2234
## Using team-based matchmaking
2335

2436
If you're looking to use team-based matchmaking in your game, please refer to the [matchmaking guide](../matchmaking/index.md). Team-based matchmaking can be used from blueprints or C++, but is only available to users of the Paid Edition.
37+
38+
<Button href="../matchmaking/" text="View matchmaking documentation" />

src/Button.tsx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,13 @@ export default function Button(props: {
44
href: string;
55
children?: React.ReactNode;
66
text?: string;
7+
type?: string;
78
}) {
89
return (
9-
<Link to={props.href} className="button button--primary">
10+
<Link
11+
to={props.href}
12+
className={`button button--${props.type ?? "primary"}`}
13+
>
1014
{props.text ?? props.children}
1115
</Link>
1216
);

0 commit comments

Comments
 (0)