devcyclehq / devcycle-docs Goto Github PK

@ajwootto said:

something about this tiny home icon bugs me, kinda looks like its not supposed to be there or its too small or something

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: https://resources.github.com/devops/fundamentals/devsecops

HTTP_308

View Actions Results

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: https://docs.github.com/en/github/site-policy/github-privacy-statement

HTTP_403

View Actions Results

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: https://docs.github.com/en/github/site-policy/github-terms-of-service

HTTP_403

View Actions Results

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: https://docs.github.com/en/github/site-policy/github-terms-of-service

HTTP_403

View Actions Results

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: /DevCycleHQ/devcycle-docs/search?l=css

HTTP_429

View Actions Results

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: /DevCycleHQ/devcycle-docs/search?l=javascript

HTTP_429

View Actions Results

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: https://docs.github.com/articles/which-remote-url-should-i-use

HTTP_403

View Actions Results

Description

Currently, the documentation for the SDK's variables does not cover some specific scenarios that could be useful for users to understand. These include:

• How a variable will default if the server sends a data type different than what the code expects.
• The behavior of variables when a user does not qualify for targeting.
• Possibility to set up a fallback variation manually.

The aim is to decide whether these special cases deserve their own section in the documentation, can be incorporated into existing sections, or are already covered somewhere.

Steps to Reproduce

1. Open the SDK Documentation on variables.
2. Look for information about the special cases listed above.

Expected Behavior

The documentation should provide clear information on these special cases for variables to guide users through best practices and how to handle these cases.

Actual Behavior

Currently, the documentation does not explicitly cover these scenarios.

Additional Context

The absence of these explanations could lead to misconceptions or misunderstandings about how variables behave under specific conditions.

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: https://github.com/apps/dependabot

HTTP_403

View Actions Results

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: https://docs.github.com/articles/which-remote-url-should-i-use

HTTP_403

View Actions Results

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: https://docs.github.com

HTTP_403

View Actions Results

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: https://docs.github.com/en/github/site-policy/github-privacy-statement

HTTP_403

View Actions Results

Description

As we are seeing an increasing number of users migrating from Taplytics to DevCycle, it would be beneficial to have a dedicated migration guide. This guide should aim to provide clear, step-by-step instructions on how to move projects, features, and other configurations from Taplytics to DevCycle.

Suggested Solution

Create a new section in the documentation dedicated to migration. This section should cover:

• Preliminary steps and considerations before migration.
• A checklist of items to be migrated.
• Step-by-step guide for each type of migration (Feature Flags, Experiments, User Segmentation, etc.)
• Troubleshooting common issues.
• Best practices for testing the migration.

Alternatives Considered

Another option could be to add migration tips and notes within the existing sections of the documentation, but this could scatter the information and make it hard for users specifically looking to migrate from Taplytics to find all the relevant details.

Broken link found

Broken Link Checker found a broken link on https://github.com/DevCycleHQ/devcycle-docs

Target: https://resources.github.com/learn/pathways

HTTP_308

View Actions Results