Update docs to use strata namespace (#203)

## Changes

Use Strata namespace in documentation

Author: baonguyenNava

README.md

@@ -1,20 +1,20 @@
-# Flex
+# Strata
 
-Use the Flex SDK to create intuitive, accessible, and effective digital-native government digital services for residents, business owners, and government staff. Leverage extensible modular components to create multi-page intake applications and case management workflows.
+Use the Strata SDK to create intuitive, accessible, and effective digital-native government digital services for residents, business owners, and government staff. Leverage extensible modular components to create multi-page intake applications and case management workflows.
 
 ## Installation
 
 See [Installation](./docs/installation.md) for instructions
-on getting the Flex SDK installed for your project.
+on getting the Strata SDK installed for your project.
 
-## Get started using Flex
+## Get started using Strata
 
-See [Getting Started](./docs/getting-started.md) for a guide on how to create your first Flex application.
+See [Getting Started](./docs/getting-started.md) for a guide on how to create your first Strata application.
 
 ## Documentation
 
-See [Flex SDK Documentation](./docs/README.md) for an organized overview of all available documentation.
+See [Strata SDK Documentation](./docs/README.md) for an organized overview of all available documentation.
 
 ## Contributing
 
-See [CONTRIBUTING.md](./CONTRIBUTING.md) for details on how to contribute to the Flex SDK.
+See [CONTRIBUTING.md](./CONTRIBUTING.md) for details on how to contribute to the Strata SDK.

docs/README.md

@@ -1,19 +1,19 @@
-# Flex SDK Documentation
+# Strata SDK Documentation
 
-Welcome to the Flex SDK documentation. This index provides an organized overview of all available documentation.
+Welcome to the Strata SDK documentation. This index provides an organized overview of all available documentation.
 
 ## Getting Started
 
-- [Getting started guide](./getting-started.md) - Begin here to create your first Flex application
+- [Getting started guide](./getting-started.md) - Begin here to create your first Strata application
 
 ## Core concepts
 
-- [Flex SDK components](./flex-sdk-components.md) - Overview of available SDK components
+- [Strata SDK components](./strata-sdk-components.md) - Overview of available SDK components
 - [Authorization](./authorization.md) - Built-in base policies for secure authorization patterns
-- [Flex Data Modeler](./flex-data-modeler.md) - Learn how to define data models using Flex Attributes and generate migrations using the Flex Migration Generator.
+- [Strata Data Modeler](./strata-data-modeler.md) - Learn how to define data models using Strata Attributes and generate migrations using the Strata Migration Generator.
 - [Multi-Page Form Builder](./multi-page-form-builder.md) - Create complex forms that span multiple pages
 - [Business process family tree](./business-process-family-tree.md) - Understanding business process hierarchies
-- [Flex Rules Engine](./flex-rules-engine.md) - Introduction to the rules engine for business logic
+- [Strata Rules Engine](./strata-rules-engine.md) - Introduction to the rules engine for business logic
 
 ## Implementation guides
 
@@ -25,5 +25,5 @@ Welcome to the Flex SDK documentation. This index provides an organized overview
 
 ## Reference
 
-- [Flex attributes](./flex-attributes.md) - Detailed documentation on all Flex attributes
-- [Generators](./generators.md) - Generate boilerplate code with Flex generators
+- [Strata attributes](./strata-attributes.md) - Detailed documentation on all Strata attributes
+- [Generators](./generators.md) - Generate boilerplate code with Strata generators

docs/contributing/contributing-strata-attributes.md

@@ -1,11 +1,11 @@
-# Contributing new Flex attributes
+# Contributing new Strata attributes
 
-This document describes how to create new Flex attributes
+This document describes how to create new Strata attributes
 
 ## Design
 
-1. Decide whether or not to create a new value object in app/models/flex/
-   By default, Flex attributes will require creating a new value object. The exception is if the type of the attribute is already a native Ruby type, such as the memorable_date attribute which represents a Date object.
+1. Decide whether or not to create a new value object in app/models/strata/
+   By default, Strata attributes will require creating a new value object. The exception is if the type of the attribute is already a native Ruby type, such as the memorable_date attribute which represents a Date object.
 
 2. Determine if the attribute is composed of multiple nested attributes:
 
@@ -67,19 +67,19 @@ This document describes how to create new Flex attributes
    ```
 
 3. Decide if there are validations that need to be added by default.
-   Note: Do not add presence option or validation. By default all Flex attributes allow nil.
+   Note: Do not add presence option or validation. By default all Strata attributes allow nil.
 
 ## Implementation
 
 1. Create the value object
-2. Create a Concern `{FlexAttributeType}Attribute` in `app/lib/strata/attributes/` with a class method `{flex_attribute_type}_attribute` that takes the attribute `name` and an `options` hash and defines the new flex_attribute type on the including class, then include the module in Strata::Attributes in `app/lib/strata/attributes.rb`
-   1. **Important**: The `flex_attribute` method in `app/lib/strata/attributes.rb` dynamically calls `#{type}_attribute`, so following the naming convention for the class method is required for the attribute to work properly.
-3. Extend the `flex:migration` generator in `migration_generator.rb` to include the new Flex attribute.
-4. For testing, add the new flex attribute to TestRecord in `spec/dummy/app/models/test_record.rb`. Try using the flex migration generator to generate this migration by running `cd spec/dummy && bin/rails generate flex:migration Add<AttributeName>ToTestRecords <attribute_name>:<flex_attribute_type>` and then run the migration with `bin/rails db:migrate`
-5. Add tests to spec/dummy/spec/lib/flex/attributes_spec.rb leveraging the new flex attribute. Make sure to test:
+2. Create a Concern `{StrataAttributeType}Attribute` in `app/lib/strata/attributes/` with a class method `{strata_attribute_type}_attribute` that takes the attribute `name` and an `options` hash and defines the new strata_attribute type on the including class, then include the module in Strata::Attributes in `app/lib/strata/attributes.rb`
+   1. **Important**: The `strata_attribute` method in `app/lib/strata/attributes.rb` dynamically calls `#{type}_attribute`, so following the naming convention for the class method is required for the attribute to work properly.
+3. Extend the `strata:migration` generator in `migration_generator.rb` to include the new Strata attribute.
+4. For testing, add the new strata attribute to TestRecord in `spec/dummy/app/models/test_record.rb`. Try using the strata migration generator to generate this migration by running `cd spec/dummy && bin/rails generate strata:migration Add<AttributeName>ToTestRecords <attribute_name>:<strata_attribute_type>` and then run the migration with `bin/rails db:migrate`
+5. Add tests to spec/dummy/spec/lib/strata/attributes_spec.rb leveraging the new strata attribute. Make sure to test:
   a. Assign a Hash to the attribute and make sure the attribute is cast to the value object type and has the correct value
   b. Load the attribute from the database and make sure the attribute is correctly cast from the database record to the value object type and has the correct value
   c. Test validation logic if relevant. When testing validation logic, check that the appropriate error objects are present and that the original uncast values are present so that they can be shown to the user to be fixed.
-1. Create the associated FormBuilder helper method for rendering the form fields associated with the Flex attribute. (See [Contributing FormBuilder helper methods](/docs/contributing/contributing-form-builder-helper-methods.md))
+1. Create the associated FormBuilder helper method for rendering the form fields associated with the Strata attribute. (See [Contributing FormBuilder helper methods](/docs/contributing/contributing-form-builder-helper-methods.md))
 
 See the existing attribute tests in the codebase for examples.

docs/contributing/data-modeling-guidelines.md

@@ -1,10 +1,10 @@
 # Data Modeling Guidelines
 
-The Flex SDK uses domain-driven design (DDD) principles. These guidelines explain key ideas in plain language, with examples, so developers can apply them consistently.
+The Strata SDK uses domain-driven design (DDD) principles. These guidelines explain key ideas in plain language, with examples, so developers can apply them consistently.
 
 ## ActiveRecord vs Repository Pattern
 
-DDD often recommends the repository pattern as a layer that separates domain logic from data persistence. To align with common Rails practice, the Flex SDK skips this extra layer. Instead, the model class itself acts as the repository.
+DDD often recommends the repository pattern as a layer that separates domain logic from data persistence. To align with common Rails practice, the Strata SDK skips this extra layer. Instead, the model class itself acts as the repository.
 
 ### What this means for you
 

docs/contributing/implementation-guidelines.md

@@ -1,6 +1,6 @@
 # Implementation Guidelines
 
-This document provides guidelines for implementing features in the Flex SDK. Following these guidelines will help ensure code quality, maintainability, and consistency.
+This document provides guidelines for implementing features in the Strata SDK. Following these guidelines will help ensure code quality, maintainability, and consistency.
 
 ## Code Simplicity
 

docs/docs/case-management-business-process.md

@@ -1,6 +1,6 @@
 # Creating a Case Management Business Process
 
-After creating an application form, the next step is to define how that application will be processed. In Flex, this is done through a case management business process, which defines the workflow and tasks needed to process the application.
+After creating an application form, the next step is to define how that application will be processed. In Strata, this is done through a case management business process, which defines the workflow and tasks needed to process the application.
 
 ## Understanding Case Management
 
@@ -17,19 +17,19 @@ A case management business process consists of:
 
 ## Creating a new business process
 
-Creating a case management business process involves generating a case model that extends from `Flex::Case` and defining a business process that specifies the workflow. The business process determines how an application moves through your organization, from initial submission to final determination. This guide continues with the passport application example to demonstrate how to create a business process for handling passport applications.
+Creating a case management business process involves generating a case model that extends from `Strata::Case` and defining a business process that specifies the workflow. The business process determines how an application moves through your organization, from initial submission to final determination. This guide continues with the passport application example to demonstrate how to create a business process for handling passport applications.
 
 ### 1. Generate the Case and Business Process
 
 First, generate the case model and business process files:
 
 ```shell
-bin/rails generate flex:case PassportCase
+bin/rails generate strata:case PassportCase
 ```
 
 This command will:
 
-- Create a case model in `app/models/flex/passport_case.rb`
+- Create a case model in `app/models/strata/passport_case.rb`
 - Generate a business process in `app/business_processes/passport_business_process.rb`
 - Set up the necessary database migrations
 - Create task models and views
@@ -40,7 +40,7 @@ Update the generated business process file to define your workflow:
 
 ```ruby
 # app/business_processes/passport_business_process.rb
-class PassportBusinessProcess < Flex::BusinessProcess
+class PassportBusinessProcess < Strata::BusinessProcess
   # Define steps
   applicant_task('submit_application')
 
@@ -65,10 +65,10 @@ end
 For each task in your business process, generate the necessary views:
 
 ```shell
-bin/rails generate flex:task verify_identity PassportCase
-bin/rails generate flex:task review_documents PassportCase
-bin/rails generate flex:task process_payment PassportCase
-bin/rails generate flex:task make_determination PassportCase
+bin/rails generate strata:task verify_identity PassportCase
+bin/rails generate strata:task review_documents PassportCase
+bin/rails generate strata:task process_payment PassportCase
+bin/rails generate strata:task make_determination PassportCase
 ```
 
 ### 5. Test the Business Process
@@ -89,4 +89,4 @@ kase.business_process_instance.current_step
 
 ## Next Steps
 
-1. [Add custom task implementations](../lib/generators/flex/task/USAGE)
+1. [Add custom task implementations](../lib/generators/strata/task/USAGE)