Skip to content

Commit 456bf7b

Browse files
committed
docs: reorder pages
1 parent 71f1ce9 commit 456bf7b

38 files changed

Lines changed: 47 additions & 40 deletions

File tree

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
22
"label": "Administration and Security",
3-
"position": 40,
3+
"position": 4,
44
"collapsed": true
55
}
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
22
"label": "Access Control",
3-
"position": 10,
3+
"position": 2,
44
"collapsed": true
55
}

docs/docs/administration-and-security/billing-api-usage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Billing and API Usage
3-
sidebar_position: 120
3+
sidebar_position: 1
44
---
55

66
When you use Flagsmith on Flagsmith-managed infrastructure (SaaS or private cloud), your pricing plan has a limit of API
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
22
"label": "Data Management",
3-
"position": 40,
3+
"position": 4,
44
"collapsed": true
55
}
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
22
"label": "Governance and Compliance",
3-
"position": 30,
3+
"position": 3,
44
"collapsed": true
55
}
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
22
"label": "Platform Configuration",
3-
"position": 50,
3+
"position": 5,
44
"collapsed": true
55
}
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
22
"label": "Best Practices",
3-
"position": 60,
3+
"position": 6,
44
"collapsed": true
55
}

docs/docs/best-practices/defensive-coding.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Defensive Coding and Designing for Failure
33
sidebar_label: Defensive Coding
4-
sidebar_position: 30
4+
sidebar_position: 4
55
---
66

77
Introducing feature flags and remote config to your applications can provide a wealth of benefits, but there are also a few drawbacks. Fortunately, the majority of these can be avoided through [defensive coding](#defensive-coding) and sensible approaches to default flags.

docs/docs/best-practices/efficient-api-usage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Efficient API Usage
33
sidebar_label: Efficient API Usage
4-
sidebar_position: 50
4+
sidebar_position: 5
55
---
66

77
It is good engineering practise to reduce the frequency of API calls made from your applications to Flagsmith. There are a number of reasons for this:

docs/docs/best-practices/flag-lifecycle.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Feature Flags Lifecycles
33
sidebar_label: Feature Flags Lifecycles
4-
sidebar_position: 10
4+
sidebar_position: 1
55
---
66

77
Feature Flags generally have two lifecycles:

0 commit comments

Comments
 (0)