diff --git a/docs/bucketeer-docs.md b/docs/bucketeer-docs.md
deleted file mode 100644
index 04f9c107..00000000
--- a/docs/bucketeer-docs.md
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: Bucketeer Docs
-sidebar_position: 1
-slug: /
-description: Describes what the Bucketeer is and its solution. In addition, the page also provides an overview of the main sections covered in the documentation.
-tags: ['home', 'guide', 'presentation', 'overview', 'contact']
----
-
-import Button from '@site/src/components/button/Button';
-import ButtonShelf from '@site/src/components/button-shelf/ButtonShelf';
-
-# Welcome to Bucketeer docs
-
-Welcome to the Bucketeer documentation site, your comprehensive resource for everything related to the Bucketeer platform, integrations, and SDKs. You will find all the information you need to utilize the Bucketeer solution effectively here. Utilize the convenient navigation buttons below to access the desired sections quickly. Furthermore, this page will provide an in-depth overview of Bucketeer, highlighting its key features and capabilities.
-
-
+ Bucketeer offers a powerful A/B testing solution beyond superficial changes, allowing teams to test substantial functionality. With the feature management platform, organizations can establish goals and effectively measure the impact of different features.
+
+ A/B Testing
+
+ Unlock the potential of highly customized metadata to achieve precise and effective user targeting. By utilizing attributes such as region, age, or email, you can create segments or groups tailored to specific criteria. This level of granularity provides complete control over determining who sees what, empowering you to deliver personalized experiences. +
++ Explore how targeting works within Bucketeer. +
++ Use prerequisites to establish dependencies between flags and improve user targeting. Define the conditions or dependencies between flags, which will determine whether a flag should be evaluated or which variation should be provided to the end user. +
++ Learn more about Bucketeer prerequisites functionality. +
++ No need to revert code to undo a feature release—Bucketeer allows anyone to deactivate any feature at any time instantly. Leveraging feature flags as a kill switch is a common practice for mitigating risks associated with feature releases. With this functionality, product and marketing teams can participate in feature testing and releases without heavy reliance on engineering support. Whether you're conducting tests in production, implementing a canary launch, or preparing to retire a feature, rest easy knowing that it's as simple as flipping a switch. +
++ Check how kill switch works on Bucketeer. +
++ Bucketeer's feature management platform is widely used for efficiently managing beta testing programs at scale. Creating specific groups based on targeting rules allows you to include entire groups or segments in tests as needed. The feedback from beta groups is invaluable, enabling you to validate new features and identify and address bugs before rolling them out to your entire user base. +
++ Explore how to use user groups when targeting with Bucketeer. +
++ Making changes to configurations for already released products can be a daunting task. However, using feature flags, you can easily configure your application through a user-friendly interface. Instead of relying solely on engineers, anyone from the business team can turn features on or off for the end user. When your application uses feature flags, anyone with the appropriate access level can manage feature releases or modify the application in real time. +
+ ++ With Bucketeer, you can introduce new features to the production environment without impacting anything by keeping the feature flags off. When the time is right, you can easily enable these features, ensuring a smooth transition. +
++ Effortlessly roll out new features to a subset of users, such as a dedicated beta tester group, and gather valuable feedback and bug reports from real-world usage scenarios. This allows you to refine and optimize features based on user experiences before launching them to a broader audience. +
++ Learn how to create roll out releases on Bucketeer. +
++ The ongoing integration of CI/CD and monitoring solutions highlights the growing need for automation in maintaining your application in real time. Utilizing triggers allows you to manage the status of feature flags efficiently and seamlessly integrate them with external solutions like Application Performance Monitoring (APM). By leveraging triggers provided by Bucketter, you can guarantee a prompt and real-time response to any feature-related issues within your system. +
++ Learn how to create and use triggers on Bucketeer. +
++ By turning off feature flags and merging feature branches more frequently, teams can reduce the number of work-in-progress branches. This approach alleviates reviewers' stress and apprehension regarding "big bang releases." +
++ Over time, older features may conflict with new ones or become obsolete. Bucketeer's platform provides visibility into which features are still in use and who is using them, enabling teams to effectively manage their code base by determining what should be retained. +
++ Bucketeer's feature management platform aids teams in troubleshooting and resolving issues in real-time. With feature flags implemented within their applications, teams can utilize Bucketeer's audit log to identify changes that led to incidents, allowing for prompt resolution and continuous improvement. +
+Log Source | +Description | +
---|---|
UNKNOWN | +Log source with an unspecified or unknown cause. | +
FEATURE_CREATED | +A feature has been created. | +
FEATURE_RENAMED | +The name of a feature has been changed. | +
FEATURE_ENABLED | +A feature has been enabled. | +
FEATURE_DISABLED | +A feature has been disabled. | +
FEATURE_DELETED | +A feature has been deleted. | +
FEATURE_DESCRIPTION_CHANGED | +The description of a feature has been changed. | +
FEATURE_VARIATION_ADDED | +A variation has been added to a feature. | +
FEATURE_VARIATION_REMOVED | +A variation has been removed from a feature. | +
FEATURE_OFF_VARIATION_CHANGED | +The off-variation of a feature has been changed. | +
VARIATION_VALUE_CHANGED | +The value of a variation has been changed. | +
VARIATION_NAME_CHANGED | +The name of a variation has been changed. | +
VARIATION_DESCRIPTION_CHANGED | +The description of a variation has been changed. | +
VARIATION_USER_ADDED | +A user has been added to a variation. | +
VARIATION_USER_REMOVED | +A user has been removed from a variation. | +
FEATURE_RULE_ADDED | +A rule has been added to a feature. | +
FEATURE_RULE_STRATEGY_CHANGED | +The strategy of a feature rule has been changed. | +
FEATURE_RULE_DELETED | +A rule has been deleted from a feature. | +
RULE_CLAUSE_ADDED | +A clause has been added to a rule. | +
RULE_CLAUSE_DELETED | +A clause has been deleted from a rule. | +
RULE_FIXED_STRATEGY_CHANGED | +The fixed strategy of a rule has been changed. | +
RULE_ROLLOUT_STRATEGY_CHANGED | +The rollout strategy of a rule has been changed. | +
CLAUSE_ATTRIBUTE_CHANGED | +The attribute of a clause has been changed. | +
CLAUSE_OPERATOR_CHANGED | +The operator of a clause has been changed. | +
CLAUSE_VALUE_ADDED | +A value has been added to a clause. | +
CLAUSE_VALUE_REMOVED | +A value has been removed from a clause. | +
FEATURE_DEFAULT_STRATEGY_CHANGED | +The default strategy of a feature has been changed. | +
FEATURE_TAG_ADDED | +A tag has been added to a feature. | +
FEATURE_TAG_REMOVED | +A tag has been removed from a feature. | +
FEATURE_VERSION_INCREMENTED | +The version of a feature has been incremented. | +
FEATURE_ARCHIVED | +A feature has been archived. | +
FEATURE_CLONED | +A feature has been cloned. | +
FEATURE_UNARCHIVED | +A feature has been unarchived. | +
SAMPLING_SEED_RESET | +The sampling seed has been reset. | +
PREREQUISITE_ADDED | +A prerequisite has been added. | +
PREREQUISITE_REMOVED | +A prerequisite has been removed. | +
PREREQUISITE_VARIATION_CHANGED | +The variation of a prerequisite has been changed. | +
GOAL_CREATED | +A goal has been created. | +
GOAL_RENAMED | +The name of a goal has been changed. | +
GOAL_DESCRIPTION_CHANGED | +The description of a goal has been changed. | +
GOAL_DELETED | +A goal has been deleted. | +
GOAL_ARCHIVED | +A goal has been archived. | +
EXPERIMENT_CREATED | +An experiment has been created. | +
EXPERIMENT_STOPPED | +An experiment has been stopped. | +
EXPERIMENT_START_AT_CHANGED | +The start time of an experiment has been changed. | +
EXPERIMENT_STOP_AT_CHANGED | +The stop time of an experiment has been changed. | +
EXPERIMENT_DELETED | +An experiment has been deleted. | +
EXPERIMENT_PERIOD_CHANGED | +The period of an experiment has been changed. | +
EXPERIMENT_NAME_CHANGED | +The name of an experiment has been changed. | +
EXPERIMENT_DESCRIPTION_CHANGED | +The description of an experiment has been changed. | +
EXPERIMENT_STARTED | +An experiment has started. | +
EXPERIMENT_FINISHED | +An experiment has finished. | +
EXPERIMENT_ARCHIVED | +An experiment has been archived. | +
ACCOUNT_CREATED | +An account has been created. | +
ACCOUNT_ROLE_CHANGED | +The role of an account has been changed. | +
ACCOUNT_ENABLED | +An account has been enabled. | +
ACCOUNT_DISABLED | +An account has been disabled. | +
ACCOUNT_DELETED | +An account has been deleted. | +
APIKEY_CREATED | +An API key has been created. | +
APIKEY_NAME_CHANGED | +The name of an API key has been changed. | +
APIKEY_ENABLED | +An API key has been enabled. | +
APIKEY_DISABLED | +An API key has been disabled. | +
SEGMENT_CREATED | +A segment has been created. | +
SEGMENT_DELETED | +A segment has been deleted. | +
SEGMENT_NAME_CHANGED | +The name of a segment has been changed. | +
SEGMENT_DESCRIPTION_CHANGED | +The description of a segment has been changed. | +
SEGMENT_RULE_ADDED | +A rule has been added to a segment. | +
SEGMENT_RULE_DELETED | +A rule has been deleted from a segment. | +
SEGMENT_RULE_CLAUSE_ADDED | +A clause has been added to a rule in a segment. | +
SEGMENT_RULE_CLAUSE_DELETED | +A clause has been deleted from a rule in a segment. | +
SEGMENT_CLAUSE_ATTRIBUTE_CHANGED | +The attribute of a clause in a segment has been changed. | +
SEGMENT_CLAUSE_OPERATOR_CHANGED | +The operator of a clause in a segment has been changed. | +
SEGMENT_CLAUSE_VALUE_ADDED | +A value has been added to a clause in a segment. | +
SEGMENT_CLAUSE_VALUE_REMOVED | +A value has been removed from a clause in a segment. | +
SEGMENT_USER_ADDED | +A user has been added to a segment. | +
SEGMENT_USER_DELETED | +A user has been deleted from a segment. | +
SEGMENT_BULK_UPLOAD_USERS | +Users have been bulk uploaded to a segment. | +
SEGMENT_BULK_UPLOAD_USERS_STATUS_CHANGED | +The status of a bulk upload of users to a segment has been changed. | +
ENVIRONMENT_CREATED | +An environment has been created. | +
ENVIRONMENT_RENAMED | +The name of an environment has been changed. | +
ENVIRONMENT_DESCRIPTION_CHANGED | +The description of an environment has been changed. | +
ENVIRONMENT_DELETED | +An environment has been deleted. | +
ADMIN_ACCOUNT_CREATED | +An admin account has been created. | +
ADMIN_ACCOUNT_ENABLED | +An admin account has been enabled. | +
ADMIN_ACCOUNT_DISABLED | +An admin account has been disabled. | +
AUTOOPS_RULE_CREATED | +An auto operation rule has been created. | +
AUTOOPS_RULE_DELETED | +An auto operation rule has been deleted. | +
AUTOOPS_RULE_OPS_TYPE_CHANGED | +The operations type of an auto operation rule has been changed. | +
AUTOOPS_RULE_CLAUSE_DELETED | +A clause has been deleted from an auto operation rule. | +
AUTOOPS_RULE_TRIGGERED_AT_CHANGED | +The triggered-at time of an auto operation rule has been changed. | +
OPS_EVENT_RATE_CLAUSE_ADDED | +A clause related to event rate has been added to an auto operation rule. | +
OPS_EVENT_RATE_CLAUSE_CHANGED | +A clause related to event rate has been changed in an auto operation rule. | +
DATETIME_CLAUSE_ADDED | +A datetime clause has been added to an auto operation rule. | +
DATETIME_CLAUSE_CHANGED | +A datetime clause has been changed in an auto operation rule. | +
PUSH_CREATED | +A push notification has been created. | +
PUSH_DELETED | +A push notification has been deleted. | +
PUSH_TAGS_ADDED | +Tags have been added to a push notification. | +
PUSH_TAGS_DELETED | +Tags have been deleted from a push notification. | +
PUSH_RENAMED | +A push notification has been renamed. | +
SUBSCRIPTION_CREATED | +A subscription has been created. | +
SUBSCRIPTION_DELETED | +A subscription has been deleted. | +
SUBSCRIPTION_ENABLED | +A subscription has been enabled. | +
SUBSCRIPTION_DISABLED | +A subscription has been disabled. | +
SUBSCRIPTION_SOURCE_TYPE_ADDED | +A source type has been added to a subscription. | +
SUBSCRIPTION_SOURCE_TYPE_DELETED | +A source type has been deleted from a subscription. | +
SUBSCRIPTION_RENAMED | +A subscription has been renamed. | +
ADMIN_SUBSCRIPTION_CREATED | +An admin subscription has been created. | +
ADMIN_SUBSCRIPTION_DELETED | +An admin subscription has been deleted. | +
ADMIN_SUBSCRIPTION_ENABLED | +An admin subscription has been enabled. | +
ADMIN_SUBSCRIPTION_DISABLED | +An admin subscription has been disabled. | +
ADMIN_SUBSCRIPTION_SOURCE_TYPE_ADDED | +A source type has been added to an admin subscription. | +
ADMIN_SUBSCRIPTION_SOURCE_TYPE_DELETED | +A source type has been deleted from an admin subscription. | +
ADMIN_SUBSCRIPTION_RENAMED | +An admin subscription has been renamed. | +
PROJECT_CREATED | +A project has been created. | +
PROJECT_DESCRIPTION_CHANGED | +The description of a project has been changed. | +
PROJECT_ENABLED | +A project has been enabled. | +
PROJECT_DISABLED | +A project has been disabled. | +
PROJECT_TRIAL_CREATED | +A trial for a project has been created. | +
PROJECT_TRIAL_CONVERTED | +A trial for a project has been converted to a full subscription. | +
PROJECT_RENAMED | +The name of a project has been changed. | +
WEBHOOK_CREATED | +A webhook has been created. | +
WEBHOOK_DELETED | +A webhook has been deleted. | +
WEBHOOK_NAME_CHANGED | +The name of a webhook has been changed. | +
WEBHOOK_DESCRIPTION_CHANGED | +The description of a webhook has been changed. | +
WEBHOOK_CLAUSE_ADDED | +A clause has been added to a webhook. | +
WEBHOOK_CLAUSE_CHANGED | +A clause has been changed in a webhook. | +
PROGRESSIVE_ROLLOUT_CREATED | +A progressive rollout has been created. | +
PROGRESSIVE_ROLLOUT_DELETED | +A progressive rollout has been deleted. | +
PROGRESSIVE_ROLLOUT_SCHEDULE_TRIGGERED_AT_CHANGED | +The scheduled trigger time of a progressive rollout has been changed. | +
ORGANIZATION_CREATED | +An organization has been created. | +
ORGANIZATION_NAME_CHANGED | +The name of an organization has been changed. | +
ORGANIZATION_DESCRIPTION_CHANGED | +The description of an organization has been changed. | +
ORGANIZATION_ENABLED | +An organization has been enabled. | +
ORGANIZATION_DISABLED | +An organization has been disabled. | +
ORGANIZATION_ARCHIVED | +An organization has been archived. | +
ORGANIZATION_UNARCHIVED | +An organization has been unarchived. | +
ORGANIZATION_TRIAL_CONVERTED | +An organization's trial has been converted to a full subscription. | +
FLAG_TRIGGER_CREATED | +A flag trigger has been created. | +
FLAG_TRIGGER_RESET | +A flag trigger has been reset. | +
FLAG_TRIGGER_DESCRIPTION_CHANGED | +The description of a flag trigger has been changed. | +
FLAG_TRIGGER_DISABLED | +A flag trigger has been disabled. | +
FLAG_TRIGGER_ENABLED | +A flag trigger has been enabled. | +
FLAG_TRIGGER_DELETED | +A flag trigger has been deleted. | +
FLAG_TRIGGER_USAGE_UPDATED | +The usage information of a flag trigger has been updated. | +
{content}
+