# github_gpt

milvus_id: 452165072252045244
data:
"source2
filestructure.py(d
%	file_path2
filestructure.py(e
%	file_name2
filestructure.py(f
	file_type2
.py(g
�!text�!2�!
�!import os
import subprocess

def get_git_tracked_files():
    """
    Executes 'git ls-tree' command to get all files tracked by git.
    
    :return: A list of all files tracked by git in the repository.
    """
    try:
        result = subprocess.run(
            ['git', 'ls-tree', '--full-tree', '-r', '--name-only', 'HEAD'],
            check=True,
            stdout=subprocess.PIPE,
            stderr=subprocess.PIPE,
            text=True
        )
        tracked_files = result.stdout.splitlines()
        return tracked_files
    except subprocess.CalledProcessError as e:
        print(f"Error executing git command: {e.stderr}")
        return []

def generate_directory_structure(tracked_files, file):
    """
    Generates a directory structure based on the list of files tracked by Git.
    
    :param tracked_files: A list of all files tracked by git.
    :param file: The file object where the directory structure will be written.
    """
    directory_tree = {}
    
    # Construct the directory tree
    for filepath in tracked_files:
        parts = filepath.split(os.sep)
        current_level = directory_tree
        
        for i, part in enumerate(parts):
            if i == len(parts) - 1:
                # This is a file, add it to the current level
                current_level.setdefault('__files__', []).append(part)
            else:
                # This is a directory, add it to the current level
                current_level = current_level.setdefault(part, {})

    def write_structure(current_level, indent='', branch='├── '):
        # Separate directories and files, then sort them
        directories = sorted((k, v) for k, v in current_level.items() if k != '__files__')
        files = sorted(current_level.get('__files__', []))

        # Write directories first
        for index, (key, value) in enumerate(directories):
            is_last = (index == len(directories) - 1 and not files)  # Check if it's the last directory
            file.write(f"{indent}{branch}{key}/\n")
            # Recursive call, adjusting the indent and branch for the next level
            new_indent = indent + ('│ ' if not is_last else '  ')
            write_structure(value, new_indent, branch)

        # Write files after directories
        for index, filename in enumerate(files):
            branch = '└── ' if index == len(files) - 1 else '├── '
            file.write(f"{indent}{branch}{filename}\t# Comment is following\n")

    write_structure(directory_tree)

def filter_files_and_directories(tracked_files):
    """
    Filters out specific files and directories based on the rules provided.
    
    :param tracked_files: A list of all files tracked by git.
    :return: A filtered list of files.
    """
    filtered_files = []
    ignore_files_and_folders = [
        'database',  # Ignore this folder and its contents
        'bootstrap', # Ignore this folder and its contents
        'storage',   # Ignore this folder and its contents
        'tests',     # Ignore this folder and its contents
        'npm-cache', # Ignore this folder and its contents
        'public/files',  # Ignore this folder and its contents
        'public/fonts',  # Ignore this folder and its contents
        'public/img'     # Ignore this folder and its contents
    ]

    for filepath in tracked_files:
        # Check if the current path should be ignored completely
        ignore = any(filepath == folder or filepath.startswith(folder + os.sep) for folder in ignore_files_and_folders)
        
        if not ignore:
            filtered_files.append(filepath)
    
    return filtered_files

def main():
    # Get all files tracked by git in the repository
    tracked_files = get_git_tracked_files()

    if not tracked_files:
        print("No files are tracked by git or an error occurred.")
        return

    # Filter the tracked files based on rules
    filtered_files = filter_files_and_directories(tracked_files)

    # Output file name
    output_file = os.path.join(os.getcwd(), 'directory_structure.txt')

    # Open the file to write the directory structure
    with open(output_file, 'w') as file:
        generate_directory_structure(filtered_files, file)

    print(f"Directory structure saved to {output_file}")


if __name__ == "__main__":
    main()
(h
pk

	����̷��(i
�0evector"�0��0
�0�+)���
=ģ�<�l&�6R���r%d�C�m�r�׼��:=�
g<r�<�B�;�f��D�8�0����K�,�<�F����<��=ۀ���=�䔼r	ݼ���;�r�P<rCK��t�;r��ϊ�;�Ƽ�ד���*�[��;���<�6��u
=D̺D�8=-��gA=��r��<,Z}�[`���#����;�[8�rE���ƀ�,x����:���;�W��F@��f�;�7=rBۻ�
B=��D��2=�,><~������<�qz:��5�D��;��J����1m<�񍹸�\�~�=Pq�:D3�<-����
r=���r(�<�+���f,=!�=,$O��YX�g��:��.�9C,��o��M��s<�f�=���!"�,�@��q��f,��0��U�<�c���f<�t���*=s
=P�=�}��5��������b��ջg��=Dݍ<�K�<D��<,�[=mp<-�;ψR�[I<�h��,[�����D2�<gz<Dj���l˼Ќ��ZS��Hż�=�;=�Q�rAk�DO����K�~٠<��!��=Dܝ;s��C�s=�L�;�a����ļ���<D��gz=r|I=~��,X<�2���<��:�1H<
��<�+��gЌ;8e<
Q=�v<�=��J<�a|<�Q=
�<�b�����;�H �Ŀ�Ϧ9=�3(�ģ<g%��󀁽�׸<g{�[�����_�\!��s��[<��28�,�@���=�#�����=�N�<r}9=
��P�<�L����3��?=��S��3�<6�<[9�<��=���;�^�!���,h��=��HE����rC˼�-&/��ʿ�[p�<-_�<D�Ƽ���<p@�Z��;�f��[�Ӽ[���������˻r�>=�w�<���<�(~��W�<�L<[��r�N�-���r��Ĉ=Ϧ9<�,��(��~��<�F@<�u:�D��:�>=,�P����<�gv�����r�P�Z7��>A=CJZ��㻸�U�����䔻sd����[��'�D���-��=�_%��ߒ�[���[T޼�`g�[�a=sG�<�f,=D�M���<���;���<��4=-�+��@!;D�?�Zp�[:7�\=�<![�;Ќ�<�w=,��8r'D=��<��+=P����
�C-c=Z6����<[�<;��<s)�<����Ƽ�J��r�7=r�ż�5-<��x;��߼�{�<���<D����7��%
=r �,���,��:P��Dڽ8DO
=���;�2]=�W�[к���:�����'�������Ӽ-a
=,%�<�޻��O=[@����<���<�晼���<P��
���U�<�ZH<�,���I5=�PD=糍<�G=Ш���'=�=Q�PŘ�
m;�D`=!@<q�<-�+�ZS�
6=�3�����r��;D3����<��L�r�л8�<��ݻϤY��'�[<��g��;,>��ω�<�bl���<[W.�D�(=r`B=gB�<-�+<�㼭a��Ӂ��z<φr<�<���<�}^��V�<�jF<D�
<�u�DO
<�:,���"�;Ĥ<�WS=[`���~<,�{=��$�T9�C�T=g�=��&=D�9��Y<��7=Ceq�,�[�-��<r{ٻgz�<���<9���PT����1=���<-�+<��ĽD�H=;��G;���:rҾ��#�ϣ�;��0��bG���������<�|���d=rz�<����[���Gռ~�"<��H�Ć =g탽���<�5-<,�;r �9-�=��T<sՎ<,?�;����Ӽ
Ó;
5��~h����	���<����7����#�r�'<�n<-��<D��r�7=P៼g�=�[8=���;��+<�XC��5-��ߒ�s���
g��x��C��<�gv�~K�����^��|n���⼡?�q����t;���x/��.x=~L
<6Һ,��;C�f<��ۼ�<ZR~���<,xd<�뛻\��!鞼�":�!͗�P��r�'�ϥ�;9���r�W<�g=
Ó;ϣ�[W��sd�;�E=
��:s򅽭Ӂ�D�ͻ��:��<�0}:�Ն�r�%<r]r�籭�s��,"o<�x
�,#_���s�;��Y�C�]��D`�\ˊ�P�<���!?��ra2=8I�[ <[ɪ<���C�x�r�@:9f����<�hf�9���Qi<���:,%�;��S��N=���9~��;g��PS��Ϧ�<
5����������G�;r
M9,�Һr-=P�;-C�<��<Di1�\ˊ<���[�J����=PS��
g=-(�,�p��Y��P�=���������l��L߼���<r��Q�r@{<!@<Z���5�;�˂��g�<r�P<�aW���:���;~0=gB	�DO��r�'���H<
��:���C�ݺr�p��59C�＠���=<��|<��%=r��9D̼C,s;D�4��!%=���,�;;,��;�HE<[���)�<��s;C�����&�,yT��F��I5<8,!=s)��6Ҽ-C&���
��f�<��-��<�&y<C�ϼP�;
�#<ZR~���*=��j��ʹ<��<!�=���<sd=�G�;�}<~��rm<�/h���������H<χ�<�O/<�#=-C�<Z�q�C�}���ؼ�D�;ZR~���<�l<g<-Ӊ���d�rﵼr|�;,�b�Ѝ=�J%�rB�<��&<!@�:!��D�F<��L;�V�D���D��<C�<[��<q0��f,���*<�����?:-C��-D;�}޼甶<畦����ې����<�(~;q0=��<9�������:��M�R�<!�DM*��l�<�=��~������!?��� 5=���g����B������:��?���=Pƈ��S��r�5=�;L�r�.��T���&��t��D�&�oP��Nd��%
:D�8<��<�����&�9���G0�s
���Ϲ-E������=,%?���<�h���w��ѡ<�F=5b���<�Eи-��:ryy<P�!���Q=[T޻���,#_�g��畦<[�J����<���:[Y=�<9���'i<r�м��
;-�=��=�@�<�z=~h��g	<�bl<D��<�:�����<�'��N?;��<��<�(Y�,�K�D���!����N�;Pp=-� �9-���b��,�K����<��
��c�㬹,^=�����;�!�Di1�U)�[0��.=��Ӽr|�<\ˊ�s� ��lK<�~N���.=,�����<����˺Z�x<[��;�=��<!�<-E<�%���;Z��N�<�s���v<��*<�?�<��üg�<��_��.x<��<��<���<��f<⼼���<C�v<��8<�=,�P���k<�����˹��s<[�c<,x���3=���<�7=��<��>���C�[8W=D��<�x����,]ͻ
��(~�[rE���z�\=�r�;r~)��w;,\]:�
 ��/h<D�����<<���rD;<��޼��ѻ甶;��@<�B�<�
�<-��<�����<��ϼ
£<���<�tʻDL�<�d�<�򪼕�=�dL<�N<9�;sb�<8�<
�;
ă<,B�<���
�#=�=�<
����k���5�Z7�<ۭ�-}��-|$<��<�C<��
<��Q��+�<�	=�x�<�v�:r]r��#�;C���\�<[�[s5���2�甶;D03�-ѩ<�*�;�d̼�����d'<��=���<~<r����˼��<��<r�.<~��D����<����<a�r&Լ[���r��<9"<�L_=��J�,?f<sc�~�	��ð��bG������a����ڼ�
�<-�	�[V�<Ϧ�<!��,"�9,]M=[���v*<D�4<�%��,��<�w��'<�Xh�g_����;���;���-&���?�;,]ͻ~�9Dڽ�,��<�u��`�������;��=���<��c����<�r<���r�μ� Z;�Cp;-�<D����ӻϢy:�Q=��V;��/��C�<��<�X�<D�==
�=�w�:糍;
��Ϧ�<����K��2ݼ���:��0��.����x�P�<�PD�r�p�-�0���=\=�<��z���_���;����L;<gz�<D�=<�?=���,��<-
(�~K=ωB�Ŀ�<C��<籭<���!��<�to�[�!��<Z6�;���sF�<�Y�8I�C\<��;D�
=9���b�r�u:�w�r�ǼD�/�DM*����u�;���[s5<Dl��s<D����z;�hf��c7����-���[�\�[��
�<χ⼸(�<�<���bG�-&/<��ܼDi1�-��<[��~��!�<�f���<�[�<�M���2]<��������-a
��*�;����,�I�D�=�Ce�-����������������<�Fe��3�<����,^�;ψR��*��rCK:�3M�D�<���;Ѝ����Q�D��\�<-D�:ra2;���sb��[�!=�g�����g��g$"��H ��&;r���g{=[�ڼsԞ��W��� �:Cܻs�	=P����u:�[;'�D�6=Ć �g�=���<�5��ZSn�D/�;,]M�
��<D�=<C�Լ�u߼���ϣi<��#=�e���T=[�üp@<,�້�ټ[ =�W���<�';�~s��3M<�{��-�<,"）N?;�n��Zo�<,B6��/<r'Ļ�YX��Q4;�5��[屻�:ܻ�g�<PŘ<,�i=r�P<r�N<D�<DO
=����^�n`��$����*���~0�<�޼�x/��!ʻ�Vc<�(Y=�7�����Ն��v*���:<[X�oл�*��-<󀁼�*�[W����z<Z��;Z�;
�
<,�{�\=�<~�<g���1��q���,xd�������;Ce���[��sb";ǥ���2���<r��<8�=,��;��	=DKJ�[W���1<!y�;�v*��Lߺ��<�4�<[�#;��;�1Ȼr�P<�l˸s�;�+μr�>�;<C�<rCK��������9�=��:��#*=�m�<r��<Z��<r
ͼ���;Cg�<�I���H<D���r��V;,>�������F�Qi<��;[�<�����)n��o�r~��~L
�DN�U)=��ۼC�ϼ�L�<,��;C,s<����vO<�U��N�g] ���<gЌ�ܒ�<��i���ʻ�ռ���,й�D/ùs���5=�1H�Ͽ�;�u_�s���D1�<���8󸏼g��<��o����;,��<oмp�;���<Ћ":�
򻡕���������<��,	8��<�9[W�<g^���i�����<D�=�q<~���9l��_���":=sG<�w���<��[Ⱥ��f,�T���+μ��;��ӻ������,��,й:�#*<o�<[9Ǽr(4�D�&�sb"���c<�
¼rE�;r(�<��{��3�;�E��(ټD���<�P�:�_�<�+��!��<~h���PD=D��D3�;,�K�r|ɻP��!�,�r��ґ���;�P�<��T������x<��㼡�!��F<,yԺ��=�Є�[��<�x/<[����|�,Z��[9G9�K�;
����1�;�WS�r�%���=Ч�:�B���
�<Q�;8��Dh���q��2�<P��<����P�糍����<,��<�#<-���n`;!y����<��<������ܼ�����>���*5���<s�=9
����<���-�0�ܮ�<ψR��K��k�;r�<
n�\!=-&/�!"��rE+=������;-�<9��;����r}9��Ko�rBۺ���<��<k��5=�k�<������C�m��_�;��;9��;r�W;��a�!͗<C�t;s
����<�4=,���!��<C��<C��<�$=���9��S��&=g�=���<D��e��*�;!�	��Ż��򼡑�;��;[s���ջ,��;C.S<6R<-��;����/�ZS�<��=�	�<�U�p�;�0�;[@=�G����<���Z��<�<��<���:��4�~h=Z�h����<r��;gB���;̻��.<Dڽ<[P=5b�Cg�<���;D��;�w����d����9�����;<����(j
RowID

	����̷��
	Timestamp

	ه��̷��(


milvus_id: 452165072252045245
data:
#source2
package-lock.json(d
&	file_path2
package-lock.json(e
&	file_name2
package-lock.json(f
	file_type	2
.json(g
��	text��	2��	
��	{
    "name": "creatify",
    "lockfileVersion": 3,
    "requires": true,
    "packages": {
        "": {
            "dependencies": {
                "@alpinejs/collapse": "^3.13.5",
                "@alpinejs/focus": "^3.13.2",
                "alpinejs": "^3.13.5",
                "animate.css": "^4.1.1",
                "aos": "^2.3.4",
                "apexcharts": "^3.49.2",
                "autoprefixer": "^10.4.15",
                "clipboard": "^2.0.11",
                "crisp-sdk-web": "^1.0.25",
                "flowbite": "^1.8.1",
                "intl-tel-input": "^18.2.1",
                "ion-rangeslider": "^2.3.1",
                "jquery": "^3.7.1",
                "jsbarcode": "^3.11.6",
                "laravel-echo": "^1.16.1",
                "lodash": "^4.17.21",
                "postcss": "^8.4.30",
                "preline": "^2.4.1",
                "puppeteer": "^22.12.1",
                "pusher-js": "^8.4.0-rc2",
                "sweetalert2": "^11.6.13",
                "tailwindcss": "^3.3.3",
                "tinymce": "^7.0.0"
            },
            "devDependencies": {
                "@tailwindcss/forms": "^0.5.2",
                "@tailwindcss/typography": "^0.5.0",
                "autoprefixer": "^10.4.7",
                "axios": "^1.1.2",
                "create-vite": "^4.4.1",
                "daisyui": "^4.7.2",
                "flowbite-typography": "^1.0.3",
                "laravel-vite-plugin": "^0.8.0",
                "postcss": "^8.4.14",
                "tailwindcss": "^3.1.0",
                "vite": "^4.0.0"
            }
        },
        "node_modules/@alloc/quick-lru": {
            "version": "5.2.0",
            "resolved": "https://registry.npmjs.org/@alloc/quick-lru/-/quick-lru-5.2.0.tgz",
            "integrity": "sha512-UrcABB+4bUrFABwbluTIBErXwvbsU/V7TZWfmbgJfbkwiBuziS9gxdODUyuiecfdGQ85jglMW6juS3+z5TsKLw==",
            "dev": true,
            "engines": {
                "node": ">=10"
            },
            "funding": {
                "url": "https://github.com/sponsors/sindresorhus"
            }
        },
        "node_modules/@alpinejs/collapse": {
            "version": "3.14.1",
            "resolved": "https://registry.npmjs.org/@alpinejs/collapse/-/collapse-3.14.1.tgz",
            "integrity": "sha512-aI0pq8SjK7c43/nMIVL1Lt8naowPRepqQGNSb9KaG7adEneOwj/vq4ZaeZYjuGbd8sq1LKPwWU+klIZIXXujUA=="
        },
        "node_modules/@alpinejs/focus": {
            "version": "3.14.1",
            "resolved": "https://registry.npmjs.org/@alpinejs/focus/-/focus-3.14.1.tgz",
            "integrity": "sha512-z4xdpK6X1LB2VitsWbL61tmABoOORuEhE5v2tnUX/be6/nAygXyeDxZ1x9s1u+bOEYlIOXXLmjdmTlhchUVWxw==",
            "dependencies": {
                "focus-trap": "^6.9.4",
                "tabbable": "^5.3.3"
            }
        },
        "node_modules/@babel/code-frame": {
            "version": "7.24.7",
            "resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.24.7.tgz",
            "integrity": "sha512-BcYH1CVJBO9tvyIZ2jVeXgSIMvGZ2FDRvDdOIVQyuklNKSsx+eppDEBq/g47Ayw+RqNFE+URvOShmf+f/qwAlA==",
            "dependencies": {
                "@babel/highlight": "^7.24.7",
                "picocolors": "^1.0.0"
            },
            "engines": {
                "node": ">=6.9.0"
            }
        },
        "node_modules/@babel/helper-validator-identifier": {
            "version": "7.24.7",
            "resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.24.7.tgz",
            "integrity": "sha512-rR+PBcQ1SMQDDyF6X0wxtG8QyLCgUB0eRAGguqRLfkCA87l7yAP7ehq8SNj96OOGTO8OBV70KhuFYcIkHXOg0w==",
            "engines": {
                "node": ">=6.9.0"
            }
        },
        "node_modules/@babel/highlight": {
            "version": "7.24.7",
            "resolved": "https://registry.npmjs.org/@babel/highlight/-/highlight-7.24.7.tgz",
            "integrity": "sha512-EStJpq4OuY8xYfhGVXngigBJRWxftKX9ksiGDnmlY3o7B/V7KIAc9X4oiK87uPJSc/vs5L869bem5fhZa8caZw==",
            "dependencies": {
                "@babel/helper-validator-identifier": "^7.24.7",
                "chalk": "^2.4.2",
                "js-tokens": "^4.0.0",
                "picocolors": "^1.0.0"
            },
            "engines": {
                "node": ">=6.9.0"
            }
        },
        "node_modules/@esbuild/android-arm": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/android-arm/-/android-arm-0.18.20.tgz",
            "integrity": "sha512-fyi7TDI/ijKKNZTUJAQqiG5T7YjJXgnzkURqmGj13C6dCqckZBLdl4h7bkhHt/t0WP+zO9/zwroDvANaOqO5Sw==",
            "cpu": [
                "arm"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "android"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/android-arm64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/android-arm64/-/android-arm64-0.18.20.tgz",
            "integrity": "sha512-Nz4rJcchGDtENV0eMKUNa6L12zz2zBDXuhj/Vjh18zGqB44Bi7MBMSXjgunJgjRhCmKOjnPuZp4Mb6OKqtMHLQ==",
            "cpu": [
                "arm64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "android"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/android-x64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/android-x64/-/android-x64-0.18.20.tgz",
            "integrity": "sha512-8GDdlePJA8D6zlZYJV/jnrRAi6rOiNaCC/JclcXpB+KIuvfBN4owLtgzY2bsxnx666XjJx2kDPUmnTtR8qKQUg==",
            "cpu": [
                "x64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "android"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/darwin-arm64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/darwin-arm64/-/darwin-arm64-0.18.20.tgz",
            "integrity": "sha512-bxRHW5kHU38zS2lPTPOyuyTm+S+eobPUnTNkdJEfAddYgEcll4xkT8DB9d2008DtTbl7uJag2HuE5NZAZgnNEA==",
            "cpu": [
                "arm64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "darwin"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/darwin-x64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/darwin-x64/-/darwin-x64-0.18.20.tgz",
            "integrity": "sha512-pc5gxlMDxzm513qPGbCbDukOdsGtKhfxD1zJKXjCCcU7ju50O7MeAZ8c4krSJcOIJGFR+qx21yMMVYwiQvyTyQ==",
            "cpu": [
                "x64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "darwin"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/freebsd-arm64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/freebsd-arm64/-/freebsd-arm64-0.18.20.tgz",
            "integrity": "sha512-yqDQHy4QHevpMAaxhhIwYPMv1NECwOvIpGCZkECn8w2WFHXjEwrBn3CeNIYsibZ/iZEUemj++M26W3cNR5h+Tw==",
            "cpu": [
                "arm64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "freebsd"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/freebsd-x64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/freebsd-x64/-/freebsd-x64-0.18.20.tgz",
            "integrity": "sha512-tgWRPPuQsd3RmBZwarGVHZQvtzfEBOreNuxEMKFcd5DaDn2PbBxfwLcj4+aenoh7ctXcbXmOQIn8HI6mCSw5MQ==",
            "cpu": [
                "x64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "freebsd"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/linux-arm": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/linux-arm/-/linux-arm-0.18.20.tgz",
            "integrity": "sha512-/5bHkMWnq1EgKr1V+Ybz3s1hWXok7mDFUMQ4cG10AfW3wL02PSZi5kFpYKrptDsgb2WAJIvRcDm+qIvXf/apvg==",
            "cpu": [
                "arm"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "linux"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/linux-arm64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/linux-arm64/-/linux-arm64-0.18.20.tgz",
            "integrity": "sha512-2YbscF+UL7SQAVIpnWvYwM+3LskyDmPhe31pE7/aoTMFKKzIc9lLbyGUpmmb8a8AixOL61sQ/mFh3jEjHYFvdA==",
            "cpu": [
                "arm64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "linux"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/linux-ia32": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/linux-ia32/-/linux-ia32-0.18.20.tgz",
            "integrity": "sha512-P4etWwq6IsReT0E1KHU40bOnzMHoH73aXp96Fs8TIT6z9Hu8G6+0SHSw9i2isWrD2nbx2qo5yUqACgdfVGx7TA==",
            "cpu": [
                "ia32"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "linux"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/linux-loong64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/linux-loong64/-/linux-loong64-0.18.20.tgz",
            "integrity": "sha512-nXW8nqBTrOpDLPgPY9uV+/1DjxoQ7DoB2N8eocyq8I9XuqJ7BiAMDMf9n1xZM9TgW0J8zrquIb/A7s3BJv7rjg==",
            "cpu": [
                "loong64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "linux"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/linux-mips64el": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/linux-mips64el/-/linux-mips64el-0.18.20.tgz",
            "integrity": "sha512-d5NeaXZcHp8PzYy5VnXV3VSd2D328Zb+9dEq5HE6bw6+N86JVPExrA6O68OPwobntbNJ0pzCpUFZTo3w0GyetQ==",
            "cpu": [
                "mips64el"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "linux"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/linux-ppc64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/linux-ppc64/-/linux-ppc64-0.18.20.tgz",
            "integrity": "sha512-WHPyeScRNcmANnLQkq6AfyXRFr5D6N2sKgkFo2FqguP44Nw2eyDlbTdZwd9GYk98DZG9QItIiTlFLHJHjxP3FA==",
            "cpu": [
                "ppc64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "linux"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/linux-riscv64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/linux-riscv64/-/linux-riscv64-0.18.20.tgz",
            "integrity": "sha512-WSxo6h5ecI5XH34KC7w5veNnKkju3zBRLEQNY7mv5mtBmrP/MjNBCAlsM2u5hDBlS3NGcTQpoBvRzqBcRtpq1A==",
            "cpu": [
                "riscv64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "linux"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/linux-s390x": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/linux-s390x/-/linux-s390x-0.18.20.tgz",
            "integrity": "sha512-+8231GMs3mAEth6Ja1iK0a1sQ3ohfcpzpRLH8uuc5/KVDFneH6jtAJLFGafpzpMRO6DzJ6AvXKze9LfFMrIHVQ==",
            "cpu": [
                "s390x"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "linux"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/linux-x64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.18.20.tgz",
            "integrity": "sha512-UYqiqemphJcNsFEskc73jQ7B9jgwjWrSayxawS6UVFZGWrAAtkzjxSqnoclCXxWtfwLdzU+vTpcNYhpn43uP1w==",
            "cpu": [
                "x64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "linux"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/netbsd-x64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/netbsd-x64/-/netbsd-x64-0.18.20.tgz",
            "integrity": "sha512-iO1c++VP6xUBUmltHZoMtCUdPlnPGdBom6IrO4gyKPFFVBKioIImVooR5I83nTew5UOYrk3gIJhbZh8X44y06A==",
            "cpu": [
                "x64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "netbsd"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/openbsd-x64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/openbsd-x64/-/openbsd-x64-0.18.20.tgz",
            "integrity": "sha512-e5e4YSsuQfX4cxcygw/UCPIEP6wbIL+se3sxPdCiMbFLBWu0eiZOJ7WoD+ptCLrmjZBK1Wk7I6D/I3NglUGOxg==",
            "cpu": [
                "x64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "openbsd"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/sunos-x64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/sunos-x64/-/sunos-x64-0.18.20.tgz",
            "integrity": "sha512-kDbFRFp0YpTQVVrqUd5FTYmWo45zGaXe0X8E1G/LKFC0v8x0vWrhOWSLITcCn63lmZIxfOMXtCfti/RxN/0wnQ==",
            "cpu": [
                "x64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "sunos"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/win32-arm64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/win32-arm64/-/win32-arm64-0.18.20.tgz",
            "integrity": "sha512-ddYFR6ItYgoaq4v4JmQQaAI5s7npztfV4Ag6NrhiaW0RrnOXqBkgwZLofVTlq1daVTQNhtI5oieTvkRPfZrePg==",
            "cpu": [
                "arm64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "win32"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/win32-ia32": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/win32-ia32/-/win32-ia32-0.18.20.tgz",
            "integrity": "sha512-Wv7QBi3ID/rROT08SABTS7eV4hX26sVduqDOTe1MvGMjNd3EjOz4b7zeexIR62GTIEKrfJXKL9LFxTYgkyeu7g==",
            "cpu": [
                "ia32"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "win32"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@esbuild/win32-x64": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/@esbuild/win32-x64/-/win32-x64-0.18.20.tgz",
            "integrity": "sha512-kTdfRcSiDfQca/y9QIkng02avJ+NCaQvrMejlsB3RRv5sE9rRoeBPISaZpKxHELzRxZyLvNts1P27W3wV+8geQ==",
            "cpu": [
                "x64"
            ],
            "dev": true,
            "optional": true,
            "os": [
                "win32"
            ],
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@isaacs/cliui": {
            "version": "8.0.2",
            "resolved": "https://registry.npmjs.org/@isaacs/cliui/-/cliui-8.0.2.tgz",
            "integrity": "sha512-O8jcjabXaleOG9DQ0+ARXWZBTfnP4WNAqzuiJK7ll44AmxGKv/J2M4TPjxjY3znBCfvBXFzucm1twdyFybFqEA==",
            "dev": true,
            "dependencies": {
                "string-width": "^5.1.2",
                "string-width-cjs": "npm:string-width@^4.2.0",
                "strip-ansi": "^7.0.1",
                "strip-ansi-cjs": "npm:strip-ansi@^6.0.1",
                "wrap-ansi": "^8.1.0",
                "wrap-ansi-cjs": "npm:wrap-ansi@^7.0.0"
            },
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/@jridgewell/gen-mapping": {
            "version": "0.3.5",
            "resolved": "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.3.5.tgz",
            "integrity": "sha512-IzL8ZoEDIBRWEzlCcRhOaCupYyN5gdIK+Q6fbFdPDg6HqX6jpkItn7DFIpW9LQzXG6Df9sA7+OKnq0qlz/GaQg==",
            "dev": true,
            "dependencies": {
                "@jridgewell/set-array": "^1.2.1",
                "@jridgewell/sourcemap-codec": "^1.4.10",
                "@jridgewell/trace-mapping": "^0.3.24"
            },
            "engines": {
                "node": ">=6.0.0"
            }
        },
        "node_modules/@jridgewell/resolve-uri": {
            "version": "3.1.2",
            "resolved": "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.1.2.tgz",
            "integrity": "sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==",
            "dev": true,
            "engines": {
                "node": ">=6.0.0"
            }
        },
        "node_modules/@jridgewell/set-array": {
            "version": "1.2.1",
            "resolved": "https://registry.npmjs.org/@jridgewell/set-array/-/set-array-1.2.1.tgz",
            "integrity": "sha512-R8gLRTZeyp03ymzP/6Lil/28tGeGEzhx1q2k703KGWRAI1VdvPIXdG70VJc2pAMw3NA6JKL5hhFu1sJX0Mnn/A==",
            "dev": true,
            "engines": {
                "node": ">=6.0.0"
            }
        },
        "node_modules/@jridgewell/sourcemap-codec": {
            "version": "1.5.0",
            "resolved": "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.5.0.tgz",
            "integrity": "sha512-gv3ZRaISU3fjPAgNsriBRqGWQL6quFx04YMPW/zD8XMLsU32mhCCbfbO6KZFLjvYpCZ8zyDEgqsgf+PwPaM7GQ==",
            "dev": true
        },
        "node_modules/@jridgewell/trace-mapping": {
            "version": "0.3.25",
            "resolved": "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.25.tgz",
            "integrity": "sha512-vNk6aEwybGtawWmy/PzwnGDOjCkLWSD2wqvjGGAgOAwCGWySYXfYoxt00IJkTF+8Lb57DwOb3Aa0o9CApepiYQ==",
            "dev": true,
            "dependencies": {
                "@jridgewell/resolve-uri": "^3.1.0",
                "@jridgewell/sourcemap-codec": "^1.4.14"
            }
        },
        "node_modules/@nodelib/fs.scandir": {
            "version": "2.1.5",
            "resolved": "https://registry.npmjs.org/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz",
            "integrity": "sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==",
            "dev": true,
            "dependencies": {
                "@nodelib/fs.stat": "2.0.5",
                "run-parallel": "^1.1.9"
            },
            "engines": {
                "node": ">= 8"
            }
        },
        "node_modules/@nodelib/fs.stat": {
            "version": "2.0.5",
            "resolved": "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz",
            "integrity": "sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==",
            "dev": true,
            "engines": {
                "node": ">= 8"
            }
        },
        "node_modules/@nodelib/fs.walk": {
            "version": "1.2.8",
            "resolved": "https://registry.npmjs.org/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz",
            "integrity": "sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==",
            "dev": true,
            "dependencies": {
                "@nodelib/fs.scandir": "2.1.5",
                "fastq": "^1.6.0"
            },
            "engines": {
                "node": ">= 8"
            }
        },
        "node_modules/@pkgjs/parseargs": {
            "version": "0.11.0",
            "resolved": "https://registry.npmjs.org/@pkgjs/parseargs/-/parseargs-0.11.0.tgz",
            "integrity": "sha512-+1VkjdD0QBLPodGrJUeqarH8VAIvQODIbwh9XpP5Syisf7YoQgsJKPNFoqqLQlu+VQ/tVSshMR6loPMn8U+dPg==",
            "dev": true,
            "optional": true,
            "engines": {
                "node": ">=14"
            }
        },
        "node_modules/@popperjs/core": {
            "version": "2.11.8",
            "resolved": "https://registry.npmjs.org/@popperjs/core/-/core-2.11.8.tgz",
            "integrity": "sha512-P1st0aksCrn9sGZhp8GMYwBnQsbvAWsZAX44oXNNvLHGqAOcoVxmjZiohstwQ7SqKnbR47akdNi+uleWD8+g6A==",
            "funding": {
                "type": "opencollective",
                "url": "https://opencollective.com/popperjs"
            }
        },
        "node_modules/@puppeteer/browsers": {
            "version": "2.3.0",
            "resolved": "https://registry.npmjs.org/@puppeteer/browsers/-/browsers-2.3.0.tgz",
            "integrity": "sha512-ioXoq9gPxkss4MYhD+SFaU9p1IHFUX0ILAWFPyjGaBdjLsYAlZw6j1iLA0N/m12uVHLFDfSYNF7EQccjinIMDA==",
            "dependencies": {
                "debug": "^4.3.5",
                "extract-zip": "^2.0.1",
                "progress": "^2.0.3",
                "proxy-agent": "^6.4.0",
                "semver": "^7.6.3",
                "tar-fs": "^3.0.6",
                "unbzip2-stream": "^1.4.3",
                "yargs": "^17.7.2"
            },
            "bin": {
                "browsers": "lib/cjs/main-cli.js"
            },
            "engines": {
                "node": ">=18"
            }
        },
        "node_modules/@tailwindcss/forms": {
            "version": "0.5.7",
            "resolved": "https://registry.npmjs.org/@tailwindcss/forms/-/forms-0.5.7.tgz",
            "integrity": "sha512-QE7X69iQI+ZXwldE+rzasvbJiyV/ju1FGHH0Qn2W3FKbuYtqp8LKcy6iSw79fVUT5/Vvf+0XgLCeYVG+UV6hOw==",
            "dev": true,
            "dependencies": {
                "mini-svg-data-uri": "^1.2.3"
            },
            "peerDependencies": {
                "tailwindcss": ">=3.0.0 || >= 3.0.0-alpha.1"
            }
        },
        "node_modules/@tailwindcss/typography": {
            "version": "0.5.14",
            "resolved": "https://registry.npmjs.org/@tailwindcss/typography/-/typography-0.5.14.tgz",
            "integrity": "sha512-ZvOCjUbsJBjL9CxQBn+VEnFpouzuKhxh2dH8xMIWHILL+HfOYtlAkWcyoon8LlzE53d2Yo6YO6pahKKNW3q1YQ==",
            "dev": true,
            "dependencies": {
                "lodash.castarray": "^4.4.0",
                "lodash.isplainobject": "^4.0.6",
                "lodash.merge": "^4.6.2",
                "postcss-selector-parser": "6.0.10"
            },
            "peerDependencies": {
                "tailwindcss": ">=3.0.0 || insiders"
            }
        },
        "node_modules/@tootallnate/quickjs-emscripten": {
            "version": "0.23.0",
            "resolved": "https://registry.npmjs.org/@tootallnate/quickjs-emscripten/-/quickjs-emscripten-0.23.0.tgz",
            "integrity": "sha512-C5Mc6rdnsaJDjO3UpGW/CQTHtCKaYlScZTly4JIu97Jxo/odCiH0ITnDXSJPTOrEKk/ycSZ0AOgTmkDtkOsvIA=="
        },
        "node_modules/@types/node": {
            "version": "22.5.0",
            "resolved": "https://registry.npmjs.org/@types/node/-/node-22.5.0.tgz",
            "integrity": "sha512-DkFrJOe+rfdHTqqMg0bSNlGlQ85hSoh2TPzZyhHsXnMtligRWpxUySiyw8FY14ITt24HVCiQPWxS3KO/QlGmWg==",
            "optional": true,
            "dependencies": {
                "undici-types": "~6.19.2"
            }
        },
        "node_modules/@types/yauzl": {
            "version": "2.10.3",
            "resolved": "https://registry.npmjs.org/@types/yauzl/-/yauzl-2.10.3.tgz",
            "integrity": "sha512-oJoftv0LSuaDZE3Le4DbKX+KS9G36NzOeSap90UIK0yMA/NhKJhqlSGtNDORNRaIbQfzjXDrQa0ytJ6mNRGz/Q==",
            "optional": true,
            "dependencies": {
                "@types/node": "*"
            }
        },
        "node_modules/@vue/reactivity": {
            "version": "3.1.5",
            "resolved": "https://registry.npmjs.org/@vue/reactivity/-/reactivity-3.1.5.tgz",
            "integrity": "sha512-1tdfLmNjWG6t/CsPldh+foumYFo3cpyCHgBYQ34ylaMsJ+SNHQ1kApMIa8jN+i593zQuaw3AdWH0nJTARzCFhg==",
            "dependencies": {
                "@vue/shared": "3.1.5"
            }
        },
        "node_modules/@vue/shared": {
            "version": "3.1.5",
            "resolved": "https://registry.npmjs.org/@vue/shared/-/shared-3.1.5.tgz",
            "integrity": "sha512-oJ4F3TnvpXaQwZJNF3ZK+kLPHKarDmJjJ6jyzVNDKH9md1dptjC7lWR//jrGuLdek/U6iltWxqAnYOu8gCiOvA=="
        },
        "node_modules/@yr/monotone-cubic-spline": {
            "version": "1.0.3",
            "resolved": "https://registry.npmjs.org/@yr/monotone-cubic-spline/-/monotone-cubic-spline-1.0.3.tgz",
            "integrity": "sha512-FQXkOta0XBSUPHndIKON2Y9JeQz5ZeMqLYZVVK93FliNBFm7LNMIZmY6FrMEB9XPcDbE2bekMbZD6kzDkxwYjA=="
        },
        "node_modules/agent-base": {
            "version": "7.1.1",
            "resolved": "https://registry.npmjs.org/agent-base/-/agent-base-7.1.1.tgz",
            "integrity": "sha512-H0TSyFNDMomMNJQBn8wFV5YC/2eJ+VXECwOadZJT554xP6cODZHPX3H9QMQECxvrgiSOP1pHjy1sMWQVYJOUOA==",
            "dependencies": {
                "debug": "^4.3.4"
            },
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/alpinejs": {
            "version": "3.14.1",
            "resolved": "https://registry.npmjs.org/alpinejs/-/alpinejs-3.14.1.tgz",
            "integrity": "sha512-ICar8UsnRZAYvv/fCNfNeKMXNoXGUfwHrjx7LqXd08zIP95G2d9bAOuaL97re+1mgt/HojqHsfdOLo/A5LuWgQ==",
            "dependencies": {
                "@vue/reactivity": "~3.1.1"
            }
        },
        "node_modules/animate.css": {
            "version": "4.1.1",
            "resolved": "https://registry.npmjs.org/animate.css/-/animate.css-4.1.1.tgz",
            "integrity": "sha512-+mRmCTv6SbCmtYJCN4faJMNFVNN5EuCTTprDTAo7YzIGji2KADmakjVA3+8mVDkZ2Bf09vayB35lSQIex2+QaQ=="
        },
        "node_modules/ansi-regex": {
            "version": "6.0.1",
            "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-6.0.1.tgz",
            "integrity": "sha512-n5M855fKb2SsfMIiFFoVrABHJC8QtHwVx+mHWP3QcEqBHYienj5dHSgjbxtC0WEZXYt4wcD6zrQElDPhFuZgfA==",
            "dev": true,
            "engines": {
                "node": ">=12"
            },
            "funding": {
                "url": "https://github.com/chalk/ansi-regex?sponsor=1"
            }
        },
        "node_modules/ansi-styles": {
            "version": "3.2.1",
            "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-3.2.1.tgz",
            "integrity": "sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==",
            "dependencies": {
                "color-convert": "^1.9.0"
            },
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/any-promise": {
            "version": "1.3.0",
            "resolved": "https://registry.npmjs.org/any-promise/-/any-promise-1.3.0.tgz",
            "integrity": "sha512-7UvmKalWRt1wgjL1RrGxoSJW/0QZFIegpeGvZG9kjp8vrRu55XTHbwnqq2GpXm9uLbcuhxm3IqX9OB4MZR1b2A==",
            "dev": true
        },
        "node_modules/anymatch": {
            "version": "3.1.3",
            "resolved": "https://registry.npmjs.org/anymatch/-/anymatch-3.1.3.tgz",
            "integrity": "sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==",
            "dev": true,
            "dependencies": {
                "normalize-path": "^3.0.0",
                "picomatch": "^2.0.4"
            },
            "engines": {
                "node": ">= 8"
            }
        },
        "node_modules/aos": {
            "version": "2.3.4",
            "resolved": "https://registry.npmjs.org/aos/-/aos-2.3.4.tgz",
            "integrity": "sha512-zh/ahtR2yME4I51z8IttIt4lC1Nw0ktsFtmeDzID1m9naJnWXhCoARaCgNOGXb5CLy3zm+wqmRAEgMYB5E2HUw==",
            "dependencies": {
                "classlist-polyfill": "^1.0.3",
                "lodash.debounce": "^4.0.6",
                "lodash.throttle": "^4.0.1"
            }
        },
        "node_modules/apexcharts": {
            "version": "3.52.0",
            "resolved": "https://registry.npmjs.org/apexcharts/-/apexcharts-3.52.0.tgz",
            "integrity": "sha512-7dg0ADKs8AA89iYMZMe2sFDG0XK5PfqllKV9N+i3hKHm3vEtdhwz8AlXGm+/b0nJ6jKiaXsqci5LfVxNhtB+dA==",
            "dependencies": {
                "@yr/monotone-cubic-spline": "^1.0.3",
                "svg.draggable.js": "^2.2.2",
                "svg.easing.js": "^2.0.0",
                "svg.filter.js": "^2.0.2",
                "svg.pathmorphing.js": "^0.1.3",
                "svg.resize.js": "^1.4.3",
                "svg.select.js": "^3.0.1"
            }
        },
        "node_modules/arg": {
            "version": "5.0.2",
            "resolved": "https://registry.npmjs.org/arg/-/arg-5.0.2.tgz",
            "integrity": "sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg==",
            "dev": true
        },
        "node_modules/argparse": {
            "version": "2.0.1",
            "resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz",
            "integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q=="
        },
        "node_modules/ast-types": {
            "version": "0.13.4",
            "resolved": "https://registry.npmjs.org/ast-types/-/ast-types-0.13.4.tgz",
            "integrity": "sha512-x1FCFnFifvYDDzTaLII71vG5uvDwgtmDTEVWAxrgeiR8VjMONcCXJx7E+USjDtHlwFmt9MysbqgF9b9Vjr6w+w==",
            "dependencies": {
                "tslib": "^2.0.1"
            },
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/asynckit": {
            "version": "0.4.0",
            "resolved": "https://registry.npmjs.org/asynckit/-/asynckit-0.4.0.tgz",
            "integrity": "sha512-Oei9OH4tRh0YqU3GxhX79dM/mwVgvbZJaSNaRk+bshkj0S5cfHcgYakreBjrHwatXKbz+IoIdYLxrKim2MjW0Q==",
            "dev": true
        },
        "node_modules/autoprefixer": {
            "version": "10.4.20",
            "resolved": "https://registry.npmjs.org/autoprefixer/-/autoprefixer-10.4.20.tgz",
            "integrity": "sha512-XY25y5xSv/wEoqzDyXXME4AFfkZI0P23z6Fs3YgymDnKJkCGOnkL0iTxCa85UTqaSgfcqyf3UA6+c7wUvx/16g==",
            "dev": true,
            "funding": [
                {
                    "type": "opencollective",
                    "url": "https://opencollective.com/postcss/"
                },
                {
                    "type": "tidelift",
                    "url": "https://tidelift.com/funding/github/npm/autoprefixer"
                },
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/ai"
                }
            ],
            "dependencies": {
                "browserslist": "^4.23.3",
                "caniuse-lite": "^1.0.30001646",
                "fraction.js": "^4.3.7",
                "normalize-range": "^0.1.2",
                "picocolors": "^1.0.1",
                "postcss-value-parser": "^4.2.0"
            },
            "bin": {
                "autoprefixer": "bin/autoprefixer"
            },
            "engines": {
                "node": "^10 || ^12 || >=14"
            },
            "peerDependencies": {
                "postcss": "^8.1.0"
            }
        },
        "node_modules/axios": {
            "version": "1.7.5",
            "resolved": "https://registry.npmjs.org/axios/-/axios-1.7.5.tgz",
            "integrity": "sha512-fZu86yCo+svH3uqJ/yTdQ0QHpQu5oL+/QE+QPSv6BZSkDAoky9vytxp7u5qk83OJFS3kEBcesWni9WTZAv3tSw==",
            "dev": true,
            "dependencies": {
                "follow-redirects": "^1.15.6",
                "form-data": "^4.0.0",
                "proxy-from-env": "^1.1.0"
            }
        },
        "node_modules/b4a": {
            "version": "1.6.6",
            "resolved": "https://registry.npmjs.org/b4a/-/b4a-1.6.6.tgz",
            "integrity": "sha512-5Tk1HLk6b6ctmjIkAcU/Ujv/1WqiDl0F0JdRCR80VsOcUlHcu7pWeWRlOqQLHfDEsVx9YH/aif5AG4ehoCtTmg=="
        },
        "node_modules/balanced-match": {
            "version": "1.0.2",
            "resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.2.tgz",
            "integrity": "sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==",
            "dev": true
        },
        "node_modules/bare-events": {
            "version": "2.4.2",
            "resolved": "https://registry.npmjs.org/bare-events/-/bare-events-2.4.2.tgz",
            "integrity": "sha512-qMKFd2qG/36aA4GwvKq8MxnPgCQAmBWmSyLWsJcbn8v03wvIPQ/hG1Ms8bPzndZxMDoHpxez5VOS+gC9Yi24/Q==",
            "optional": true
        },
        "node_modules/bare-fs": {
            "version": "2.3.1",
            "resolved": "https://registry.npmjs.org/bare-fs/-/bare-fs-2.3.1.tgz",
            "integrity": "sha512-W/Hfxc/6VehXlsgFtbB5B4xFcsCl+pAh30cYhoFyXErf6oGrwjh8SwiPAdHgpmWonKuYpZgGywN0SXt7dgsADA==",
            "optional": true,
            "dependencies": {
                "bare-events": "^2.0.0",
                "bare-path": "^2.0.0",
                "bare-stream": "^2.0.0"
            }
        },
        "node_modules/bare-os": {
            "version": "2.4.0",
            "resolved": "https://registry.npmjs.org/bare-os/-/bare-os-2.4.0.tgz",
            "integrity": "sha512-v8DTT08AS/G0F9xrhyLtepoo9EJBJ85FRSMbu1pQUlAf6A8T0tEEQGMVObWeqpjhSPXsE0VGlluFBJu2fdoTNg==",
            "optional": true
        },
        "node_modules/bare-path": {
            "version": "2.1.3",
            "resolved": "https://registry.npmjs.org/bare-path/-/bare-path-2.1.3.tgz",
            "integrity": "sha512-lh/eITfU8hrj9Ru5quUp0Io1kJWIk1bTjzo7JH1P5dWmQ2EL4hFUlfI8FonAhSlgIfhn63p84CDY/x+PisgcXA==",
            "optional": true,
            "dependencies": {
                "bare-os": "^2.1.0"
            }
        },
        "node_modules/bare-stream": {
            "version": "2.1.3",
            "resolved": "https://registry.npmjs.org/bare-stream/-/bare-stream-2.1.3.tgz",
            "integrity": "sha512-tiDAH9H/kP+tvNO5sczyn9ZAA7utrSMobyDchsnyyXBuUe2FSQWbxhtuHB8jwpHYYevVo2UJpcmvvjrbHboUUQ==",
            "optional": true,
            "dependencies": {
                "streamx": "^2.18.0"
            }
        },
        "node_modules/base64-js": {
            "version": "1.5.1",
            "resolved": "https://registry.npmjs.org/base64-js/-/base64-js-1.5.1.tgz",
            "integrity": "sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==",
            "funding": [
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/feross"
                },
                {
                    "type": "patreon",
                    "url": "https://www.patreon.com/feross"
                },
                {
                    "type": "consulting",
                    "url": "https://feross.org/support"
                }
            ]
        },
        "node_modules/basic-ftp": {
            "version": "5.0.5",
            "resolved": "https://registry.npmjs.org/basic-ftp/-/basic-ftp-5.0.5.tgz",
            "integrity": "sha512-4Bcg1P8xhUuqcii/S0Z9wiHIrQVPMermM1any+MX5GeGD7faD3/msQUDGLol9wOcz4/jbg/WJnGqoJF6LiBdtg==",
            "engines": {
                "node": ">=10.0.0"
            }
        },
        "node_modules/binary-extensions": {
            "version": "2.3.0",
            "resolved": "https://registry.npmjs.org/binary-extensions/-/binary-extensions-2.3.0.tgz",
            "integrity": "sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==",
            "dev": true,
            "engines": {
                "node": ">=8"
            },
            "funding": {
                "url": "https://github.com/sponsors/sindresorhus"
            }
        },
        "node_modules/brace-expansion": {
            "version": "2.0.1",
            "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.1.tgz",
            "integrity": "sha512-XnAIvQ8eM+kC6aULx6wuQiwVsnzsi9d3WxzV3FpWTGA19F621kwdbsAcFKXgKUHZWsy+mY6iL1sHTxWEFCytDA==",
            "dev": true,
            "dependencies": {
                "balanced-match": "^1.0.0"
            }
        },
        "node_modules/braces": {
            "version": "3.0.3",
            "resolved": "https://registry.npmjs.org/braces/-/braces-3.0.3.tgz",
            "integrity": "sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==",
            "dev": true,
            "dependencies": {
                "fill-range": "^7.1.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/browserslist": {
            "version": "4.23.3",
            "resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.23.3.tgz",
            "integrity": "sha512-btwCFJVjI4YWDNfau8RhZ+B1Q/VLoUITrm3RlP6y1tYGWIOa+InuYiRGXUBXo8nA1qKmHMyLB/iVQg5TT4eFoA==",
            "dev": true,
            "funding": [
                {
                    "type": "opencollective",
                    "url": "https://opencollective.com/browserslist"
                },
                {
                    "type": "tidelift",
                    "url": "https://tidelift.com/funding/github/npm/browserslist"
                },
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/ai"
                }
            ],
            "dependencies": {
                "caniuse-lite": "^1.0.30001646",
                "electron-to-chromium": "^1.5.4",
                "node-releases": "^2.0.18",
                "update-browserslist-db": "^1.1.0"
            },
            "bin": {
                "browserslist": "cli.js"
            },
            "engines": {
                "node": "^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7"
            }
        },
        "node_modules/buffer": {
            "version": "5.7.1",
            "resolved": "https://registry.npmjs.org/buffer/-/buffer-5.7.1.tgz",
            "integrity": "sha512-EHcyIPBQ4BSGlvjB16k5KgAJ27CIsHY/2JBmCRReo48y9rQ3MaUzWX3KVlBa4U7MyX02HdVj0K7C3WaB3ju7FQ==",
            "funding": [
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/feross"
                },
                {
                    "type": "patreon",
                    "url": "https://www.patreon.com/feross"
                },
                {
                    "type": "consulting",
                    "url": "https://feross.org/support"
                }
            ],
            "dependencies": {
                "base64-js": "^1.3.1",
                "ieee754": "^1.1.13"
            }
        },
        "node_modules/buffer-crc32": {
            "version": "0.2.13",
            "resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.13.tgz",
            "integrity": "sha512-VO9Ht/+p3SN7SKWqcrgEzjGbRSJYTx+Q1pTQC0wrWqHx0vpJraQ6GtHx8tvcg1rlK1byhU5gccxgOgj7B0TDkQ==",
            "engines": {
                "node": "*"
            }
        },
        "node_modules/callsites": {
            "version": "3.1.0",
            "resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz",
            "integrity": "sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==",
            "engines": {
                "node": ">=6"
            }
        },
        "node_modules/camelcase-css": {
            "version": "2.0.1",
            "resolved": "https://registry.npmjs.org/camelcase-css/-/camelcase-css-2.0.1.tgz",
            "integrity": "sha512-QOSvevhslijgYwRx6Rv7zKdMF8lbRmx+uQGx2+vDc+KI/eBnsy9kit5aj23AgGu3pa4t9AgwbnXWqS+iOY+2aA==",
            "dev": true,
            "engines": {
                "node": ">= 6"
            }
        },
        "node_modules/caniuse-lite": {
            "version": "1.0.30001653",
            "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001653.tgz",
            "integrity": "sha512-XGWQVB8wFQ2+9NZwZ10GxTYC5hk0Fa+q8cSkr0tgvMhYhMHP/QC+WTgrePMDBWiWc/pV+1ik82Al20XOK25Gcw==",
            "dev": true,
            "funding": [
                {
                    "type": "opencollective",
                    "url": "https://opencollective.com/browserslist"
                },
                {
                    "type": "tidelift",
                    "url": "https://tidelift.com/funding/github/npm/caniuse-lite"
                },
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/ai"
                }
            ]
        },
        "node_modules/chalk": {
            "version": "2.4.2",
            "resolved": "https://registry.npmjs.org/chalk/-/chalk-2.4.2.tgz",
            "integrity": "sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==",
            "dependencies": {
                "ansi-styles": "^3.2.1",
                "escape-string-regexp": "^1.0.5",
                "supports-color": "^5.3.0"
            },
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/chokidar": {
            "version": "3.6.0",
            "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-3.6.0.tgz",
            "integrity": "sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==",
            "dev": true,
            "dependencies": {
                "anymatch": "~3.1.2",
                "braces": "~3.0.2",
                "glob-parent": "~5.1.2",
                "is-binary-path": "~2.1.0",
                "is-glob": "~4.0.1",
                "normalize-path": "~3.0.0",
                "readdirp": "~3.6.0"
            },
            "engines": {
                "node": ">= 8.10.0"
            },
            "funding": {
                "url": "https://paulmillr.com/funding/"
            },
            "optionalDependencies": {
                "fsevents": "~2.3.2"
            }
        },
        "node_modules/chokidar/node_modules/glob-parent": {
            "version": "5.1.2",
            "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
            "integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==",
            "dev": true,
            "dependencies": {
                "is-glob": "^4.0.1"
            },
            "engines": {
                "node": ">= 6"
            }
        },
        "node_modules/chromium-bidi": {
            "version": "0.6.3",
            "resolved": "https://registry.npmjs.org/chromium-bidi/-/chromium-bidi-0.6.3.tgz",
            "integrity": "sha512-qXlsCmpCZJAnoTYI83Iu6EdYQpMYdVkCfq08KDh2pmlVqK5t5IA9mGs4/LwCwp4fqisSOMXZxP3HIh8w8aRn0A==",
            "dependencies": {
                "mitt": "3.0.1",
                "urlpattern-polyfill": "10.0.0",
                "zod": "3.23.8"
            },
            "peerDependencies": {
                "devtools-protocol": "*"
            }
        },
        "node_modules/classlist-polyfill": {
            "version": "1.2.0",
            "resolved": "https://registry.npmjs.org/classlist-polyfill/-/classlist-polyfill-1.2.0.tgz",
            "integrity": "sha512-GzIjNdcEtH4ieA2S8NmrSxv7DfEV5fmixQeyTmqmRmRJPGpRBaSnA2a0VrCjyT8iW8JjEdMbKzDotAJf+ajgaQ=="
        },
        "node_modules/clipboard": {
            "version": "2.0.11",
            "resolved": "https://registry.npmjs.org/clipboard/-/clipboard-2.0.11.tgz",
            "integrity": "sha512-C+0bbOqkezLIsmWSvlsXS0Q0bmkugu7jcfMIACB+RDEntIzQIkdr148we28AfSloQLRdZlYL/QYyrq05j/3Faw==",
            "dependencies": {
                "good-listener": "^1.2.2",
                "select": "^1.1.2",
                "tiny-emitter": "^2.0.0"
            }
        },
        "node_modules/cliui": {
            "version": "8.0.1",
            "resolved": "https://registry.npmjs.org/cliui/-/cliui-8.0.1.tgz",
            "integrity": "sha512-BSeNnyus75C4//NQ9gQt1/csTXyo/8Sb+afLAkzAptFuMsod9HFokGNudZpi/oQV73hnVK+sR+5PVRMd+Dr7YQ==",
            "dependencies": {
                "string-width": "^4.2.0",
                "strip-ansi": "^6.0.1",
                "wrap-ansi": "^7.0.0"
            },
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/cliui/node_modules/ansi-regex": {
            "version": "5.0.1",
            "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
            "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/cliui/node_modules/ansi-styles": {
            "version": "4.3.0",
            "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
            "integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
            "dependencies": {
                "color-convert": "^2.0.1"
            },
            "engines": {
                "node": ">=8"
            },
            "funding": {
                "url": "https://github.com/chalk/ansi-styles?sponsor=1"
            }
        },
        "node_modules/cliui/node_modules/color-convert": {
            "version": "2.0.1",
            "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
            "integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
            "dependencies": {
                "color-name": "~1.1.4"
            },
            "engines": {
                "node": ">=7.0.0"
            }
        },
        "node_modules/cliui/node_modules/color-name": {
            "version": "1.1.4",
            "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz",
            "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA=="
        },
        "node_modules/cliui/node_modules/emoji-regex": {
            "version": "8.0.0",
            "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz",
            "integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A=="
        },
        "node_modules/cliui/node_modules/string-width": {
            "version": "4.2.3",
            "resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
            "integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
            "dependencies": {
                "emoji-regex": "^8.0.0",
                "is-fullwidth-code-point": "^3.0.0",
                "strip-ansi": "^6.0.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/cliui/node_modules/strip-ansi": {
            "version": "6.0.1",
            "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
            "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
            "dependencies": {
                "ansi-regex": "^5.0.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/cliui/node_modules/wrap-ansi": {
            "version": "7.0.0",
            "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz",
            "integrity": "sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==",
            "dependencies": {
                "ansi-styles": "^4.0.0",
                "string-width": "^4.1.0",
                "strip-ansi": "^6.0.0"
            },
            "engines": {
                "node": ">=10"
            },
            "funding": {
                "url": "https://github.com/chalk/wrap-ansi?sponsor=1"
            }
        },
        "node_modules/color-convert": {
            "version": "1.9.3",
            "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-1.9.3.tgz",
            "integrity": "sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==",
            "dependencies": {
                "color-name": "1.1.3"
            }
        },
        "node_modules/color-name": {
            "version": "1.1.3",
            "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.3.tgz",
            "integrity": "sha512-72fSenhMw2HZMTVHeCA9KCmpEIbzWiQsjN+BHcBbS9vr1mtt+vJjPdksIBNUmKAW8TFUDPJK5SUU3QhE9NEXDw=="
        },
        "node_modules/combined-stream": {
            "version": "1.0.8",
            "resolved": "https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.8.tgz",
            "integrity": "sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==",
            "dev": true,
            "dependencies": {
                "delayed-stream": "~1.0.0"
            },
            "engines": {
                "node": ">= 0.8"
            }
        },
        "node_modules/commander": {
            "version": "4.1.1",
            "resolved": "https://registry.npmjs.org/commander/-/commander-4.1.1.tgz",
            "integrity": "sha512-NOKm8xhkzAjzFx8B2v5OAHT+u5pRQc2UCa2Vq9jYL/31o2wi9mxBA7LIFs3sV5VSC49z6pEhfbMULvShKj26WA==",
            "dev": true,
            "engines": {
                "node": ">= 6"
            }
        },
        "node_modules/cosmiconfig": {
            "version": "9.0.0",
            "resolved": "https://registry.npmjs.org/cosmiconfig/-/cosmiconfig-9.0.0.tgz",
            "integrity": "sha512-itvL5h8RETACmOTFc4UfIyB2RfEHi71Ax6E/PivVxq9NseKbOWpeyHEOIbmAw1rs8Ak0VursQNww7lf7YtUwzg==",
            "dependencies": {
                "env-paths": "^2.2.1",
                "import-fresh": "^3.3.0",
                "js-yaml": "^4.1.0",
                "parse-json": "^5.2.0"
            },
            "engines": {
                "node": ">=14"
            },
            "funding": {
                "url": "https://github.com/sponsors/d-fischer"
            },
            "peerDependencies": {
                "typescript": ">=4.9.5"
            },
            "peerDependenciesMeta": {
                "typescript": {
                    "optional": true
                }
            }
        },
        "node_modules/create-vite": {
            "version": "4.4.1",
            "resolved": "https://registry.npmjs.org/create-vite/-/create-vite-4.4.1.tgz",
            "integrity": "sha512-VbE5lc4aO7gterlwTDPxfnEhp/e0xAJui7NydmQiLpKq2yBLTQGcfMXeZeyoIH+E/Di2MQpE4o0K3lZNjlFL+A==",
            "dev": true,
            "bin": {
                "create-vite": "index.js",
                "cva": "index.js"
            },
            "engines": {
                "node": "^14.18.0 || >=16.0.0"
            },
            "funding": {
                "url": "https://github.com/vitejs/vite?sponsor=1"
            }
        },
        "node_modules/crisp-sdk-web": {
            "version": "1.0.25",
            "resolved": "https://registry.npmjs.org/crisp-sdk-web/-/crisp-sdk-web-1.0.25.tgz",
            "integrity": "sha512-CWTHFFeHRV0oqiXoPh/aIAKhFs6xcIM4NenGPnClAMCZUDQgQsF1OWmZWmnVNjJriXUmWRgDfeUxcxygS0dCRA=="
        },
        "node_modules/cross-spawn": {
            "version": "7.0.3",
            "resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz",
            "integrity": "sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==",
            "dev": true,
            "dependencies": {
                "path-key": "^3.1.0",
                "shebang-command": "^2.0.0",
                "which": "^2.0.1"
            },
            "engines": {
                "node": ">= 8"
            }
        },
        "node_modules/css-selector-tokenizer": {
            "version": "0.8.0",
            "resolved": "https://registry.npmjs.org/css-selector-tokenizer/-/css-selector-tokenizer-0.8.0.tgz",
            "integrity": "sha512-Jd6Ig3/pe62/qe5SBPTN8h8LeUg/pT4lLgtavPf7updwwHpvFzxvOQBHYj2LZDMjUnBzgvIUSjRcf6oT5HzHFg==",
            "dev": true,
            "dependencies": {
                "cssesc": "^3.0.0",
                "fastparse": "^1.1.2"
            }
        },
        "node_modules/cssesc": {
            "version": "3.0.0",
            "resolved": "https://registry.npmjs.org/cssesc/-/cssesc-3.0.0.tgz",
            "integrity": "sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==",
            "dev": true,
            "bin": {
                "cssesc": "bin/cssesc"
            },
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/culori": {
            "version": "3.3.0",
            "resolved": "https://registry.npmjs.org/culori/-/culori-3.3.0.tgz",
            "integrity": "sha512-pHJg+jbuFsCjz9iclQBqyL3B2HLCBF71BwVNujUYEvCeQMvV97R59MNK3R2+jgJ3a1fcZgI9B3vYgz8lzr/BFQ==",
            "dev": true,
            "engines": {
                "node": "^12.20.0 || ^14.13.1 || >=16.0.0"
            }
        },
        "node_modules/daisyui": {
            "version": "4.12.10",
            "resolved": "https://registry.npmjs.org/daisyui/-/daisyui-4.12.10.tgz",
            "integrity": "sha512-jp1RAuzbHhGdXmn957Z2XsTZStXGHzFfF0FgIOZj3Wv9sH7OZgLfXTRZNfKVYxltGUOBsG1kbWAdF5SrqjebvA==",
            "dev": true,
            "dependencies": {
                "css-selector-tokenizer": "^0.8",
                "culori": "^3",
                "picocolors": "^1",
                "postcss-js": "^4"
            },
            "engines": {
                "node": ">=16.9.0"
            },
            "funding": {
                "type": "opencollective",
                "url": "https://opencollective.com/daisyui"
            }
        },
        "node_modules/data-uri-to-buffer": {
            "version": "6.0.2",
            "resolved": "https://registry.npmjs.org/data-uri-to-buffer/-/data-uri-to-buffer-6.0.2.tgz",
            "integrity": "sha512-7hvf7/GW8e86rW0ptuwS3OcBGDjIi6SZva7hCyWC0yYry2cOPmLIjXAUHI6DK2HsnwJd9ifmt57i8eV2n4YNpw==",
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/debug": {
            "version": "4.3.6",
            "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.6.tgz",
            "integrity": "sha512-O/09Bd4Z1fBrU4VzkhFqVgpPzaGbw6Sm9FEkBT1A/YBXQFGuuSxa1dN2nxgxS34JmKXqYx8CZAwEVoJFImUXIg==",
            "dependencies": {
                "ms": "2.1.2"
            },
            "engines": {
                "node": ">=6.0"
            },
            "peerDependenciesMeta": {
                "supports-color": {
                    "optional": true
                }
            }
        },
        "node_modules/degenerator": {
            "version": "5.0.1",
            "resolved": "https://registry.npmjs.org/degenerator/-/degenerator-5.0.1.tgz",
            "integrity": "sha512-TllpMR/t0M5sqCXfj85i4XaAzxmS5tVA16dqvdkMwGmzI+dXLXnw3J+3Vdv7VKw+ThlTMboK6i9rnZ6Nntj5CQ==",
            "dependencies": {
                "ast-types": "^0.13.4",
                "escodegen": "^2.1.0",
                "esprima": "^4.0.1"
            },
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/delayed-stream": {
            "version": "1.0.0",
            "resolved": "https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz",
            "integrity": "sha512-ZySD7Nf91aLB0RxL4KGrKHBXl7Eds1DAmEdcoVawXnLD7SDhpNgtuII2aAkg7a7QS41jxPSZ17p4VdGnMHk3MQ==",
            "dev": true,
            "engines": {
                "node": ">=0.4.0"
            }
        },
        "node_modules/delegate": {
            "version": "3.2.0",
            "resolved": "https://registry.npmjs.org/delegate/-/delegate-3.2.0.tgz",
            "integrity": "sha512-IofjkYBZaZivn0V8nnsMJGBr4jVLxHDheKSW88PyxS5QC4Vo9ZbZVvhzlSxY87fVq3STR6r+4cGepyHkcWOQSw=="
        },
        "node_modules/devtools-protocol": {
            "version": "0.0.1312386",
            "resolved": "https://registry.npmjs.org/devtools-protocol/-/devtools-protocol-0.0.1312386.tgz",
            "integrity": "sha512-DPnhUXvmvKT2dFA/j7B+riVLUt9Q6RKJlcppojL5CoRywJJKLDYnRlw0gTFKfgDPHP5E04UoB71SxoJlVZy8FA=="
        },
        "node_modules/didyoumean": {
            "version": "1.2.2",
            "resolved": "https://registry.npmjs.org/didyoumean/-/didyoumean-1.2.2.tgz",
            "integrity": "sha512-gxtyfqMg7GKyhQmb056K7M3xszy/myH8w+B4RT+QXBQsvAOdc3XymqDDPHx1BgPgsdAA5SIifona89YtRATDzw==",
            "dev": true
        },
        "node_modules/dlv": {
            "version": "1.1.3",
            "resolved": "https://registry.npmjs.org/dlv/-/dlv-1.1.3.tgz",
            "integrity": "sha512-+HlytyjlPKnIG8XuRG8WvmBP8xs8P71y+SKKS6ZXWoEgLuePxtDoUEiH7WkdePWrQ5JBpE6aoVqfZfJUQkjXwA==",
            "dev": true
        },
        "node_modules/eastasianwidth": {
            "version": "0.2.0",
            "resolved": "https://registry.npmjs.org/eastasianwidth/-/eastasianwidth-0.2.0.tgz",
            "integrity": "sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA==",
            "dev": true
        },
        "node_modules/electron-to-chromium": {
            "version": "1.5.13",
            "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.13.tgz",
            "integrity": "sha512-lbBcvtIJ4J6sS4tb5TLp1b4LyfCdMkwStzXPyAgVgTRAsep4bvrAGaBOP7ZJtQMNJpSQ9SqG4brWOroNaQtm7Q==",
            "dev": true
        },
        "node_modules/emoji-regex": {
            "version": "9.2.2",
            "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-9.2.2.tgz",
            "integrity": "sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg==",
            "dev": true
        },
        "node_modules/end-of-stream": {
            "version": "1.4.4",
            "resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.4.4.tgz",
            "integrity": "sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q==",
            "dependencies": {
                "once": "^1.4.0"
            }
        },
        "node_modules/env-paths": {
            "version": "2.2.1",
            "resolved": "https://registry.npmjs.org/env-paths/-/env-paths-2.2.1.tgz",
            "integrity": "sha512-+h1lkLKhZMTYjog1VEpJNG7NZJWcuc2DDk/qsqSTRRCOXiLjeQ1d1/udrUGhqMxUgAlwKNZ0cf2uqan5GLuS2A==",
            "engines": {
                "node": ">=6"
            }
        },
        "node_modules/error-ex": {
            "version": "1.3.2",
            "resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.2.tgz",
            "integrity": "sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==",
            "dependencies": {
                "is-arrayish": "^0.2.1"
            }
        },
        "node_modules/esbuild": {
            "version": "0.18.20",
            "resolved": "https://registry.npmjs.org/esbuild/-/esbuild-0.18.20.tgz",
            "integrity": "sha512-ceqxoedUrcayh7Y7ZX6NdbbDzGROiyVBgC4PriJThBKSVPWnnFHZAkfI1lJT8QFkOwH4qOS2SJkS4wvpGl8BpA==",
            "dev": true,
            "hasInstallScript": true,
            "bin": {
                "esbuild": "bin/esbuild"
            },
            "engines": {
                "node": ">=12"
            },
            "optionalDependencies": {
                "@esbuild/android-arm": "0.18.20",
                "@esbuild/android-arm64": "0.18.20",
                "@esbuild/android-x64": "0.18.20",
                "@esbuild/darwin-arm64": "0.18.20",
                "@esbuild/darwin-x64": "0.18.20",
                "@esbuild/freebsd-arm64": "0.18.20",
                "@esbuild/freebsd-x64": "0.18.20",
                "@esbuild/linux-arm": "0.18.20",
                "@esbuild/linux-arm64": "0.18.20",
                "@esbuild/linux-ia32": "0.18.20",
                "@esbuild/linux-loong64": "0.18.20",
                "@esbuild/linux-mips64el": "0.18.20",
                "@esbuild/linux-ppc64": "0.18.20",
                "@esbuild/linux-riscv64": "0.18.20",
                "@esbuild/linux-s390x": "0.18.20",
                "@esbuild/linux-x64": "0.18.20",
                "@esbuild/netbsd-x64": "0.18.20",
                "@esbuild/openbsd-x64": "0.18.20",
                "@esbuild/sunos-x64": "0.18.20",
                "@esbuild/win32-arm64": "0.18.20",
                "@esbuild/win32-ia32": "0.18.20",
                "@esbuild/win32-x64": "0.18.20"
            }
        },
        "node_modules/escalade": {
            "version": "3.1.2",
            "resolved": "https://registry.npmjs.org/escalade/-/escalade-3.1.2.tgz",
            "integrity": "sha512-ErCHMCae19vR8vQGe50xIsVomy19rg6gFu3+r3jkEO46suLMWBksvVyoGgQV+jOfl84ZSOSlmv6Gxa89PmTGmA==",
            "engines": {
                "node": ">=6"
            }
        },
        "node_modules/escape-string-regexp": {
            "version": "1.0.5",
            "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz",
            "integrity": "sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==",
            "engines": {
                "node": ">=0.8.0"
            }
        },
        "node_modules/escodegen": {
            "version": "2.1.0",
            "resolved": "https://registry.npmjs.org/escodegen/-/escodegen-2.1.0.tgz",
            "integrity": "sha512-2NlIDTwUWJN0mRPQOdtQBzbUHvdGY2P1VXSyU83Q3xKxM7WHX2Ql8dKq782Q9TgQUNOLEzEYu9bzLNj1q88I5w==",
            "dependencies": {
                "esprima": "^4.0.1",
                "estraverse": "^5.2.0",
                "esutils": "^2.0.2"
            },
            "bin": {
                "escodegen": "bin/escodegen.js",
                "esgenerate": "bin/esgenerate.js"
            },
            "engines": {
                "node": ">=6.0"
            },
            "optionalDependencies": {
                "source-map": "~0.6.1"
            }
        },
        "node_modules/esprima": {
            "version": "4.0.1",
            "resolved": "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz",
            "integrity": "sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==",
            "bin": {
                "esparse": "bin/esparse.js",
                "esvalidate": "bin/esvalidate.js"
            },
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/estraverse": {
            "version": "5.3.0",
            "resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
            "integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
            "engines": {
                "node": ">=4.0"
            }
        },
        "node_modules/esutils": {
            "version": "2.0.3",
            "resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz",
            "integrity": "sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==",
            "engines": {
                "node": ">=0.10.0"
            }
        },
        "node_modules/extract-zip": {
            "version": "2.0.1",
            "resolved": "https://registry.npmjs.org/extract-zip/-/extract-zip-2.0.1.tgz",
            "integrity": "sha512-GDhU9ntwuKyGXdZBUgTIe+vXnWj0fppUEtMDL0+idd5Sta8TGpHssn/eusA9mrPr9qNDym6SxAYZjNvCn/9RBg==",
            "dependencies": {
                "debug": "^4.1.1",
                "get-stream": "^5.1.0",
                "yauzl": "^2.10.0"
            },
            "bin": {
                "extract-zip": "cli.js"
            },
            "engines": {
                "node": ">= 10.17.0"
            },
            "optionalDependencies": {
                "@types/yauzl": "^2.9.1"
            }
        },
        "node_modules/fast-fifo": {
            "version": "1.3.2",
            "resolved": "https://registry.npmjs.org/fast-fifo/-/fast-fifo-1.3.2.tgz",
            "integrity": "sha512-/d9sfos4yxzpwkDkuN7k2SqFKtYNmCTzgfEpz82x34IM9/zc8KGxQoXg1liNC/izpRM/MBdt44Nmx41ZWqk+FQ=="
        },
        "node_modules/fast-glob": {
            "version": "3.3.2",
            "resolved": "https://registry.npmjs.org/fast-glob/-/fast-glob-3.3.2.tgz",
            "integrity": "sha512-oX2ruAFQwf/Orj8m737Y5adxDQO0LAB7/S5MnxCdTNDd4p6BsyIVsv9JQsATbTSq8KHRpLwIHbVlUNatxd+1Ow==",
            "dev": true,
            "dependencies": {
                "@nodelib/fs.stat": "^2.0.2",
                "@nodelib/fs.walk": "^1.2.3",
                "glob-parent": "^5.1.2",
                "merge2": "^1.3.0",
                "micromatch": "^4.0.4"
            },
            "engines": {
                "node": ">=8.6.0"
            }
        },
        "node_modules/fast-glob/node_modules/glob-parent": {
            "version": "5.1.2",
            "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
            "integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==",
            "dev": true,
            "dependencies": {
                "is-glob": "^4.0.1"
            },
            "engines": {
                "node": ">= 6"
            }
        },
        "node_modules/fastparse": {
            "version": "1.1.2",
            "resolved": "https://registry.npmjs.org/fastparse/-/fastparse-1.1.2.tgz",
            "integrity": "sha512-483XLLxTVIwWK3QTrMGRqUfUpoOs/0hbQrl2oz4J0pAcm3A3bu84wxTFqGqkJzewCLdME38xJLJAxBABfQT8sQ==",
            "dev": true
        },
        "node_modules/fastq": {
            "version": "1.17.1",
            "resolved": "https://registry.npmjs.org/fastq/-/fastq-1.17.1.tgz",
            "integrity": "sha512-sRVD3lWVIXWg6By68ZN7vho9a1pQcN/WBFaAAsDDFzlJjvoGx0P8z7V1t72grFJfJhu3YPZBuu25f7Kaw2jN1w==",
            "dev": true,
            "dependencies": {
                "reusify": "^1.0.4"
            }
        },
        "node_modules/fd-slicer": {
            "version": "1.1.0",
            "resolved": "https://registry.npmjs.org/fd-slicer/-/fd-slicer-1.1.0.tgz",
            "integrity": "sha512-cE1qsB/VwyQozZ+q1dGxR8LBYNZeofhEdUNGSMbQD3Gw2lAzX9Zb3uIU6Ebc/Fmyjo9AWWfnn0AUCHqtevs/8g==",
            "dependencies": {
                "pend": "~1.2.0"
            }
        },
        "node_modules/fill-range": {
            "version": "7.1.1",
            "resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.1.1.tgz",
            "integrity": "sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==",
            "dev": true,
            "dependencies": {
                "to-regex-range": "^5.0.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/flowbite": {
            "version": "1.8.1",
            "resolved": "https://registry.npmjs.org/flowbite/-/flowbite-1.8.1.tgz",
            "integrity": "sha512-lXTcO8a6dRTPFpINyOLcATCN/pK1Of/jY4PryklPllAiqH64tSDUsOdQpar3TO59ZXWwugm2e92oaqwH6X90Xg==",
            "dependencies": {
                "@popperjs/core": "^2.9.3",
                "mini-svg-data-uri": "^1.4.3"
            }
        },
        "node_modules/flowbite-typography": {
            "version": "1.0.3",
            "resolved": "https://registry.npmjs.org/flowbite-typography/-/flowbite-typography-1.0.3.tgz",
            "integrity": "sha512-UbdQFIIOb7xx2TS+QQrqr79B6ZSkSZurxYWzV0npth6Wns3/j7KfeDJoH9QFU+Zs7zjrvejNtyzgzWLWyCrdiA==",
            "dev": true,
            "dependencies": {
                "lodash.castarray": "^4.4.0",
                "lodash.isplainobject": "^4.0.6",
                "lodash.merge": "^4.6.2"
            },
            "peerDependencies": {
                "tailwindcss": ">=3.0.0 || insiders"
            }
        },
        "node_modules/focus-trap": {
            "version": "6.9.4",
            "resolved": "https://registry.npmjs.org/focus-trap/-/focus-trap-6.9.4.tgz",
            "integrity": "sha512-v2NTsZe2FF59Y+sDykKY+XjqZ0cPfhq/hikWVL88BqLivnNiEffAsac6rP6H45ff9wG9LL5ToiDqrLEP9GX9mw==",
            "dependencies": {
                "tabbable": "^5.3.3"
            }
        },
        "node_modules/follow-redirects": {
            "version": "1.15.6",
            "resolved": "https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.15.6.tgz",
            "integrity": "sha512-wWN62YITEaOpSK584EZXJafH1AGpO8RVgElfkuXbTOrPX4fIfOyEpW/CsiNd8JdYrAoOvafRTOEnvsO++qCqFA==",
            "dev": true,
            "funding": [
                {
                    "type": "individual",
                    "url": "https://github.com/sponsors/RubenVerborgh"
                }
            ],
            "engines": {
                "node": ">=4.0"
            },
            "peerDependenciesMeta": {
                "debug": {
                    "optional": true
                }
            }
        },
        "node_modules/foreground-child": {
            "version": "3.3.0",
            "resolved": "https://registry.npmjs.org/foreground-child/-/foreground-child-3.3.0.tgz",
            "integrity": "sha512-Ld2g8rrAyMYFXBhEqMz8ZAHBi4J4uS1i/CxGMDnjyFWddMXLVcDp051DZfu+t7+ab7Wv6SMqpWmyFIj5UbfFvg==",
            "dev": true,
            "dependencies": {
                "cross-spawn": "^7.0.0",
                "signal-exit": "^4.0.1"
            },
            "engines": {
                "node": ">=14"
            },
            "funding": {
                "url": "https://github.com/sponsors/isaacs"
            }
        },
        "node_modules/form-data": {
            "version": "4.0.0",
            "resolved": "https://registry.npmjs.org/form-data/-/form-data-4.0.0.tgz",
            "integrity": "sha512-ETEklSGi5t0QMZuiXoA/Q6vcnxcLQP5vdugSpuAyi6SVGi2clPPp+xgEhuMaHC+zGgn31Kd235W35f7Hykkaww==",
            "dev": true,
            "dependencies": {
                "asynckit": "^0.4.0",
                "combined-stream": "^1.0.8",
                "mime-types": "^2.1.12"
            },
            "engines": {
                "node": ">= 6"
            }
        },
        "node_modules/fraction.js": {
            "version": "4.3.7",
            "resolved": "https://registry.npmjs.org/fraction.js/-/fraction.js-4.3.7.tgz",
            "integrity": "sha512-ZsDfxO51wGAXREY55a7la9LScWpwv9RxIrYABrlvOFBlH/ShPnrtsXeuUIfXKKOVicNxQ+o8JTbJvjS4M89yew==",
            "dev": true,
            "engines": {
                "node": "*"
            },
            "funding": {
                "type": "patreon",
                "url": "https://github.com/sponsors/rawify"
            }
        },
        "node_modules/fs-extra": {
            "version": "11.2.0",
            "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-11.2.0.tgz",
            "integrity": "sha512-PmDi3uwK5nFuXh7XDTlVnS17xJS7vW36is2+w3xcv8SVxiB4NyATf4ctkVY5bkSjX0Y4nbvZCq1/EjtEyr9ktw==",
            "dependencies": {
                "graceful-fs": "^4.2.0",
                "jsonfile": "^6.0.1",
                "universalify": "^2.0.0"
            },
            "engines": {
                "node": ">=14.14"
            }
        },
        "node_modules/fsevents": {
            "version": "2.3.3",
            "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.3.tgz",
            "integrity": "sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==",
            "dev": true,
            "hasInstallScript": true,
            "optional": true,
            "os": [
                "darwin"
            ],
            "engines": {
                "node": "^8.16.0 || ^10.6.0 || >=11.0.0"
            }
        },
        "node_modules/function-bind": {
            "version": "1.1.2",
            "resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.2.tgz",
            "integrity": "sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==",
            "dev": true,
            "funding": {
                "url": "https://github.com/sponsors/ljharb"
            }
        },
        "node_modules/get-caller-file": {
            "version": "2.0.5",
            "resolved": "https://registry.npmjs.org/get-caller-file/-/get-caller-file-2.0.5.tgz",
            "integrity": "sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==",
            "engines": {
                "node": "6.* || 8.* || >= 10.*"
            }
        },
        "node_modules/get-stream": {
            "version": "5.2.0",
            "resolved": "https://registry.npmjs.org/get-stream/-/get-stream-5.2.0.tgz",
            "integrity": "sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA==",
            "dependencies": {
                "pump": "^3.0.0"
            },
            "engines": {
                "node": ">=8"
            },
            "funding": {
                "url": "https://github.com/sponsors/sindresorhus"
            }
        },
        "node_modules/get-uri": {
            "version": "6.0.3",
            "resolved": "https://registry.npmjs.org/get-uri/-/get-uri-6.0.3.tgz",
            "integrity": "sha512-BzUrJBS9EcUb4cFol8r4W3v1cPsSyajLSthNkz5BxbpDcHN5tIrM10E2eNvfnvBn3DaT3DUgx0OpsBKkaOpanw==",
            "dependencies": {
                "basic-ftp": "^5.0.2",
                "data-uri-to-buffer": "^6.0.2",
                "debug": "^4.3.4",
                "fs-extra": "^11.2.0"
            },
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/glob": {
            "version": "10.4.5",
            "resolved": "https://registry.npmjs.org/glob/-/glob-10.4.5.tgz",
            "integrity": "sha512-7Bv8RF0k6xjo7d4A/PxYLbUCfb6c+Vpd2/mB2yRDlew7Jb5hEXiCD9ibfO7wpk8i4sevK6DFny9h7EYbM3/sHg==",
            "dev": true,
            "dependencies": {
                "foreground-child": "^3.1.0",
                "jackspeak": "^3.1.2",
                "minimatch": "^9.0.4",
                "minipass": "^7.1.2",
                "package-json-from-dist": "^1.0.0",
                "path-scurry": "^1.11.1"
            },
            "bin": {
                "glob": "dist/esm/bin.mjs"
            },
            "funding": {
                "url": "https://github.com/sponsors/isaacs"
            }
        },
        "node_modules/glob-parent": {
            "version": "6.0.2",
            "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-6.0.2.tgz",
            "integrity": "sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==",
            "dev": true,
            "dependencies": {
                "is-glob": "^4.0.3"
            },
            "engines": {
                "node": ">=10.13.0"
            }
        },
        "node_modules/good-listener": {
            "version": "1.2.2",
            "resolved": "https://registry.npmjs.org/good-listener/-/good-listener-1.2.2.tgz",
            "integrity": "sha512-goW1b+d9q/HIwbVYZzZ6SsTr4IgE+WA44A0GmPIQstuOrgsFcT7VEJ48nmr9GaRtNu0XTKacFLGnBPAM6Afouw==",
            "dependencies": {
                "delegate": "^3.1.2"
            }
        },
        "node_modules/graceful-fs": {
            "version": "4.2.11",
            "resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.11.tgz",
            "integrity": "sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ=="
        },
        "node_modules/has-flag": {
            "version": "3.0.0",
            "resolved": "https://registry.npmjs.org/has-flag/-/has-flag-3.0.0.tgz",
            "integrity": "sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw==",
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/hasown": {
            "version": "2.0.2",
            "resolved": "https://registry.npmjs.org/hasown/-/hasown-2.0.2.tgz",
            "integrity": "sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ==",
            "dev": true,
            "dependencies": {
                "function-bind": "^1.1.2"
            },
            "engines": {
                "node": ">= 0.4"
            }
        },
        "node_modules/http-proxy-agent": {
            "version": "7.0.2",
            "resolved": "https://registry.npmjs.org/http-proxy-agent/-/http-proxy-agent-7.0.2.tgz",
            "integrity": "sha512-T1gkAiYYDWYx3V5Bmyu7HcfcvL7mUrTWiM6yOfa3PIphViJ/gFPbvidQ+veqSOHci/PxBcDabeUNCzpOODJZig==",
            "dependencies": {
                "agent-base": "^7.1.0",
                "debug": "^4.3.4"
            },
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/https-proxy-agent": {
            "version": "7.0.5",
            "resolved": "https://registry.npmjs.org/https-proxy-agent/-/https-proxy-agent-7.0.5.tgz",
            "integrity": "sha512-1e4Wqeblerz+tMKPIq2EMGiiWW1dIjZOksyHWSUm1rmuvw/how9hBHZ38lAGj5ID4Ik6EdkOw7NmWPy6LAwalw==",
            "dependencies": {
                "agent-base": "^7.0.2",
                "debug": "4"
            },
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/ieee754": {
            "version": "1.2.1",
            "resolved": "https://registry.npmjs.org/ieee754/-/ieee754-1.2.1.tgz",
            "integrity": "sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==",
            "funding": [
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/feross"
                },
                {
                    "type": "patreon",
                    "url": "https://www.patreon.com/feross"
                },
                {
                    "type": "consulting",
                    "url": "https://feross.org/support"
                }
            ]
        },
        "node_modules/import-fresh": {
            "version": "3.3.0",
            "resolved": "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.0.tgz",
            "integrity": "sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==",
            "dependencies": {
                "parent-module": "^1.0.0",
                "resolve-from": "^4.0.0"
            },
            "engines": {
                "node": ">=6"
            },
            "funding": {
                "url": "https://github.com/sponsors/sindresorhus"
            }
        },
        "node_modules/intl-tel-input": {
            "version": "18.5.3",
            "resolved": "https://registry.npmjs.org/intl-tel-input/-/intl-tel-input-18.5.3.tgz",
            "integrity": "sha512-ncFqSpkdGf2YC/FvAiwBH44KAeRG8L7aqDODEpOvMAT3ZpBtvc/WtwaQ/6X4+HKDTlGkobdBjr6P3nAMwO8jtA=="
        },
        "node_modules/ion-rangeslider": {
            "version": "2.3.1",
            "resolved": "https://registry.npmjs.org/ion-rangeslider/-/ion-rangeslider-2.3.1.tgz",
            "integrity": "sha512-6V+24FD13/feliI485gnRHZYD9Ev64M5NAFTxnVib516ATHa9PlXQrC+nOiPngouRYTCLPJyokAJEi3e1Umi5g==",
            "peerDependencies": {
                "jquery": ">=1.8"
            }
        },
        "node_modules/ip-address": {
            "version": "9.0.5",
            "resolved": "https://registry.npmjs.org/ip-address/-/ip-address-9.0.5.tgz",
            "integrity": "sha512-zHtQzGojZXTwZTHQqra+ETKd4Sn3vgi7uBmlPoXVWZqYvuKmtI0l/VZTjqGmJY9x88GGOaZ9+G9ES8hC4T4X8g==",
            "dependencies": {
                "jsbn": "1.1.0",
                "sprintf-js": "^1.1.3"
            },
            "engines": {
                "node": ">= 12"
            }
        },
        "node_modules/is-arrayish": {
            "version": "0.2.1",
            "resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz",
            "integrity": "sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg=="
        },
        "node_modules/is-binary-path": {
            "version": "2.1.0",
            "resolved": "https://registry.npmjs.org/is-binary-path/-/is-binary-path-2.1.0.tgz",
            "integrity": "sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==",
            "dev": true,
            "dependencies": {
                "binary-extensions": "^2.0.0"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/is-core-module": {
            "version": "2.15.1",
            "resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.15.1.tgz",
            "integrity": "sha512-z0vtXSwucUJtANQWldhbtbt7BnL0vxiFjIdDLAatwhDYty2bad6s+rijD6Ri4YuYJubLzIJLUidCh09e1djEVQ==",
            "dev": true,
            "dependencies": {
                "hasown": "^2.0.2"
            },
            "engines": {
                "node": ">= 0.4"
            },
            "funding": {
                "url": "https://github.com/sponsors/ljharb"
            }
        },
        "node_modules/is-extglob": {
            "version": "2.1.1",
            "resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz",
            "integrity": "sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==",
            "dev": true,
            "engines": {
                "node": ">=0.10.0"
            }
        },
        "node_modules/is-fullwidth-code-point": {
            "version": "3.0.0",
            "resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz",
            "integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==",
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/is-glob": {
            "version": "4.0.3",
            "resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
            "integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
            "dev": true,
            "dependencies": {
                "is-extglob": "^2.1.1"
            },
            "engines": {
                "node": ">=0.10.0"
            }
        },
        "node_modules/is-number": {
            "version": "7.0.0",
            "resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz",
            "integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==",
            "dev": true,
            "engines": {
                "node": ">=0.12.0"
            }
        },
        "node_modules/isexe": {
            "version": "2.0.0",
            "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
            "integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==",
            "dev": true
        },
        "node_modules/jackspeak": {
            "version": "3.4.3",
            "resolved": "https://registry.npmjs.org/jackspeak/-/jackspeak-3.4.3.tgz",
            "integrity": "sha512-OGlZQpz2yfahA/Rd1Y8Cd9SIEsqvXkLVoSw/cgwhnhFMDbsQFeZYoJJ7bIZBS9BcamUW96asq/npPWugM+RQBw==",
            "dev": true,
            "dependencies": {
                "@isaacs/cliui": "^8.0.2"
            },
            "funding": {
                "url": "https://github.com/sponsors/isaacs"
            },
            "optionalDependencies": {
                "@pkgjs/parseargs": "^0.11.0"
            }
        },
        "node_modules/jiti": {
            "version": "1.21.6",
            "resolved": "https://registry.npmjs.org/jiti/-/jiti-1.21.6.tgz",
            "integrity": "sha512-2yTgeWTWzMWkHu6Jp9NKgePDaYHbntiwvYuuJLbbN9vl7DC9DvXKOB2BC3ZZ92D3cvV/aflH0osDfwpHepQ53w==",
            "dev": true,
            "bin": {
                "jiti": "bin/jiti.js"
            }
        },
        "node_modules/jquery": {
            "version": "3.7.1",
            "resolved": "https://registry.npmjs.org/jquery/-/jquery-3.7.1.tgz",
            "integrity": "sha512-m4avr8yL8kmFN8psrbFFFmB/If14iN5o9nw/NgnnM+kybDJpRsAynV2BsfpTYrTRysYUdADVD7CkUUizgkpLfg=="
        },
        "node_modules/js-tokens": {
            "version": "4.0.0",
            "resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz",
            "integrity": "sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ=="
        },
        "node_modules/js-yaml": {
            "version": "4.1.0",
            "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz",
            "integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==",
            "dependencies": {
                "argparse": "^2.0.1"
            },
            "bin": {
                "js-yaml": "bin/js-yaml.js"
            }
        },
        "node_modules/jsbarcode": {
            "version": "3.11.6",
            "resolved": "https://registry.npmjs.org/jsbarcode/-/jsbarcode-3.11.6.tgz",
            "integrity": "sha512-G5TKGyKY1zJo0ZQKFM1IIMfy0nF2rs92BLlCz+cU4/TazIc4ZH+X1GYeDRt7TKjrYqmPfTjwTBkU/QnQlsYiuA=="
        },
        "node_modules/jsbn": {
            "version": "1.1.0",
            "resolved": "https://registry.npmjs.org/jsbn/-/jsbn-1.1.0.tgz",
            "integrity": "sha512-4bYVV3aAMtDTTu4+xsDYa6sy9GyJ69/amsu9sYF2zqjiEoZA5xJi3BrfX3uY+/IekIu7MwdObdbDWpoZdBv3/A=="
        },
        "node_modules/json-parse-even-better-errors": {
            "version": "2.3.1",
            "resolved": "https://registry.npmjs.org/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz",
            "integrity": "sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w=="
        },
        "node_modules/jsonfile": {
            "version": "6.1.0",
            "resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-6.1.0.tgz",
            "integrity": "sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==",
            "dependencies": {
                "universalify": "^2.0.0"
            },
            "optionalDependencies": {
                "graceful-fs": "^4.1.6"
            }
        },
        "node_modules/laravel-echo": {
            "version": "1.16.1",
            "resolved": "https://registry.npmjs.org/laravel-echo/-/laravel-echo-1.16.1.tgz",
            "integrity": "sha512-++Ylb6M3ariC9Rk5WE5gZjj6wcEV5kvLF8b+geJ5/rRIfdoOA+eG6b9qJPrarMD9rY28Apx+l3eelIrCc2skVg==",
            "engines": {
                "node": ">=10"
            }
        },
        "node_modules/laravel-vite-plugin": {
            "version": "0.8.1",
            "resolved": "https://registry.npmjs.org/laravel-vite-plugin/-/laravel-vite-plugin-0.8.1.tgz",
            "integrity": "sha512-fxzUDjOA37kOsYq8dP+3oPIlw8/kJVXwu0hOXLun82R1LpV02shGeWGYKx2lbpKffL5I0sfPPjfqbYxuqBluAA==",
            "dev": true,
            "dependencies": {
                "picocolors": "^1.0.0",
                "vite-plugin-full-reload": "^1.0.5"
            },
            "engines": {
                "node": ">=14"
            },
            "peerDependencies": {
                "vite": "^3.0.0 || ^4.0.0"
            }
        },
        "node_modules/lilconfig": {
            "version": "2.1.0",
            "resolved": "https://registry.npmjs.org/lilconfig/-/lilconfig-2.1.0.tgz",
            "integrity": "sha512-utWOt/GHzuUxnLKxB6dk81RoOeoNeHgbrXiuGk4yyF5qlRz+iIVWu56E2fqGHFrXz0QNUhLB/8nKqvRH66JKGQ==",
            "dev": true,
            "engines": {
                "node": ">=10"
            }
        },
        "node_modules/lines-and-columns": {
            "version": "1.2.4",
            "resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.2.4.tgz",
            "integrity": "sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg=="
        },
        "node_modules/lodash": {
            "version": "4.17.21",
            "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz",
            "integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg=="
        },
        "node_modules/lodash.castarray": {
            "version": "4.4.0",
            "resolved": "https://registry.npmjs.org/lodash.castarray/-/lodash.castarray-4.4.0.tgz",
            "integrity": "sha512-aVx8ztPv7/2ULbArGJ2Y42bG1mEQ5mGjpdvrbJcJFU3TbYybe+QlLS4pst9zV52ymy2in1KpFPiZnAOATxD4+Q==",
            "dev": true
        },
        "node_modules/lodash.debounce": {
            "version": "4.0.8",
            "resolved": "https://registry.npmjs.org/lodash.debounce/-/lodash.debounce-4.0.8.tgz",
            "integrity": "sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow=="
        },
        "node_modules/lodash.isplainobject": {
            "version": "4.0.6",
            "resolved": "https://registry.npmjs.org/lodash.isplainobject/-/lodash.isplainobject-4.0.6.tgz",
            "integrity": "sha512-oSXzaWypCMHkPC3NvBEaPHf0KsA5mvPrOPgQWDsbg8n7orZ290M0BmC/jgRZ4vcJ6DTAhjrsSYgdsW/F+MFOBA==",
            "dev": true
        },
        "node_modules/lodash.merge": {
            "version": "4.6.2",
            "resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz",
            "integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==",
            "dev": true
        },
        "node_modules/lodash.throttle": {
            "version": "4.1.1",
            "resolved": "https://registry.npmjs.org/lodash.throttle/-/lodash.throttle-4.1.1.tgz",
            "integrity": "sha512-wIkUCfVKpVsWo3JSZlc+8MB5it+2AN5W8J7YVMST30UrvcQNZ1Okbj+rbVniijTWE6FGYy4XJq/rHkas8qJMLQ=="
        },
        "node_modules/lru-cache": {
            "version": "7.18.3",
            "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-7.18.3.tgz",
            "integrity": "sha512-jumlc0BIUrS3qJGgIkWZsyfAM7NCWiBcCDhnd+3NNM5KbBmLTgHVfWBcg6W+rLUsIpzpERPsvwUP7CckAQSOoA==",
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/merge2": {
            "version": "1.4.1",
            "resolved": "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz",
            "integrity": "sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==",
            "dev": true,
            "engines": {
                "node": ">= 8"
            }
        },
        "node_modules/micromatch": {
            "version": "4.0.8",
            "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.8.tgz",
            "integrity": "sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==",
            "dev": true,
            "dependencies": {
                "braces": "^3.0.3",
                "picomatch": "^2.3.1"
            },
            "engines": {
                "node": ">=8.6"
            }
        },
        "node_modules/mime-db": {
            "version": "1.52.0",
            "resolved": "https://registry.npmjs.org/mime-db/-/mime-db-1.52.0.tgz",
            "integrity": "sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg==",
            "dev": true,
            "engines": {
                "node": ">= 0.6"
            }
        },
        "node_modules/mime-types": {
            "version": "2.1.35",
            "resolved": "https://registry.npmjs.org/mime-types/-/mime-types-2.1.35.tgz",
            "integrity": "sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw==",
            "dev": true,
            "dependencies": {
                "mime-db": "1.52.0"
            },
            "engines": {
                "node": ">= 0.6"
            }
        },
        "node_modules/mini-svg-data-uri": {
            "version": "1.4.4",
            "resolved": "https://registry.npmjs.org/mini-svg-data-uri/-/mini-svg-data-uri-1.4.4.tgz",
            "integrity": "sha512-r9deDe9p5FJUPZAk3A59wGH7Ii9YrjjWw0jmw/liSbHl2CHiyXj6FcDXDu2K3TjVAXqiJdaw3xxwlZZr9E6nHg==",
            "bin": {
                "mini-svg-data-uri": "cli.js"
            }
        },
        "node_modules/minimatch": {
            "version": "9.0.5",
            "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz",
            "integrity": "sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==",
            "dev": true,
            "dependencies": {
                "brace-expansion": "^2.0.1"
            },
            "engines": {
                "node": ">=16 || 14 >=14.17"
            },
            "funding": {
                "url": "https://github.com/sponsors/isaacs"
            }
        },
        "node_modules/minipass": {
            "version": "7.1.2",
            "resolved": "https://registry.npmjs.org/minipass/-/minipass-7.1.2.tgz",
            "integrity": "sha512-qOOzS1cBTWYF4BH8fVePDBOO9iptMnGUEZwNc/cMWnTV2nVLZ7VoNWEPHkYczZA0pdoA7dl6e7FL659nX9S2aw==",
            "dev": true,
            "engines": {
                "node": ">=16 || 14 >=14.17"
            }
        },
        "node_modules/mitt": {
            "version": "3.0.1",
            "resolved": "https://registry.npmjs.org/mitt/-/mitt-3.0.1.tgz",
            "integrity": "sha512-vKivATfr97l2/QBCYAkXYDbrIWPM2IIKEl7YPhjCvKlG3kE2gm+uBo6nEXK3M5/Ffh/FLpKExzOQ3JJoJGFKBw=="
        },
        "node_modules/ms": {
            "version": "2.1.2",
            "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
            "integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w=="
        },
        "node_modules/mz": {
            "version": "2.7.0",
            "resolved": "https://registry.npmjs.org/mz/-/mz-2.7.0.tgz",
            "integrity": "sha512-z81GNO7nnYMEhrGh9LeymoE4+Yr0Wn5McHIZMK5cfQCl+NDX08sCZgUc9/6MHni9IWuFLm1Z3HTCXu2z9fN62Q==",
            "dev": true,
            "dependencies": {
                "any-promise": "^1.0.0",
                "object-assign": "^4.0.1",
                "thenify-all": "^1.0.0"
            }
        },
        "node_modules/nanoid": {
            "version": "3.3.7",
            "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.7.tgz",
            "integrity": "sha512-eSRppjcPIatRIMC1U6UngP8XFcz8MQWGQdt1MTBQ7NaAmvXDfvNxbvWV3x2y6CdEUciCSsDHDQZbhYaB8QEo2g==",
            "dev": true,
            "funding": [
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/ai"
                }
            ],
            "bin": {
                "nanoid": "bin/nanoid.cjs"
            },
            "engines": {
                "node": "^10 || ^12 || ^13.7 || ^14 || >=15.0.1"
            }
        },
        "node_modules/netmask": {
            "version": "2.0.2",
            "resolved": "https://registry.npmjs.org/netmask/-/netmask-2.0.2.tgz",
            "integrity": "sha512-dBpDMdxv9Irdq66304OLfEmQ9tbNRFnFTuZiLo+bD+r332bBmMJ8GBLXklIXXgxd3+v9+KUnZaUR5PJMa75Gsg==",
            "engines": {
                "node": ">= 0.4.0"
            }
        },
        "node_modules/node-releases": {
            "version": "2.0.18",
            "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.18.tgz",
            "integrity": "sha512-d9VeXT4SJ7ZeOqGX6R5EM022wpL+eWPooLI+5UpWn2jCT1aosUQEhQP214x33Wkwx3JQMvIm+tIoVOdodFS40g==",
            "dev": true
        },
        "node_modules/normalize-path": {
            "version": "3.0.0",
            "resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
            "integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
            "dev": true,
            "engines": {
                "node": ">=0.10.0"
            }
        },
        "node_modules/normalize-range": {
            "version": "0.1.2",
            "resolved": "https://registry.npmjs.org/normalize-range/-/normalize-range-0.1.2.tgz",
            "integrity": "sha512-bdok/XvKII3nUpklnV6P2hxtMNrCboOjAcyBuQnWEhO665FwrSNRxU+AqpsyvO6LgGYPspN+lu5CLtw4jPRKNA==",
            "dev": true,
            "engines": {
                "node": ">=0.10.0"
            }
        },
        "node_modules/object-assign": {
            "version": "4.1.1",
            "resolved": "https://registry.npmjs.org/object-assign/-/object-assign-4.1.1.tgz",
            "integrity": "sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==",
            "dev": true,
            "engines": {
                "node": ">=0.10.0"
            }
        },
        "node_modules/object-hash": {
            "version": "3.0.0",
            "resolved": "https://registry.npmjs.org/object-hash/-/object-hash-3.0.0.tgz",
            "integrity": "sha512-RSn9F68PjH9HqtltsSnqYC1XXoWe9Bju5+213R98cNGttag9q9yAOTzdbsqvIa7aNm5WffBZFpWYr2aWrklWAw==",
            "dev": true,
            "engines": {
                "node": ">= 6"
            }
        },
        "node_modules/once": {
            "version": "1.4.0",
            "resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz",
            "integrity": "sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==",
            "dependencies": {
                "wrappy": "1"
            }
        },
        "node_modules/pac-proxy-agent": {
            "version": "7.0.2",
            "resolved": "https://registry.npmjs.org/pac-proxy-agent/-/pac-proxy-agent-7.0.2.tgz",
            "integrity": "sha512-BFi3vZnO9X5Qt6NRz7ZOaPja3ic0PhlsmCRYLOpN11+mWBCR6XJDqW5RF3j8jm4WGGQZtBA+bTfxYzeKW73eHg==",
            "dependencies": {
                "@tootallnate/quickjs-emscripten": "^0.23.0",
                "agent-base": "^7.0.2",
                "debug": "^4.3.4",
                "get-uri": "^6.0.1",
                "http-proxy-agent": "^7.0.0",
                "https-proxy-agent": "^7.0.5",
                "pac-resolver": "^7.0.1",
                "socks-proxy-agent": "^8.0.4"
            },
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/pac-resolver": {
            "version": "7.0.1",
            "resolved": "https://registry.npmjs.org/pac-resolver/-/pac-resolver-7.0.1.tgz",
            "integrity": "sha512-5NPgf87AT2STgwa2ntRMr45jTKrYBGkVU36yT0ig/n/GMAa3oPqhZfIQ2kMEimReg0+t9kZViDVZ83qfVUlckg==",
            "dependencies": {
                "degenerator": "^5.0.0",
                "netmask": "^2.0.2"
            },
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/package-json-from-dist": {
            "version": "1.0.0",
            "resolved": "https://registry.npmjs.org/package-json-from-dist/-/package-json-from-dist-1.0.0.tgz",
            "integrity": "sha512-dATvCeZN/8wQsGywez1mzHtTlP22H8OEfPrVMLNr4/eGa+ijtLn/6M5f0dY8UKNrC2O9UCU6SSoG3qRKnt7STw==",
            "dev": true
        },
        "node_modules/parent-module": {
            "version": "1.0.1",
            "resolved": "https://registry.npmjs.org/parent-module/-/parent-module-1.0.1.tgz",
            "integrity": "sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==",
            "dependencies": {
                "callsites": "^3.0.0"
            },
            "engines": {
                "node": ">=6"
            }
        },
        "node_modules/parse-json": {
            "version": "5.2.0",
            "resolved": "https://registry.npmjs.org/parse-json/-/parse-json-5.2.0.tgz",
            "integrity": "sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==",
            "dependencies": {
                "@babel/code-frame": "^7.0.0",
                "error-ex": "^1.3.1",
                "json-parse-even-better-errors": "^2.3.0",
                "lines-and-columns": "^1.1.6"
            },
            "engines": {
                "node": ">=8"
            },
            "funding": {
                "url": "https://github.com/sponsors/sindresorhus"
            }
        },
        "node_modules/path-key": {
            "version": "3.1.1",
            "resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz",
            "integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==",
            "dev": true,
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/path-parse": {
            "version": "1.0.7",
            "resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz",
            "integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==",
            "dev": true
        },
        "node_modules/path-scurry": {
            "version": "1.11.1",
            "resolved": "https://registry.npmjs.org/path-scurry/-/path-scurry-1.11.1.tgz",
            "integrity": "sha512-Xa4Nw17FS9ApQFJ9umLiJS4orGjm7ZzwUrwamcGQuHSzDyth9boKDaycYdDcZDuqYATXw4HFXgaqWTctW/v1HA==",
            "dev": true,
            "dependencies": {
                "lru-cache": "^10.2.0",
                "minipass": "^5.0.0 || ^6.0.2 || ^7.0.0"
            },
            "engines": {
                "node": ">=16 || 14 >=14.18"
            },
            "funding": {
                "url": "https://github.com/sponsors/isaacs"
            }
        },
        "node_modules/path-scurry/node_modules/lru-cache": {
            "version": "10.4.3",
            "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-10.4.3.tgz",
            "integrity": "sha512-JNAzZcXrCt42VGLuYz0zfAzDfAvJWW6AfYlDBQyDV5DClI2m5sAmK+OIO7s59XfsRsWHp02jAJrRadPRGTt6SQ==",
            "dev": true
        },
        "node_modules/pend": {
            "version": "1.2.0",
            "resolved": "https://registry.npmjs.org/pend/-/pend-1.2.0.tgz",
            "integrity": "sha512-F3asv42UuXchdzt+xXqfW1OGlVBe+mxa2mqI0pg5yAHZPvFmY3Y6drSf/GQ1A86WgWEN9Kzh/WrgKa6iGcHXLg=="
        },
        "node_modules/picocolors": {
            "version": "1.0.1",
            "resolved": "https://registry.npmjs.org/picocolors/-/picocolors-1.0.1.tgz",
            "integrity": "sha512-anP1Z8qwhkbmu7MFP5iTt+wQKXgwzf7zTyGlcdzabySa9vd0Xt392U0rVmz9poOaBj0uHJKyyo9/upk0HrEQew=="
        },
        "node_modules/picomatch": {
            "version": "2.3.1",
            "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz",
            "integrity": "sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==",
            "dev": true,
            "engines": {
                "node": ">=8.6"
            },
            "funding": {
                "url": "https://github.com/sponsors/jonschlinkert"
            }
        },
        "node_modules/pify": {
            "version": "2.3.0",
            "resolved": "https://registry.npmjs.org/pify/-/pify-2.3.0.tgz",
            "integrity": "sha512-udgsAY+fTnvv7kI7aaxbqwWNb0AHiB0qBO89PZKPkoTmGOgdbrHDKD+0B2X4uTfJ/FT1R09r9gTsjUjNJotuog==",
            "dev": true,
            "engines": {
                "node": ">=0.10.0"
            }
        },
        "node_modules/pirates": {
            "version": "4.0.6",
            "resolved": "https://registry.npmjs.org/pirates/-/pirates-4.0.6.tgz",
            "integrity": "sha512-saLsH7WeYYPiD25LDuLRRY/i+6HaPYr6G1OUlN39otzkSTxKnubR9RTxS3/Kk50s1g2JTgFwWQDQyplC5/SHZg==",
            "dev": true,
            "engines": {
                "node": ">= 6"
            }
        },
        "node_modules/postcss": {
            "version": "8.4.41",
            "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.41.tgz",
            "integrity": "sha512-TesUflQ0WKZqAvg52PWL6kHgLKP6xB6heTOdoYM0Wt2UHyxNa4K25EZZMgKns3BH1RLVbZCREPpLY0rhnNoHVQ==",
            "dev": true,
            "funding": [
                {
                    "type": "opencollective",
                    "url": "https://opencollective.com/postcss/"
                },
                {
                    "type": "tidelift",
                    "url": "https://tidelift.com/funding/github/npm/postcss"
                },
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/ai"
                }
            ],
            "dependencies": {
                "nanoid": "^3.3.7",
                "picocolors": "^1.0.1",
                "source-map-js": "^1.2.0"
            },
            "engines": {
                "node": "^10 || ^12 || >=14"
            }
        },
        "node_modules/postcss-import": {
            "version": "15.1.0",
            "resolved": "https://registry.npmjs.org/postcss-import/-/postcss-import-15.1.0.tgz",
            "integrity": "sha512-hpr+J05B2FVYUAXHeK1YyI267J/dDDhMU6B6civm8hSY1jYJnBXxzKDKDswzJmtLHryrjhnDjqqp/49t8FALew==",
            "dev": true,
            "dependencies": {
                "postcss-value-parser": "^4.0.0",
                "read-cache": "^1.0.0",
                "resolve": "^1.1.7"
            },
            "engines": {
                "node": ">=14.0.0"
            },
            "peerDependencies": {
                "postcss": "^8.0.0"
            }
        },
        "node_modules/postcss-js": {
            "version": "4.0.1",
            "resolved": "https://registry.npmjs.org/postcss-js/-/postcss-js-4.0.1.tgz",
            "integrity": "sha512-dDLF8pEO191hJMtlHFPRa8xsizHaM82MLfNkUHdUtVEV3tgTp5oj+8qbEqYM57SLfc74KSbw//4SeJma2LRVIw==",
            "dev": true,
            "dependencies": {
                "camelcase-css": "^2.0.1"
            },
            "engines": {
                "node": "^12 || ^14 || >= 16"
            },
            "funding": {
                "type": "opencollective",
                "url": "https://opencollective.com/postcss/"
            },
            "peerDependencies": {
                "postcss": "^8.4.21"
            }
        },
        "node_modules/postcss-load-config": {
            "version": "4.0.2",
            "resolved": "https://registry.npmjs.org/postcss-load-config/-/postcss-load-config-4.0.2.tgz",
            "integrity": "sha512-bSVhyJGL00wMVoPUzAVAnbEoWyqRxkjv64tUl427SKnPrENtq6hJwUojroMz2VB+Q1edmi4IfrAPpami5VVgMQ==",
            "dev": true,
            "funding": [
                {
                    "type": "opencollective",
                    "url": "https://opencollective.com/postcss/"
                },
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/ai"
                }
            ],
            "dependencies": {
                "lilconfig": "^3.0.0",
                "yaml": "^2.3.4"
            },
            "engines": {
                "node": ">= 14"
            },
            "peerDependencies": {
                "postcss": ">=8.0.9",
                "ts-node": ">=9.0.0"
            },
            "peerDependenciesMeta": {
                "postcss": {
                    "optional": true
                },
                "ts-node": {
                    "optional": true
                }
            }
        },
        "node_modules/postcss-load-config/node_modules/lilconfig": {
            "version": "3.1.2",
            "resolved": "https://registry.npmjs.org/lilconfig/-/lilconfig-3.1.2.tgz",
            "integrity": "sha512-eop+wDAvpItUys0FWkHIKeC9ybYrTGbU41U5K7+bttZZeohvnY7M9dZ5kB21GNWiFT2q1OoPTvncPCgSOVO5ow==",
            "dev": true,
            "engines": {
                "node": ">=14"
            },
            "funding": {
                "url": "https://github.com/sponsors/antonk52"
            }
        },
        "node_modules/postcss-nested": {
            "version": "6.2.0",
            "resolved": "https://registry.npmjs.org/postcss-nested/-/postcss-nested-6.2.0.tgz",
            "integrity": "sha512-HQbt28KulC5AJzG+cZtj9kvKB93CFCdLvog1WFLf1D+xmMvPGlBstkpTEZfK5+AN9hfJocyBFCNiqyS48bpgzQ==",
            "dev": true,
            "funding": [
                {
                    "type": "opencollective",
                    "url": "https://opencollective.com/postcss/"
                },
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/ai"
                }
            ],
            "dependencies": {
                "postcss-selector-parser": "^6.1.1"
            },
            "engines": {
                "node": ">=12.0"
            },
            "peerDependencies": {
                "postcss": "^8.2.14"
            }
        },
        "node_modules/postcss-nested/node_modules/postcss-selector-parser": {
            "version": "6.1.2",
            "resolved": "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.1.2.tgz",
            "integrity": "sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg==",
            "dev": true,
            "dependencies": {
                "cssesc": "^3.0.0",
                "util-deprecate": "^1.0.2"
            },
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/postcss-selector-parser": {
            "version": "6.0.10",
            "resolved": "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.0.10.tgz",
            "integrity": "sha512-IQ7TZdoaqbT+LCpShg46jnZVlhWD2w6iQYAcYXfHARZ7X1t/UGhhceQDs5X0cGqKvYlHNOuv7Oa1xmb0oQuA3w==",
            "dev": true,
            "dependencies": {
                "cssesc": "^3.0.0",
                "util-deprecate": "^1.0.2"
            },
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/postcss-value-parser": {
            "version": "4.2.0",
            "resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz",
            "integrity": "sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==",
            "dev": true
        },
        "node_modules/preline": {
            "version": "2.4.1",
            "resolved": "https://registry.npmjs.org/preline/-/preline-2.4.1.tgz",
            "integrity": "sha512-30yx5s2gEOTBWXSTPa+Th23/kGryn9Inhmp9KPzz9G8DZPp9j/LkGyyrSvdsuXh4Clc/sJFLObumFrbI/WmB0w==",
            "dependencies": {
                "@popperjs/core": "^2.11.2"
            }
        },
        "node_modules/progress": {
            "version": "2.0.3",
            "resolved": "https://registry.npmjs.org/progress/-/progress-2.0.3.tgz",
            "integrity": "sha512-7PiHtLll5LdnKIMw100I+8xJXR5gW2QwWYkT6iJva0bXitZKa/XMrSbdmg3r2Xnaidz9Qumd0VPaMrZlF9V9sA==",
            "engines": {
                "node": ">=0.4.0"
            }
        },
        "node_modules/proxy-agent": {
            "version": "6.4.0",
            "resolved": "https://registry.npmjs.org/proxy-agent/-/proxy-agent-6.4.0.tgz",
            "integrity": "sha512-u0piLU+nCOHMgGjRbimiXmA9kM/L9EHh3zL81xCdp7m+Y2pHIsnmbdDoEDoAz5geaonNR6q6+yOPQs6n4T6sBQ==",
            "dependencies": {
                "agent-base": "^7.0.2",
                "debug": "^4.3.4",
                "http-proxy-agent": "^7.0.1",
                "https-proxy-agent": "^7.0.3",
                "lru-cache": "^7.14.1",
                "pac-proxy-agent": "^7.0.1",
                "proxy-from-env": "^1.1.0",
                "socks-proxy-agent": "^8.0.2"
            },
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/proxy-from-env": {
            "version": "1.1.0",
            "resolved": "https://registry.npmjs.org/proxy-from-env/-/proxy-from-env-1.1.0.tgz",
            "integrity": "sha512-D+zkORCbA9f1tdWRK0RaCR3GPv50cMxcrz4X8k5LTSUD1Dkw47mKJEZQNunItRTkWwgtaUSo1RVFRIG9ZXiFYg=="
        },
        "node_modules/pump": {
            "version": "3.0.0",
            "resolved": "https://registry.npmjs.org/pump/-/pump-3.0.0.tgz",
            "integrity": "sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==",
            "dependencies": {
                "end-of-stream": "^1.1.0",
                "once": "^1.3.1"
            }
        },
        "node_modules/puppeteer": {
            "version": "22.15.0",
            "resolved": "https://registry.npmjs.org/puppeteer/-/puppeteer-22.15.0.tgz",
            "integrity": "sha512-XjCY1SiSEi1T7iSYuxS82ft85kwDJUS7wj1Z0eGVXKdtr5g4xnVcbjwxhq5xBnpK/E7x1VZZoJDxpjAOasHT4Q==",
            "hasInstallScript": true,
            "dependencies": {
                "@puppeteer/browsers": "2.3.0",
                "cosmiconfig": "^9.0.0",
                "devtools-protocol": "0.0.1312386",
                "puppeteer-core": "22.15.0"
            },
            "bin": {
                "puppeteer": "lib/esm/puppeteer/node/cli.js"
            },
            "engines": {
                "node": ">=18"
            }
        },
        "node_modules/puppeteer-core": {
            "version": "22.15.0",
            "resolved": "https://registry.npmjs.org/puppeteer-core/-/puppeteer-core-22.15.0.tgz",
            "integrity": "sha512-cHArnywCiAAVXa3t4GGL2vttNxh7GqXtIYGym99egkNJ3oG//wL9LkvO4WE8W1TJe95t1F1ocu9X4xWaGsOKOA==",
            "dependencies": {
                "@puppeteer/browsers": "2.3.0",
                "chromium-bidi": "0.6.3",
                "debug": "^4.3.6",
                "devtools-protocol": "0.0.1312386",
                "ws": "^8.18.0"
            },
            "engines": {
                "node": ">=18"
            }
        },
        "node_modules/pusher-js": {
            "version": "8.4.0-rc2",
            "resolved": "https://registry.npmjs.org/pusher-js/-/pusher-js-8.4.0-rc2.tgz",
            "integrity": "sha512-d87GjOEEl9QgO5BWmViSqW0LOzPvybvX6WA9zLUstNdB57jVJuR27zHkRnrav2a3+zAMlHbP2Og8wug+rG8T+g==",
            "dependencies": {
                "tweetnacl": "^1.0.3"
            }
        },
        "node_modules/queue-microtask": {
            "version": "1.2.3",
            "resolved": "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz",
            "integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==",
            "dev": true,
            "funding": [
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/feross"
                },
                {
                    "type": "patreon",
                    "url": "https://www.patreon.com/feross"
                },
                {
                    "type": "consulting",
                    "url": "https://feross.org/support"
                }
            ]
        },
        "node_modules/queue-tick": {
            "version": "1.0.1",
            "resolved": "https://registry.npmjs.org/queue-tick/-/queue-tick-1.0.1.tgz",
            "integrity": "sha512-kJt5qhMxoszgU/62PLP1CJytzd2NKetjSRnyuj31fDd3Rlcz3fzlFdFLD1SItunPwyqEOkca6GbV612BWfaBag=="
        },
        "node_modules/read-cache": {
            "version": "1.0.0",
            "resolved": "https://registry.npmjs.org/read-cache/-/read-cache-1.0.0.tgz",
            "integrity": "sha512-Owdv/Ft7IjOgm/i0xvNDZ1LrRANRfew4b2prF3OWMQLxLfu3bS8FVhCsrSCMK4lR56Y9ya+AThoTpDCTxCmpRA==",
            "dev": true,
            "dependencies": {
                "pify": "^2.3.0"
            }
        },
        "node_modules/readdirp": {
            "version": "3.6.0",
            "resolved": "https://registry.npmjs.org/readdirp/-/readdirp-3.6.0.tgz",
            "integrity": "sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==",
            "dev": true,
            "dependencies": {
                "picomatch": "^2.2.1"
            },
            "engines": {
                "node": ">=8.10.0"
            }
        },
        "node_modules/require-directory": {
            "version": "2.1.1",
            "resolved": "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz",
            "integrity": "sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q==",
            "engines": {
                "node": ">=0.10.0"
            }
        },
        "node_modules/resolve": {
            "version": "1.22.8",
            "resolved": "https://registry.npmjs.org/resolve/-/resolve-1.22.8.tgz",
            "integrity": "sha512-oKWePCxqpd6FlLvGV1VU0x7bkPmmCNolxzjMf4NczoDnQcIWrAF+cPtZn5i6n+RfD2d9i0tzpKnG6Yk168yIyw==",
            "dev": true,
            "dependencies": {
                "is-core-module": "^2.13.0",
                "path-parse": "^1.0.7",
                "supports-preserve-symlinks-flag": "^1.0.0"
            },
            "bin": {
                "resolve": "bin/resolve"
            },
            "funding": {
                "url": "https://github.com/sponsors/ljharb"
            }
        },
        "node_modules/resolve-from": {
            "version": "4.0.0",
            "resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz",
            "integrity": "sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==",
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/reusify": {
            "version": "1.0.4",
            "resolved": "https://registry.npmjs.org/reusify/-/reusify-1.0.4.tgz",
            "integrity": "sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==",
            "dev": true,
            "engines": {
                "iojs": ">=1.0.0",
                "node": ">=0.10.0"
            }
        },
        "node_modules/rollup": {
            "version": "3.29.4",
            "resolved": "https://registry.npmjs.org/rollup/-/rollup-3.29.4.tgz",
            "integrity": "sha512-oWzmBZwvYrU0iJHtDmhsm662rC15FRXmcjCk1xD771dFDx5jJ02ufAQQTn0etB2emNk4J9EZg/yWKpsn9BWGRw==",
            "dev": true,
            "bin": {
                "rollup": "dist/bin/rollup"
            },
            "engines": {
                "node": ">=14.18.0",
                "npm": ">=8.0.0"
            },
            "optionalDependencies": {
                "fsevents": "~2.3.2"
            }
        },
        "node_modules/run-parallel": {
            "version": "1.2.0",
            "resolved": "https://registry.npmjs.org/run-parallel/-/run-parallel-1.2.0.tgz",
            "integrity": "sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==",
            "dev": true,
            "funding": [
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/feross"
                },
                {
                    "type": "patreon",
                    "url": "https://www.patreon.com/feross"
                },
                {
                    "type": "consulting",
                    "url": "https://feross.org/support"
                }
            ],
            "dependencies": {
                "queue-microtask": "^1.2.2"
            }
        },
        "node_modules/select": {
            "version": "1.1.2",
            "resolved": "https://registry.npmjs.org/select/-/select-1.1.2.tgz",
            "integrity": "sha512-OwpTSOfy6xSs1+pwcNrv0RBMOzI39Lp3qQKUTPVVPRjCdNa5JH/oPRiqsesIskK8TVgmRiHwO4KXlV2Li9dANA=="
        },
        "node_modules/semver": {
            "version": "7.6.3",
            "resolved": "https://registry.npmjs.org/semver/-/semver-7.6.3.tgz",
            "integrity": "sha512-oVekP1cKtI+CTDvHWYFUcMtsK/00wmAEfyqKfNdARm8u1wNVhSgaX7A8d4UuIlUI5e84iEwOhs7ZPYRmzU9U6A==",
            "bin": {
                "semver": "bin/semver.js"
            },
            "engines": {
                "node": ">=10"
            }
        },
        "node_modules/shebang-command": {
            "version": "2.0.0",
            "resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz",
            "integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==",
            "dev": true,
            "dependencies": {
                "shebang-regex": "^3.0.0"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/shebang-regex": {
            "version": "3.0.0",
            "resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz",
            "integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==",
            "dev": true,
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/signal-exit": {
            "version": "4.1.0",
            "resolved": "https://registry.npmjs.org/signal-exit/-/signal-exit-4.1.0.tgz",
            "integrity": "sha512-bzyZ1e88w9O1iNJbKnOlvYTrWPDl46O1bG0D3XInv+9tkPrxrN8jUUTiFlDkkmKWgn1M6CfIA13SuGqOa9Korw==",
            "dev": true,
            "engines": {
                "node": ">=14"
            },
            "funding": {
                "url": "https://github.com/sponsors/isaacs"
            }
        },
        "node_modules/smart-buffer": {
            "version": "4.2.0",
            "resolved": "https://registry.npmjs.org/smart-buffer/-/smart-buffer-4.2.0.tgz",
            "integrity": "sha512-94hK0Hh8rPqQl2xXc3HsaBoOXKV20MToPkcXvwbISWLEs+64sBq5kFgn2kJDHb1Pry9yrP0dxrCI9RRci7RXKg==",
            "engines": {
                "node": ">= 6.0.0",
                "npm": ">= 3.0.0"
            }
        },
        "node_modules/socks": {
            "version": "2.8.3",
            "resolved": "https://registry.npmjs.org/socks/-/socks-2.8.3.tgz",
            "integrity": "sha512-l5x7VUUWbjVFbafGLxPWkYsHIhEvmF85tbIeFZWc8ZPtoMyybuEhL7Jye/ooC4/d48FgOjSJXgsF/AJPYCW8Zw==",
            "dependencies": {
                "ip-address": "^9.0.5",
                "smart-buffer": "^4.2.0"
            },
            "engines": {
                "node": ">= 10.0.0",
                "npm": ">= 3.0.0"
            }
        },
        "node_modules/socks-proxy-agent": {
            "version": "8.0.4",
            "resolved": "https://registry.npmjs.org/socks-proxy-agent/-/socks-proxy-agent-8.0.4.tgz",
            "integrity": "sha512-GNAq/eg8Udq2x0eNiFkr9gRg5bA7PXEWagQdeRX4cPSG+X/8V38v637gim9bjFptMk1QWsCTr0ttrJEiXbNnRw==",
            "dependencies": {
                "agent-base": "^7.1.1",
                "debug": "^4.3.4",
                "socks": "^2.8.3"
            },
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/source-map": {
            "version": "0.6.1",
            "resolved": "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz",
            "integrity": "sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==",
            "optional": true,
            "engines": {
                "node": ">=0.10.0"
            }
        },
        "node_modules/source-map-js": {
            "version": "1.2.0",
            "resolved": "https://registry.npmjs.org/source-map-js/-/source-map-js-1.2.0.tgz",
            "integrity": "sha512-itJW8lvSA0TXEphiRoawsCksnlf8SyvmFzIhltqAHluXd88pkCd+cXJVHTDwdCr0IzwptSm035IHQktUu1QUMg==",
            "dev": true,
            "engines": {
                "node": ">=0.10.0"
            }
        },
        "node_modules/sprintf-js": {
            "version": "1.1.3",
            "resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.1.3.tgz",
            "integrity": "sha512-Oo+0REFV59/rz3gfJNKQiBlwfHaSESl1pcGyABQsnnIfWOFt6JNj5gCog2U6MLZ//IGYD+nA8nI+mTShREReaA=="
        },
        "node_modules/streamx": {
            "version": "2.19.0",
            "resolved": "https://registry.npmjs.org/streamx/-/streamx-2.19.0.tgz",
            "integrity": "sha512-5z6CNR4gtkPbwlxyEqoDGDmWIzoNJqCBt4Eac1ICP9YaIT08ct712cFj0u1rx4F8luAuL+3Qc+RFIdI4OX00kg==",
            "dependencies": {
                "fast-fifo": "^1.3.2",
                "queue-tick": "^1.0.1",
                "text-decoder": "^1.1.0"
            },
            "optionalDependencies": {
                "bare-events": "^2.2.0"
            }
        },
        "node_modules/string-width": {
            "version": "5.1.2",
            "resolved": "https://registry.npmjs.org/string-width/-/string-width-5.1.2.tgz",
            "integrity": "sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA==",
            "dev": true,
            "dependencies": {
                "eastasianwidth": "^0.2.0",
                "emoji-regex": "^9.2.2",
                "strip-ansi": "^7.0.1"
            },
            "engines": {
                "node": ">=12"
            },
            "funding": {
                "url": "https://github.com/sponsors/sindresorhus"
            }
        },
        "node_modules/string-width-cjs": {
            "name": "string-width",
            "version": "4.2.3",
            "resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
            "integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
            "dev": true,
            "dependencies": {
                "emoji-regex": "^8.0.0",
                "is-fullwidth-code-point": "^3.0.0",
                "strip-ansi": "^6.0.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/string-width-cjs/node_modules/ansi-regex": {
            "version": "5.0.1",
            "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
            "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
            "dev": true,
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/string-width-cjs/node_modules/emoji-regex": {
            "version": "8.0.0",
            "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz",
            "integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==",
            "dev": true
        },
        "node_modules/string-width-cjs/node_modules/strip-ansi": {
            "version": "6.0.1",
            "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
            "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
            "dev": true,
            "dependencies": {
                "ansi-regex": "^5.0.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/strip-ansi": {
            "version": "7.1.0",
            "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-7.1.0.tgz",
            "integrity": "sha512-iq6eVVI64nQQTRYq2KtEg2d2uU7LElhTJwsH4YzIHZshxlgZms/wIc4VoDQTlG/IvVIrBKG06CrZnp0qv7hkcQ==",
            "dev": true,
            "dependencies": {
                "ansi-regex": "^6.0.1"
            },
            "engines": {
                "node": ">=12"
            },
            "funding": {
                "url": "https://github.com/chalk/strip-ansi?sponsor=1"
            }
        },
        "node_modules/strip-ansi-cjs": {
            "name": "strip-ansi",
            "version": "6.0.1",
            "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
            "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
            "dev": true,
            "dependencies": {
                "ansi-regex": "^5.0.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/strip-ansi-cjs/node_modules/ansi-regex": {
            "version": "5.0.1",
            "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
            "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
            "dev": true,
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/sucrase": {
            "version": "3.35.0",
            "resolved": "https://registry.npmjs.org/sucrase/-/sucrase-3.35.0.tgz",
            "integrity": "sha512-8EbVDiu9iN/nESwxeSxDKe0dunta1GOlHufmSSXxMD2z2/tMZpDMpvXQGsc+ajGo8y2uYUmixaSRUc/QPoQ0GA==",
            "dev": true,
            "dependencies": {
                "@jridgewell/gen-mapping": "^0.3.2",
                "commander": "^4.0.0",
                "glob": "^10.3.10",
                "lines-and-columns": "^1.1.6",
                "mz": "^2.7.0",
                "pirates": "^4.0.1",
                "ts-interface-checker": "^0.1.9"
            },
            "bin": {
                "sucrase": "bin/sucrase",
                "sucrase-node": "bin/sucrase-node"
            },
            "engines": {
                "node": ">=16 || 14 >=14.17"
            }
        },
        "node_modules/supports-color": {
            "version": "5.5.0",
            "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-5.5.0.tgz",
            "integrity": "sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==",
            "dependencies": {
                "has-flag": "^3.0.0"
            },
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/supports-preserve-symlinks-flag": {
            "version": "1.0.0",
            "resolved": "https://registry.npmjs.org/supports-preserve-symlinks-flag/-/supports-preserve-symlinks-flag-1.0.0.tgz",
            "integrity": "sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==",
            "dev": true,
            "engines": {
                "node": ">= 0.4"
            },
            "funding": {
                "url": "https://github.com/sponsors/ljharb"
            }
        },
        "node_modules/svg.draggable.js": {
            "version": "2.2.2",
            "resolved": "https://registry.npmjs.org/svg.draggable.js/-/svg.draggable.js-2.2.2.tgz",
            "integrity": "sha512-JzNHBc2fLQMzYCZ90KZHN2ohXL0BQJGQimK1kGk6AvSeibuKcIdDX9Kr0dT9+UJ5O8nYA0RB839Lhvk4CY4MZw==",
            "dependencies": {
                "svg.js": "^2.0.1"
            },
            "engines": {
                "node": ">= 0.8.0"
            }
        },
        "node_modules/svg.easing.js": {
            "version": "2.0.0",
            "resolved": "https://registry.npmjs.org/svg.easing.js/-/svg.easing.js-2.0.0.tgz",
            "integrity": "sha512-//ctPdJMGy22YoYGV+3HEfHbm6/69LJUTAqI2/5qBvaNHZ9uUFVC82B0Pl299HzgH13rKrBgi4+XyXXyVWWthA==",
            "dependencies": {
                "svg.js": ">=2.3.x"
            },
            "engines": {
                "node": ">= 0.8.0"
            }
        },
        "node_modules/svg.filter.js": {
            "version": "2.0.2",
            "resolved": "https://registry.npmjs.org/svg.filter.js/-/svg.filter.js-2.0.2.tgz",
            "integrity": "sha512-xkGBwU+dKBzqg5PtilaTb0EYPqPfJ9Q6saVldX+5vCRy31P6TlRCP3U9NxH3HEufkKkpNgdTLBJnmhDHeTqAkw==",
            "dependencies": {
                "svg.js": "^2.2.5"
            },
            "engines": {
                "node": ">= 0.8.0"
            }
        },
        "node_modules/svg.js": {
            "version": "2.7.1",
            "resolved": "https://registry.npmjs.org/svg.js/-/svg.js-2.7.1.tgz",
            "integrity": "sha512-ycbxpizEQktk3FYvn/8BH+6/EuWXg7ZpQREJvgacqn46gIddG24tNNe4Son6omdXCnSOaApnpZw6MPCBA1dODA=="
        },
        "node_modules/svg.pathmorphing.js": {
            "version": "0.1.3",
            "resolved": "https://registry.npmjs.org/svg.pathmorphing.js/-/svg.pathmorphing.js-0.1.3.tgz",
            "integrity": "sha512-49HWI9X4XQR/JG1qXkSDV8xViuTLIWm/B/7YuQELV5KMOPtXjiwH4XPJvr/ghEDibmLQ9Oc22dpWpG0vUDDNww==",
            "dependencies": {
                "svg.js": "^2.4.0"
            },
            "engines": {
                "node": ">= 0.8.0"
            }
        },
        "node_modules/svg.resize.js": {
            "version": "1.4.3",
            "resolved": "https://registry.npmjs.org/svg.resize.js/-/svg.resize.js-1.4.3.tgz",
            "integrity": "sha512-9k5sXJuPKp+mVzXNvxz7U0uC9oVMQrrf7cFsETznzUDDm0x8+77dtZkWdMfRlmbkEEYvUn9btKuZ3n41oNA+uw==",
            "dependencies": {
                "svg.js": "^2.6.5",
                "svg.select.js": "^2.1.2"
            },
            "engines": {
                "node": ">= 0.8.0"
            }
        },
        "node_modules/svg.resize.js/node_modules/svg.select.js": {
            "version": "2.1.2",
            "resolved": "https://registry.npmjs.org/svg.select.js/-/svg.select.js-2.1.2.tgz",
            "integrity": "sha512-tH6ABEyJsAOVAhwcCjF8mw4crjXSI1aa7j2VQR8ZuJ37H2MBUbyeqYr5nEO7sSN3cy9AR9DUwNg0t/962HlDbQ==",
            "dependencies": {
                "svg.js": "^2.2.5"
            },
            "engines": {
                "node": ">= 0.8.0"
            }
        },
        "node_modules/svg.select.js": {
            "version": "3.0.1",
            "resolved": "https://registry.npmjs.org/svg.select.js/-/svg.select.js-3.0.1.tgz",
            "integrity": "sha512-h5IS/hKkuVCbKSieR9uQCj9w+zLHoPh+ce19bBYyqF53g6mnPB8sAtIbe1s9dh2S2fCmYX2xel1Ln3PJBbK4kw==",
            "dependencies": {
                "svg.js": "^2.6.5"
            },
            "engines": {
                "node": ">= 0.8.0"
            }
        },
        "node_modules/sweetalert2": {
            "version": "11.12.4",
            "resolved": "https://registry.npmjs.org/sweetalert2/-/sweetalert2-11.12.4.tgz",
            "integrity": "sha512-ZSpyaLbAmn4b7xjnV9x9BFD1UOrCAhIzm1D8dZ443kGxtVKqbTIA5SgXs4xeEtmFfEXUyC3RBgpSlu1AXmCiHA==",
            "funding": {
                "type": "individual",
                "url": "https://github.com/sponsors/limonte"
            }
        },
        "node_modules/tabbable": {
            "version": "5.3.3",
            "resolved": "https://registry.npmjs.org/tabbable/-/tabbable-5.3.3.tgz",
            "integrity": "sha512-QD9qKY3StfbZqWOPLp0++pOrAVb/HbUi5xCc8cUo4XjP19808oaMiDzn0leBY5mCespIBM0CIZePzZjgzR83kA=="
        },
        "node_modules/tailwindcss": {
            "version": "3.4.10",
            "resolved": "https://registry.npmjs.org/tailwindcss/-/tailwindcss-3.4.10.tgz",
            "integrity": "sha512-KWZkVPm7yJRhdu4SRSl9d4AK2wM3a50UsvgHZO7xY77NQr2V+fIrEuoDGQcbvswWvFGbS2f6e+jC/6WJm1Dl0w==",
            "dev": true,
            "dependencies": {
                "@alloc/quick-lru": "^5.2.0",
                "arg": "^5.0.2",
                "chokidar": "^3.5.3",
                "didyoumean": "^1.2.2",
                "dlv": "^1.1.3",
                "fast-glob": "^3.3.0",
                "glob-parent": "^6.0.2",
                "is-glob": "^4.0.3",
                "jiti": "^1.21.0",
                "lilconfig": "^2.1.0",
                "micromatch": "^4.0.5",
                "normalize-path": "^3.0.0",
                "object-hash": "^3.0.0",
                "picocolors": "^1.0.0",
                "postcss": "^8.4.23",
                "postcss-import": "^15.1.0",
                "postcss-js": "^4.0.1",
                "postcss-load-config": "^4.0.1",
                "postcss-nested": "^6.0.1",
                "postcss-selector-parser": "^6.0.11",
                "resolve": "^1.22.2",
                "sucrase": "^3.32.0"
            },
            "bin": {
                "tailwind": "lib/cli.js",
                "tailwindcss": "lib/cli.js"
            },
            "engines": {
                "node": ">=14.0.0"
            }
        },
        "node_modules/tailwindcss/node_modules/postcss-selector-parser": {
            "version": "6.1.2",
            "resolved": "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.1.2.tgz",
            "integrity": "sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg==",
            "dev": true,
            "dependencies": {
                "cssesc": "^3.0.0",
                "util-deprecate": "^1.0.2"
            },
            "engines": {
                "node": ">=4"
            }
        },
        "node_modules/tar-fs": {
            "version": "3.0.6",
            "resolved": "https://registry.npmjs.org/tar-fs/-/tar-fs-3.0.6.tgz",
            "integrity": "sha512-iokBDQQkUyeXhgPYaZxmczGPhnhXZ0CmrqI+MOb/WFGS9DW5wnfrLgtjUJBvz50vQ3qfRwJ62QVoCFu8mPVu5w==",
            "dependencies": {
                "pump": "^3.0.0",
                "tar-stream": "^3.1.5"
            },
            "optionalDependencies": {
                "bare-fs": "^2.1.1",
                "bare-path": "^2.1.0"
            }
        },
        "node_modules/tar-stream": {
            "version": "3.1.7",
            "resolved": "https://registry.npmjs.org/tar-stream/-/tar-stream-3.1.7.tgz",
            "integrity": "sha512-qJj60CXt7IU1Ffyc3NJMjh6EkuCFej46zUqJ4J7pqYlThyd9bO0XBTmcOIhSzZJVWfsLks0+nle/j538YAW9RQ==",
            "dependencies": {
                "b4a": "^1.6.4",
                "fast-fifo": "^1.2.0",
                "streamx": "^2.15.0"
            }
        },
        "node_modules/text-decoder": {
            "version": "1.1.1",
            "resolved": "https://registry.npmjs.org/text-decoder/-/text-decoder-1.1.1.tgz",
            "integrity": "sha512-8zll7REEv4GDD3x4/0pW+ppIxSNs7H1J10IKFZsuOMscumCdM2a+toDGLPA3T+1+fLBql4zbt5z83GEQGGV5VA==",
            "dependencies": {
                "b4a": "^1.6.4"
            }
        },
        "node_modules/thenify": {
            "version": "3.3.1",
            "resolved": "https://registry.npmjs.org/thenify/-/thenify-3.3.1.tgz",
            "integrity": "sha512-RVZSIV5IG10Hk3enotrhvz0T9em6cyHBLkH/YAZuKqd8hRkKhSfCGIcP2KUY0EPxndzANBmNllzWPwak+bheSw==",
            "dev": true,
            "dependencies": {
                "any-promise": "^1.0.0"
            }
        },
        "node_modules/thenify-all": {
            "version": "1.6.0",
            "resolved": "https://registry.npmjs.org/thenify-all/-/thenify-all-1.6.0.tgz",
            "integrity": "sha512-RNxQH/qI8/t3thXJDwcstUO4zeqo64+Uy/+sNVRBx4Xn2OX+OZ9oP+iJnNFqplFra2ZUVeKCSa2oVWi3T4uVmA==",
            "dev": true,
            "dependencies": {
                "thenify": ">= 3.1.0 < 4"
            },
            "engines": {
                "node": ">=0.8"
            }
        },
        "node_modules/through": {
            "version": "2.3.8",
            "resolved": "https://registry.npmjs.org/through/-/through-2.3.8.tgz",
            "integrity": "sha512-w89qg7PI8wAdvX60bMDP+bFoD5Dvhm9oLheFp5O4a2QF0cSBGsBX4qZmadPMvVqlLJBBci+WqGGOAPvcDeNSVg=="
        },
        "node_modules/tiny-emitter": {
            "version": "2.1.0",
            "resolved": "https://registry.npmjs.org/tiny-emitter/-/tiny-emitter-2.1.0.tgz",
            "integrity": "sha512-NB6Dk1A9xgQPMoGqC5CVXn123gWyte215ONT5Pp5a0yt4nlEoO1ZWeCwpncaekPHXO60i47ihFnZPiRPjRMq4Q=="
        },
        "node_modules/tinymce": {
            "version": "7.3.0",
            "resolved": "https://registry.npmjs.org/tinymce/-/tinymce-7.3.0.tgz",
            "integrity": "sha512-Ls4PgYlpk73XAxBSBqbVmSl8Mb3DuNfgF01GZ0lY6/MOEVRl3IL+VxC1Oe6165e8WqbqVsxO3Qj/PmoYNvQKGQ=="
        },
        "node_modules/to-regex-range": {
            "version": "5.0.1",
            "resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz",
            "integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==",
            "dev": true,
            "dependencies": {
                "is-number": "^7.0.0"
            },
            "engines": {
                "node": ">=8.0"
            }
        },
        "node_modules/ts-interface-checker": {
            "version": "0.1.13",
            "resolved": "https://registry.npmjs.org/ts-interface-checker/-/ts-interface-checker-0.1.13.tgz",
            "integrity": "sha512-Y/arvbn+rrz3JCKl9C4kVNfTfSm2/mEp5FSz5EsZSANGPSlQrpRI5M4PKF+mJnE52jOO90PnPSc3Ur3bTQw0gA==",
            "dev": true
        },
        "node_modules/tslib": {
            "version": "2.7.0",
            "resolved": "https://registry.npmjs.org/tslib/-/tslib-2.7.0.tgz",
            "integrity": "sha512-gLXCKdN1/j47AiHiOkJN69hJmcbGTHI0ImLmbYLHykhgeN0jVGola9yVjFgzCUklsZQMW55o+dW7IXv3RCXDzA=="
        },
        "node_modules/tweetnacl": {
            "version": "1.0.3",
            "resolved": "https://registry.npmjs.org/tweetnacl/-/tweetnacl-1.0.3.tgz",
            "integrity": "sha512-6rt+RN7aOi1nGMyC4Xa5DdYiukl2UWCbcJft7YhxReBGQD7OAM8Pbxw6YMo4r2diNEA8FEmu32YOn9rhaiE5yw=="
        },
        "node_modules/unbzip2-stream": {
            "version": "1.4.3",
            "resolved": "https://registry.npmjs.org/unbzip2-stream/-/unbzip2-stream-1.4.3.tgz",
            "integrity": "sha512-mlExGW4w71ebDJviH16lQLtZS32VKqsSfk80GCfUlwT/4/hNRFsoscrF/c++9xinkMzECL1uL9DDwXqFWkruPg==",
            "dependencies": {
                "buffer": "^5.2.1",
                "through": "^2.3.8"
            }
        },
        "node_modules/undici-types": {
            "version": "6.19.8",
            "resolved": "https://registry.npmjs.org/undici-types/-/undici-types-6.19.8.tgz",
            "integrity": "sha512-ve2KP6f/JnbPBFyobGHuerC9g1FYGn/F8n1LWTwNxCEzd6IfqTwUQcNXgEtmmQ6DlRrC1hrSrBnCZPokRrDHjw==",
            "optional": true
        },
        "node_modules/universalify": {
            "version": "2.0.1",
            "resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.1.tgz",
            "integrity": "sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==",
            "engines": {
                "node": ">= 10.0.0"
            }
        },
        "node_modules/update-browserslist-db": {
            "version": "1.1.0",
            "resolved": "https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.1.0.tgz",
            "integrity": "sha512-EdRAaAyk2cUE1wOf2DkEhzxqOQvFOoRJFNS6NeyJ01Gp2beMRpBAINjM2iDXE3KCuKhwnvHIQCJm6ThL2Z+HzQ==",
            "dev": true,
            "funding": [
                {
                    "type": "opencollective",
                    "url": "https://opencollective.com/browserslist"
                },
                {
                    "type": "tidelift",
                    "url": "https://tidelift.com/funding/github/npm/browserslist"
                },
                {
                    "type": "github",
                    "url": "https://github.com/sponsors/ai"
                }
            ],
            "dependencies": {
                "escalade": "^3.1.2",
                "picocolors": "^1.0.1"
            },
            "bin": {
                "update-browserslist-db": "cli.js"
            },
            "peerDependencies": {
                "browserslist": ">= 4.21.0"
            }
        },
        "node_modules/urlpattern-polyfill": {
            "version": "10.0.0",
            "resolved": "https://registry.npmjs.org/urlpattern-polyfill/-/urlpattern-polyfill-10.0.0.tgz",
            "integrity": "sha512-H/A06tKD7sS1O1X2SshBVeA5FLycRpjqiBeqGKmBwBDBy28EnRjORxTNe269KSSr5un5qyWi1iL61wLxpd+ZOg=="
        },
        "node_modules/util-deprecate": {
            "version": "1.0.2",
            "resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
            "integrity": "sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==",
            "dev": true
        },
        "node_modules/vite": {
            "version": "4.5.3",
            "resolved": "https://registry.npmjs.org/vite/-/vite-4.5.3.tgz",
            "integrity": "sha512-kQL23kMeX92v3ph7IauVkXkikdDRsYMGTVl5KY2E9OY4ONLvkHf04MDTbnfo6NKxZiDLWzVpP5oTa8hQD8U3dg==",
            "dev": true,
            "dependencies": {
                "esbuild": "^0.18.10",
                "postcss": "^8.4.27",
                "rollup": "^3.27.1"
            },
            "bin": {
                "vite": "bin/vite.js"
            },
            "engines": {
                "node": "^14.18.0 || >=16.0.0"
            },
            "funding": {
                "url": "https://github.com/vitejs/vite?sponsor=1"
            },
            "optionalDependencies": {
                "fsevents": "~2.3.2"
            },
            "peerDependencies": {
                "@types/node": ">= 14",
                "less": "*",
                "lightningcss": "^1.21.0",
                "sass": "*",
                "stylus": "*",
                "sugarss": "*",
                "terser": "^5.4.0"
            },
            "peerDependenciesMeta": {
                "@types/node": {
                    "optional": true
                },
                "less": {
                    "optional": true
                },
                "lightningcss": {
                    "optional": true
                },
                "sass": {
                    "optional": true
                },
                "stylus": {
                    "optional": true
                },
                "sugarss": {
                    "optional": true
                },
                "terser": {
                    "optional": true
                }
            }
        },
        "node_modules/vite-plugin-full-reload": {
            "version": "1.2.0",
            "resolved": "https://registry.npmjs.org/vite-plugin-full-reload/-/vite-plugin-full-reload-1.2.0.tgz",
            "integrity": "sha512-kz18NW79x0IHbxRSHm0jttP4zoO9P9gXh+n6UTwlNKnviTTEpOlum6oS9SmecrTtSr+muHEn5TUuC75UovQzcA==",
            "dev": true,
            "dependencies": {
                "picocolors": "^1.0.0",
                "picomatch": "^2.3.1"
            }
        },
        "node_modules/which": {
            "version": "2.0.2",
            "resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz",
            "integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==",
            "dev": true,
            "dependencies": {
                "isexe": "^2.0.0"
            },
            "bin": {
                "node-which": "bin/node-which"
            },
            "engines": {
                "node": ">= 8"
            }
        },
        "node_modules/wrap-ansi": {
            "version": "8.1.0",
            "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-8.1.0.tgz",
            "integrity": "sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ==",
            "dev": true,
            "dependencies": {
                "ansi-styles": "^6.1.0",
                "string-width": "^5.0.1",
                "strip-ansi": "^7.0.1"
            },
            "engines": {
                "node": ">=12"
            },
            "funding": {
                "url": "https://github.com/chalk/wrap-ansi?sponsor=1"
            }
        },
        "node_modules/wrap-ansi-cjs": {
            "name": "wrap-ansi",
            "version": "7.0.0",
            "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz",
            "integrity": "sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==",
            "dev": true,
            "dependencies": {
                "ansi-styles": "^4.0.0",
                "string-width": "^4.1.0",
                "strip-ansi": "^6.0.0"
            },
            "engines": {
                "node": ">=10"
            },
            "funding": {
                "url": "https://github.com/chalk/wrap-ansi?sponsor=1"
            }
        },
        "node_modules/wrap-ansi-cjs/node_modules/ansi-regex": {
            "version": "5.0.1",
            "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
            "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
            "dev": true,
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/wrap-ansi-cjs/node_modules/ansi-styles": {
            "version": "4.3.0",
            "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
            "integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
            "dev": true,
            "dependencies": {
                "color-convert": "^2.0.1"
            },
            "engines": {
                "node": ">=8"
            },
            "funding": {
                "url": "https://github.com/chalk/ansi-styles?sponsor=1"
            }
        },
        "node_modules/wrap-ansi-cjs/node_modules/color-convert": {
            "version": "2.0.1",
            "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
            "integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
            "dev": true,
            "dependencies": {
                "color-name": "~1.1.4"
            },
            "engines": {
                "node": ">=7.0.0"
            }
        },
        "node_modules/wrap-ansi-cjs/node_modules/color-name": {
            "version": "1.1.4",
            "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz",
            "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==",
            "dev": true
        },
        "node_modules/wrap-ansi-cjs/node_modules/emoji-regex": {
            "version": "8.0.0",
            "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz",
            "integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==",
            "dev": true
        },
        "node_modules/wrap-ansi-cjs/node_modules/string-width": {
            "version": "4.2.3",
            "resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
            "integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
            "dev": true,
            "dependencies": {
                "emoji-regex": "^8.0.0",
                "is-fullwidth-code-point": "^3.0.0",
                "strip-ansi": "^6.0.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/wrap-ansi-cjs/node_modules/strip-ansi": {
            "version": "6.0.1",
            "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
            "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
            "dev": true,
            "dependencies": {
                "ansi-regex": "^5.0.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/wrap-ansi/node_modules/ansi-styles": {
            "version": "6.2.1",
            "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-6.2.1.tgz",
            "integrity": "sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug==",
            "dev": true,
            "engines": {
                "node": ">=12"
            },
            "funding": {
                "url": "https://github.com/chalk/ansi-styles?sponsor=1"
            }
        },
        "node_modules/wrappy": {
            "version": "1.0.2",
            "resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz",
            "integrity": "sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ=="
        },
        "node_modules/ws": {
            "version": "8.18.0",
            "resolved": "https://registry.npmjs.org/ws/-/ws-8.18.0.tgz",
            "integrity": "sha512-8VbfWfHLbbwu3+N6OKsOMpBdT4kXPDDB9cJk2bJ6mh9ucxdlnNvH1e+roYkKmN9Nxw2yjz7VzeO9oOz2zJ04Pw==",
            "engines": {
                "node": ">=10.0.0"
            },
            "peerDependencies": {
                "bufferutil": "^4.0.1",
                "utf-8-validate": ">=5.0.2"
            },
            "peerDependenciesMeta": {
                "bufferutil": {
                    "optional": true
                },
                "utf-8-validate": {
                    "optional": true
                }
            }
        },
        "node_modules/y18n": {
            "version": "5.0.8",
            "resolved": "https://registry.npmjs.org/y18n/-/y18n-5.0.8.tgz",
            "integrity": "sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==",
            "engines": {
                "node": ">=10"
            }
        },
        "node_modules/yaml": {
            "version": "2.5.0",
            "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.5.0.tgz",
            "integrity": "sha512-2wWLbGbYDiSqqIKoPjar3MPgB94ErzCtrNE1FdqGuaO0pi2JGjmE8aW8TDZwzU7vuxcGRdL/4gPQwQ7hD5AMSw==",
            "dev": true,
            "bin": {
                "yaml": "bin.mjs"
            },
            "engines": {
                "node": ">= 14"
            }
        },
        "node_modules/yargs": {
            "version": "17.7.2",
            "resolved": "https://registry.npmjs.org/yargs/-/yargs-17.7.2.tgz",
            "integrity": "sha512-7dSzzRQ++CKnNI/krKnYRV7JKKPUXMEh61soaHKg9mrWEhzFWhFnxPxGl+69cD1Ou63C13NUPCnmIcrvqCuM6w==",
            "dependencies": {
                "cliui": "^8.0.1",
                "escalade": "^3.1.1",
                "get-caller-file": "^2.0.5",
                "require-directory": "^2.1.1",
                "string-width": "^4.2.3",
                "y18n": "^5.0.5",
                "yargs-parser": "^21.1.1"
            },
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/yargs-parser": {
            "version": "21.1.1",
            "resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.1.1.tgz",
            "integrity": "sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw==",
            "engines": {
                "node": ">=12"
            }
        },
        "node_modules/yargs/node_modules/ansi-regex": {
            "version": "5.0.1",
            "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
            "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/yargs/node_modules/emoji-regex": {
            "version": "8.0.0",
            "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz",
            "integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A=="
        },
        "node_modules/yargs/node_modules/string-width": {
            "version": "4.2.3",
            "resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz",
            "integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==",
            "dependencies": {
                "emoji-regex": "^8.0.0",
                "is-fullwidth-code-point": "^3.0.0",
                "strip-ansi": "^6.0.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/yargs/node_modules/strip-ansi": {
            "version": "6.0.1",
            "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
            "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
            "dependencies": {
                "ansi-regex": "^5.0.1"
            },
            "engines": {
                "node": ">=8"
            }
        },
        "node_modules/yauzl": {
            "version": "2.10.0",
            "resolved": "https://registry.npmjs.org/yauzl/-/yauzl-2.10.0.tgz",
            "integrity": "sha512-p4a9I6X6nu6IhoGmBqAcbJy1mlC4j27vEPZX9F4L4/vZT3Lyq1VkFHw/V/PUcB9Buo+DG3iHkT0x3Qya58zc3g==",
            "dependencies": {
                "buffer-crc32": "~0.2.3",
                "fd-slicer": "~1.1.0"
            }
        },
        "node_modules/zod": {
            "version": "3.23.8",
            "resolved": "https://registry.npmjs.org/zod/-/zod-3.23.8.tgz",
            "integrity": "sha512-XBx9AXhXktjUqnepgTiE5flcKIYWi/rme0Eaj+5Y0lftuGBq+jyRu/md4WnuxqgP1ubdpNCsYEYPxrzVHD8d6g==",
            "funding": {
                "url": "https://github.com/sponsors/colinhacks"
            }
        }
    }
}
(h
pk

	����̷��(i
�0evector"�0��0
�0�DF���λ�N<���h�<w��;�)|�����,��rL<�>�=ކ-<#��O镼)��<-k�<�!w�(rݼ���A�<6�=i���=��.�͓L�^�<�$��a��=h�=��5�&�I=Y#⼚�<�-�<���e|@<)�@=�'
��f<Juy<_^�<;����4�;>����߼�^
� �W�s�{<��G�\�=���+����_�(c=���]�\�Xv��1=0��<�1��͟=�c���\��a�����u�x<c_���t<��+="C�1�<.��<<
k�CƗ�7�<���Ff<���=dϻb�?��΂�u4=����*��7�t�QU��ʍ.�i�G���d�oj=<�݄��%��K�p��<���<U��Qr�X���>3~��+P=Q>C=i$�s�^���T;@G'=�F�<���<�D.�8��D�<�A��<�<�⫼�q�<��z<,F,�͸��"}=͌Ҽۚȼ�bؼLA�;}�=Q׻y{�<���'��hnѻ��?�k�)�o��<a"�;��s=���&�	��\����ༀ��:��Ƽ�=;�`�[�9��=�ĝ;�T:���[����;��<�ǚ�tү<c�w;	;p�)һ�.<U��򫁽��=�Y=���֥P��%|���9<<J輈��:c���Jڔ��\e���A<���g���p=F�W��3"��U<Ễ<ك'���=�x�Ԍ�,�<ZDk<�=�G;�P�+�>׉�����">�<�/=�<�6<"�˻�F�<k+T=� �<�w=������<2��E��;:6m<���=�<N�@=��1�M
1����&�/����2;I��p��<�b�<,�>��<~䣻	賻�e<��e���};��c��{'��T=�#�=Ђ\;�12<��<�A<���6�G<o��<ȕ!<Iƫ<���$�;Z;H��6�:�d��;]X������R��
����<ҏ�<��<�L�<h���!�D�>��`y;���<�a�<i�<�K@��c��V�d�{����<Y$���!�<B��ߥ<�5$��;=�2��4�;�_w<E�=x��;U��鲆=J�=��=0P-�Xd��X4x<W���Y�=�㈽�!=Wrּ�b<�X<.�<lm�98=�";���ܬ=(�ǻD<9U���<a�a��[&=S!�:l�=�F����;�p��:'=�r����;<��w��=H3s<"�ʻ�<T><}
޼	л���\fo�&�ȞҼؕ���P����:��?=nO���0<F ��=�2�<c�.<x�;�`�<����(n�;��93��������<��=�,<bH�����"�;��"��8�<!"��雽��Ǽ�>����<�r���Y::�'�!L<v)�;�`6�M�_<!����< �9������
<�^������<^'��f=~.���樼��C<���<kq��q'=��9�$E�@�=E��<e�񻕏p�����&<���?=���<�m=���<�N;�
�����<@ű���>;Ł3��o<��W<��=���>S������<:��: �=�JP�%j�;L�Ҽ3F2=�=���l҉;sG(<(.�<s�E=0b?=����SI;��ߘ<C[�;�;!����<B�\�xaM=�M%���<=�2=�W�C���
��<O�Rr���+=r�=������;h&ļt$&�d���ϸ=�<��B�<.[Z��y�J��<yD;�'�;�ٞ�0FF�Ax�>v)<a�� �0:�g�O'��/��XV���qѼ�p�x�=
�O���滔�<=�s���x=��N;O�D=��
=�aU���;�G=����ZG��z<��b=
]�<�54=I�d�[H~�U�׼����T��7<�����<p`ڼ
��CK��k��Mx�)ܫ�0��=�=̼2w�W�;�p�<K�ͺ���<o�<^���e	<,E=gѼ����y���z��kaK=΄�C!p��]=�C���1����<秨��_���K�;��N;_]��h�;=A���μ��	=-�/��@&=gՈ;�M�;�?�;n$��{<d�1;�5ּ���k<��	RɼZN��lz=��� �a��D����d �<E�]<ꤼȬ�<���QQ<��=�hi����<}���C�=9<q��<V���`mu<y��<�L-�=M�"�~�b<w����<,���q�p�:H�<Td6=�+��H=1�X;�@��K=�_
=ut�<{`�W��;0�������J�<x�</r+�]t���żq��:��"������`�><_�h;�m��K�%=d��<a�z��M�;��;'�<��<R氺-�5<�W;j2�:�)=�u�8�/�f��4��j����L:�b�<�DA�hν��V�<�V��ᆼ��=(�;Z��<�T���C�8�缻.b<�қ:�r���	<��������T��
���j�Ļ�s=+�<1P8�X�L�����IV�;P����
�<д�<�9�;B�v����;S��<���<��K<c�{�j<15#<zZ{<� м+�<�@�撣�P@ =l�y�<�P����D?)��e��@�<�(�<Gan���
��B��=�5���&=r	8����<�#�ދ<�+"��<��:=g��;
��<�M�;�}�;�=�HT=p8�<�M=fI��PB��j�l�3���
^�<�Fb<>y=��e���|�f^�<�RC� 9;<�5�<ϛ�<�3���+<�I;��
=K�:ֽ�<�=�u�<��<�༪A���sлo.;l�'��^�Q����1����N=�D�;YD=����5.���:8E>�Uz��:�:���=PY�:-$�-O���8~����mV����9G@���Mx<I�����<{W��]
<#�<�=�
��3}0������=h���
=�-��"=�cϻ�*^��Z:o<\����EJ��>�=XH�g.m<n���e	=<WY����?�;7������:�fF<A=<X��<��<%��<Չ�o?�<D�4<ڷ�<�I���ޝ�\Q�)�:BGպ�u�X�;:��;676=`ٻ��=�#b�@��>�Q�����10��4m���N���������^��
5�����¼
��š���'<�;��к͒�����x��i��4R�:k?�
��㺘<.��;��=g��:��:~�<+�;)�n�_P��o�9<n�����=R?�o1`<�_v��Q���<�����2=J���<
�<K��;�����<q�껮�.<�^d<�E�<4�Ӻ�������<�����[�<<@k<<�-<�~�4�9��D[��n};@�a;�}��}T�;���Wy<!x��%��u�<�qO���@<4����;ҥ<�1=�v.�<\b��\7<�s̻��?��3�<�Pr�A�B���[�rav<}�&�����E{<6��<�L/;Շ/�j�I<�����Nn���;�r.���i=M���Gl@<A��Ͽ�;�����B���i�<��<��#<f?=$�9<q̲<�0���s���;�a�<��=�����<�=`$D�qn��߯�+��<~�v���/$üʿ�<���<ꁼ�c�+��q�;3P��%�9��ع�����*�<��꺳g<V�a<����<m���@��<�C<�J�ZO����ԼO+�<�м��̻���0�F=������<\�}:x1�x�F<���;3��y�<�e��D<��;"���а�<����^ͻ��_=x�ͼ}$��3�6=&�P�Ÿ=��~���n�&��6�����<J;��:`��JU;�lG�<⫼5!ۼh?h�~'ɺ��<��Ⱥ�֒<���w�<��=�d�<;�=�=-�<����>�=<J���t�b;?��<"a`=�0<=M�<�E�<f}����<�v�<w�/=�7l;��<j�`�H���o�;(1<�E=���<ܪb=V=�F= b�X;���<�?p�|t�;�,�<rN�<h�ӹ�$f=��¼d"�<c�	��2�<4��<�5�;8;�����;��<$�/<>�=�o<��?���	=��<�P��I�;K<�;����:����<���<ౖ��I%:�	=>��;�h庄<����^6s<9�r���]:\n�;r��
�<���;�?��y����<���<��:@���h;N+y<u=H#��}�=ZL!<��)<$	»;����5�|ê�q������<�^�<�v<m�e��]�<c(�;�/="�D��=J<����
�����?;�����	�`���͒�aa1;p����T������B
�M	��ꆻpb��-���C��rwE�Ҙ��*��7�����<W݊<sf';l悼�=@;<�mB<�����6���|9�~k]��)��q���R<� ����:'��;�Q=�H��\-���I̺�ߖ</6<D0/<��><T��:����W�@<��R�L<�<EB�:R��<Y໼��&<	N=j�%���:�\.��L���j�zа��ֆ<)
<�;ٻ2�l<k��<�w���;`#�<T����׼#ʾ=��%</��I}=��F<6��_-�3k<�%�<���uQm��=$=Xr�;d�<���v<V`�<
»��$<��
=[��<��q�b�B��V<�ϕ�iz_�w�~<�� =�<#<���1����NC<�sH���<B�Իb�n;`�<z���;�d����q�7�𻏌��
4��D��:,~�<z�Ϻn�^:�⼼tw�<��Z;f���Y��;	�{;xɀ<�8z=f�	=Nsr<2ͼk��;�ӝ�	�)��Q<����
<]�ݻg�Ta=ڳܺ��ƻ�&�:�;`;�ʹ;66?<<	�<��;t"�<-c�Բ���G~�z�O<K�S=�(�{�μǟ�;j1��FἫ�<=
H;��9k�<�F�<��h<�(�;M�ͼM;<AÈ<I=���<�g<���*�:���(芼�ꇼu�	�Z}<��;0E%;m/<Z��<*����張q;"~8:␼�1��
W��=?;��@��.�Ql��(�@5���X���o;�,<^ub;ѭK<_�T;F9<0ݐ���5<�3l�%I=b��.��鼈�a6<��B��cO=��&=�ޮ����;+V0�;y�<UA�;NM�����Ӊ<1r<d(��b�?�<�������;�]Լ0{м��P��i�<�jT�Yn�<R��ޛ^���;�(һ�;�M<\_�Ҁ�����;�խ<��{��ݩ�1�R<��=;��;�m�������D$;k_<!�i�ɠ��@#�dvs�Ip;y�q���?��:Ԧ<�&=`A�ーl�4<.�����=�-����F����<�1�<;��Ï%���D�Q�x<��׻~������R?����;���<BG=;1���u&��=�u���F4��w[��+��1�<�+���:�_��<�Q<؁���;_�a<8�O�-�;n�^�&ҼA�E=�Х�	+v<F�<���;=V�׬�����JI��k�<�>�,=�$�<O<OoŻ*k<3~I�(�<;���N�������	��<H�0��m�<}�ջ��<Bp�:	�X<���<���<t
�:1�y<����+Tż=TB��蛼;��<v��+13<���<�&�<�*k< \<ic��;�����=�#�<���𿬺)R�<�=�;F�7�Px�<�Ǡ<��<�Ҍ<=�Z�ٱм8?��|�L�<%�L<��N<ƭ�<�żd�^�><�4h<��<#������}!=:9�;4��1f�<�� =��q;!ˉ<x����I�;h�<�`���y0=��g<��һ�a�;Z����=^��;�T��'}ϻ����ü�<*��<���:��#�r�K�v=�{;�=B=
�u��{O;4<�<����@�k���<��-�o�����<��<H��qJ��?��;���;A� =$?���s<Q5��l�:���;��Ữ	f;�)*�'Y��<E�:<4J���wb;�w;���<-=k=};8�Ǽ�
 ��:����f��F�̪
<�ǝ�ُC��4���̺����Z?�<!P���<d�<�i���k���]<,���V<(j
RowID

	����̷��
	Timestamp

	ه��̷��(


milvus_id: 452165072252045246
data:
source2
package.json(d
!	file_path2
package.json(e
!	file_name2
package.json(f
	file_type	2
.json(g
�
text�
2�

�
{
    "private": true,
    "type": "module",
    "scripts": {
        "dev": "vite",
        "build": "vite build"
    },
    "devDependencies": {
        "@tailwindcss/forms": "^0.5.2",
        "@tailwindcss/typography": "^0.5.0",
        "autoprefixer": "^10.4.7",
        "axios": "^1.1.2",
        "create-vite": "^4.4.1",
        "daisyui": "^4.7.2",
        "flowbite-typography": "^1.0.3",
        "laravel-vite-plugin": "^0.8.0",
        "postcss": "^8.4.14",
        "tailwindcss": "^3.1.0",
        "vite": "^4.0.0"
    },
    "dependencies": {
        "@alpinejs/collapse": "^3.13.5",
        "@alpinejs/focus": "^3.13.2",
        "alpinejs": "^3.13.5",
        "animate.css": "^4.1.1",
        "aos": "^2.3.4",
        "apexcharts": "^3.49.2",
        "autoprefixer": "^10.4.15",
        "clipboard": "^2.0.11",
        "crisp-sdk-web": "^1.0.25",
        "flowbite": "^1.8.1",
        "intl-tel-input": "^18.2.1",
        "ion-rangeslider": "^2.3.1",
        "jquery": "^3.7.1",
        "jsbarcode": "^3.11.6",
        "laravel-echo": "^1.16.1",
        "lodash": "^4.17.21",
        "postcss": "^8.4.30",
        "preline": "^2.4.1",
        "puppeteer": "^22.12.1",
        "pusher-js": "^8.4.0-rc2",
        "sweetalert2": "^11.6.13",
        "tailwindcss": "^3.3.3",
        "tinymce": "^7.0.0"
    }
}
(h
pk

	����̷��(i
�0evector"�0��0
�0Qz2�l?��6K-=�A0���e<������'��7��J��MJ�&�	<D�9;�̻�C�tG?<��7=R���,鼠,�4W=]=�9���<��y[ļ�<XӸ�a�U=�Q=�z�o�%�7d��)��<�6�ğ���&;̓=c\����=0�&<���<
%��tM<,<u���6K��*HJ���=�����<kP<�_�qS���c�=��v;�,#�����<�=�rV=x�=تM�j�J;���<U~J���<"�����q<]H��X�<�����˼�p߼�߷<�ͻѻo;��=�+^<<��L�A:��<7d�;��{���.������N�<^aS���=U�r�"@���@n����<޾�<4��<����s¼�U5�
��<戉=9
D;�
�9k<	V=�p�<I�=!��q�����k<�u��2�Q�b��<�Ę;�B��-+��U�<+X7=ݥ�vc�Qz2:�C<1�P=�k���M<�V!=���������1�ȣR��Y<�>��L1�=F����	<.�;�4�#��<�?c��
Q=�>�<�^���_�=�܋<V�˹�:OE<'�ǻb^����:�����<�\���=<6K��*HJ��BF=MJ�<�/�����g������z��9���|4�-3���	�����ց��r>�Pj�<*��������;�͊=Y����{r��1����;5ї<=����'=}*ȼ�Ts;0��������d�<9k=�)9�>�;��@���<R��<Պ�;�&=�u���:B"�<b��<V$<_}��q�~oI<ʳ��=o��J̼s��$��;=o�:�(��/�-h�<\�P�P�=󤾻
�¼�7�<H̽<��=�r�<5pԼ�_��Mv�=�T�,#�<�=!e�<K�Y��:�W
=$�m���λ,<u��7�<�`ȼ[Ay�����9hD�;!�wg�<�-�;b�.<�1C<]��<5pT<��ܼğ��F�<۞x<މ>=N%D7��<��"�%4�<9?X���'���<������<d@ļ��<�L<|{=]H�)� =�8=�}?= @;+X7��i�<
:�<���<��@�uW�<]<�T�-��<�!
��ڔ=����������`=���;ͷW=���5�=b��<�&<��0=
�|=��k;� K����<��=�8=y[D<��W<�x��Ԥ<t��B=����
�<��<�-U<�<�<����u�h<�3<�{ȼ.���#��}�����w0;�+=A>#���<�_;���<���<������?<��=��o��~=x�k��=;ߙ+�>���D��<'(p<��?����Z�w=�
ϻIܪ<y�켄N:�B�L��EH���<�yѻ�Sh���I���<��<�r��ԅ�4�|�^aS�(�aU~;������Ż�M�R��<�I`9���<{����7<�9=�F�<��Ӽ:�<��<�I�p��<�{�<�۟<���;�(��̼y[ļ���<&=1�кX�$=�<�	<8&�;_�;|{��:�;b�:Ï�<�[=8[=X�$<�1m�,<�l�<�p5<qS�<U"�	!<צ���=���<y�l��gm<y��<��;mX�<�M/���?<uW,����<Q
�U�<oɑ��\�;m�:_=��/�Xi=�JL<� ˼�댻��4��I���ǼN���ѻo=�
�����]H�����;Ir��5[=�Y�Kv<��b���k�<��-=9k�7F�<��U<���J!,�q����%���
ϼ�`���(���D�(mq���2=�kۻ����<ȣҼ�><�Ę;(=R��<�2�<�=�r�0�&��)==X�$;`�=���<��X=��$���<E
�<U�
�Uߍ�⹅�F�<�V-�:�,i� ��(��@č;��k�L����;;��:�"��=]����`Ȼ��1<1�<PjE<-3�;F��qj��;�<�g�<���]H�pC';~���T*=���!0��ͷW=��1=FR(=B�8=�Yͻ�Ѣ�5����s���y��<Qo��^�;�-�<�K���ct=�瞻��@�Wru�ź5;@�;�"�������;)d����(��"�<F�d�tG�9��e��������<bƮ;�~;vc=&D��l��<�/=�h�۞�:�n>��\�<?cJ�]���\��.�<YMN= @�&�뫻y��<q�<b^<��M������<:OE=�5�pC�<��l༣�=y[D<��=��z�f��<�V���N���tͼ���<�B�XӸ��@��
ϼN��;@��:mX�^����;�(�<�b?��D�<|�2=TϠ<�<�@�;�=Т=9?ؼk�<���)�4<U;As�<�།ǚ�uW����6���<�~+<���󤾻(=#�̞��� !=b��<��<�sB�l`�#$ؼq���;
�B�
:T<�Ə�U�
�uW,�=�<`҃<��"<6�<n3�<v㼍��-3<uW,��(=��=6ᄼm�<�+4����<��=�F}���I�O���5�<<�	=�=����;��:"u��i�]=�9*<Ԧ����;.x�<����=xKW<�M�1b�a�U:�2���3=�Y��.N<%���\<����<�>M<d@�<�;���:�x����1=�Y�<�Z=ߙ+=����ױ<p�O�r�;aU�<��o<�S�<g+��Z(�<eP1<����px;<_��<�\Z;eP���ә<�1m<_�;̞�<E��:�ԅ<�<�=?�^<sͩ<Y�v��d�q��<F�d�}��"�;}*H=i�<Q�<c\�Ҳ
�ȣ�;��(�u�@��+��|O��9*�F��;������;�VY#�6��<H�)�q'e���n�^�*<lt�:	��<�ţ;m�<#�C<���<�W��V�7<5��4W=����B"�;�ǚ�p<`����4�*<6K-9���`�<?cJ<F)<~oI�.x�;⹅��)<9������n��]�9�LC<&��:��j=d@D=�h;�gC���<j<�5:��<E
'�9k<)I<\����L������;Z�=e�Y�6����������Ҳ��rl�vc��
�:��<���;�r�<MJ�<,������U"��j������08�V��<MA�<w2<sͩ���_{;ݥ�^aӼ��k��'F=�;�<	!�<�:�<'��<H-=QE��-U�K�չ"��3=�	���<U"<4����<���|�<�5���Pˈ�~��84W�<�����<�������1l�<���/��<��<Y:;1b=�73�̓�u��;�/����<��<��<�͊�=�����r�<��)��\0<>S�<M�����=Ǌ�</';��<�vn<�l<)d���$9<�<�;\�<���<�O��	�*9Ir�;4�|�A	�E:�N�m�<=:����;���O�m����߼���%�=x���Wr��5pT<��T<
�B;� K�.x<�?�<)d���I�<ğ::��λ5;@��h<!Ƅ<���<�a�<�Z;�ױ�1=?cʺ)d<�Ts<�k���"�;ە��p5��-�����;Q�<*ޡ��
����<�����1m<�O�<q��<�Y=�i:�|��<L1=r�����/�q�м�4P��������<��Ҽ'�3=�C�<YM�;��λ�)=�'����<�t���N:�=�;�M/<%4żb��<x�k���6=y[�:۞x��<
�¼u"�V�K=�/=��7��\Z=RU�:�B<«�>Sݼ�z�<�����b =��j<q��<��rK<"@��������1l�<�߷<k��<��</';��c�<��'�l�7=�r�<e��{�<��O��>�<Ԧ�;���b��<�#w=�P;~�q;��,�K�U��6q�GҺ�h�<� !;t|S<�����fW�f�F<�<�a
=l��<#�/=��=�n>=iTɻK�U<�F<�����!�<�K�<rlf��4л���<^�{��
=f�F�Y:=qS�<6�=x�k�[A�:�%���h��ֶ��
���9կ�L��;|Oo��@%�޾�:���<D���q'e<�w0�p�<�\�<�姼�2��,<�<<������;y�=�����_=�?c�<�RҼ�b���vļi� �U"���,=&�n�5�<��;;��5���-=hp=����
f=��μ�&<��#��Ԥ�j:���<���<�WV<�F4=h�=
��;�m�<���;�V�<Ԧ���lG=������	�������2/��-������׺uW�<5��BN��ә��Ԥ���1�ꌡ�.�%�=o�:f�2����;R��;ѻo�`=J�;X���ݥ��n�b=�V!<�t�<���:��;� K:�Z�o�����ܻe��92$<4��&O<څ&<VY#�g8<Xͼ`<��6<;Պ�;�=�]e���C�3���������;|{�<M$<�s��H�<I?�>S�<~oI=��f��#�����}���y�X<��;E�</'����J;�ì:�G =Ư'�3�><�s�;�G�܀���~=%��<ӎ<'�3��s�S���"l��s�<�����s;<�jd��N�<��N�B�8;�3�:1<��<:5=��N�MJ�;�QG���#=!eA��Ε<\���^Ƽ��<�c�<��=x�;�h�e�Y<;��;/';</�w<ż����Q<��켍fW��Â�UI������#�;���~��UI�<R�G�'T<=:�:jd6=����&���<�ㆻ���<1�;MJ�:E�I{�|��;��];*�
���I<�5�<��<��;���;��<9���F�;!eA<�{H�5;�<8[=�A�<z
���4<��;�2x���g�.�<��'=��;~���g<��< ��p��<��;�I�q'e<N�=	�<�Oм}�p�溥l�<�>ͼ��;Y:�6�A�>�<�d����9I{�;:�ټ�ʧ;�m|�F�<hp����';!e���8<�ǻ{	<�=B<���[�;B���������t�EwO��vD<��a<�Nd<[A��6K�<�<Xͼ{��B�'���5,���;��z\;�!
�H�)��s�������;��#;��=#=�������i� =����Y<*HJ�� K��x�<i꠼��u<�7|����<[A�;�,�<�~+��7|���<MA=�w����<������,��T�K�;�m���L;����~����<�l�<9��<Z��;RU=E��<��_����k�9����<H�=<J��%���hڳ�a)�MW��4;��<�D��eP��1b�q=���<�z\���O�t�=X���q��;��~<MJ�<�/�����K�ռ��k;W�:���8+�K�A�K<��f�6<;��2=A�_��Ts�D�<��<�������<b��<"�B�������<���<I���j&<]��<y[Ļ]}�;���<����;=�����/<��<F;�������H-��Iܪ�h�3<B�$�EB;=�:�2x;��׼�	�<��(�9
D=rl�;Mv<*�!��F4���W�H-�k/"=���D�=R^�b�<��:ˎ=���;�n><��!���RҼt�g�U�r<e�E��m�<`q�;Y��<���Ew�<�rV;#�üz
��;��<����V$�<�|}�Q��-3�<vc<�({<��a<6�;Z(���g:5;צ<-3�}��<�&<U�:���:���<�;���<!��vc�;��<(mq�e�E�"@<aU�<���:�=6�<�7����<Dȥ;B�$<�~<�ͻ�9�<F���3=6�ռAs��t�;=\�u��<�V!=P5�<%����!=�F4=
@�I{�<�qj���;��<�&;���;!:!Ƅ;��E;�#����<���m���b�����@<�b�<QE�<�8><�T*<}�������5;��/\�<�F}��v��:r�<�	�f`���:��;\=1l�<��<�#�����5�<`҃��ʧ��M����4�=o��-3��>;�v�;	�:�,�<=ܻ���<�^���-���ɻ��7|<��7���=(j
RowID

	����̷��
	Timestamp

	ه��̷��(


milvus_id: 452165072252045247
data:
source2
phpunit.xml(d
 	file_path2
phpunit.xml(e
 	file_name2
phpunit.xml(f
	file_type2
.xml(g
�text�2�
�<?xml version="1.0" encoding="UTF-8"?>
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:noNamespaceSchemaLocation="vendor/phpunit/phpunit/phpunit.xsd"
         bootstrap="vendor/autoload.php"
         colors="true"
>
    <testsuites>
        <testsuite name="Unit">
            <directory>tests/Unit</directory>
        </testsuite>
        <testsuite name="Feature">
            <directory>tests/Feature</directory>
        </testsuite>
    </testsuites>
    <source>
        <include>
            <directory>app</directory>
        </include>
    </source>
    <php>
        <env name="APP_ENV" value="testing"/>
        <env name="BCRYPT_ROUNDS" value="4"/>
        <env name="CACHE_DRIVER" value="array"/>
        <!-- <env name="DB_CONNECTION" value="sqlite"/> -->
        <!-- <env name="DB_DATABASE" value=":memory:"/> -->
        <env name="MAIL_MAILER" value="array"/>
        <env name="QUEUE_CONNECTION" value="sync"/>
        <env name="SESSION_DRIVER" value="array"/>
        <env name="TELESCOPE_ENABLED" value="false"/>
    </php>
</phpunit>
(h
pk

	����̷��(i
�0evector"�0��0
�0�#����H�(�"=k��.�u<w�j�5 �<�.���5�<�\;�׼?�������D��:�#=Q8�<6�;�R\=5 ����<�F�=���;���ܼ����Y���rG�Ԏ�<:|J=u1̼	{�u���.=�]j���@�'�*:ӷ�<
b�;/u<ol���)�<��;�����囼�8�Ǣ��(��<�i*<�3=�z��	�<ԎP:�W
<�&$<�
�#��;n'��u��<>{;��;!��l��Q�����=a��]<�F��d���_u<؍��$@=5��<�;�3�:sw�=����",8=	�T=���;���;]$�;]=X���=�`���<��*�g���U��A�;��)�����؂<'E��sw��~U�<�^��D�<e�»�H�'E���
e=����w��Ǣ�;?��<��ϻ�Y:%�'�W�(�"�q=�����T��Ƽ�9�<��y<((�<��@=n'}�E�:=�D���F=��)�b�?;�s����<V����7�t�;gb�����<z��<�F=��:=6��<�ᒻ�Ф;к���`�:�(��f;
ͨ<�D���<�}�<�׻��L	�j��<xh=�<h��`�<<pOF�H����	=����S��	=��1L#���2<�^6<y���1ݻ~�����s<��n�r�d�*6�<+\߼*6����<��2<��=�b�o�t</[ ��b��t�����<���n�����mڼl��O�<%T�;�ys�/u����<�H;�ݼ��=�.=�S���;���:wD�ܘ=8H4�'�=j�=6��90X���k�f<?ة;o���W���*<j�<	;��<x��Z:���<���<��<��,;�C���<��Z=��ȼL��O�=ֶ�<�����B<	��o�';:�<J0��>
���Q7<��;U79�$�B@���.<����g9=�]j��O��k�<�k��՜=��S�Ԃ�<oxN<��|����;����I<[�6���;"o˼�_ۼaf�<��_=��\��d	=�(��n�ּ��5<�:�<�=�;�4�+ָ<#����+=���<a#�=��A<���´�<�ȼЃB=3�=s�5<%��'�w�B��m��<ėm<U�_;C����ò9��	=�'c=�ݰ�&ظ�5�<�Tg���.�ɰ9<5 k;�����ЃB<�H�<�f=`L=xe⻬�4=��]��W�<�f����<ؙ޼?�)�>�<�ra�ֶ<�O�<��Q�����U����<j�ȼIY�<�|���;��<�����u���&������=؍��o��_����������=J2�ӷ�8�|=J0��Y/=��Z���9����t����H<dc���;��<��i=}��;���<�{d�BC�!�<%��9WkO��\<x߻;�ڀ;j"<�<\A=��<=*:<~`<I�<?�)��$&<�����%����<{��5�ܤl�}~.�(�o<��
���=�?�<�~!=u�r<8H����,=p�<��<f�:�vC<6�b<���:#0�ys =X}�:��<"��X}=W(�<�F=��<��N=@���:����E]�1L#<�f��U�=�^6�Ϭʼ6��<ܘ���f��?R���H=ċ;������%ڧ<4=��N!<'>=4�L��z�<dcq���?8:���<��=M-�<�꼸�i�N;(�D�|���|#=;͛;H?<%�<�����tR������<Ϭʼ�;�;՜����@������C��6�<?�)�=��;zR��H�L�8�r�d=���;�2=J�����;R�<�v<B�=�Pk�]�9=�Y=\A�>�غS.��uw:���pV<�^)����z���J��
G���;��ԓ����٧���Z��\<�~<���"��=�Q*��12<k白'��=d��;��o�	HA��m3���(�5=J�@=X�m��[��*6���<�T�;Zn��U=i��=`���Eμdc��ٴ�{~��U��+\߻;͛�
����弨s=� ��Ԏ�<ⅻ޼����o�<�豼xY���A�<��
��=_�k����V��_�D�x�(<'���5���f��W�:H���o�;�'c<
bL��IY:���<�6S<?R�:���P�=�hx;?�<j��<��:ї�9���
�<ċ<���C�7<Q8�:�f��9���o�t��(/<�2���;:q<1L�<Q�Q=�S<�μ�[�<�e�:k���|�<�����
�?�:�j�'�w�?���3r{���;N���Ԃ��}Gh<I"\=� �u�%��=��@�
���=3r�<��ݲ��´(��^=I"ܹ�̵<LV�<�0��Tg<�<`X�;S�;~U���9;�L�<�:�<���;�޼8�'���,'
�M�ù���	=>{=�f;J������<RF���@:4��IY"�e.=E�t<��7;�
�������<	�Լaf���<<䅳<E�t�,3׼s�\�o�t;mZ<�<�l�;g=�pV=r�d;#���]<U�%�'QQ<J���0;�Cl�&X�o1;#��ė�</�3<��<,3׼�3#�&����	=��LV�<"��tA��#:��< �[����[<��_:��ͼ��<V��$�;�;=���<��;mD��┰�Zn=�u��^)=�4�\
B�:97;�+E;����<��=1�<k��[j�;�E�_�k�Gh<;SB��<tZT�m�޻���(��;;͛<tԭ:�v�;�O�&ؼ-���Q�Q<@5H:�.�ؙ޼�!v<s���\���D@V<�q;�֑<",8�+�%���W><DR<��E=���R�<��~��P�][�y��<`L�;wļ5�D�p�=��<�%���%����}��:M-j<�W�<]���Y�b�y�������)�Z�+���<'E=�
5���N�Q�<��;-���V˝<���;k白L�<٧=�_u7�F=�$��n�V<t�z;p�=�.���=
�<���?�k�=2%�����%ڧ�?�v�r&��]����)���;(��<\MU<�|�;Kz<�!v��1�V�W��>˼�rễ��;�\E��ջ?$��+żX}��;=��=�t;tZԼ뢽)�;�*��=��Rp��f���H<��3=.��e�B=��=��;W���ԎP;�O=���;�<���?ة<��=m�'QQ�4�L<&zY<xY��`<�Q���^��*6�<��7��:O;~U&<��㼤h�<�`��6�b<V���!����<0>e<���Q�Ѽ�@"���=��ӼzJ���O;�S�;�F��xe�<����`Ҽ<>���#}	=�.�<ܤ�<�}ռ-�(�V��:#��<ė��\A��0>弧���u��R�;���,��|�������	�<�<�Φ;�^���5����"o˻�F���ڼ��=�X�3=��9�@l:6�b=��˻��⻹��<к<��<,�;w?�<�=�<��k�y<Z<�����<�������f<W�;o�<",���A��Q�Q<��ǼWkϺL�<�x4�jo�E����$&<��ӻ�IY<
�(<�厼}G�<�B�<'�w;;S»�Z:���<3f�<�#�;�����_[�>{����E���ڼe.����м4�<��<
���iD<���<w?
��rG=>2�[�#�#�i<�Y�:9�����<�9��+��<�(���:-
�<l<��'��<��߻���j=��Լh�X��Gμ!�Ӽ�>1=�%�Gh����<'˪<i�P<�:�<o��;�J�����;��;�偻�q"<�q�9[�#<r�*<K��;�%r=m��;>���Iٻ�~��=Wkϼd�7��\�;r�< ����
K<��c<#FC=I�<ėm<3�T;���;/�3�ֶ�����<P��<�D�<���<Z�!z=@�<�[y����d�7�P���㐻wD��	<�=;V1<�|�<C=�.�<!�ӻCi�<V���C]���۲�.��9|�I;�/�;3f�;3�����;h��<d�7��R\����<>��<���<W�=�׼ܤl:���:p�����x<!-���;�K=���;<�� ���\�B��<�쭼;/��
�<�iD<"�;%T=Kz<�'c<L���Eݻ�=0�>��`�<m%=�����<i9����\<�:���x4<���<5 k���a;#�<%���G�<��&<V�W<d�<´�;5 ���¼IY"�k�<�F�Z��,3׸N�<\A��;/<���gS������#<ӷ�<[v]�S`��!��<��<�0u+=�^)�Md0�dcq��+_=p��m��j"=�\���B�;O`�:�:��� �[�]��a/[:&ػ��!<L����K��w��_u��H?��
e<�;�r]��N~;�X����O���KJ�",8���=��;:h��$g:d�����=��-��
�/g������+\_�Y/�s�"�)<Ԏм�6�;ӫ�<�iD���	��,�<&��<�|�;�ք<{��;��$=���;8�
=�e�;
�b</��ޖ<�}U<��D<���<�O�j͎�uh=�
�<p�<�I��٧�V˝�މ�<n�ּ�+�<M�C����<�vC<;��\A��D@V�:���+E<�== ;���<�S(����<�7<��<�x�;�z�<�3�<3#���`��G<���<�����q<��<�7<��1<Rp<�+E<_u��3==�ͼ9�=i���d�:���<�s<"��<ǖ.�ƿ���9��Ԡ<=��<��<��+��>�:W娹��1����<��<V��:'�w�e.<�~!<w)=r&>=l�jo;���4�!v<���\Ǯ��N;�9�dW����<������5<�^�Js�<�~��^���M=Kz<�rG<���_�k9��<���8\�=�("����tN�<�A�:"�$���~9f�gb��+P�<R��8���j=Z�e��+_<�S������\
B;���%��<b=�	����c<J�;������<d�J<`	����-���:9���x����ۼ`L���
=��$����h�X��5���Ң;p�<p
=?R���iļGh�;4����b7Ն9=�&=#�i�}�;dc�<���<M�C<��
�ܘ����߼J0��G��*<�K��d�ʻbS<.�u=>{�0>�< ��;!U�<",������rG<�;��Cl��ݰ<�+E<�B:�y<Z���<�s�s�\��&$=�P�B��*��<�[y<ɰ9<��F<�2��;�֞<��`�
ܥ�O�<����\
»HŽ<	{��o$;}~����!����U�߼|�6=��<N;(���=��1?�jS��}����D�<zJ=W>=n0�I����Nz=��R:��<��i���b�ol=8�Z<�rG<Ci^�ť+�>2�&�;i�=�2<[j���d���'��<�iD���n;i�л��ϼ���<	�9���̻3r��ʇ1�*6���:���T�+�8<�-�;#}����(�=*:;
b�;u�r<��¼�!���1�����<к�1�;��w�0<�Ø<Q�Q=,'
����<�\��Z֫����<��,:�&<W��f������՜�<
bL�X��:k��;��Y<��
���b��|�N�9�&�������ǻ}�;:97<�޺������<�g�<o5;;�S��* ;m���Z�<8��
�%=Mމ�4I���.<���N��<�>><y<Z<��h��x'=f�:=n؜��8^<Md0<�X�<*��<�{�;���n�;�;Qo>=糼��;9��<RF���t;���
<=y0������+_=��=+\߼��<C];�߮<�����E=�L�˼}��<
ͨ<�D<�0�J��<-�9/[���12<�C켢@�<8<�_[<������<��^)=r]=i���
K<�'=�������<I"�<D�|���!-<�,=z��;u8<�ݣ<��<�7�8�Z��S�<�����;8��;��y;��Z<C=5 k��@<",��3�T<�&$;dW���[����r��6�<(j
RowID

	����̷��
	Timestamp

	ه��̷��(


milvus_id: 452165072252045248
data:
#source2
postcss.config.js(d
&	file_path2
postcss.config.js(e
&	file_name2
postcss.config.js(f
	file_type2
.js(g
mtexta2_
]export default {
    plugins: {
        tailwindcss: {},
        autoprefixer: {},
    },
};
(h
pk

	����̷��(i
�0evector"�0��0
�0�T��$P���q=�K���@u<&���-d=���ͼt༚��;���� ��=G�<&�Ӽ=G�<�,�<k�¼��V���3<��j=<=�@���a;=e!����M�m:=YԼ��&=ԛ"=<$���<�((=No=y��=ˇ�ݯ�=��N��j�< �=�0F<gf��\
�<8�@<��<�b<��<6x#=+b�i��<y��<k�»	�<��=��M����<�[��a\< �2��9N���5=J�Y���:�=b�;��u����7��#���=��=����;2����%G�8���8��<����ݯk<J�<��=i�� ���#�=Q���1� ���F���׼(T����c�}<ϯ���<�,!�b�;�������P=)ڮ<�=r���}=�0r=��G�":��@�<ĸ<=�~)�Ec���A�pz��ݯk<i�;��h���V=�|�;Q���}�������<k�W�Y� �'�6xZ�\
~=]��43�<$PL;�j��`�ʺ�q�=G.�\
�<Q��<�=YȈ:&��k�=��μ-d=���i�=y�X=�q�<�00=�7��r���`���NoR���)<+��wI�<�B	���<�r��<�h���jz�L*K<43��/��;�hm�?�a���<F��q��43<Y��gf���=$P���@�e!�<`���pz��<��==�j�<��<�?��#�</�=n5`<��<�#�J墻��r� ���,���_e�ԛ�<�I�Y�	M<"�;�V����;�̭�r�;�~;+��쒏�(3�$P �	B<=G�<�%Ǽ��;�3��������;ԛN�ˇG:]�:�h ��"=43i�������<��O<}�<ˇ=A���B���@�=}�	=�ʶ:�C;�����;�j��^R��<< �S�-dӻvI�L**��,���B<�~�<�7W��,����^R�:�׋<i�;<�.�<����B<�q�\
��ĸ<�=��y<�s�ԛ�:ĸ<��%]��s�E!�{Ӓ<㕽�sּU>=$P�<��9��,=Z��<��)�43=`��<r��=��<�_����/�p<��l<=Gp�Aѱ<�
�J��<W��ĸ���j�;+
=8�w<ĸ�<+��U>�<��j=����CD=�=�ކ�{�_��76=Aѐ=-d�; Ƨ�E[*<43��(�
=�L�?�5=�%�<]7�`���Q�Y=���r�X<0<�TP�C.���V��_�$P���9μ�i�/�p<W�Y=Y���́�W�C��b<i��;/��:/�Z<�q<�Vݼ	�:�<bܚ���;���<E=	M��S��h�;t�</�D��_#<������BV�vI�<�B�<=G�<��Vs<�V<�Ï;��1���+�����i���><k���S�`<H��:};�i��ĸ<���<�q�����r��;�q>;S��</=E!=43�	�<��<y����@�L*�����i�Ѽ<=F[K=���q�<}=<ۼ��;�L*��������<)ڣ<�=��������;2�˼pz�:}=��<��M<W�����<t4��K�<����C��+68���<�篼��:`�ʻ�]n��%s�6xZ=c�g�$P�H�R<�j-;�h���x=�0F������<�|�;��W=�_�������9N�L*��E<ԛμ����$��������.e=y��<�~U���$<�%�^R8=ˇ1=^R�bܚ�(�
<�������(���|��x��q(�<ۼ-d��a��8��<Y�ԛN�43�<S���k�^R�<���<�|=n5J=L*=`����M�;��3=��
<�.{=+�<���<�%����;�~)=ĸ�}�t��`�?�&�<L*˼�,!�Y����F;(���9��7���|޼&�>�B�;����&�2�?�a=(�<m�<Y�9��?��<���<�MU����<:S<mۻpz0=��m���n5v<�B�<��<��%�8������`�)<]X�"ۼ}���鼼A����=`����2=i���L*��><+b�C�<Y��Ey;�7A:H��;�T����6x9��#�<�ۼ�T�;�u7�}�;"��Y�<���;�s�<�B�����;��=Q�C��0r�A�����A9{��<�B<P��;No=CZ;�s	���H8W���Ú<������;���;U>�����;�.�;���<{��<���Zȩ<C�=<�;��=2�w����s����V:�@�/�Ļ���<�s�<t4��j���%;��e<�|����$=	�<��>=C�=�%�=)ڣ<�|Ȼ��P<���m5=�V�;���<m5�C�<�
=/�D=Q�８Tf�t`<�u��U>R;^Rﺷ^�8��<��;y���2��:�KH=i�0<�q_;�q3�����L�쒏�Q���y���ԛN�l�n���{;W��(ڂ<6x�;F���<�0</�D�^R���=<=��{�<ĸ&��.�<�-d�;�=&�S�)�ڼ���;�jz��|�<L*K��%�<���n5��.�<	�<&��6xĺ=�h�;��=CD��V�<$P��m/=�@3��h�<�a�y��<�BV�����_�:���<i��<�<+�����j"���<�
<t�<-d==��5��T:;�u,;���ĸ<pzQ<�u�<�_���M��U>�<�%�c�Q�$P6=�W;�|�?��<��e<��<:�<�@<��V=r��<ˇ�;<=�@=bܻ<����	�^R;(��ԛ�<�9�<��<��O=S�J����Y�<ݯk���$�y�¼����<�TP���λ�F�A�h<��;�u��uB;���?�	=}�;�<�9���MU;�7���_�;��^;+�<F:��-<���C��c�Q�wI}�c��:S�J�<E<A�����t<ˇ<����y�=���;?�K��K^�J��;����t��L*����A�~<:�����
�<A��<��e=r���S��<�黄纼�M�E[�;�A�J�C<��d�	��C�;�q�;Q�=�VG<(ژ�����"ż�j��ĸ1=�Bl<�żgf��ĸ�;2�w�S��<��<i��;}%���
��,��0%=\
��43�<�K�<�ކ��u��(��AѦ��aܼ Ɔ��x;i��� �=43��#f<��e;+�<$P+�gf�(ڍ���.�:�<;�Oo~��M��gf����<�7���T���B�E�;]ػ�a�;U>�;�@I<��r���=�����|�<<G�<n5�<�98<k�����
=6x��m/��~4�-d�ԛ8Z�`��jC<��ϼgf�<���]�;/�9�i��<H��<�s�쒥<����j8����9�|�<���;m���,=m�Aх��7m<gf���ð��j<쒥�H�Ҽ�j<��e!�<"�;`���ԛ�No��]����;�@����7=8�K;�ܼ��l< �=�T�;gf<�%&=�#�<��޻��9=}���O�-d���ð<ˇ�;��N����<���:�Ú��K�<-d�<n5�<W��<����H��:�M)��uͼ?�����;$P�<�9�6xڼ�a\=��H�n5ʼm�<��:C=��;Y�<�,7=L*����r�ĸ�{�(����� �'�ԛd<�@I�`�=Z�ʼn5J�F[a;{Ӈ<����C�<��<�����+<Y�;i���/�<�����u�<��<-d�Q��<���;������*=�U<L*a�i��<k𷼜�t=i�%�L*K< ����V�^R�<��ĸǻ�7m��@�<<�<��$�?��<L*�:��e!�<���U��9<�#=�_#=����8��<��_;W��<�u�<����0r=�#=/�.�i����%s<ݯ�;��{��.O;6x�<"��^R�<	,;���9"=\
��=
�<�m<�.O<��<�a������ �i�gf����<�B�<-d�<��λԛ�<W�-;�%�<+�6x��":���<E��ޑ<��>�S��n5�;?��;k���.��0r�����	=�ކ<}��+ <\
R=�_<��<�#$��9ι���;�7��Y�;��c�A�~���!=gf�$P�;{Ӈ<�V]���7�(>�?���Ec<���<{Ӓ<J�<��;����)��<2��<pzQ<���<�����L<"�"E�i��;L*=�T�<No&<	;�Mk��sl<�9�<�ժ<1�<U>~< �=�����.ϼˇs�{��<��N���!;`��;�9"=)�ڼĸG��.e�ݯU�:�<���;CD��jC<t�y���-d2�`���(�<�;Q�C<Cڼ��{��a��q�;F[�;�s@���N�����@(�L*�;�.���<A��^RY�U>���M�;�j�<��l����ˇ�9pzѺ+6��
���k<��:	�;�_�<�,�;�#�;$P⼥�=GZ���{<�9�<(ژ<�[<�@�:ӼL*�<����@�<�����|;"<�0�<�ާ�2��:C��&���K�;�a\=�a�<��;Ϥ<�S�432<�̭��0򻋶л��W<�����_�i�=�C��������;�T��y�!�-d�<y��`�=�M��{�_<6x=ĸ�<�j"�t��+�<A����><Z��;Z�?�}�6x={�I<�3<��-d�C#;�~뼪|��E[�}������r�ԛ介�:�����++��,�;43'�{�=�j"�";:�<"�;�j�:��;{��<�M�<]��F[�<]���<���<-d�;�|�<�uͺ�7W�S�<ĸ�<���<}Ѽ`��<�@_<^R=��;�T�+b<8��<�Լ"�(ژ<��=���<�=��M�;:�;y��<ĸ�<�_�;r���4���=�I�Ey;������;b�%<�Tл���<��{�y�7���<m�;$P
�-d�;�=�\<mۼ<q�<G
�Aћ;������������</��<CD��ʠ��,�<r�<���;E[	�/��<�MU<L*�<ĸ]�&��<?��<<�;����࿼�@_����)�ļ�u�;"ۻ�_e��5�����j�:�B�<��#=�TP=H�~�vI�;W�Y�1vI<�@�����2��<����q�<ݯ�<AѼ<(<��<��H������;P�=�uͻ�=����s5����'�;��>�P�<No�;(���_�;6xD���<ݯ��$PL<mE<m�;�9����ü	�;��'<쒥�i�%����gf��0F�U>�<J�8��~��ˇ&<6x#��u��1�<��;}%�}缮={�<ĸ<wI�:Y�<}}�}}���^�?��<pzѻ�TP��M=��Ϻpz�gf໋��<���	<&��<��\;��=���;��<���;t�< ��:k�;}�<E�(><$P<�j���x<�a����H�ˇs=����#$�ˇǼ�ާ�E�;��No<���W�L*�<��μ��3=)ڮ;<�����r�<�s���.{<������=�j�\
��Q�C< ����<�,�;��=�K����<��:�@�<e!<���<<G;8�˼pz�:ĸ<<��<�M�<W�8<pz��̢;{�3����<��s�NoҼY�<C�<`���sV</�
�c��m/���f<��׻ݯ�<1�<No;�T����<43i<�%s;vI����r<��ͼJ�"��a�L*5;n5);<��?;�:�ԛμ�9���qɼU>�9�s�<����ĸ&=k�;�������������Ϻ��@<\
����<6x�;ԛ=mE<�T�;]��^R����/=Q�=�#�<?�˼���<��<����<�%�"�����<���pz�:�q�<�7W�����T�<�I=c�}��0ܻ��<�;k�!��T�<Ϥ��L������B�ˇ&��먼Ey��@��9�=G9=���n5��(�8���<+b<]»432=�U:���3<^RC<=G�;����ĸ;</<�r���<^R�;�K�<�9����ϼQ�û6xp�����]����
��VǼA��;(j
RowID

	����̷��
	Timestamp

	ه��̷��(


milvus_id: 452165072252045249
data:
$source2
tailwind.config.js(d
'	file_path2
tailwind.config.js(e
'	file_name2
tailwind.config.js(f
	file_type2
.js(g
�text�2�
�import defaultTheme from 'tailwindcss/defaultTheme';
import forms from '@tailwindcss/forms';
import typography from '@tailwindcss/typography';

/** @type {import('tailwindcss').Config} */
export default {
    content: [
        './vendor/laravel/framework/src/Illuminate/Pagination/resources/views/*.blade.php',
        './vendor/laravel/jetstream/**/*.blade.php',
        './storage/framework/views/*.php',
        './resources/views/**/*.blade.php',
        './resources/css/**/*.css',
        './resources/js/**/*.js',
        "./node_modules/flowbite/**/*.js",
        "./node_modules/preline/dist/*.js",
    ],
    safelist: [
        'border-creatify-2',
        'border-red-800',
        'border-gray-800',
        'border-purple-800',
        'border-teal-800',
        'border-yellow-800',
        'border-blue-800',
        'border-green-800',
        'text-red-800',
        'bg-red-100',
        'text-gray-800',
        'bg-gray-100',
        'text-purple-800',
        'bg-purple-100',
        'text-teal-800',
        'bg-teal-100',
        'text-yellow-800',
        'bg-yellow-100',
        'text-blue-800',
        'bg-blue-100',
        'text-green-800',
        'bg-green-100'
    ],    
    darkMode: 'media', // or 'media' or 'class'
    theme: {
        extend: {
            fontFamily: {
                sans: "Figtree, sans-serif",
            },
            backgroundColor: {
                'creatify-bg': '#F6FFFE',
                'creatify-1': '#046F67', //dark
                'creatify-2': '#3CC7BD',
                'creatify-3': '#21E2D5',
                'creatify-4': '#05FEED', //shiny
            },
            borderColor: {
                'creatify-1': '#046F67', //dark
                'creatify-2': '#3CC7BD',
                'creatify-3': '#21E2D5',
                'creatify-4': '#05FEED', //shiny
            },
            ringColor: {
                'creatify-1': '#046F67', //dark
                'creatify-2': '#3CC7BD',
                'creatify-3': '#21E2D5',
                'creatify-4': '#05FEED', //shiny
            },
            textColor: {
                'creatify-1': '#046F67', //dark
                'creatify-2': '#3CC7BD',
                'creatify-3': '#21E2D5',
                'creatify-4': '#05FEED', //shiny
            },
            outlineColor: {
                'creatify-1': '#046F67', //dark
                'creatify-2': '#3CC7BD',
                'creatify-3': '#21E2D5',
                'creatify-4': '#05FEED', //shiny
            },
        },
    },

    plugins: [
        require('@tailwindcss/typography'),
        require('@tailwindcss/forms'),
        require('flowbite/plugin')({
            charts: true,
        }),
        require('flowbite-typography'),
        require('daisyui'),
        require('preline/plugin'),
    ],
};
(h
pk

	����̷��(i
�0evector"�0��0
�0w��3�;�]�<]Ɉ�M� =7*�=���̼*$��l��[׼��<�.�;����%y=�9=Ж�;�?��O�<�}j=�d=��:\<~;矧<����.{<��׼��,=i=�1 <U�<�I�=j
=r<2�T=��ټ��l=�]��O�<���5����A���`�;[�;�9[<�
��1U��(bM=e'׼�Pw=��k<�FG��m<�dY=K�
��5I;��ʽ��<l�k<G=5�=�~<w��}���Y#���<ф�^����d�<"��<��=����/��F�c����<��d;�	=��<��7<B�e�����m=t=.�����UP���*%�e�(<	5ڼ�\�����
/�Z�>��5ɻN<�[�<�мjR�<��`�8G^=7��=H$�k��m�;�T=!�����<nr�ou��p�<.���o��G,�<�52<y����*�`�M���.=
<���_�;����څ'=��<��s��DҺ]f7�t9<�b��&���@g&<���:�="h���<�'�;͚�J�<(^$�
`X��{<@g�:,�K=r=9�:��y�<qٗ�O�<î0��N�:&�6�a�/�#7ϼ�[�<;"<3₽>=
���߼',�5JB�a�ؼ��_��ܒ<B.<8G^�xh���䎼��o��%��<�\��̡ۻm��%Ȃ=�$<(^$���d:6S<��<gY�<9�:=�+X�i�<��D����<m�v�=��B.=:�t��dY���k<z3==䶼g��;���8G�<��=�Á<��<�+A�V��:[�<h�D:jRռ�B����7��.{<����v�ļ�p?;',���<~b�<X�\�Z
s<�<�<?5�<�m[=�&)::����m�=�Z��d�=z��<�<�k��]c;}�<�B�<���<V���H^�;.�����i2<b������<����	�{ș<0�>���< >\<��������\;�j��a[<��.=�G�;�-<��<
�)<���9u��FY�<y���<?��<r\�~bd=c`o��d:څ��*�=�=Pᓻ)���r=�C�<O��<墋���;���i��;	��<�K_��k'=�Ӑ��j!����;�w
=������=w��<W�"���#=R��Q'=0�=4N�3`�4�<��(=�1�`�M���4=p�����:@g&��<<n3;�=�8��n��<B27=�;�<�Yy���=�;<���[��t=.�Ct��p��î0��)�<��(<��8�
<(^�<��*=1Q�;�=6|�<�:����:Q~B�jN���E��:q���'n<8G^<��<K��I�t9=�:���=����n��K����ƻe'W<R��<�_�� ;N�M��<&��xҼ�"��G�k����)�<uk��A@�6ߞ<���i=�л�f���<�C<֌4��W�<�C=+������<���;��<O�<E�/�n�$�׈��O��<B˼<Cd¼�R�;��<z/�<ru<>��<nG;kJ�=�}j<xh,=�9[<����#�;�&����<�~�;��';۷�<|��;�[n;�����=jI<C��9u@<��<�G�X��<�4�VBF��H<�CdB=����D$<}0Y��E<
g�;��~=���T{�<�f�;<���]L<f�3�p���7�A��<���=��8���⻚\��=9�"����=H�<�w
;��*<[�O�	1�<ou=d���PH��\�<i��<� �ZЕ��9�:��t:�Lv����)���]�1=�};)�����<N�;v>���;��<E�X;��F=�"�=�Յ��UP9x[=�D��
ƍ<� �#�I=�6�z��<:F=�U�<������7��e��N��K �w6����޻Q~B=�"ֻ��Ｖ�d���ȼ���=�oP��s��μq@=~(��J�3<RIӼn}S��*��лT{^��U��ɨ輾�U��>4=۷2�X���<�b�<�<�T�;t=.<(Ş�!���n�)���t)<H��8_;_=&�e�X=K�
���)�p��~ŵ;>��;~�����<�,ǻ_5q;�������ӓA�p=���R�M<',��C���<��A����B/=D$�֌�<@g&=�O���H���ȼu�
=D3|;똚�׾�<�(=G,o=�Ь�ٍ�<��ƼZ
s��+A�k�:܂ü�X���f�<k�7<���}0�<ԧ<�ʎ< �=gU9<�ƻ<
ܻ䶺,�ż�R-�����2λX�3<�t�9�:;�����;�t�<_5q�p��9z/��3�<Ѽ��<(�{=����M�x:{e�;���:-�"=qD���%=��,��u<�%#��B�<�l��(�p��<�J�ϼ��=;�w���9;�
=V�K�ɤ��n}S=�I�8(�����jRU�H�<�p��;������:��o<� ����a�i��:��<��.9�Y�<�hû[i��'�Ǽl|<�[׼p�9_��<d�=�슼2�+;6x$�{�<%e�<ѻ��������;�G�< �-��m=��<c&�9ܺ<��<ƫ̼� �&�6=b����_A<NU<~(�<�u��q�i<6����<���^f<$̫��}+<�<��|��<���<�,G�u�;B.��C�&�
=̡�;�o<�@)=�]
�v>s;X�\�u�;r=�WE�ɤ�<�"V�"l>�V��<�Լt�\�#��<�+�<�#�<r�;�[�<��=�
<]Ɉ�R=��s<m��<��;a����
/��󮺜]L��[�<Ư���"�:"��<�}=�=�VV��mۼO�<ʠ������B]��)�;��8<���;h�m�����$�+�]Ɉ�L���"<�%#<�#E=I�V��.{<Z�<i���r�9IV(=���!p�<��;�oy�<��%Ȃ���<3`;a_*��p�v/������
<�ɟ�!pg����;�[n;�zG�|�$;��<6�:�ü�X4��)
�i���O2;�d<�8-=p=��*=;<��gQ���f���$K�y�<m-<��ȼ���;6|ͻ#7O�MO;�����F0=.M�4<'�<��!�?K�LSD=}0Y<�b���4�;y�<G����E+*<��*��N��H$�~^���Rl;Ưu�i=)�X=�K_����똚��0���Ҽ��A�&���s�;�7}<|��;�͉�C�;i��;��;��*<�:�;�e	���.=�㟼Tw5��'<�+��6<��<�i2��kf��6���Q':֌�<�+X�p<���<�}�gY�<|a<�2�<	�<�P��CdB=.�ֻG�:�K1��K߼���<�Wż/��<*%�;�Ȱ<�oP��]
=�1��#��:��<���Wע�����z/�i�<?K<�=�y�֌�;�����$���q.=0#��������)�t=��c`�nG�<ƫٍ̼y<���;+[@����a_��C���\��S�=��<�<�惼RI�<��<_���<Q��<g���G��=�g��;<x[<�.�<�EA<p�^<U�:Q�v��R�<	�����<V��<�����j<����!���5����T{^���^�/P�����<qD;��}+�7�<H^z<�=��<��=��<\<~��Á��_��_�B�qٗ����,�<����U=a[���k�;܆켈�=����Q~�<)�/=C��R�<_�;����{iq<��,��=�DR;��:��<NU;���
�6=��<��Ｈ
=����;�"=��ռH��t�<�\���;uҊ;y=�Y��X	�<�[�-*z���B27<!x<����Vֻ�ڝ�]f7;墋9NU=�]={�¼��;',��p��5��<�E��gYb=(��<�k}:�w����<*$8D�$<��;�&)<	�<J�;>��;-*z�OP`=���:U��<�_<H�K=]0=3�<"�򼘕�2�<�hC�[��<�j�<G,�<�Yy�3�=+º�e�"=�Һ:q�<�����t)=QH��)�;&�NU����;�dY;����>�>;B����b�}��<M��<�v�;nr<�=�{<
é<��h��a6;/�a<G�����;�͉�<r�; >\<oy*��䎼��<�DҼ͙���"��2�;Y�
<D�$=�އ<LW�;�]c<`g|��l=��;=�NC���|<�b%�غ�;wp��
c<���:v>�<B˼<Ư�9_��;�1 <�ć;~(�<LWm;x�&=:�t<i�<)����[��^�l|���[׼��Ի�߻�G����<{eH���ȼ?5�"h��gU���';%���Z�,�O�t=��4�<�/�8<�ҡ���0<-*z��6<J�-���=���
�6�G�:;�D�N�&<�лJ�3<z3�;�����k}��< �-;�}�<��F�K%b�i<T�<r���th:#7O�����&�<<��!<Qz�{i�;xۼ�qE<E+*��E�;�T�<F���^�����i�ϼuo9<�8;��,=�?���O�;�����ٻU���;�_�����)�����L=��U<5��<�N�<ӓ�;,����ʼ�䎼�%��OP�<	����;���<���0#m<G�� ��P���f=�J��k�7=�I�=9=f#�9��*<���;ް%;��z<��;<|��;3�<�\�;��|�e�<1��:��U�-*z�U���X�<�2N�����`-�)�X���S����۷2���N�_5q<�%�����ļ7*=��`����;��	<�Z)���=_=��<,W;��7���<��!�� �<_5�<"�r<7
<����@��̡[;|��<8����xһ',�<��<N=����I��B�<��~<i J�_�B�gY��'=',;]f7�X���%�����U�<O��;Nջ?˻F�c=��ﺞ���|�$�y�;�th= 3:0#�<�X�<M�I�E+�<[�9܆l<-*z<����7����S�1QO�l|��A<
���LWm<�A��i:���<���W�"�h��<��.<"��a_��<n3<dX=wp�;�������;I��<��s:,�=)�ؼG�:��'�6S�ru<غ��齼۷2��_���交�MO=�T=��׼�<!�8=�DҼs�Q��}+�C����Y=��d;� a<M� ;H$<�p�����:�
�;$���$̫�6�<H�˼׈�<�<��R�M��;b.�;v�ļ�Ӑ<��m��qE��"�;[i���`<�_����;l|<��<�/��^b�M�x�)���g��<U;<-�"�r���}����<"h��뛼	11<A���VBF<�׹<���4���w
�dX<��;�'���W<@�<M���,�˼:q���W<Y�g�����g�
�0#�:���<�=h�=�,G<�
<��==y��<�P8�k��;�{=*$<mKH=��<�D�;a�/<i���*�c:]f�<H�K��c�<6Ӽ�~�<�Gu=]0���ѺH^z<��ʻ�{������]0���]c���;����)c=3`< �;�yA�܂C<��J��<�th<�\<��μ��B��8��	���<jRU���<�����<Y��.��<K%b:X==�������<��컜]�;O��<0#m<�]
;a_�<b.d<[�<L��uk����m���J<
ge<Y7�)��;{iq����b.d9�C<�P<��=A�<���[�:�l����B�Y��;܆l��-<H$�X	.��0�;�v<��!<�߻�H%�Q�v�񊀼jR�;�I�;�N����=N�;5<���;����R;G,�q��:�'<�@�<����*=�G������~=Qz=`-�<
<�M�<VBF=]Ɉ9
ge<X�3��><���<O�<F��(^$<U�i��H��]���r=��<	���l��?K<y���-=֌�:U"�����᪻���;\�;X�3<T{^�z/��},�<x�&�@g&�uo9<'�<+��8{�=6�<'��<�����ļX	���m=8��K1<IV(;A���?�<;��;�*<K�:FY�������H������V�<��2�4�:(j
RowID

	����̷��
	Timestamp

	ه��̷��(


milvus_id: 452165072252045250
data:
source2

version.md(d
	file_path2

version.md(e
	file_name2

version.md(f
	file_type2
.md(g
��5text��52��5
��5## #217 Introduction
This pull request introduces several enhancements and new features to the application, primarily focusing on lead management, data migration, and user interface improvements. Key changes include the addition of new models and migrations for handling lead activities, updates to existing models to include new attributes, and significant user interface updates to improve the user experience. These changes aim to streamline lead tracking, improve data integrity, and enhance the overall functionality of the application.

## Changes Overview

1. **File: `app/Models/LeadActivity.php`**
   - **Status:** Added
   - **Changes:** Introduced a new `LeadActivity` model with relationships to `Lead`, `LeadNote`, and `User`.
   - **Description:** This model represents activities related to leads, such as notes, status updates, and due dates.
   - **Impact:** Facilitates better tracking of lead-related activities and integrates with the existing lead management system.

2. **File: `database/migrations/2024_08_27_204602_add_source_to_data_cnpjs_table.php`**
   - **Status:** Added
   - **Changes:** Added a migration to modify the `data_cnpjs` table by adding a `source` column, dropping several columns, and adding JSON columns for activities and partners.
   - **Description:** Enhances the `data_cnpjs` table to include source information and better structure for activities and partners.
   - **Impact:** Improves data organization and integrity, ensuring more accurate and comprehensive data storage.

3. **File: `database/migrations/2024_08_27_210118_add_source_to_data_cpfs_table.php`**
   - **Status:** Added
   - **Changes:** Added a migration to add a `source` column to the `data_cpfs` table.
   - **Description:** Introduces a source attribute to track the origin of CPF data.
   - **Impact:** Enhances data traceability and integrity for CPF records.

4. **File: `database/migrations/2024_08_27_215023_add_source_to_data_cnpjs_table.php`**
   - **Status:** Added
   - **Changes:** Added a migration to drop `consultaID` and `delay` columns from the `data_cnpjs` table.
   - **Description:** Simplifies the `data_cnpjs` table by removing unnecessary columns.
   - **Impact:** Streamlines the table structure, improving performance and maintainability.

5. **File: `database/migrations/2024_08_27_215344_add_source_to_data_cpfs_table.php`**
   - **Status:** Added
   - **Changes:** Added a migration to drop `consultaID` and `delay` columns from the `data_cpfs` table.
   - **Description:** Simplifies the `data_cpfs` table by removing unnecessary columns.
   - **Impact:** Streamlines the table structure, improving performance and maintainability.

6. **File: `database/migrations/2024_08_27_222416_add_columns_to_lead_notes_table.php`**
   - **Status:** Added
   - **Changes:** Added `type` and `status` columns to the `lead_notes` table.
   - **Description:** Enhances the `lead_notes` table to categorize notes and track their status.
   - **Impact:** Improves the ability to manage and filter lead notes based on type and status.

7. **File: `database/migrations/2024_08_27_222830_create_lead_activities_table.php`**
   - **Status:** Added
   - **Changes:** Created a new `lead_activities` table to store lead activity records.
   - **Description:** Introduces a dedicated table for tracking lead activities, including foreign keys to leads, notes, and users.
   - **Impact:** Enhances lead management by providing a structured way to track activities.

8. **File: `database/migrations/2024_08_28_012009_add_columns_to_user_admins_table.php`**
   - **Status:** Added
   - **Changes:** Added `crisp_operator_id` and `crisp_nickname` columns to the `user_admins` table.
   - **Description:** Stores additional information for user admins related to Crisp integration.
   - **Impact:** Facilitates better integration with Crisp, enhancing user communication capabilities.

9. **File: `database/migrations/2024_08_28_030330_add_columns_to_leads_table.php`**
   - **Status:** Added
   - **Changes:** Added a `cnpj` column to the `leads` table.
   - **Description:** Introduces a CNPJ attribute to leads for better identification and tracking.
   - **Impact:** Improves lead data completeness and accuracy.

10. **File: `resources/views/admin/components/lead-notes.blade.php`**
    - **Status:** Added
    - **Changes:** Added a new Blade view for managing lead notes and activities.
    - **Description:** Provides a user interface for adding, editing, and viewing lead notes and activities.
    - **Impact:** Enhances the user experience by offering a comprehensive view and management of lead-related activities.

11. **File: `resources/views/admin/lead/reminder.blade.php`**
    - **Status:** Added
    - **Changes:** Added a new Blade view for managing lead reminders.
    - **Description:** Provides a user interface for viewing and managing lead reminders.
    - **Impact:** Improves user ability to track and manage reminders for leads.

12. **File: `app/Http/Controllers/AdminController.php`**
    - **Status:** Modified
    - **Changes:** Added methods for handling lead reminders and updated lead import functionality.
    - **Description:** Enhances the controller to support new lead reminder features and improve lead import processes.
    - **Impact:** Extends the functionality of the admin panel, improving lead management capabilities.

13. **File: `app/Livewire/Admin/FormAddLead.php`**
    - **Status:** Modified
    - **Changes:** Added validation and handling for the new `cnpj` field.
    - **Description:** Ensures that the CNPJ field is properly validated and processed when adding new leads.
    - **Impact:** Improves data integrity and validation for new leads.

14. **File: `app/Livewire/Admin/LeadNotes.php`**
    - **Status:** Modified
    - **Changes:** Added functionality for managing different types of notes and activities.
    - **Description:** Extends the component to handle various note types and lead activities, including email sending.
    - **Impact:** Enhances the flexibility and functionality of lead note management.

15. **File: `app/Livewire/OnboardingForm.php`**
    - **Status:** Modified
    - **Changes:** Added logic to handle CNPJ validation and API integration for data retrieval.
    - **Description:** Ensures that CNPJ data is validated and retrieved from external APIs during onboarding.
    - **Impact:** Improves the accuracy and completeness of onboarding data.

16. **File: `app/Models/DataCnpj.php`**
    - **Status:** Modified
    - **Changes:** Added new attributes to the fillable array.
    - **Description:** Updates the model to include new attributes for better data management.
    - **Impact:** Enhances data integrity and completeness for CNPJ records.

17. **File: `app/Models/Lead.php`**
    - **Status:** Modified
    - **Changes:** Added a `cnpj` attribute and a relationship to `LeadActivity`.
    - **Description:** Enhances the model to support new attributes and relationships.
    - **Impact:** Improves lead data management and tracking.

18. **File: `app/Models/LeadNote.php`**
    - **Status:** Modified
    - **Changes:** Added `type` and `status` attributes to the fillable array.
    - **Description:** Updates the model to support new attributes for better note management.
    - **Impact:** Enhances the ability to categorize and track lead notes.

19. **File: `app/Models/UserAdmin.php`**
    - **Status:** Modified
    - **Changes:** Added `crisp_operator_id` and `crisp_nickname` attributes to the fillable array.
    - **Description:** Updates the model to support new attributes for Crisp integration.
    - **Impact:** Improves user admin data management and integration with Crisp.

20. **File: `app/Services/CrispService.php`**
    - **Status:** Modified
    - **Changes:** Added methods for handling Crisp conversation messages and improved error handling.
    - **Description:** Extends the service to fetch and process Crisp conversation messages.
    - **Impact:** Enhances integration with Crisp, providing better communication tracking.

21. **File: `resources/views/admin/components/form-add-lead.blade.php`**
    - **Status:** Modified
    - **Changes:** Added input fields for the new `cnpj` attribute.
    - **Description:** Updates the form to include CNPJ input for new leads.
    - **Impact:** Improves data collection for new leads.

22. **File: `resources/views/admin/components/profile-conversations.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated the link to open Crisp conversations.
    - **Description:** Fixes the URL format for opening Crisp conversations.
    - **Impact:** Ensures correct navigation to Crisp conversations.

23. **File: `resources/views/admin/components/sidebar.blade.php`**
    - **Status:** Modified
    - **Changes:** Added a link to the lead reminders page.
    - **Description:** Updates the sidebar to include navigation to the new lead reminders feature.
    - **Impact:** Enhances user navigation and access to lead reminders.

24. **File: `resources/views/admin/lead/add.blade.php`**
    - **Status:** Modified
    - **Changes:** Added a script for CNPJ input masking.
    - **Description:** Improves user input experience by adding a mask for CNPJ fields.
    - **Impact:** Enhances data entry accuracy and user experience.

25. **File: `resources/views/admin/lead/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated the lead listing to include new attributes and activity information.
    - **Description:** Enhances the lead listing view to show more comprehensive lead information.
    - **Impact:** Improves the visibility of lead data and activities.

26. **File: `resources/views/admin/lead/mapping.blade.php`**
    - **Status:** Modified
    - **Changes:** Added options for mapping new lead attributes.
    - **Description:** Updates the mapping view to include new lead attributes.
    - **Impact:** Enhances the flexibility of lead data import mapping.

27. **File: `resources/views/admin/lead/profile.blade.php`**
    - **Status:** Modified
    - **Changes:** Added fields for displaying and editing the CNPJ attribute.
    - **Description:** Updates the lead profile view to include CNPJ information.
    - **Impact:** Improves the completeness of lead profile data.

28. **File: `resources/views/admin/settings.blade.php`**
    - **Status:** Modified
    - **Changes:** Added fields for displaying Crisp operator ID and nickname.
    - **Description:** Updates the settings view to include Crisp integration details.
    - **Impact:** Enhances user settings management for Crisp integration.

29. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added a route for the lead reminders page.
    - **Description:** Introduces a new route for accessing lead reminders.
    - **Impact:** Extends the routing to support new lead management features.

30. **File: `resources/views/admin/components/profile-notes.blade.php`**
    - **Status:** Deleted
    - **Changes:** Removed the old profile notes view.
    - **Description:** Deprecated the old notes view in favor of the new lead notes component.
    - **Impact:** Streamlines the codebase by removing outdated components.

---

# #216 Addition of User Conversations Management and Email Enhancements  

## Introduction 
This pull request introduces a new feature for managing user conversations within the admin panel, along with several enhancements to the email sending functionality. The changes impact various aspects of the application, including the user experience, email content, and admin interface. The main areas of changes are:

- New Feature Addition: User Conversations Management
- Email Sending Enhancements
- UI/UX Improvements in Admin Panel

## Changes Overview 
1. **File: `app/Livewire/Admin/UserConversations.php`**
   - **Status:** Added
   - **Changes:** Added a new Livewire component for managing user conversations.
   - **Description:** This component handles loading and displaying user conversations, including messages from different sessions. It includes methods for mounting the component, loading conversations and messages, switching between conversation tabs, and rendering the view.
   - **Impact:** Enhances the admin's ability to manage and view user conversations, improving user support and interaction tracking.

2. **File: `app/Console/Commands/Sendmail/LeadEmails.php`**
   - **Status:** Modified
   - **Changes:** Updated the sender field to include the sender's first name.
   - **Description:** This change personalizes the email sender information by appending the sender's first name to the configured sender address.
   - **Impact:** Improves the personalization of emails sent to leads, potentially increasing engagement and response rates.

3. **File: `app/Console/Commands/Sendmail/UserEmails.php`**
   - **Status:** Modified
   - **Changes:** Updated the sender field to include the sender's first name.
   - **Description:** Similar to the changes in `LeadEmails.php`, this modification personalizes the sender information in emails sent to users.
   - **Impact:** Enhances email personalization for user communications, likely improving user engagement.

4. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Updated the email signature format to include an image and a more structured layout.
   - **Description:** The email signature now includes an avatar image and a more visually appealing structure, replacing the previous plain text format.
   - **Impact:** Improves the professional appearance of emails sent from the admin panel, enhancing brand image and credibility.

5. **File: `app/Livewire/Admin/LeadConversations.php`**
   - **Status:** Modified
   - **Changes:** Added a new variable to store `people_id` and passed it to the Blade view.
   - **Description:** This change aligns the `LeadConversations` component with the new `UserConversations` component, ensuring consistency in handling conversation data.
   - **Impact:** Ensures that lead conversations are managed similarly to user conversations, providing a unified approach to conversation management.

6. **File: `resources/views/admin/components/profile-conversations.blade.php`**
   - **Status:** Modified
   - **Changes:** Added display for `people_id` and a button to open conversations in Crisp.
   - **Description:** The view now shows the `people_id` and includes a button that links to the Crisp chat session, enhancing the admin's ability to manage conversations directly in Crisp.
   - **Impact:** Improves the admin's workflow by providing direct access to Crisp chat sessions, enhancing efficiency in managing user and lead conversations.

7. **File: `resources/views/admin/lead/profile.blade.php`**
   - **Status:** Modified
   - **Changes:** Added a button for sending mail and integrated the `LeadConversations` component.
   - **Description:** This update includes a new button for sending emails directly from the lead profile and integrates the `LeadConversations` component to display lead conversations.
   - **Impact:** Enhances the admin's ability to manage lead communications and view conversation history directly from the lead profile page.

8. **File: `resources/views/admin/user/profile.blade.php`**
   - **Status:** Modified
   - **Changes:** Adjusted the layout to include the `UserConversations` component.
   - **Description:** The user profile page now includes the `UserConversations` component, allowing admins to view and manage user conversations directly from the profile page.
   - **Impact:** Improves the admin's ability to manage user communications and view conversation history, enhancing overall user support capabilities.

---

# #215 Pull Request

## Introduction
This pull request introduces several significant changes and additions to the admin section of the application, focusing on enhancing the user experience and functionality related to lead management. The key updates include the addition of a new feature for managing lead conversations, improvements to the lead notes functionality, and various model and view updates to support these changes. These updates aim to provide a more seamless and efficient way for administrators to interact with and manage leads, ultimately improving the overall user experience and system robustness.

## Changes Overview
1. **File: `app/Livewire/Admin/LeadConversations.php`**
   - **Status:** Added
   - **Changes:** Introduced a new Livewire component for managing lead conversations.
   - **Description:** This component handles the loading and displaying of conversations and messages related to a specific lead. It includes methods for loading conversations, loading messages, switching between conversation tabs, and loading more messages.
   - **Impact:** Enhances the admin's ability to manage and view lead conversations, providing a more organized and user-friendly interface for handling multiple conversations.

2. **File: `resources/views/admin/components/profile-conversations.blade.php`**
   - **Status:** Added
   - **Changes:** Added a new Blade view for displaying lead conversations.
   - **Description:** This view includes the layout and styling for displaying conversation tabs and messages. It supports switching between different conversations and loading more messages dynamically.
   - **Impact:** Provides a visually appealing and functional interface for viewing and interacting with lead conversations, improving the overall user experience.

3. **File: `app/Livewire/Admin/FormAddLead.php`**
   - **Status:** Modified
   - **Changes:** Added a 'label' field to the lead address data.
   - **Description:** This change ensures that the label 'Main' is added to the lead address data when a new lead is created.
   - **Impact:** Improves data consistency by ensuring that all lead addresses have a label, which can be useful for categorization and retrieval.

4. **File: `app/Livewire/Admin/LeadNotes.php`**
   - **Status:** Modified
   - **Changes:** Updated the component to handle pagination and dynamic loading of notes.
   - **Description:** The component now initializes with an empty collection of notes and loads more notes dynamically as the user scrolls. It also includes pagination logic to handle loading notes in chunks.
   - **Impact:** Enhances the performance and user experience by loading notes incrementally, reducing the initial load time and improving the responsiveness of the interface.

5. **File: `app/Models/CrispMessage.php`**
   - **Status:** Modified
   - **Changes:** Added a relationship method to link messages to sessions.
   - **Description:** This method defines a belongs-to relationship between `CrispMessage` and `CrispSession`.
   - **Impact:** Improves the data model by establishing clear relationships between messages and sessions, facilitating easier data retrieval and manipulation.

6. **File: `app/Models/CrispPeople.php`**
   - **Status:** Modified
   - **Changes:** Added relationship methods to link people to users, leads, and sessions.
   - **Description:** These methods define belongs-to and has-many relationships, enhancing the model's ability to navigate related data.
   - **Impact:** Provides a more robust and interconnected data model, allowing for more complex queries and data manipulations.

7. **File: `app/Models/CrispSession.php`**
   - **Status:** Modified
   - **Changes:** Added relationship methods to link sessions to people and messages.
   - **Description:** These methods define belongs-to and has-many relationships, improving the model's relational capabilities.
   - **Impact:** Enhances the data model's integrity and usability, making it easier to work with related data.

8. **File: `resources/views/admin/lead/profile.blade.php`**
   - **Status:** Modified
   - **Changes:** Updated the profile view to include the new lead conversations component and adjusted the layout for lead notes.
   - **Description:** This change integrates the new lead conversations feature into the lead profile view and refines the layout for better usability.
   - **Impact:** Improves the lead profile interface by adding new functionality and enhancing the layout, providing a more comprehensive view of lead-related information.

9. **File: `resources/views/admin/components/profile-notes.blade.php`**
   - **Status:** Renamed and Modified
   - **Changes:** Renamed from `lead-notes.blade.php` and updated to include dynamic loading of notes.
   - **Description:** The view now supports dynamic loading of notes and includes a button to load more notes, improving the user experience.
   - **Impact:** Enhances the notes interface by allowing users to load notes incrementally, reducing initial load times and improving performance.

---

# #214 Pull Request

## Introduction
This pull request introduces several modifications across multiple files, aimed at improving the application's functionality, user experience, and maintainability. The changes include enhancements to the GitHub pull request handling, updates to the webhook controller, removal of unnecessary logging, and configuration updates for various APIs. These updates are expected to streamline the process of handling pull requests, ensure better data handling in webhooks, and improve the overall configuration management of API keys and URLs.

## Changes Overview
1. **File: `app/Console/Commands/GithubWTD.php`**
   - **Status:** Modified
   - **Changes:** 
     - Reformatting of the code to improve readability.
     - Enhanced logic for processing GitHub pull request descriptions.
     - Added checks and modifications for pull request titles and bodies.
     - Improved error handling and logging.
   - **Description:** The changes were made to improve the readability and maintainability of the code. The logic for handling pull request descriptions and titles has been refined to ensure accurate updates. Error handling has been enhanced to provide better logging and debugging information.
   - **Impact:** These changes will make the code easier to maintain and debug, and ensure that pull request titles and bodies are processed correctly.

2. **File: `app/Http/Controllers/WebhookController.php`**
   - **Status:** Modified
   - **Changes:** 
     - Reordered the update of `people_id` and `last_activity` fields in the `crispSession` update method.
   - **Description:** This change ensures that the `people_id` is updated before the `last_activity`, which might be a logical requirement for the correct processing of webhook data.
   - **Impact:** This minor change ensures the correct order of operations when updating session data, potentially preventing data inconsistencies.

3. **File: `app/Services/CrispService.php`**
   - **Status:** Modified
   - **Changes:** 
     - Removed an unnecessary logging statement.
   - **Description:** The removal of the logging statement was likely done to clean up the code and reduce unnecessary log output.
   - **Impact:** This change will reduce the amount of log data generated, making logs cleaner and more relevant.

4. **File: `config/app_custom.php`**
   - **Status:** Modified
   - **Changes:** 
     - Added new configuration entries for various APIs (CloudConvert, CPFCNPJ, Asaas, Crisp, ContaAzul, Facebook, TikTok).
     - Removed duplicate or outdated configuration entries.
   - **Description:** The configuration file has been updated to include new API configurations and remove redundant entries. This ensures that all necessary API keys and URLs are properly configured and managed.
   - **Impact:** These changes improve the configuration management of the application, ensuring that all necessary APIs are correctly set up and reducing the risk of configuration errors.

---

# #214 Pull Request

## Introduction
This pull request includes a series of modifications aimed at improving the functionality, maintainability, and security of the application. The changes span several files and involve updates to API requests, configuration settings, and logging mechanisms. The primary focus areas include:

- Enhancements to the GitHub Pull Request handling logic.
- Minor fixes in the Crisp webhook handling.
- Removal of unnecessary logging in the Crisp service.
- Consolidation and reorganization of configuration settings.

These updates are expected to improve the application's efficiency in handling API requests, ensure better organization of configuration settings, and streamline the logging process.

## Changes Overview
1. **File: `app/Console/Commands/GithubWTD.php`**
   - **Status:** Modified
   - **Changes:** 41 additions, 34 deletions
   - **Description:** 
     - Refactored the API request to OpenAI for better readability and maintainability.
     - Added logic to clean up and format the content fetched from OpenAI, specifically handling the "Pull Request Description" and "Headline" sections.
     - Updated the logic for inserting the pull request number into the `version.md` file.
     - Simplified the process of updating the GitHub Pull Request title and body.
   - **Impact:** 
     - Improved code readability and maintainability.
     - Enhanced the accuracy and formatting of the data fetched from OpenAI.
     - Streamlined the process of updating GitHub Pull Requests, reducing potential errors.

2. **File: `app/Http/Controllers/WebhookController.php`**
   - **Status:** Modified
   - **Changes:** 1 addition, 1 deletion
   - **Description:** 
     - Fixed the order of updating the `people_id` and `last_activity` fields in the Crisp session update logic.
   - **Impact:** 
     - Ensured the correct order of operations when updating Crisp session data, potentially preventing data inconsistencies.

3. **File: `app/Services/CrispService.php`**
   - **Status:** Modified
   - **Changes:** 1 deletion
   - **Description:** 
     - Removed an unnecessary logging statement that was used for debugging purposes.
   - **Impact:** 
     - Reduced unnecessary logging, which can improve performance and reduce log clutter.

4. **File: `config/app_custom.php`**
   - **Status:** Modified
   - **Changes:** 40 additions, 39 deletions
   - **Description:** 
     - Reorganized and consolidated API configuration settings for various services such as CloudConvert, CPFCNPJ, Asaas, Crisp, ContaAzul, Facebook, and TikTok.
     - Ensured that sensitive information is conditionally loaded based on the environment (production or non-production).
   - **Impact:** 
     - Improved organization and readability of the configuration file.
     - Enhanced security by ensuring that sensitive information is appropriately managed based on the environment.

---

# #213 Enhancements to Crisp Session Management: Database Migration, Command Update, Model Adjustment, and Service Improvement

## Introduction
This pull request introduces several key changes aimed at enhancing the management of Crisp sessions within the application. The changes include a new database migration to add columns to the `crisp_sessions` table, modifications to the `SyncCrispPeople` command, updates to the `CrispSession` model, and significant improvements to the `CrispService`. These updates will improve the application's functionality by allowing more detailed session tracking, enhance the user experience by ensuring better data synchronization, and maintain the overall architecture's robustness.

## Changes Overview
1. **File: `database/migrations/2024_08_26_092456_add_columns_to_crisp_sessions_table.php`**
   - **Status:** Added
   - **Changes:** Introduced a new migration file to add three columns (`meta`, `status`, `is_blocked`) to the `crisp_sessions` table.
   - **Description:** 
     - The `meta` column is of type JSON and nullable, allowing storage of additional metadata.
     - The `status` column is a nullable string to store the session's status.
     - The `is_blocked` column is a boolean with a default value of `false` to indicate if a session is blocked.
   - **Impact:** These changes will allow for more detailed tracking and management of session data, providing greater flexibility and control over session states and metadata.

2. **File: `app/Console/Commands/SyncCrispPeople.php`**
   - **Status:** Modified
   - **Changes:** Swapped the calls to `getAllPeople` and `getAllConversations` methods.
   - **Description:** The command now calls `getAllConversations` instead of `getAllPeople` to sync conversation data from the Crisp API.
   - **Impact:** This change shifts the focus of the synchronization process to conversations rather than people, which might be more relevant for current application needs.

3. **File: `app/Models/CrispSession.php`**
   - **Status:** Modified
   - **Changes:** Updated the `$fillable` property to include the new columns (`meta`, `status`, `is_blocked`) and removed the old ones (`p_id_changed`, `user_id`, `lead_id`).
   - **Description:** This update ensures that the new columns can be mass-assigned while removing obsolete columns.
   - **Impact:** This change aligns the model with the new database schema, ensuring data integrity and consistency.

4. **File: `app/Services/CrispService.php`**
   - **Status:** Modified
   - **Changes:** 
     - Added logging for conversation processing.
     - Included the `status` field in session creation and updates.
     - Enhanced the logic for handling `lastActivity` and improved the matching process for Instagram usernames and phone numbers.
     - Added logic to update the `meta` column if no `people_id` is found.
   - **Description:** 
     - Logging helps in tracking the processing of each conversation.
     - Including the `status` field ensures that the session's state is accurately recorded.
     - Improved logic for `lastActivity` and matching processes enhances data accuracy.
     - Updating the `meta` column ensures that all relevant metadata is stored even if no `people_id` is found.
   - **Impact:** These changes improve the robustness and accuracy of session data processing, leading to better data management and potentially more insightful analytics.

---

# #212 Addition of New Features and Refactoring for Lead Management and Crisp Integration

## Introduction
This pull request introduces several new features and significant refactoring to the application. The changes include the addition of new console commands, Livewire components for managing leads, updates to the database schema, and enhancements to the Crisp integration service. These updates aim to improve the application's functionality, user experience, and maintainability. The main areas of change are:

- New feature additions for lead management (addresses, emails, notes, people, phones, websites).
- Security improvements by validating user permissions.
- UX/UI enhancements with new Livewire components.
- Route updates and command renaming for better organization.
- Database schema updates to support new features and improve data integrity.

## Changes Overview
1. **File: `app/Console/Commands/SyncCrispPeople.php`**
   - **Status:** Added
   - **Changes:** Introduced a new console command `SyncCrispPeople` to sync people data from the Crisp API.
   - **Description:** This command uses the `CrispService` to fetch and sync people and conversation data from the Crisp API.
   - **Impact:** Automates the synchronization of Crisp data, ensuring the application has the latest information from Crisp.

2. **File: `app/Livewire/Admin/LeadAddresses.php`**
   - **Status:** Added
   - **Changes:** Added a new Livewire component to manage lead addresses.
   - **Description:** This component allows users to add, validate, and display addresses associated with a lead.
   - **Impact:** Enhances lead management by allowing users to associate multiple addresses with a lead.

3. **File: `app/Livewire/Admin/LeadEmails.php`**
   - **Status:** Added
   - **Changes:** Added a new Livewire component to manage lead emails.
   - **Description:** This component allows users to add, validate, and display emails associated with a lead.
   - **Impact:** Improves lead management by enabling users to manage multiple email addresses for a lead.

4. **File: `app/Livewire/Admin/LeadNotes.php`**
   - **Status:** Added
   - **Changes:** Added a new Livewire component to manage lead notes.
   - **Description:** This component allows users to add, edit, and display notes associated with a lead.
   - **Impact:** Provides a way to keep detailed notes on leads, improving lead tracking and follow-up.

5. **File: `app/Livewire/Admin/LeadPeople.php`**
   - **Status:** Added
   - **Changes:** Added a new Livewire component to manage lead people.
   - **Description:** This component allows users to add, validate, and display people associated with a lead.
   - **Impact:** Enhances lead management by allowing users to track individuals associated with a lead.

6. **File: `app/Livewire/Admin/LeadPhones.php`**
   - **Status:** Added
   - **Changes:** Added a new Livewire component to manage lead phones.
   - **Description:** This component allows users to add, validate, and display phone numbers associated with a lead.
   - **Impact:** Improves lead management by enabling users to manage multiple phone numbers for a lead.

7. **File: `app/Livewire/Admin/LeadWebsites.php`**
   - **Status:** Added
   - **Changes:** Added a new Livewire component to manage lead websites.
   - **Description:** This component allows users to add, validate, and display websites associated with a lead.
   - **Impact:** Enhances lead management by allowing users to associate multiple websites with a lead.

8. **File: `app/Models/LeadPerson.php`**
   - **Status:** Added
   - **Changes:** Added a new model for lead people.
   - **Description:** This model represents individuals associated with a lead.
   - **Impact:** Supports the new feature for managing people associated with leads.

9. **File: `app/Services/CrispService.php`**
   - **Status:** Added
   - **Changes:** Added a new service for interacting with the Crisp API.
   - **Description:** This service handles fetching and processing data from the Crisp API.
   - **Impact:** Centralizes Crisp API interactions, improving code maintainability and readability.

10. **File: `database/migrations/2024_08_25_133559_change_lead_lists_column_type_in_leads_table.php`**
    - **Status:** Added
    - **Changes:** Migration to change the `lead_lists` column type in the `leads` table.
    - **Description:** This migration changes the column type to an integer to support the new lead list structure.
    - **Impact:** Ensures data integrity and supports the new lead list feature.

11. **File: `database/migrations/2024_08_25_162342_create_lead_people_table.php`**
    - **Status:** Added
    - **Changes:** Migration to create the `lead_people` table.
    - **Description:** This migration creates a new table to store people associated with leads.
    - **Impact:** Supports the new feature for managing people associated with leads.

12. **File: `database/migrations/2024_08_25_162802_add_branch_to_leads_table.php`**
    - **Status:** Added
    - **Changes:** Migration to add new columns to the `leads` table.
    - **Description:** This migration adds `branch`, `type`, and `status` columns to the `leads` table.
    - **Impact:** Enhances the lead data model to support additional lead attributes.

13. **File: `database/migrations/2024_08_25_180635_add_data_to_crisp_people_table.php`**
    - **Status:** Added
    - **Changes:** Migration to add a `data` column to the `crisp_people` table.
    - **Description:** This migration adds a JSON column to store additional data for Crisp people.
    - **Impact:** Supports storing nested data from the Crisp API.

14. **File: `database/migrations/2024_08_25_225538_drop_crisp_events_table.php`**
    - **Status:** Added
    - **Changes:** Migration to drop the `crisp_events` table and update related tables.
    - **Description:** This migration removes the `crisp_events` table and updates the `crisp_people` and `crisp_sessions` tables.
    - **Impact:** Simplifies the data model and removes unnecessary tables.

15. **File: `app/Console/Kernel.php`**
    - **Status:** Modified
    - **Changes:** Added new scheduled commands and updated existing ones.
    - **Description:** This update schedules the new `crisp:sync-people` command and renames existing email commands.
    - **Impact:** Ensures the new command runs automatically and improves command organization.

16. **File: `app/Http/Controllers/AdminController.php`**
    - **Status:** Modified
    - **Changes:** Added new methods for managing users and leads.
    - **Description:** These methods handle user and lead management, including permission checks and data updates.
    - **Impact:** Enhances user and lead management capabilities and improves security by validating permissions.

17. **File: `app/Http/Controllers/WebhookController.php`**
    - **Status:** Modified
    - **Changes:** Refactored the Crisp webhook handling logic.
    - **Description:** This update simplifies the webhook logic and removes the `CrispEvents` model.
    - **Impact:** Improves code readability and maintainability.

18. **File: `app/Livewire/Admin/FormAddLead.php`**
    - **Status:** Modified
    - **Changes:** Updated to use the new `lead_list` column.
    - **Description:** This update changes the form to use the new `lead_list` column instead of `lead_lists`.
    - **Impact:** Ensures compatibility with the updated database schema.

19. **File: `app/Models/CrispPeople.php`**
    - **Status:** Modified
    - **Changes:** Added the `data` attribute to the fillable array.
    - **Description:** This update allows the `data` attribute to be mass-assigned.
    - **Impact:** Supports storing additional data for Crisp people.

20. **File: `app/Models/Lead.php`**
    - **Status:** Modified
    - **Changes:** Added new attributes and relationships.
    - **Description:** This update adds `branch`, `type`, `status`, and relationships to the `Lead` model.
    - **Impact:** Enhances the lead data model to support additional attributes and relationships.

21. **File: `app/Models/LeadNote.php`**
    - **Status:** Modified
    - **Changes:** Added a relationship to the `User` model.
    - **Description:** This update adds a relationship to the `User` model for the `created_by` attribute.
    - **Impact:** Supports tracking the user who created a note.

22. **File: `config/app_custom.php`**
    - **Status:** Modified
    - **Changes:** Added Crisp API configuration.
    - **Description:** This update adds configuration settings for the Crisp API.
    - **Impact:** Centralizes Crisp API configuration, making it easier to manage.

23. **File: `app/Console/Commands/Cloudconvert/OrderFiles.php`**
    - **Status:** Renamed
    - **Changes:** Renamed and updated namespace.
    - **Description:** This command was renamed and moved to the `Cloudconvert` namespace.
    - **Impact:** Improves command organization and readability.

24. **File: `app/Console/Commands/Cloudconvert/References.php`**
    - **Status:** Renamed
    - **Changes:** Renamed and updated namespace.
    - **Description:** This command was renamed and moved to the `Cloudconvert` namespace.
    - **Impact:** Improves command organization and readability.

25. **File: `app/Console/Commands/Cloudconvert/Setcardvideo.php`**
    - **Status:** Renamed
    - **Changes:** Renamed and updated namespace.
    - **Description:** This command was renamed and moved to the `Cloudconvert` namespace.
    - **Impact:** Improves command organization and readability.

26. **File: `app/Console/Commands/Sendmail/BusinessNewApplications.php`**
    - **Status:** Renamed
    - **Changes:** Renamed and updated namespace.
    - **Description:** This command was renamed and moved to the `Sendmail` namespace.
    - **Impact:** Improves command organization and readability.

27. **File: `app/Console/Commands/Sendmail/CreatorNewOrderAvailable.php`**
    - **Status:** Renamed
    - **Changes:** Renamed and updated namespace.
    - **Description:** This command was renamed and moved to the `Sendmail` namespace.
    - **Impact:** Improves command organization and readability.

28. **File: `app/Console/Commands/Sendmail/CreatorSetcardVideoMissing.php`**
    - **Status:** Renamed
    - **Changes:** Renamed and updated namespace.
    - **Description:** This command was renamed and moved to the `Sendmail` namespace.
    - **Impact:** Improves command organization and readability.

29. **File: `app/Console/Commands/Sendmail/LeadEmails.php`**
    - **Status:** Renamed
    - **Changes:** Renamed and updated namespace.
    - **Description:** This command was renamed and moved to the `Sendmail` namespace.
    - **Impact:** Improves command organization and readability.

30. **File: `app/Console/Commands/Sendmail/UserEmails.php`**
    - **Status:** Renamed
    - **Changes:** Renamed and updated namespace.
    - **Description:** This command was renamed and moved to the `Sendmail` namespace.
    - **Impact:** Improves command organization and readability.

---

# #207 Update Order Progress and File Display Logic in Dashboard

## Introduction
This pull request focuses on refining the order progress tracking and file display logic within the dashboard. The changes aim to improve the accuracy of file status checks and enhance the user experience by displaying appropriate images based on their approval status. These updates are crucial for maintaining accurate order tracking and providing a better visual representation of files to users. The main areas of changes include logic updates for file status checks and conditional image rendering based on file approval.

## Changes Overview
1. **File: `resources/views/dashboard/business/order/progress.blade.php`**
   - **Status:** Modified
   - **Changes:** Updated the condition to check if files are read instead of sent.
   - **Description:** The condition within the order progress button was changed from checking if files have a status of 'sent' to checking if files are marked as 'read'.
   - **Impact:** This change ensures that the progress indicator is based on whether files have been read, which may provide a more accurate reflection of order progress.

2. **File: `resources/views/dashboard/components/order-files.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Updated conditions to check for file counts using `== 0` instead of `< 1`.
     - Simplified conditional checks for file types (video, hook, image) and their counts.
     - Added logic to display either the original image or a watermarked version based on the file's approval status.
   - **Description:** 
     - The conditions for checking file counts were made more explicit by using `== 0` instead of `< 1`.
     - The conditional checks for file types were streamlined to improve readability and maintainability.
     - The image display logic was enhanced to show the watermarked version of an image if it is not approved, ensuring that only approved images are displayed without watermarks.
   - **Impact:** These changes improve the accuracy of file count checks, enhance code readability, and ensure that users see the appropriate version of images based on their approval status, thereby improving the overall user experience.

---

# #206 Enhanced Modal Design and Improved User Experience for Application Previews

## Introduction
This pull request introduces significant updates to the `applications.blade.php` file within the dashboard's business order livewire component. The changes primarily focus on enhancing the user interface and user experience of the application preview modal. The modifications include a more responsive design, improved accessibility, and a cleaner, more modern look. These updates are crucial for ensuring that users have a seamless and visually appealing experience when interacting with application previews. The changes also include performance improvements and better handling of loading states.

## Changes Overview
1. **File: `resources/views/dashboard/business/order/livewire/applications.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Updated the modal's class bindings to improve responsiveness and visibility.
     - Simplified the modal structure by reducing redundant divs and classes.
     - Enhanced the modal's visual design with better spacing, alignment, and typography.
     - Added a loading spinner to indicate when data is being fetched.
     - Improved the layout of the application preview details, making it more user-friendly and visually appealing.
     - Updated the close button design for better accessibility and usability.
     - Reorganized the content within the modal to provide a clearer hierarchy and better readability.
     - Added gradient overlays and improved image handling for better visual effects.
   - **Description:** 
     - The modal's class bindings were updated to ensure that it is always centered and visible when triggered. This change enhances the user experience by making the modal more responsive and easier to interact with.
     - Simplifying the modal structure reduces the complexity of the HTML, making it easier to maintain and improving performance.
     - The visual design enhancements, including better spacing, alignment, and typography, make the modal more modern and visually appealing. This is important for maintaining a professional look and feel.
     - Adding a loading spinner provides users with feedback when data is being fetched, improving the overall user experience by making the application feel more responsive.
     - The reorganization of the application preview details ensures that important information is easily accessible and readable, enhancing the usability of the modal.
     - The updated close button design improves accessibility by making it easier for users to close the modal, especially for those using assistive technologies.
     - The gradient overlays and improved image handling add visual interest and make the modal more engaging.
   - **Impact:**
     - These changes significantly improve the user experience by making the modal more responsive, accessible, and visually appealing.
     - The performance improvements and better handling of loading states ensure that users have a smoother and more seamless experience.
     - The enhanced design and usability of the application preview modal contribute to a more professional and polished look for the application, which can positively impact user satisfaction and engagement.

---

# #206 Improved Modal Design and Layout for Order Applications

## Introduction
This pull request focuses on enhancing the user interface and user experience of the order applications modal within the dashboard. The changes involve significant modifications to the Blade template file, which integrates Livewire and AlpineJS for dynamic behavior. The primary goal is to improve the visual presentation, accessibility, and responsiveness of the modal, making it more intuitive and user-friendly. The changes include UI/UX enhancements, code refactoring, and better alignment with modern design principles.

## Changes Overview
1. **File: `resources/views/dashboard/business/order/livewire/applications.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Refactored the modal's class bindings for better readability and maintainability.
     - Updated the modal's layout to use a grid system for a more responsive design.
     - Enhanced the visual presentation of the modal with improved styling and alignment.
     - Simplified the structure of the modal content, including the user profile and application details.
     - Added a loading spinner to provide feedback during data loading.
     - Removed redundant and outdated code to streamline the modal's functionality.
   - **Description:** 
     - The modal's class bindings have been refactored to use more descriptive and consistent class names, improving readability and maintainability.
     - The layout has been updated to use a grid system, which enhances the responsiveness and adaptability of the modal across different screen sizes.
     - Visual enhancements include better alignment, spacing, and styling to create a more polished and professional look.
     - The structure of the modal content has been simplified, focusing on key information such as the user profile and application details, making it easier for users to navigate and understand.
     - A loading spinner has been added to provide visual feedback during data loading, improving the user experience.
     - Redundant and outdated code has been removed to streamline the modal's functionality and reduce potential maintenance issues.
   - **Impact:**
     - The improved modal design enhances the overall user experience by making the interface more intuitive and visually appealing.
     - The responsive layout ensures that the modal is accessible and usable across various devices and screen sizes.
     - The addition of a loading spinner provides better feedback to users, reducing uncertainty during data loading.
     - The refactored codebase is easier to maintain and extend, which can lead to faster development cycles and fewer bugs.

This description provides a clear and structured overview of the changes made in the pull request, making it accessible to both technical and non-technical stakeholders.

---

# #205 New Command & Models Integration for Crisp Chat Data Management

## Introduction
This pull request introduces a significant new feature to the application by integrating a command that imports data from Crisp Chat webhook into various tables within the system. This integration entails adding new models, updating existing controllers, and introducing migration files for necessary database tables. The changes will streamline data synchronization between Crisp Chat and the application, improving data management efficiency and user interaction tracking. Additionally, minor adjustments have been made in the JavaScript to handle user data dynamically. 

Overall, the main areas of changes include:
- New Feature Addition: `CrispImport.php` command and associated model classes/files for data handling.
- Database Schema Updates: New migration files for tables related to Crisp Chat data.
- Controller Updates: Logic additions to manage Crisp Chat webhook and import data.
- UX/UI Enhancement: Ensuring valid email display in the Crisp Chat interface.

## Changes Overview
1. **File: `app/Console/Commands/CrispImport.php`**
   - **Status:** Added
   - **Changes:** 200 lines added introducing a new command.
   - **Description:** This command processes incoming webhooks from Crisp Chat. It extracts, verifies, and saves data into appropriate tables (`CrispPeople`, `CrispSession`, `CrispMessage`, `CrispEvents`).
   - **Impact:** Automates the synchronization and logging of interaction data from Crisp Chat into the application's database, enhancing data accuracy and reducing manual handling.

2. **File: `app/Models/CrispEvents.php`**
   - **Status:** Added
   - **Changes:** 21 lines added defining the `CrispEvents` model.
   - **Description:** This model represents events captured from Crisp Chat, mapping to the `crisp_events` table and managing event-related data.
   - **Impact:** Facilitates structured storage and retrieval of event data from Crisp Chat.

3. **File: `app/Models/CrispMessage.php`**
   - **Status:** Added
   - **Changes:** 23 lines added defining the `CrispMessage` model.
   - **Description:** Handles the message data from Crisp Chat and connects to the `crisp_messages` table.
   - **Impact:** Ensures message data from Crisp Chat is appropriately stored and accessible.

4. **File: `app/Models/CrispPeople.php`**
   - **Status:** Added
   - **Changes:** 21 lines added introducing the `CrispPeople` model.
   - **Description:** Model for storing information about individuals interacted with via Crisp Chat.
   - **Impact:** Helps synchronize and manage user-related data from Crisp Chat effectively.

5. **File: `app/Models/CrispSession.php`**
   - **Status:** Added
   - **Changes:** 22 lines added defining the `CrispSession` model.
   - **Description:** Manages session data linked to Crisp Chat, mapping to its respective database table.
   - **Impact:** Ensures session information from Crisp Chat is accurately reflected in the application’s database.

6. **File: `database/migrations/2024_08_14_125908_create_crisp_messages_table.php`**
   - **Status:** Added
   - **Changes:** 34 lines introducing the migration for `crisp_messages` table.
   - **Description:** Schema setup for storing message-related data from Crisp Chat.
   - **Impact:** Establishes a dedicated structure for storing message data from Crisp, aiding in the organization and management of communication logs.

7. **File: `database/migrations/2024_08_14_125933_create_crisp_sessions_table.php`**
   - **Status:** Added
   - **Changes:** 33 lines added for migrating the `crisp_sessions` table.
   - **Description:** Sets up the database schema for managing session data from Crisp Chat.
   - **Impact:** Provides a foundation to store and manage session activity data, improving data tracking.

8. **File: `database/migrations/2024_08_14_130016_create_crisp_events_table.php`**
   - **Status:** Added
   - **Changes:** 32 lines added to create the `crisp_events` table.
   - **Description:** Migration creating a table for storing various events captured from Crisp Chat.
   - **Impact:** Supports the structured logging of event data, enhancing the ability to track and analyze chat interactions.

9. **File: `database/migrations/2024_08_14_211730_create_crisp_people_table.php`**
   - **Status:** Added
   - **Changes:** 32 lines defining the migration for the `crisp_people` table.
   - **Description:** Schema definition for storing people data from Crisp Chat.
   - **Impact:** Aids in the maintenance and synchronization of user-related data across systems.

10. **File: `app/Http/Controllers/AdminController.php`**
    - **Status:** Modified
    - **Changes:** 44 additions, 37 deletions.
    - **Description:** Refactored methods related to bad word management, ensuring a clean structure and functional consistency.
    - **Impact:** Streamlines the process of managing flagged words, enhancing the admin control panel functionality.

11. **File: `app/Http/Controllers/WebhookController.php`**
    - **Status:** Modified
    - **Changes:** 162 additions, 3 deletions.
    - **Description:** Adds logic to handle Crisp Chat webhooks, parsing and saving data into relevant models.
    - **Impact:** Ensures that incoming webhooks from Crisp Chat are processed and the data is synchronized with the system, enhancing real-time data integration.

12. **File: `resources/js/crispChat.js`**
    - **Status:** Modified
    - **Changes:** 3 additions, 1 deletion.
    - **Description:** Enhances the script to conditionally set user email in Crisp Chat.
    - **Impact:** Improves robustness by ensuring only valid email addresses are set, preventing errors.

13. **File: `resources/views/layouts/partials/head.blade.php`**
    - **Status:** Modified
    - **Changes:** 3 additions, 1 deletion.
    - **Description:** Adds a conditional check to exclude deleted accounts from setting an email in Crisp Chat.
    - **Impact:** Enhances user data handling by ensuring the accuracy of displayed information.

This pull request represents a comprehensive augmentation of the system’s integration with Crisp Chat, enhancing data management, synchronization, and overall application functionality.

---

# #203 Update to Email Input Field in Password Reset View

## Introduction
This pull request modifies the email input field within the password reset view template of the application. The changes have significant impacts on the user experience and security of the application. The field's appearance and behavior have been altered to prevent users from changing the email address when resetting their password, thus ensuring that the password reset process is securely tied to the email address initially provided.

## Changes Overview
1. **File: `resources/views/auth/reset-password.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Changed the `input` element for the email field to:
    ```html
    <input type="email" name="email" value="{{ request()->get('email', old('email')) }}" id="email" class="bg-gray-100 cursor-not-allowed authpage-input-field dark:bg-neutral-700" placeholder=" " required readonly autocomplete="username" />
    ```
  - Modified CSS classes to include `bg-gray-100 cursor-not-allowed` and `dark:bg-neutral-700`.
  - Changed the input field to be `readonly`.
  
- **Description:** 
  - The `:value` binding for the input field has been replaced with standard Blade syntax `{{ }}` to ensure proper data binding.
  - CSS classes have been updated to provide different background colors and cursor style to indicate the field is non-editable.
  - The field has been set to `readonly` to ensure users cannot alter the email once it is populated.

- **Impact:**
  - **Functionality:** Users will no longer be able to edit the email address when resetting their password, reducing the risk of email address manipulation during the password reset process.
  - **Security:** This change enhances security by ensuring that the password reset process is firmly tied to the email address originally submitted by the user.
  - **User Experience:** The visual indication (grayed out field and restricted cursor) clearly communicates to users that the email address cannot be changed at this stage, thus reducing potential confusion.
  - **Overall Architecture:** Minimal impact on overall architecture but improves the robustness of the password reset workflow by enforcing immutability on the email field during the reset process.

---

# #202 Enhanced Email Deletion, Improved Error Handling, and Miscellaneous Fixes Pull Request

## Introduction
This pull request addresses several critical areas, encompassing new feature additions, enhanced error handling, and minor UI adjustments to improve the overall user experience. The primary changes include:
- Enhancing the email deletion process.
- Modifying error handling to improve UX.
- Updating UI components for better accessibility and visual consistency.

## Changes Overview
1. **File: `app/Http/Controllers/AdminController.php`**
- **Status:** Modified
- **Changes:** Updated the email modification logic to include the current date when marking an email as deleted.
- **Description:** Ensures that email addresses of deleted users are more unique by prefixing with the current date.
- **Impact:** Enhances traceability and reduces potential conflicts with email addresses of deleted users.

2. **File: `app/Http/Controllers/TaskController.php`**
- **Status:** Modified
- **Changes:** 
  - Redirects changes from specific task overview to a more general dashboard or the previous page.
  - Added default empty string handling for the application message.
- **Description:** Provides more appropriate feedback routes and prevents errors when the application message is null.
- **Impact:** Improves user flow and ensures application stability even if optional fields are left empty.

3. **File: `app/Http/Controllers/UserProfileController.php`**
- **Status:** Modified
- **Changes:** Adjusted the redirect success message post-wallet payout operation.
- **Description:** Updates the success message to use a more relevant localization key.
- **Impact:** Minor UI/UX improvement by ensuring correct messages are shown to the user.

4. **File: `app/Livewire/CustomDeleteUser.php`**
- **Status:** Modified
- **Changes:** Similar to AdminController, included the current date when modifying the email of deleted users.
- **Description:** Introduces the same email uniqueness logic as AdminController for consistency.
- **Impact:** Ensures uniform handling of deleted user details across different components.

5. **File: `app/Livewire/OnboardingForm.php`**
- **Status:** Modified
- **Changes:** 
  - Updates the user’s birthday to ensure it is correctly formatted and validated.
  - Adds null checks to safeguard against missing response data.
- **Description:** Prevents faulty date conversion and ensures robust handling of API responses.
- **Impact:** Enhances data integrity and UI form validation.

6. **File: `app/Services/CloudConvert.php`**
- **Status:** Modified
- **Changes:** Removed exception throws when export tasks fail, retaining error logging.
- **Description:** Streamlines the control flow by removing direct exception throws, opting instead to log errors.
- **Impact:** Potentially smoothens error handling during batch processing, but may reduce immediate visibility of critical failures.

7. **File: `config/backup.php`**
- **Status:** Modified
- **Changes:** Adjusted the notifications array to remove email from various notification types.
- **Description:** Refines backup notification settings by disabling email notifications.
- **Impact:** Reduces clutter from email notifications, shifting alert mechanisms perhaps to other channels.

8. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** Added a new success message for wallet balance transfer.
- **Description:** Enhances localization by adding Portuguese language support for a new success message.
- **Impact:** Improves user feedback in Portuguese-speaking regions.

9. **File: `resources/views/admin/components/menu.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted user avatar image size and styles.
- **Description:** Ensures avatars are uniformly styled and sized across different devices.
- **Impact:** Provides better visual consistency within the user interface.

10. **File: `resources/views/admin/user/payout.blade.php`**
- **Status:** Modified
- **Changes:** Refactored the HTML structure of user payout table rows for better readability and access.
- **Description:** Enhances table layout by separating data cells and adding more href links for improved navigation.
- **Impact:** Improves aesthetics and usability of the admin payout interface.

These changes cumulatively aim to enhance the application's robustness, user experience, and maintainability by introducing more consistent handling of user data, refining error feedback, and ensuring UI consistency.

---

# #201 Update to Language Localization and Wallet Payout Form in Dashboard

## Introduction
This pull request includes critical updates to the Portuguese (Brazil) language localization file and significant modifications to the wallet payout form within the dashboard. The changes aim to improve the clarity of messages related to payment methods and enhance user experience by adding a tooltip functionality that informs users to set up their payout method before attempting a payout. These adjustments help in making the application more intuitive and user-friendly, preventing errors related to missing payout information, and ensuring smoother transactions.

## Changes Overview

1. **File: `resources/lang/pt_br/dashboard.php`**
   - **Status:** Modified
   - **Changes:** 
     - Updated the label from 'Método de Pagamento' to 'Método de recebimento'.
     - Added a new entry 'payoutmethod_missing' to guide users to add a payout method if it is missing.
     - Updated the error messages to use 'recebimento' instead of 'pagamento'.
   - **Description:** 
     - The term 'Método de recebimento' (Method of receiving) is more accurate in this context as it pertains to payouts.
     - Introducing the 'payoutmethod_missing' entry helps in providing context-sensitive help to users directly within the interface.
     - The error message changes ensure consistency with the updated terminology, reducing confusion for users.
   - **Impact:** 
     - Improves clarity and user guidance related to payout processes.
     - Helps in preventing issues related to missing payout methods, thereby enhancing overall user experience and reducing potential support requests.

2. **File: `resources/views/dashboard/creator/wallet.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Added an `@if` condition to check whether the user has a payout method set up.
     - Introduced a tooltip that informs users they need to add a payout method if they attempt to submit the form without one.
     - Updated the button class and added new classes to handle the tooltip and disabled states more elegantly.
   - **Description:** 
     - The condition prevents the form from being submitted if the user has not set up a payout method, displaying a tooltip instead.
     - The tooltip provides a direct link to the profile page where users can add their payout method, improving navigation and usability.
   - **Impact:** 
     - Reduces the likelihood of form submission errors due to missing payout methods.
     - Enhances user interface with an informative tooltip, promoting better user self-service and reducing frustration.
     - Ensures smoother and more guided user interactions with the wallet payout feature.
     
By incorporating these updates, the application is expected to deliver a heightened user experience with better clarity in payment-related processes and a reduction in common user errors regarding payout setup.

---

# #200 Pull Request Description

## Headline
Add Lead Import Sample File and Update Lead Upload Validation

## Introduction
This pull request introduces several changes aimed at improving the lead import functionality. A new sample file for lead import has been added to the public directory, and specific file validation rules have been modified for the lead upload feature. Additionally, minor adjustments to the views have been made to enhance user experience by providing more informative instructions and removing unnecessary code. These changes collectively aim to streamline the lead import process and ensure users have the necessary resources and information for successful file uploads.

## Changes Overview

1. **File: `public/files/lead_import_sample.xlsx`**
- **Status:** Added
- **Changes:** A new Excel file named `lead_import_sample.xlsx` has been added.
- **Description:** This file serves as a sample template that users can download and use to format their lead data correctly before uploading.
- **Impact:** This addition provides users with a clear example of how their lead data should be structured, potentially reducing upload errors and support queries.

2. **File: `app/Http/Controllers/AdminController.php`**
- **Status:** Modified
- **Changes:** Modified the validation rule for lead file uploads in the `lead_upload_store` method.
   ```php
   - 'leadlist' => 'required|file|mimes:txt,csv,xls,xlsx',
   + 'leadlist' => 'required|file',
   ```
- **Description:** The validation now only checks if a file is uploaded, irrespective of the file type.
- **Impact:** This change relaxes file type restrictions, allowing more flexibility in the types of files that can be uploaded. However, it might increase the risk of users uploading incompatible file formats.

3. **File: `app/Models/LeadTempfile.php`**
- **Status:** Modified
- **Changes:** Added a new fillable attribute `list_id`.
   ```php
   + 'list_id',
   ```
- **Description:** This change allows the `LeadTempfile` model to handle a new attribute, `list_id`, which can be used for associating files with specific lists or categories.
- **Impact:** Adds more flexibility in how temporary lead files are managed and categorized in the system.

4. **File: `resources/views/admin/lead/mapping.blade.php`**
- **Status:** Modified
- **Changes:** Removed an unnecessary Livewire component call.
   ```html
   - @livewire('admin.modal-add-lead')
   ```
- **Description:** The removal of the `@livewire('admin.modal-add-lead')` line suggests a cleanup of unused or redundant code in the view template.
- **Impact:** This change simplifies the view and may improve page load times slightly by removing an unneeded component.

5. **File: `resources/views/admin/lead/upload.blade.php`**
- **Status:** Modified
- **Changes:** Added a link to download the sample file alongside the instructions for lead file upload.
   ```html
   + You can download the sample file here: <a href="{{ url('/files/lead_import_sample.xlsx') }}" class="font-bold">Download Sample File</a>
   ```
- **Description:** This modification provides a direct link for users to download the newly added sample file, making it more convenient for them to get started with the correct file format.
- **Impact:** Enhances user experience by providing easy access to a sample file, potentially reducing errors and improving the overall usability of the lead upload process.

---

# #199 Enhances Admin Roles Management and UI Improvements in User Profile

## Introduction
This pull request introduces significant changes to the AdminController and associated UI views, focusing on role management and new route additions. It includes new functionalities for changing user roles, permission checks for product and order viewing, and enhancements to the user profile interface. These changes are aimed at enhancing security with better permission checks, improving the user experience by allowing dynamic role changes, and maintaining overall system reliability by refactoring and adding cleaner routes.

## Changes Overview

1. **File: `app/Http/Controllers/AdminController.php`**
- **Status:** Modified
- **Changes:** Added several new methods (`changeRole`, `product_index`, `order_index`, `order_show`, `order_visible`, and `chat_index`), revised permission checks, and changed existing method implementations.
- **Description:** 
  - The `changeRole` method allows admin users to change the roles of other users, ensuring that the role is valid before applying changes.
  - Methods to handle product and order management (`product_index`, `order_index`, `order_show`, `order_visible`) were updated to include permission checks ensuring only authorized users can access these functionalities.
  - `chat_index` method to support viewing chat messages with similar permission checks.
- **Impact:**
  - Improves security by ensuring unauthorized users cannot access restricted functionalities.
  - Refactoring old methods to include permission checks enhances maintainability.
  - The role change feature facilitates dynamic role management, improving administrative efficiency.

2. **File: `resources/views/admin/user/profile.blade.php`**
- **Status:** Modified
- **Changes:** Enhanced user profile view to support dynamic role changes through a dropdown interface.
- **Description:**
  - Introduced a dropdown on the user profile page allowing admins to change the user's role directly from the interface.
  - Each role change option includes a form that sends a POST request to update the user's role.
- **Impact:**
  - Improves the user experience by providing an intuitive interface for role changes.
  - Reduces administrative overhead by allowing quick and easy role updates directly within the user profile view.

3. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** Added a new route to support the `changeRole` functionality.
- **Description:**
  - Added `Route::post('/change-role/{user}/{role}', [AdminController::class, 'changeRole'])->name('changeRole');` to support POST requests for changing user roles.
- **Impact:**
  - Ensures role change requests are routed correctly, supporting the newly implemented functionality in the AdminController.
  - Enhances overall application architecture by expanding the route table to include all administrative operations related to user management.

These changes collectively enhance the application's security, user experience, and administrative capabilities, positioning the platform for greater operational efficiency and improved Role-Based Access Control (RBAC) implementation.

---

# #198 Implementing Permission-Based Role Management for Admins

## Introduction
This pull request introduces a comprehensive overhaul to how admin permissions and roles are managed within the application. The changes include the implementation of a new permission model to better control admin actions based on assigned roles. Key enhancements involve the creation of a new `UserAdminPermission` model, associated Livewire components for dynamic updates, and Blade views for the user interface. Furthermore, the system security is bolstered by ensuring that only authorized admins can access certain functionalities, thereby improving overall application security and user experience.

## Changes Overview
1. **File: `app/Livewire/Admin/Roles.php`**
    - **Status:** Added
    - **Changes:** New Livewire component for managing admin roles and permissions.
    - **Description:** This file contains the logic to display and update admin roles and permissions using the Livewire framework.
    - **Impact:** Enables dynamic interaction with the admin role management interface, enhancing the admin user experience.

2. **File: `app/Models/UserAdminPermission.php`**
    - **Status:** Added
    - **Changes:** New Eloquent model for handling admin permissions.
    - **Description:** This model defines the schema and relationships for admin permissions, enabling CRUD operations.
    - **Impact:** Centralizes and streamlines the management of admin permissions within the application.

3. **File: `database/migrations/2024_08_07_112025_create_user_admin_permissions_table.php`**
    - **Status:** Added
    - **Changes:** Migration to create `user_admin_permissions` table.
    - **Description:** Defines the database schema for storing admin permissions.
    - **Impact:** Sets up the necessary database structure for the new permission model.

4. **File: `resources/views/admin/components/roles.blade.php`**
    - **Status:** Added
    - **Changes:** New Blade view for the admin roles interface.
    - **Description:** Provides the UI for displaying and toggling admin permissions.
    - **Impact:** Improves user interface for admin role management, making it more intuitive and accessible.

5. **File: `resources/views/admin/role/index.blade.php`**
    - **Status:** Added
    - **Changes:** New Blade view for the admin role index page.
    - **Description:** Integrates the roles component into the admin panel.
    - **Impact:** Enhances navigability and the overall structure of the admin panel.

6. **File: `app/Http/Controllers/AdminController.php`**
    - **Status:** Modified
    - **Changes:** Added checks for admin permissions for various actions and views.
    - **Description:** Incorporates permission checks to ensure that only authorized admins can access certain pages or perform specific actions.
    - **Impact:** Enhances security by restricting access based on admin permissions, preventing unauthorized actions.

7. **File: `app/Http/Middleware/CheckUserRole.php`**
    - **Status:** Modified
    - **Changes:** Added dependency for `UserAdminPermission` model.
    - **Description:** Middleware now checks permissions using the new admin permission model.
    - **Impact:** Improves the robustness of role-based access control.

8. **File: `app/Providers/VariablesServiceProvider.php`**
    - **Status:** Modified
    - **Changes:** Added logic to pass permission data to views.
    - **Description:** Ensures that views have access to the current admin’s permissions.
    - **Impact:** Enhances dynamic display logic based on admin permissions, improving UX.

9. **File: `app/Services/MessageFilterService.php`**
    - **Status:** Modified
    - **Changes:** Added checks to preserve tracking codes while masking phone numbers.
    - **Description:** Improves the message filtering process by preserving valid tracking codes.
    - **Impact:** Ensures important data, such as tracking codes, is not mistakenly obscured.

10. **File: `resources/lang/pt_br/admin.php`**
    - **Status:** Modified
    - **Changes:** Added translations for the role management terms.
    - **Description:** Introduces localization for new admin role management features.
    - **Impact:** Improves accessibility for Portuguese-speaking users.

11. **File: `resources/views/admin/components/sidebar.blade.php`**
    - **Status:** Modified
    - **Changes:** Added conditional display logic based on admin permissions.
    - **Description:** Integrates permission checks within the sidebar to dynamically hide/show menu items.
    - **Impact:** Improves navigation and access control within the admin panel.

12. **File: `resources/views/admin/user/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated data and UI elements to reflect the new permission model.
    - **Description:** Enhances the user index page with permission-based data.
    - **Impact:** Enhances clarity and usability by displaying relevant data based on permissions.

13. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added routes for new roles functionality.
    - **Description:** Introduces routing structure for managing admin roles.
    - **Impact:** Facilitates navigation and access to new role management features.

---

# #197 Improved Validation for Birthday Field in Onboarding Form

## Introduction
This pull request introduces an important enhancement to the user onboarding process. Specifically, it adds validation to the birthday field, ensuring that only valid dates are submitted. This improvement aims to increase the accuracy of the user data collected during the onboarding process, potentially reducing errors and improving overall data quality. The change primarily affects the application's functionality by adding an extra layer of validation, which will enhance user experience and prevent possible discrepancies in stored data.

## Changes Overview
1. **File: `app/Livewire/OnboardingForm.php`**
- **Status:** Modified
- **Changes:**
  ```diff
  - $this->user->data->update(['birthday' => $this->birthday]);
  + if (!empty($this->birthday) && strtotime($this->birthday)) {
  +     $this->user->data->update(['birthday' => $this->birthday]);
  + } else {
  +     $this->addError('birthday', __('validation.date', ['attribute' => 'data de nascimento']));
  + }
  ```
- **Description:** The function `updateBirthday` is modified to include a validation check before updating the user's birthday. This check ensures that the birthday field is not empty and contains a valid date. If the birthday is invalid or empty, an error message is added using the `addError` method.
- **Impact:**
  - **Functionality:** Enhances the validation process for the birthday field, reducing invalid entries.
  - **User Experience:** Improves user experience by providing clear feedback when invalid data is entered.
  - **Data Integrity:** Ensures that only valid dates are stored, improving the reliability and quality of the data in the system.

---

# #196 Enhanced Order and Product Management Sorting and UI Adjustments

## Introduction
The pull request introduces several updates aimed at enhancing the application's functionality and user experience. Primarily, it focuses on organizing the display of orders by their status, introducing an improved hierarchical structure, and making minor UI adjustments to ensure better presentation and usability of the dashboard views. These changes improve the application's efficiency in handling data and provide a clearer visual structure, enhancing overall user experience and maintainability.

## Changes Overview

1. **File: `app/Http/Controllers/DashboardController.php`**
   - **Status:** Modified
   - **Changes:** Added 3 lines, deleted 1 line.
   - **Description:** Modified the `dashboard` method to exclude orders with the status 'CANCELADO' and added a custom order prioritization for the remaining statuses.
     ```php
     $orders = Order::where('user_id', Auth::id())
                      ->where('status', '!=', 'CANCELADO')
                      ->orderByRaw("FIELD(status, 'AGUARDANDO PAGAMENTO', 'AGUARDANDO BRIEFING', 'ESCOLHA O CRIADOR', 'EM PRODUÇÃO', 'PENDENTE')")
                      ->get();
     ```
   - **Impact:** This change improves the usability of the dashboard by ensuring that the orders are displayed in a meaningful order, thereby helping users quickly grasp the status of their orders.

2. **File: `app/Http/Controllers/OrderProcessController.php`**
   - **Status:** Modified
   - **Changes:** Added 3 lines, deleted 3 lines.
   - **Description:** Modified the `list` method to exclude orders with the status 'CANCELADO' and added the same custom order prioritization logic.
     ```php
     $orders = Order::where('user_id', Auth::id())
                      ->where('status', '!=', 'CANCELADO')
                      ->orderByRaw("FIELD(status, 'AGUARDANDO PAGAMENTO', 'AGUARDANDO BRIEFING', 'ESCOLHA O CRIADOR', 'EM PRODUÇÃO', 'PENDENTE')")
                      ->get();
     ```
   - **Impact:** Enhances order display effectiveness in the order processing view, helping users manage and process orders more efficiently.

3. **File: `resources/lang/pt_br/dashboard.php`**
   - **Status:** Modified
   - **Changes:** Changed 1 line.
   - **Description:** Updated a text string to improve clarity.
     ```php
     'check_orders' => 'Ver Produção',
     ```
   - **Impact:** Improves user understanding by using more accurate terminology in the interface.

4. **File: `resources/views/dashboard/business/order/index.blade.php`**
   - **Status:** Modified
   - **Changes:** Added 2 lines, deleted 2 lines.
   - **Description:** Updated the CSS classes for links to ensure a more consistent user interface by changing the line-clamp from 2 to 1.
     ```html
     <a href="{{ route('orders.create_order') }}" class="text-sm font-semibold text-center md:text-base 2xl:text-lg text-creatify-1 dark:text-creatify-3 after:absolute after:inset-0 line-clamp-1">{{ __('dashboard.products.create') }}</a>
     ```
   - **Impact:** Ensures better text handling, preventing text overflow and maintaining a clean layout.

5. **File: `resources/views/dashboard/business/product/index.blade.php`**
   - **Status:** Modified
   - **Changes:** Added 3 lines, deleted 3 lines.
   - **Description:** Made similar changes to the product index view for a consistent appearance across the dashboard.
     ```html
     <a href="{{ route('products.create_product') }}" class="text-sm font-semibold text-center md:text-base 2xl:text-lg text-creatify-1 dark:text-creatify-3 after:absolute after:inset-0 line-clamp-1">{{ __('dashboard.products.create') }}</a>
     ```
   - **Impact:** Enhances consistency and readability in the product view, contributing to a more professional and user-friendly interface.

These changes collectively work towards improving the application's performance, functionality, and user experience by introducing better data handling and UI enhancements.

---

# #195 Enhanced Application Management and UX Improvements

## Introduction
This pull request encompasses a series of changes aimed at enhancing the application management process and improving the user experience (UX) for the business dashboard. The modifications include the addition of new features for managing applications, updating the database schema, enhancing the frontend with new interactive elements, and updating various controllers to support the newly added functionalities. These changes are designed to streamline the administrative workflow, allow for more advanced search and filter options, and provide a more intuitive interface for users.

## Changes Overview

1. **File: `app/Livewire/Business/Applications.php`**
   - **Status:** Added
   - **Changes:** 168 new lines adding a new Livewire Component for managing business applications.
   - **Description:** This component manages the state and displays a list of applications allowing users to filter by search terms, gender, age, and state. It also supports viewing detailed information for each application.
   - **Impact:** Enhances the ability to manage and filter applications dynamically without the need for full page reloads, improving efficiency and user experience.

2. **File: `database/migrations/2024_07_29_172750_change_table_birthday_in_user_data.php`**
   - **Status:** Added
   - **Changes:** 28 new lines for a migration file to alter the `user_data` table, changing the `birthday` field to be nullable.
   - **Description:** Updates the database schema to allow null values in the `birthday` column of the `user_data` table.
   - **Impact:** Provides greater flexibility in handling user data where the birthday may not be available or applicable.

3. **File: `resources/views/dashboard/business/order/livewire/applications.blade.php`**
   - **Status:** Added
   - **Changes:** 471 new lines creating a new Blade template for the applications view.
   - **Description:** Implements a new interactive user interface for displaying and filtering applications using Livewire and Alpine.js for reactivity.
   - **Impact:** Improves the frontend experience by providing more responsive and interactive elements, enhancing usability and engagement.

4. **File: `storage/tmp/productimages/1722310869_PdPAQFJfr2xRAJv0DNwCOjWIk.jpg`**
   - **Status:** Added
   - **Changes:** New image file added.
   - **Description:** Adds a product image for the temporary storage.
   - **Impact:** Ensures that the product images required for the dashboard are available, thereby improving the visual presentation.

5. **File: `storage/tmp/productimages/1722310933_42gbHFarCDhsO2STYSIB7jU1N.jpg`**
   - **Status:** Added
   - **Changes:** New image file added.
   - **Description:** Adds another product image for the temporary storage.
   - **Impact:** Similar to the previous file, it supports the visual components of the dashboard.

6. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** 1 addition and 1 deletion for a total change of 2 lines.
   - **Description:** Changes the order of listed users from descending to ascending by `created_at`.
   - **Impact:** Updates the order in which user levels are displayed, likely to now show older users first.

7. **File: `app/Http/Controllers/OrderProcessController.php`**
   - **Status:** Modified
   - **Changes:** 7 additions and 13 deletions for a total change of 20 lines.
   - **Description:** Refactors the logic for fetching applications and approved applications for an order to enhance clarity and efficiency.
   - **Impact:** Simplifies the order process application view logic, potentially improving performance and maintainability.

8. **File: `package.json`**
   - **Status:** Modified
   - **Changes:** 1 addition and 1 deletion for a total change of 2 lines.
   - **Description:** Updates the version of the `preline` library from `2.0.3` to `2.4.1`.
   - **Impact:** Ensures that the latest features, improvements, and bug fixes of the `preline` library are included in the project.

9. **File: `resources/lang/pt_br/dashboard.php`**
   - **Status:** Modified
   - **Changes:** 7 additions and 1 deletion for a total change of 8 lines.
   - **Description:** Adds new language strings and updates existing ones to support the new application management features.
   - **Impact:** Enhances the localization and provides better support for Portuguese-speaking users.

10. **File: `resources/views/dashboard/business/order/applications.blade.php`**
    - **Status:** Modified
    - **Changes:** 1 addition and 248 deletions for a total change of 249 lines.
    - **Description:** Replaces the old static application view with the new `business.applications` Livewire component.
    - **Impact:** Streamlines the application view with a more dynamic, maintainable, and interactive implementation.

These consolidated changes will collectively make the application management system more robust, user-friendly, and adaptable to various scenarios, reflecting a significant enhancement in both UI and backend logic.

---

# #193 UI Enhancements and Code Refactoring for Error Pages

## Introduction
This pull request introduces a series of changes aimed at improving the overall user experience (UX) of the error pages within the application. These updates include CSS adjustments, refactoring of Blade template files for error pages, and improvements in the semantic structure and reusability of the code. The primary focus is to make error messages more informative and visually appealing, streamline the code, and enhance maintainability.

## Changes Overview
1. **File: `resources/css/app.css`**
- **Status:** Modified
- **Changes:**
   - Adjusted the `.btn` class to include `!h-auto` and `!min-h-max`.
   - Fixed a missing newline at the end of the file.
- **Description:** The `!h-auto` ensures that the buttons have an automatic height adjustment, while `!min-h-max` sets a minimum height ensuring the buttons adapt better to different content sizes.
- **Impact:** Enhances the responsiveness and visual consistency of buttons across different views.

2. **File: `resources/views/errors/503.blade.php`**
- **Status:** Modified
- **Changes:**
   - Refactored the layout to extend from `layouts.errors`.
   - Introduced a new header arrangement using the `@php` directive.
   - Reorganized the content structure to utilize Blade sections effectively.
   - Reduced redundant HTML and replaced static content with dynamic and maintainable Blade scripts.
- **Description:** This refactoring aims to unify the error page design by leveraging a common layout. The dynamic header helps in making the content more customizable and the overall code is more maintainable and cleaner.
- **Impact:** Simplifies future updates to the 503 error page and ensures consistency with other error layouts, improving the UX.

3. **File: `resources/views/layouts/errors.blade.php`**
- **Status:** Modified
- **Changes:**
   - Removed the inclusion of several CSS and JS files that might not be necessary.
   - Updated the structure to improve spacing, alignment, and overall visual hierarchy.
   - Replaced hardcoded footer content with Blade directives to enhance readability.
- **Description:** By removing non-essential CSS and JS, the file is optimized for faster load times. The new layout structure improves readability and maintainability.
- **Impact:** Reduces page load time and simplifies footer modifications, enhancing UX and performance.

These changes collectively aim to modernize the error pages, making them more adaptable to future requirements and easier to maintain.

---

# #191 New Chat Management Feature in Admin Dashboard

## Introduction
This pull request introduces a new feature to the admin dashboard: chat management. The changes include the addition of views and functionalities to allow administrators to view and manage chats between users. This enhancement impacts several parts of the application, including the view templates, routes, controllers, and Livewire components. The changes aim to improve user experience by centralizing chat operations, ensuring better order processing oversight, and enabling the administration to monitor communications effectively.

## Changes Overview
1. **File: `resources/views/admin/chat/index.blade.php`**
   - **Status:** Added
   - **Changes:** Introduced a new view template for displaying a list of chats in the admin dashboard. The view includes a table that lists chat messages with columns for order, sender, receiver, message content, and creation date.
   - **Description:** This file was added to create the interface where administrators can view chat messages related to orders.
   - **Impact:** This new view will provide administrators with a centralized location to monitor all chat communications, improving oversight and the ability to address customer issues promptly.

2. **File: `app/Console/Commands/CloudconvertOrderFiles.php`**
   - **Status:** Modified
   - **Changes:** Enhanced the handle method for watermarking both images and videos instead of just videos.
   - **Description:** This change was likely made to expand the functionality of the CloudConvert command to handle image watermarking alongside videos.
   - **Impact:** It enhances the versatility of the application by allowing different types of media (images and videos) to be processed uniformly.

3. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Added a `chat_index` method to load chat messages for the admin interface and display them in the newly added view.
   - **Description:** This addition supports the new chat management feature, retrieving chat messages for display in the admin view.
   - **Impact:** This change allows administrators to access and view chat histories, facilitating better communication management and transparency.

4. **File: `app/Livewire/OrderChat.php`**
   - **Status:** Modified
   - **Changes:** Significant refactoring to accommodate different user roles (brand vs. creator) and update the chat functionalities and views accordingly.
   - **Description:** The updates ensure that chats are correctly attributed and managed based on user roles, enhancing overall functionality and user experience.
   - **Impact:** This change improves message handling between distinct user types, thus reducing potential communication errors and ensuring better order management.

5. **File: `app/Services/CloudConvert.php`**
   - **Status:** Modified
   - **Changes:** Added a method to handle image watermarking.
   - **Description:** This change adds functionality to watermark images, broadening the service's capabilities.
   - **Impact:** This makes the CloudConvert service more robust, allowing it to handle additional media types (images) and enhancing its utility within the application.

6. **File: `resources/lang/pt_br/admin.php`**
   - **Status:** Modified
   - **Changes:** Added localization support for the new "Chats" feature.
   - **Description:** This change ensures that the new chat management feature is supported in the Brazilian Portuguese language pack.
   - **Impact:** It ensures that the application remains accessible and understandable for Portuguese-speaking users.

7. **File: `resources/views/admin/components/sidebar.blade.php`**
   - **Status:** Modified
   - **Changes:** Added a new sidebar link to the chat management view.
   - **Description:** This addition provides a direct link from the admin sidebar to the new chat management section.
   - **Impact:** Enhances the user experience by improving navigation within the admin panel.

8. **File: `resources/views/admin/order/show.blade.php`**
   - **Status:** Modified
   - **Changes:** Enhanced existing views to better display order details and related chats.
   - **Description:** These updates ensure that related chat information is easily accessible within the order details view.
   - **Impact:** Improves the administrator’s ability to correlate chats with specific orders, enhancing order management efficiency.

9. **File: `resources/views/dashboard/business/order/progress.blade.php`**
   - **Status:** Modified
   - **Changes:** Updated to reflect new structure in handling chats within the business dashboard.
   - **Description:** This refactor ensures that business users can efficiently manage and view their ongoing order-related chats.
   - **Impact:** Enhances communication management for business users, potentially improving service delivery.

10. **File: `resources/views/dashboard/components/order-chat.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated to improve the chat component UI and handling based on user roles.
    - **Description:** These changes improve the chat component’s usability and alignment with the new role-based messaging strategy.
    - **Impact:** Provides a clearer and more functional UI for chat interactions, enhancing user engagement and experience.

11. **File: `resources/views/dashboard/components/order-files.blade.php`**
    - **Status:** Modified
    - **Changes:** Adjusted the file display logic to handle cases where no watermark exists.
    - **Description:** This ensures that files without watermarks are still properly displayed.
    - **Impact:** Ensures that all relevant order files are visible to users, preventing potential confusion or mismanagement.

12. **File: `resources/views/dashboard/creator/task/progress.blade.php`**
    - **Status:** Modified
    - **Changes:** Refactored to improve chat handling within the creator's task progress view.
    - **Description:** This change aligns the chat functionalities with the overall improvements and role-based handling.
    - **Impact:** Streamlines the communication process for creators, enabling better task management.

13. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added routes to support the new chat functionalities.
    - **Description:** The new routes facilitate accessing the chat index and related functionalities in the admin interface.
    - **Impact:** Provides the necessary backend support for the new chat management features, enabling smooth operation and navigation.

By implementing these changes, the admin dashboard’s functionality is significantly enhanced, offering a more centralized and efficient way to manage communications related to orders. This addition is expected to improve administrative oversight and facilitate seamless user interactions.

---

# #190 Pull Request Overview: New Watermark Feature for Order Files

## Introduction
This pull request introduces significant changes aimed at enhancing the functionalities related to handling order files within the application. The primary focus is on adding watermark capabilities to video files, which includes the creation of a new console command, modifications to existing commands, updates to the database schema, and various code adjustments to support the new feature. The changes improve the overall user experience by ensuring that watermarked videos are appropriately managed and provide safeguards for file handling, enhancing security and application reliability.

## Changes Overview

### 1. **File: `app/Console/Commands/CloudconvertOrderFiles.php`**
- **Status:** Newly Added
- **Changes:** 74 lines added to create a new command class.
- **Description:** This new console command `CloudconvertOrderFiles` processes order files to add watermarks and convert file formats. It iterates over specific order types (video and hook), checks for null or empty watermark fields, calculates new dimensions based on video formats, and uses the CloudConvert service to apply the watermark.
- **Impact:** This addition automates and streamlines the watermarking process, ensuring that all relevant videos are processed consistently.

### 2. **File: `database/migrations/2024_07_20_172631_add_watermark_to_order_files_table.php`**
- **Status:** Newly Added
- **Changes:** 28 lines added to create a migration file.
- **Description:** The migration adds a new `watermark` column to the `order_files` table to store the path of watermarked videos.
- **Impact:** Enables the database to store information about watermarked files, which is crucial for the new watermark feature.

### 3. **File: `app/Console/Commands/CloudconvertReferences.php`**
- **Status:** Modified
- **Changes:** 1 line added, 1 line deleted.
- **Description:** The command now uses the `videoAndThumb` method instead of `video` to process video files.
- **Impact:** Extends the functionality to handle both video conversion and thumbnail generation.

### 4. **File: `app/Console/Commands/CloudconvertSetcardvideo.php`**
- **Status:** Modified
- **Changes:** 1 line added, 1 line deleted.
- **Description:** The command now uses the `videoAndThumb` method instead of `video` to process video files.
- **Impact:** Similar to the previous command, this change extends the capability to also generate thumbnails alongside video conversion.

### 5. **File: `app/Console/Kernel.php`**
- **Status:** Modified
- **Changes:** 1 line added.
- **Description:** Schedules the new `cloudconvert:orderfiles` command to run every minute.
- **Impact:** Ensures regular and automated processing of order files, improving workflow automation.

### 6. **File: `app/Http/Controllers/TaskController.php`**
- **Status:** Modified
- **Changes:** 3 lines added.
- **Description:** Ensures that any associated watermark files are also deleted when deleting an order file.
- **Impact:** Enhances data integrity by ensuring all related files are removed, preventing orphaned files and saving storage space.

### 7. **File: `app/Models/OrderFiles.php`**
- **Status:** Modified
- **Changes:** 5 lines added.
- **Description:** Adds a relationship method to retrieve order details.
- **Impact:** Facilitates the fetching of video format details directly related to the order, aiding in effective file processing.

### 8. **File: `app/Services/CloudConvert.php`**
- **Status:** Modified
- **Changes:** 65 lines added, 2 lines deleted.
- **Description:** Adds a new method `videoAndThumb` and updates the `video` method to include a watermark with configurable opacity.
- **Impact:** Expands the service's capabilities, enabling it to handle more complex video processing tasks.

### 9. **File: `resources/views/dashboard/components/order-files.blade.php`**
- **Status:** Modified
- **Changes:** 47 lines added, 43 lines deleted.
- **Description:** Updates the frontend to support displaying videos with watermarks when the files are not approved and includes necessary conditionals to switch between original and watermarked videos based on file status.
- **Impact:** Enhances the user interface by providing visual feedback and control over different video file states, improving user experience for business users managing orders.

These changes collectively enhance the application's robustness in handling video conversions, watermarks, and file management, ensuring a smoother and more reliable experience for end-users and administrators.

---

# #189 Addition of New Order Filtering Logic and User Payout Management

## Introduction
This pull request introduces several significant improvements and additions to the application. We have added a new class, `OrderFilterMatch`, for filtering orders based on user data, which enhances the application's logic for matching users to specific orders. Furthermore, user payout management has been enhanced with new routes, views, and functionalities to support the payout processes within the admin panel. These changes improve the application's functionality, augmenting the order-handling capabilities and introducing a clearer workflow for managing user payouts. 

Our updates encapsulate new features including: 
- New filtering logic to ensure orders adhere to specified user criteria.
- Enhanced admin interfaces for managing user payouts.
- New service methods for handling payment transfers, improving security, and operational efficiency.

## Changes Overview
1. **File: `app/Services/OrderFilterMatch.php`**
   - **Status:** Added
   - **Changes:** Introduced a new service class, `OrderFilterMatch`, with a method to check if an order matches a user's age range and gender.
   - **Description:** This class implements business logic to validate if an order's specifications (age and gender) match the user's details. 
   - **Impact:** Ensures that orders are filtered and matched accurately, improving the quality and appropriateness of order assignments.

2. **File: `resources/views/admin/user/payout.blade.php`**
   - **Status:** Added
   - **Changes:** Created a new blade template for displaying user payout information in the admin panel.
   - **Description:** The new view shows a table listing user payouts with details such as user, amount, status, type, destination, and timestamps for when initiated and completed.
   - **Impact:** Enhances the admin's ability to manage and monitor user payouts efficiently, providing a better user interface for administrative tasks.

3. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Added new methods for handling user payouts, updated constructor to include service dependencies.
   - **Description:** Introduced methods `user_payout` and `user_payout_action` to list and process user payout requests. Added service injections for payment and wallet services.
   - **Impact:** Adds functionality to handle user payout requests within the admin dashboard, improving the system's payout management processes.

4. **File: `app/Http/Controllers/TaskController.php`**
   - **Status:** Modified
   - **Changes:** Integrated the newly added `OrderFilterMatch` service for task viewing and application.
   - **Description:** Injected `OrderFilterMatch` service to validate tasks against user data when viewing and applying to tasks.
   - **Impact:** Ensures tasks are only visible and applicable to users that meet the specified criteria, enhancing task-user matching accuracy.

5. **File: `app/Models/WalletPayouts.php`**
   - **Status:** Modified
   - **Changes:** Added relationships to user and wallet models.
   - **Description:** Established model relationships to link payouts with users and wallets directly.
   - **Impact:** Improves data access and integrity for user payout operations, ensuring related data can be easily retrieved and managed.

6. **File: `app/Services/MessageFilterService.php`**
   - **Status:** Modified
   - **Changes:** Removed redundant comment in constructor.
   - **Description:** Cleaned up the constructor method by removing an unnecessary comment.
   - **Impact:** Minor code cleanup with no significant impact on functionality.

7. **File: `app/Services/PaymentService.php`**
   - **Status:** Modified
   - **Changes:** Added method `createPixTransfer` for handling PIX payment transfers.
   - **Description:** New method to create a PIX transfer request using the service's client and log any errors that occur.
   - **Impact:** Adds support for handling PIX payment transfers, enhancing the application's capabilities for financial operations and improving error logging and handling for these operations.

8. **File: `app/Services/WalletService.php`**
   - **Status:** Modified
   - **Changes:** Updated methods for fulfilling and initiating payouts to use new fields and processes.
   - **Description:** Adjusted service methods to ensure payouts are correctly initiated and fulfilled using updated logic and field references.
   - **Impact:** Ensures accurate handling of payout requests and their statuses, improving the reliability of financial transactions.

9. **File: `resources/lang/pt_br/admin.php`**
   - **Status:** Modified
   - **Changes:** Added a new translation string for 'payouts'.
   - **Description:** Enhanced the Brazilian Portuguese language pack with new translations related to user payouts.
   - **Impact:** Improves localization and user experience for Portuguese-speaking admin users.

10. **File: `resources/lang/pt_br/dashboard.php`**
    - **Status:** Modified
    - **Changes:** Added a new translation string for 'transfer_failed' error message.
    - **Description:** Included additional error messaging in the Brazilian Portuguese language pack for transfer failures.
    - **Impact:** Enhances user feedback and error handling for Portuguese-speaking users during transfer operations.

11. **File: `resources/views/admin/components/sidebar.blade.php`**
    - **Status:** Modified
    - **Changes:** Added a sidebar link for the new user payout route.
    - **Description:** Updated the admin sidebar to include a navigation link for accessing user payout management.
    - **Impact:** Provides easier access to payout management for admin users, enhancing navigation and user convenience.

12. **File: `resources/views/admin/order/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Fixed table HTML structure for better alignment.
    - **Description:** Corrected HTML tags to ensure proper table structure and alignment.
    - **Impact:** Minor UI fix enhancing the presentation and alignment of table elements in the admin order index view.

13. **File: `resources/views/admin/product/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Removed redundant modal markup from the product index view.
    - **Description:** Cleaned up the blade template by removing an unused modal section.
    - **Impact:** Reduces unnecessary code, improving maintainability and readability of the template.

14. **File: `resources/views/dashboard/creator/task/view.blade.php`**
    - **Status:** Modified
    - **Changes:** Added conditional alert and application section based on filter check.
    - **Description:** Displays an alert if the user does not meet the task criteria and conditionally shows the application section if criteria are met.
    - **Impact:** Enhances user feedback and ensures that users are aware of their eligibility to apply for tasks, improving user experience and task management.

15. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added routes for new payout-related functionalities.
    - **Description:** Introduced new routes to handle GET and PUT requests for user payouts, linking to the respective controller methods.
    - **Impact:** Enables routing for the new payout management features, integrating them into the application’s existing structure for routing and controller actions.

---

# #187 New Feature for Managing Order Visibility and Code Cleanup in UserProfileController

## Introduction
This pull request introduces several key changes to our application. The primary addition is the new functionality to toggle the visibility of individual orders in the admin panel. This feature enhances the control administrators have over the display of orders. Additionally, there are some clean-up changes to the `UserProfileController` for better code quality. There are also updates to the views in the admin order section to accommodate the new visibility feature. These changes impact the application's functionality by adding new capabilities for admins, enhancing user experience, and maintaining code cleanliness.

## Changes Overview
1. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Added a new method `order_visible()` to toggle the visibility of an order based on its `uuid`. This method checks if the order exists, negates its `visible` attribute, saves the update, and returns a success message.
   - **Description:** The new method provides administrators with an additional control to toggle the visibility status of an order. This is aimed at improving the manageability of order display within the admin interface.
   - **Impact:** Enhances functionality by providing an admin control for order visibility, potentially affecting redirect behavior if the order is not found.

2. **File: `app/Http/Controllers/UserProfileController.php`**
   - **Status:** Modified
   - **Changes:** Removed the `dd($user)` line from the `wallet_payout()` method.
   - **Description:** The removal of this line, which was likely used for debugging purposes, cleans up the code.
   - **Impact:** Improves code quality and ensures the function returns properly after initiating a payout without unnecessary interruption.

3. **File: `resources/views/admin/order/index.blade.php`**
   - **Status:** Modified
   - **Changes:** Added a new column with a form and button to toggle the visibility of an order.
   - **Description:** This update integrates the visibility toggle feature into the admin orders index table, allowing admins to easily change the visibility status directly from the order list.
   - **Impact:** Enhances user experience for administrators by making the order visibility control more accessible and visually integrated with the existing order list.

4. **File: `resources/views/admin/order/show.blade.php`**
   - **Status:** Modified
   - **Changes:** Added a visibility toggle button within the order details view.
   - **Description:** Similar to the index view, this change makes it possible for admins to toggle the visibility of an order directly from the order details page.
   - **Impact:** Improves the user experience by providing more direct control within different parts of the admin interface.

5. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Added a route to handle the PUT request for changing order visibility.
   - **Description:** This route connects the new `order_visible` method in the `AdminController` to the web application, allowing visibility changes to be processed.
   - **Impact:** Important for enabling the new functionality of order visibility management; ensures the route is properly defined to handle the operation.

---

# #186 Integration of Wallet Payout Feature in the Application

## Introduction
The pull request introduces new functionality to handle wallet payouts in the application. This includes creating new database schemas, adding relevant models, updating the user profile controller, and modifying necessary service classes to support wallet payout operations. The changes impact both the backend logic and user interface components, enabling users to initiate and manage wallet payouts seamlessly.

## Changes Overview
1. **File: `app/Models/WalletPayouts.php`**
   - **Status:** Added
   - **Changes:** A new model `WalletPayouts` was created.
   - **Description:** This model includes relevant fields such as `user_id`, `wallet_id`, `amount`, `status`, `type`, `destination`, `initiated_at`, `completed_at`, and `cancelled_at`. These fields capture all necessary details for tracking wallet payouts.
   - **Impact:** Facilitates tracking and managing wallet payouts within the system, ensuring payouts are recorded and processed accurately.

2. **File: `database/migrations/2024_07_15_150839_create_wallet_payouts_table.php`**
   - **Status:** Added
   - **Changes:** Introduced a new migration script to create a `wallet_payouts` table in the database.
   - **Description:** The script defines the schema for the `wallet_payouts` table, including foreign key constraints tying payouts to users and wallets, and timestamps tracking the payout process.
   - **Impact:** Establishes a dedicated database table for storing wallet payout information, ensuring data integrity and relationship consistency between users, wallets, and payouts.

3. **File: `app/Http/Controllers/UserProfileController.php`**
   - **Status:** Modified
   - **Changes:** Added wallet payout logic, including the use of `WalletService` and `WalletPayouts`.
   - **Description:** The controller now includes a method `wallet_payout()` to handle payout requests. It checks for existing initiated payouts, verifies user wallet balance, and initiates new payouts using the wallet service.
   - **Impact:** Enhances user profile functionality by allowing users to initiate wallet payouts directly from their profile page, improving user experience.

4. **File: `app/Services/WalletService.php`**
   - **Status:** Modified
   - **Changes:** Added methods for initiating and fulfilling payouts.
   - **Description:** The `WalletService` now includes `initiatedPayout()` and `fulfilledPayout()` methods to handle payout initiation and completion, updating both `WalletPayouts` and `WalletTransaction` models accordingly.
   - **Impact:** Centralizes payout logic within the service layer, promoting code reuse and maintaining clear separation of concerns.

5. **File: `resources/lang/pt_br/dashboard.php`**
   - **Status:** Modified
   - **Changes:** Added new localization strings for wallet payout-related messages.
   - **Description:** Introduced new strings such as 'payout', 'error_pending', and 'error_balance' to handle payout-related errors and success messages in the Portuguese language file.
   - **Impact:** Ensures that users receive localized messages during the payout process, enhancing user experience for Portuguese-speaking users.

6. **File: `resources/views/dashboard/components/header.blade.php`**
   - **Status:** Modified
   - **Changes:** Corrected the route for the wallet link.
   - **Description:** Updated the route from `wallet` to `wallet.index` to match new route naming conventions.
   - **Impact:** Ensures accurate routing for accessing the wallet page, preventing broken links.

7. **File: `resources/views/dashboard/components/sidebar.blade.php`**
   - **Status:** Modified
   - **Changes:** Corrected the route for the wallet link in the sidebar.
   - **Description:** Updated the route from `wallet` to `wallet.index`.
   - **Impact:** Consistency in routing ensures users can navigate to the wallet section from the sidebar without issues.

8. **File: `resources/views/dashboard/creator/wallet.blade.php`**
   - **Status:** Modified
   - **Changes:** Added a form to initiate a wallet payout and adjusted the transactions listing.
   - **Description:** The interface now includes a form button to initiate payouts and sorts wallet transactions in descending order by creation date.
   - **Impact:** Enhances the UI by allowing users to start payouts directly and view their transactions in a logical order.

9. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Updated routing for wallet-related paths including a new post route for payout initiation.
   - **Description:** The wallet routes are now organized under a prefix with named routes for `index` and `payout`.
   - **Impact:** Cleaner route management and the addition of a route for handling wallet payout requests, ensuring logical URL structuring and better route organization.

---

# #185 Enhanced Onboarding and Multi-Select UI Improvements

## Introduction
This pull request introduces several significant improvements to the onboarding process and user interface for multi-select dropdown elements. The main focus is on enhancing the experience for users when selecting interests and languages, ensuring data consistency, and improving overall code functionality. The changes include the addition of new JavaScript functionalities, updates to middleware checks, modifications to Livewire components, and updates to language files and Blade templates. These changes impact the application's functionality by providing a more interactive and user-friendly interface, improving security checks during the onboarding process, and adding necessary validations.

## Changes Overview

1. **File: `public/js/custom-select.js`**
   - **Status:** Added
   - **Changes:** Introduces JavaScript code to handle custom multi-select dropdowns for interests and languages.
   - **Description:** This file contains code for managing the selection of interests and languages, initializing the selected tags, updating tags and input fields dynamically, and handling click events to show/hide the dropdown options.
   - **Impact:** Enhances the user experience by providing a more interactive and visually appealing multi-select dropdown. Improves data consistency by updating the input fields dynamically based on selections.

2. **File: `app/Http/Middleware/CheckOnboarding.php`**
   - **Status:** Modified
   - **Changes:** Added checks for missing interests and languages during the onboarding process.
   - **Description:** This modification ensures that users cannot proceed without selecting their interests and languages during the onboarding. Additional route updates prevent users from skipping essential steps.
   - **Impact:** Strengthens the onboarding process by ensuring all required user data is collected, reducing errors and improving user profiles' completeness.

3. **File: `app/Livewire/OnboardingForm.php`**
   - **Status:** Modified
   - **Changes:** Corrected a typo from `selectedLangugage` to `selectedLanguage` and added error handling for specific API responses.
   - **Description:** Fixes a typo that could cause issues with data binding and enhances error handling by displaying generic error messages for insufficient credits.
   - **Impact:** Enhances data integrity and ensures more informative error messages for users.

4. **File: `app/Livewire/UpdateProfileForm.php`**
   - **Status:** Modified
   - **Changes:** Added support for handling interests and languages in the profile update process.
   - **Description:** Introduces properties and methods for managing interests and languages, including fetching interests from the `ProductCategory` model and handling multiple selections.
   - **Impact:** Provides users with the ability to update their interests and languages more conveniently within their profile, increasing user engagement and profile accuracy.

5. **File: `config/socialstream.php`**
   - **Status:** Modified
   - **Changes:** Commented out lines for Google and Facebook providers.
   - **Description:** Temporarily disables Google and Facebook authentication providers.
   - **Impact:** Prevents users from using these authentication methods, which could be a temporary measure for maintenance or other reasons.

6. **File: `resources/lang/pt_br/dashboard.php`**
   - **Status:** Modified
   - **Changes:** Added translations for missing interests and languages error messages.
   - **Description:** Provides Portuguese translations for new validation messages during the onboarding process.
   - **Impact:** Improves the user experience for Portuguese-speaking users by providing localized error messages.

7. **File: `resources/views/livewire/onboarding-form.blade.php`**
   - **Status:** Modified
   - **Changes:** Corrected the wire model binding for the multi-select languages input field.
   - **Description:** Fixes the binding issue due to the previous typo, ensuring the correct data is passed to the backend.
   - **Impact:** Ensures smoother data flow and reduces potential errors during the onboarding process.

8. **File: `resources/views/profile/setcard.blade.php`**
   - **Status:** Modified
   - **Changes:** Included the `custom-select.js` script.
   - **Description:** Adds the newly created JavaScript file to the profile setcard view.
   - **Impact:** Integrates the enhanced multi-select functionality into the profile setcard, improving user interactions.

9. **File: `resources/views/profile/update-profile-form.blade.php`**
   - **Status:** Modified
   - **Changes:** Added HTML and JavaScript for custom multi-select dropdowns in the profile update form.
   - **Description:** Introduces the custom multi-select UI elements for interests and languages within the profile update form, including dynamically generated tags and placeholder visibility toggles.
   - **Impact:** Significantly enhances the usability and interactivity of the profile update form, making it easier for users to manage their interests and languages.

This pull request enhances the application's user experience, ensures data integrity during the onboarding process, and improves the readability and maintainability of the code.

---

# #184 Improved Sorting and Dashboard Enhancements

## Introduction
This pull request introduces several modifications and enhancements across various parts of the application, aimed at improving functionality, user experience, and data presentation. The main areas of changes include updating sorting mechanisms, enhancing UI to display additional information, and improving layout consistency across various dashboard views.

## Changes Overview

1. **File: `app/Livewire/Creator/DashboardMyTasks.php`**
- **Status:** Modified
- **Changes:** 
  - Adjusted the `Order` query to include sorting by `created_at` in descending order.
  - Reformatted how the query segments and conditions are structured for better readability.
- **Description:** The query for fetching orders is now ordered by the creation date, ensuring that the most recent orders are shown first.
- **Impact:** This change improves the relevancy of displayed tasks for creators, likely enhancing user satisfaction by prioritizing recent tasks.

2. **File: `app/Livewire/Creator/DashboardOpenTasks.php`**
- **Status:** Modified
- **Changes:** 
  - Added ordering by `created_at` in descending order in the task query.
- **Description:** Ensures open tasks are listed from the newest to oldest, improving task tracking efficiency.
- **Impact:** Users can now quickly find the most recent open tasks, enhancing productivity and task management.

3. **File: `resources/views/dashboard/business/order/livewire/modal-briefing.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Added a new section to display the number of ads associated with an order if the count is greater than zero.
- **Description:** Introduced a visual representation of ads related to the order with a clear and concise layout.
- **Impact:** Improves transparency and provides additional context within the order modal, aiding in better decision-making for business users.

4. **File: `resources/views/dashboard/business/order/progress.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Adjusted the grid structure from six columns to a more responsive layout ranging from two to five columns based on screen size.
  - Added a conditional section to display ad counts if it is greater than zero.
- **Description:** These changes enhance the visual consistencies and adaptability of the order progress grid, making it more user-friendly and informative.
- **Impact:** Improved user experience with a more flexible and informative grid structure, aiding users in tracking order progress effectively.

5. **File: `resources/views/dashboard/creator/livewire/dashboard-tasks.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Added a new section that displays the order's product category.
- **Description:** Introduced a label for showing the order's product category, providing immediate context about the nature of tasks.
- **Impact:** This small but meaningful addition helps creators quickly understand the type of tasks/orders at a glance, improving efficiency.

6. **File: `resources/views/dashboard/creator/task/progress.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Adjusted the grid structure from six columns to a more responsive layout ranging from two to five columns based on screen size.
  - Added a conditional section to display ad counts if it is greater than zero.
- **Description:** The grid restructuring and additional ad count display improve the task progress view's adaptability and informativeness.
- **Impact:** Enhances the creator’s ability to monitor and track task progress efficiently across different devices, ensuring better task management.

7. **File: `resources/views/dashboard/creator/task/view.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Adjusted the grid structure from four columns to a more responsive layout ranging from two to five columns based on screen size.
  - Corrected the condition for displaying hooks to check that the count is greater than zero.
  - Added a conditional section to display ad counts if it is greater than zero.
- **Description:** These changes collectively contribute to a more responsive and informative task view, accommodating various screen sizes and enhancing data presentation.
- **Impact:** Users benefit from a more consistent and user-friendly interface, aiding in better management and monitoring of tasks.

These changes collectively streamline the user workflow, enhance data presentation, and improve the overall usability of the application’s dashboard components.

---

# #183 Addition of Multi-Language Support for User Onboarding

## Introduction
This pull request introduces a new feature that allows users to specify their preferred language during the onboarding process. The changes span several files, affecting the database schema, backend logic, and front-end components. The primary impact of this update is the enhancement of user experience by accommodating multilingual preferences, thus making the application more inclusive and accessible to a wider audience. These updates also ensure that new data related to the user's language preference is correctly stored and retrieved, maintaining the integrity of user data.

## Changes Overview
1. **File: `database/migrations/2024_07_17_171321_add_language_to_user_data.php`**
    - **Status:** Added
    - **Changes:**
        - Created a new migration file to add a nullable 'language' column to the 'user_data' table.
        - Included schema updates to add and remove the 'language' column in the `up` and `down` methods respectively.
    - **Description:** This new migration is necessary to store the preferred language of a user, which is a prerequisite for providing language-specific content.
    - **Impact:** This lays the groundwork for storing language preferences, impacting database schema and requiring any existing user data handling processes to accommodate this new column.

2. **File: `app/Livewire/OnboardingForm.php`**
    - **Status:** Modified
    - **Changes:**
        - Added a new property `$selectedLangugage` to store the language selected during onboarding.
        - Updated the method `updateAdditionalDetails` to save the selected language to the user's data.
    - **Description:** These updates ensure that the selected language is captured during the onboarding form submission and stored in the database.
    - **Impact:** These changes will directly affect how user data is stored and retrieved during onboarding, ensuring language preferences are saved.

3. **File: `app/Models/UserData.php`**
    - **Status:** Modified
    - **Changes:**
        - Added 'language' to the `$fillable` property to allow mass assignment.
    - **Description:** This enables the application to mass-assign language data to the UserData model.
    - **Impact:** This modification ensures seamless data operations involving the user's language preference, contributing to safer and more reliable data handling.

4. **File: `resources/views/dashboard/onboarding.blade.php`**
    - **Status:** Modified
    - **Changes:**
        - Added JavaScript code to handle the selection of languages on the onboarding view.
        - Managed the display of language options and the tagging system to show the selected languages.
        - Updated the function to dispatch input event for language selection.
    - **Description:** These front-end changes provide the UI elements necessary for users to select and view their language choices, with a dynamic and interactive approach.
    - **Impact:** Enhances the interactivity and usability of the language selection feature, making the onboarding process more user-friendly and visually coherent.

5. **File: `resources/views/livewire/onboarding-form.blade.php`**
    - **Status:** Modified
    - **Changes:**
        - Integrated language selection UI components within the onboarding form.
        - Created a div container and hidden input field to capture selected languages.
        - Utilized Laravel Blade and Livewire directives to manage the language tags and options dynamically.
    - **Description:** These changes bring the new language selection feature to the onboarding form, ensuring users can specify and visualize their language preference.
    - **Impact:** Directly improves the onboarding user experience by adding a multilingual dimension, allowing users to tailor their experience from the very beginning.

In summary, this pull request significantly enhances the user onboarding process by adding support for language selection, affecting several layers of the application from database schema to the UI. These changes collectively aim to improve user engagement and cater to a diverse user base, fostering inclusivity and better user interaction.

---

# #182 Feature Update: Enhanced User Status Middleware and UI/UX Updates

## Introduction
This pull request introduces significant changes across multiple files, focusing primarily on enhancing user management, improving UI/UX for admin interfaces, and adding a new feature for handling underage users. **Key areas of impact** include:
- **New feature additions**: Added checks in middleware for user status, particularly handling underage users.
- **UI/UX enhancements**: Improved the display of user-related information on admin and dashboard pages.
- **Data integrity updates**: Consolidation and consistency improvements in user data management.

These changes will improve the system's robustness in user age verification and enhance the overall user experience for both administrators and end-users.

## Changes Overview

1. **File: `app/Http/Middleware/CheckUserStatus.php`**
   - **Status:** Modified
   - **Changes:** Added conditions to handle underage users and updated existing birthday-check logic.
   - **Description:** 
     - Introduced a check for user status being 'underage'. If the user is underage, the system logs them out and redirects them to the login page with a relevant error message.
     - Updated the logic to parse and check the user's birthday, moving user data access from direct attributes to nested data attributes for better data structure.
   - **Impact:** Improved user verification, enhanced security by ensuring underage users cannot access certain areas, and maintained data integrity across nested user data structure.

2. **File: `resources/views/admin/order/show.blade.php`**
   - **Status:** Modified
   - **Changes:** Updated product title references to utilize the `order->details->title` if available.
   - **Description:** 
     - Updated multiple instances where the product title is displayed to use a fallback mechanism (`order->details->title` or `order->product->title`).
   - **Impact:** Enhanced flexibility in displaying order details, ensuring robustness in UI rendering even when certain attributes are not available.

3. **File: `resources/views/admin/user/index.blade.php`**
   - **Status:** Modified
   - **Changes:** Extensive modifications including new columns in the table for user data and updates to existing user data presentation.
   - **Description:** 
     - Added new columns for Onboarding, Video, Socials, Reviews, References, and Location to provide comprehensive details about each user.
     - Improved the overall layout and user data presentation in the admin interface.
   - **Impact:** Improved admin interface usability and data visibility, allowing for more efficient user management and assessment.

4. **File: `resources/views/dashboard/business/order/index.blade.php`**
   - **Status:** Modified
   - **Changes:** Added a new UI component for creating orders.
   - **Description:** 
     - Introduced a 'Create' button at the beginning of the order list to improve user navigation.
   - **Impact:** Enhanced user experience by making order creation more accessible and visible within the dashboard.

5. **File: `resources/views/dashboard/business/order/select_product.blade.php`**
   - **Status:** Modified
   - **Changes:** Minor adjustments in class names for consistency.
   - **Description:** 
     - Updated CSS classes to maintain a consistent look and feel across different screen sizes.
   - **Impact:** Improved visual consistency and user experience.

6. **File: `resources/views/dashboard/business/product/index.blade.php`**
   - **Status:** Modified
   - **Changes:** Added a new UI component for creating products.
   - **Description:** 
     - Introduced a 'Create' button similarly as done in orders to improve user navigation.
   - **Impact:** Enhanced user experience by making product creation more accessible and visible within the dashboard.

These changes collectively aim at improving the functionality, security, and user experience of the system, ensuring a more user-friendly and secure platform.

---

# #181 Adding Role Feature to User Data and UI Enhancements in Dashboard

## Introduction
This pull request introduces significant updates and enhancements to the application. A new feature has been added to the user data model to capture the role or position of users within their companies. Additionally, there are several improvements in the onboarding process and various UI elements, ensuring a more consistent and user-friendly experience. The changes impact multiple facets of the application, including data management, user interface, and multilingual support.

These updates are categorized as follows:
- New Feature Addition: Adding a new column "position" to the `user_data` table.
- UX/UI Enhancements: Changes to the onboarding forms and dashboard interface for better usability and consistency.
- Multilingual Support: Translation additions for the new position feature in Portuguese.

## Changes Overview

1. **File: `database/migrations/2024_07_16_193019_add_position_to_user_data.php`**
- **Status:** Added
- **Changes:** Introduces a migration that adds a new column "position" to the `user_data` table.
- **Description:** This migration adds a nullable string column "position" to the `user_data` table and defines both the `up` and `down` methods for handling schema changes.
- **Impact:** This update allows storing additional information about users' roles within the company, enhancing the dataset available for user profiling and analytics.

2. **File: `app/Livewire/OnboardingForm.php`**
- **Status:** Modified
- **Changes:** Changes include the addition of a new variable `$companyrole`, conditional updates to the `user_data`, and improvements in the `updateAdditionalDetails` method.
- **Description:** The modifications capture the user's company role and update the `user_data` table accordingly if the value is provided. This enhancement enriches user profiles by adding an important detail about the user's position.
- **Impact:** Ensures that users’ roles are accurately recorded and updated, which can be leveraged in future features and analytics processes.

3. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** Added three new language lines: 'role', 'size', and 'select_size'.
- **Description:** Enhancing the application’s multilingual support by adding translations for new UI texts related to the user's role and company size selection.
- **Impact:** Improves user experience for Portuguese-speaking users by providing translated text for new fields, enhancing accessibility and usability.

4. **File: `resources/views/dashboard/business/product/create.blade.php`**
- **Status:** Modified
- **Changes:** Refactored the select element for product categories, ensuring consistent styling and classes for better UX.
- **Description:** The modifications standardize the dropdown select element, making it visually consistent and more accessible across different themes.
- **Impact:** Improves the visual consistency and user interaction with the product creation interface, leading to a more polished and professional appearance.

5. **File: `resources/views/dashboard/business/product/edit.blade.php`**
- **Status:** Modified
- **Changes:** Similar to the create view, the edit view dropdown for product categories has been refactored to ensure consistent styling and classes.
- **Description:** The update applies the same styling improvements as in the create view, ensuring that the dropdown select element looks and behaves consistently.
- **Impact:** Enhances the user experience by providing a consistent interface, reducing user errors and improving ease of use during product edits.

6. **File: `resources/views/dashboard/onboarding.blade.php`**
- **Status:** Modified
- **Changes:** Added new classes to tags for a more unified design and improved visual consistency.
- **Description:** These changes ensure that tags within the onboarding view conform to the same design standards as the rest of the application, particularly under different themes (light/dark modes).
- **Impact:** Offers a cohesive visual experience and ensures that styling is maintained across different parts of the application.

7. **File: `resources/views/livewire/onboarding-form.blade.php`**
- **Status:** Modified
- **Changes:** Enhanced the onboarding form to include a company role field and updated the UI to be more consistent with the design guidelines for both light and dark modes.
- **Description:** Expanded the onboarding form to capture the user's role within their company and applied consistent styling classes to various elements.
- **Impact:** This significantly boosts the onboarding experience by collecting more relevant user information and ensuring visual consistency, which can help in making informed design decisions and data analysis later on.

These comprehensive updates aim to enhance the user experience, improve data collection, and ensure greater consistency across the application.

---

# #180 Pull Request Overview: Add Additional User Interests to Onboarding Process

## Introduction
This pull request introduces several enhancements to the user onboarding process, including modifications to database structure, additions to user interface components, and new functionality to handle user interests. These changes aim to improve user experience by allowing users to specify their interests during the onboarding process, which can lead to more personalized content and interactions.

Key areas of changes:
- **Feature additions:** Introduces a new feature for users to select their interests.
- **UX/UI enhancements:** Updates the interface to support the new interests selection step in the onboarding process.
- **Database updates:** Adds a new column in the `user_data` table for storing user interests.
- **Localization:** Updates language files to include new terms related to the new onboarding step.

## Changes Overview
1. **File: `database/migrations/2024_07_13_122511_add_interests_to_user_data_table.php`**
   - **Status:** Added
   - **Changes:** Creates a new migration script to add an `interests` column to the `user_data` table.
   - **Description:** The script adds a nullable `string` column named `interests` to the `user_data` table and includes methods to run and reverse the migration.
   - **Impact:** This change modifies the database schema to store user interests, allowing for more personalized user experiences based on their interests.

2. **File: `app/Livewire/OnboardingForm.php`**
   - **Status:** Modified
   - **Changes:**
     - Adds new properties (`interests`, `selectedInterests`, `selectedOptions`) for managing user interests.
     - Updates the `mount` method to fetch and preset categories excluding 'Outros'.
     - Adds new methods (`goToStep4`, `updateAdditionalDetails`, `goToStep5`) to handle the additional onboarding steps.
   - **Description:** These changes enable the onboarding form to display interest categories and handle user selections, updating the user's data accordingly.
   - **Impact:** Enhances the onboarding process by introducing a new step for users to select their interests, improving data personalization.

3. **File: `app/Models/UserData.php`**
   - **Status:** Modified
   - **Changes:** Adds `interests` to the `fillable` array, enabling mass assignment of this field.
   - **Description:** This change allows the `UserData` model to handle the new `interests` attribute safely.
   - **Impact:** Ensures that user interests can be saved to the database during mass updates, aligning with the new onboarding step functionality.

4. **File: `resources/lang/pt_br/dashboard.php`**
   - **Status:** Modified
   - **Changes:** Includes new translations for the additional onboarding step and minor text adjustments.
   - **Description:** Adds language terms such as `additional`, `interests`, and `select_interests` for the new onboarding step.
   - **Impact:** Ensures that the new onboarding features are properly localized for users in Portuguese (Brazil).

5. **File: `resources/views/dashboard/onboarding.blade.php`**
   - **Status:** Modified
   - **Changes:** Updates the view to include the new step for selecting interests and integrates JavaScript for handling interest selections.
   - **Description:** These UI changes present a new section for users to select their interest categories through a custom multi-select component.
   - **Impact:** Improves user experience by allowing interaction with new onboarding features within a richer, more dynamic interface.

6. **File: `resources/views/livewire/onboarding-form.blade.php`**
   - **Status:** Modified
   - **Changes:** Major updates to include the interest selection UI and corresponding JavaScript for handling user interactions.
   - **Description:** Adds a custom select component for user interests, showing selected options as tags, and handling frontend interactions.
   - **Impact:** Significantly enhances the form's interactivity and usability during onboarding, making it easier for users to select and manage their interests.

---

# #179 Simplification and Cleanup of Orders Management on Dashboard

## Introduction
This pull request focuses on streamlining and simplifying the orders management functionality for the creator's dashboard in the application. Significant changes include the reduction of redundant code, the removal of unnecessary database queries, and the consolidation of various Laravel Livewire components that handle different states of orders. These updates aim to improve the application's performance, enhance maintainability, and provide a clearer and more intuitive user interface. The primary areas of change include database queries for orders, language translation adjustments, and updates to both backend controllers and frontend views.

## Changes Overview

1. **File: `app/Http/Controllers/DashboardController.php`**
   - **Status:** Modified
   - **Changes:** 
     - Reduced the database queries to fetch orders in different states to a single query.
     - Removed unnecessary variables (`$appliedorders`, `$activeorders`, `$finishedorders`).
   - **Description:** Consolidated the logic to count visible open orders. Simplified the switch case for role 'creator'.
   - **Impact:** The changes reduce the number of database queries, improve performance, and make the code more maintainable.

2. **File: `app/Livewire/Creator/DashboardOpenTasks.php`**
   - **Status:** Modified
   - **Changes:** 
     - Modified the conditions for fetching orders.
   - **Description:** Simplified the logic to exclude certain statuses and fetch a limited number of visible orders.
   - **Impact:** Improved performance by reducing complex nested queries, making the data fetching more efficient.

3. **File: `resources/lang/pt_br/dashboard.php`**
   - **Status:** Modified
   - **Changes:** 
     - Removed and added various language strings to support the simplified UI.
   - **Description:** Updated the translation file to reflect the new simplified structure and terms.
   - **Impact:** Enhanced clarity and consistency in the user interface text.

4. **File: `resources/views/dashboard/business/dashboard.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Changed the translation key for displaying no open orders.
   - **Description:** Updated the view to use the new translation key `dashboard.index.no_orders`.
   - **Impact:** Minor impact; ensures the consistency of translated terms.

5. **File: `resources/views/dashboard/creator/dashboard.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Removed complex conditional tab panels for different orders statuses.
     - Simplified the navigation buttons.
   - **Description:** Modernized the UI by removing multiple conditional checks for order tabs and consolidating them into a single tab.
   - **Impact:** Cleaner, more user-friendly interface; improves maintainability.

6. **File: `resources/views/dashboard/creator/livewire/dashboard-tasks.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Revamped the display logic for orders, adding better handling of closed campaigns and applied statuses.
   - **Description:** Improved the user interface to provide clearer feedback for order status with visual overlays.
   - **Impact:** Enhanced user experience with more intuitive status indications.

7. **File: `app/Livewire/Creator/DashboardMyTasks.php`**
   - **Status:** Renamed (from `app/Livewire/Creator/DashboardFinishedTasks.php`)
   - **Changes:** 
     - Renamed the class and modified the rendered orders logic.
   - **Description:** Refactored to handle multiple order statuses under a single consolidated component.
   - **Impact:** Simplifies component logic, reduces redundancy, and aligns with new simplified tab structure.

8. **File: `app/Livewire/Creator/DashboardActiveTasks.php`**
   - **Status:** Removed
   - **Changes:** 
     - Deleted the component.
   - **Description:** This component was removed as its functionality was merged into the new `DashboardMyTasks` component.
   - **Impact:** Reduces code redundancy and simplifies codebase.

9. **File: `app/Livewire/Creator/DashboardAppliedTasks.php`**
   - **Status:** Removed
   - **Changes:** 
     - Deleted the component.
   - **Description:** Similar to `DashboardActiveTasks`, this component was removed and its logic integrated into `DashboardMyTasks`.
   - **Impact:** Further reduces codebase complexity and maintenance overhead.

---

# #178 Feature Addition for User Impersonation

## Introduction
This pull request introduces a new feature that allows administrators to impersonate other users within the application. The feature will enable admins to troubleshoot issues or provide support by operating the system as another user, without needing direct access to their credentials. The changes impact several parts of the application, including the User model, package dependencies, configuration files, UI components, and routing.

The changes can be categorized as follows:
- **New feature addition**: User impersonation.
- **Dependency addition**: Adds the laravel-impersonate package.
- **UI enhancements**: Adds UI elements to start and leave impersonation sessions.
- **Route updates**: Introduces routes necessary for impersonation.

## Changes Overview

1. **File: `app/Models/User.php`**
    - **Status:** Modified
    - **Changes:** 
        - Imported `Impersonate` trait from `Lab404\Impersonate\Models\Impersonate`.
        - Added `Impersonate` to the `use` statements.
        - Added `canImpersonate` and `canBeImpersonated` methods.
    - **Description:** These changes enable the User model to support impersonation functionality. The `canImpersonate` method checks if a user has permission to impersonate (e.g., if the user is an admin), and `canBeImpersonated` checks if the user can be impersonated.
    - **Impact:** Enhances the User model with new methods that determine impersonation eligibility, ensuring that only authorized users can use this feature.

2. **File: `composer.json`**
    - **Status:** Modified 
    - **Changes:** 
        - Added `"lab404/laravel-impersonate": "^1.7"` to the list of dependencies.
    - **Description:** This change adds the package needed for the impersonation functionality.
    - **Impact:** Requires the new package to be installed, which introduces new functionalities and dependencies to the application.

3. **File: `config/app.php`**
    - **Status:** Modified
    - **Changes:** 
        - Added `Lab404\Impersonate\ImpersonateServiceProvider::class` to the list of service providers.
    - **Description:** Includes the impersonation service provider to the configuration, thereby enabling its services throughout the application.
    - **Impact:** Registers the service provider necessary for the impersonation feature, thus activating the package functionalities.

4. **File: `resources/views/admin/user/index.blade.php`**
    - **Status:** Modified
    - **Changes:** 
        - Modified and added several lines of HTML/Blade template code to update the user list table and include options for impersonation.
    - **Description:** Enhances the admin user interface to include options for starting and ending impersonation sessions, making the feature accessible and usable through the admin panel.
    - **Impact:** Improves the user interface by adding new controls that allow admins to initiate and manage impersonation sessions directly from the user list.

5. **File: `resources/views/dashboard/components/header.blade.php`**
    - **Status:** Modified
    - **Changes:** 
        - Added a section to display a button for leaving impersonation if an admin is currently impersonating a user.
    - **Description:** Adds UI elements in the dashboard header to provide an option for admins to exit impersonation mode conveniently.
    - **Impact:** Enhances user experience by offering a straightforward way for admins to discontinue impersonation, ensuring smoother transitions back to their admin roles.

6. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** 
        - Added `Route::impersonate();` to register routes for impersonation.
    - **Description:** Adds routes that support the impersonation functionality, allowing route-based methods to handle impersonation actions.
    - **Impact:** Introduces new routes that are essential for the feature to function, integrating impersonation capabilities into the application's routing system.

---

# #177 Email Display Improvement in Dashboard Header Component

## Introduction
This pull request focuses on improving the display of user email addresses in the dashboard's header component. The changes aim to enhance the user experience by ensuring that email addresses are displayed more neatly within the UI. The update particularly addresses the issue of long email addresses potentially causing layout problems or being difficult to read.

## Changes Overview
1. **File: `resources/views/dashboard/components/header.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted the way user email addresses are displayed by adding a class for better text wrapping and limiting the email length.
- **Description:** 
  - Added `break-all dark:text-neutral-500 line-clamp-1` classes to the paragraph tag for the email.
  - Limited the email display to 26 characters using `{{ Str::limit(Auth::user()->email, 26) }}`.
- **Impact:**
  - The email will now break properly and be clamped to one line, ensuring a clean and consistent display even for long email addresses.
  - By truncating the email to 26 characters, it prevents UI layout disruptions, providing a more streamlined user interface in the dashboard.


---

# #176 New Feature for Video Conversion and Schema Updates

## Introduction
This pull request introduces a new command to convert video references to a specific format and resolution with a watermark. It also includes database schema updates to accommodate new fields required for this feature. The changes impact application functionality by automating video processing and enhance data integrity through schema updates. This PR improves user experience by ensuring video content conforms to required specifications and adds a mechanism for flagging videos that have been processed.

## Changes Overview
1. **File: `app/Console/Commands/CloudconvertReferences.php`**
- **Status:** Added
- **Changes:** This newly added command converts user reference videos to a 360x640 mp4 format with a watermark. It updates the video path and thumbnail path in the database once conversion is successful.
- **Description:** The command retrieves unconverted user reference videos, processes them using the CloudConvert service, and updates the database with new video and thumbnail paths. It also deletes the original video file after successful conversion.
- **Impact:** Automates video conversion, ensuring all user reference videos meet specific format requirements with a watermark, which improves video content consistency and user experience.

2. **File: `database/migrations/2024_07_10_151356_add_thumbnail_and_converted_to_user_references_table.php`**
- **Status:** Added
- **Changes:** Adds two new columns, `thumbnail` and `converted`, to the `user_references` table.
- **Description:** The `thumbnail` column stores the path to the video thumbnail, and the `converted` column is a boolean indicating if the video has been converted.
- **Impact:** Enhances the database schema to support new features, providing additional metadata for user reference videos.

3. **File: `app/Console/Commands/CloudconvertSetcardvideo.php`**
- **Status:** Modified
- **Changes:** Removed references to the `UserSetcardVideo` model and its querying logic.
- **Description:** The removed lines are legacy or commented-out code related to the `UserSetcardVideo` that is no longer applicable.
- **Impact:** Cleans up and simplifies the existing command, ensuring it only processes relevant user data.

4. **File: `app/Console/Kernel.php`**
- **Status:** Modified
- **Changes:** Adds a new scheduled task to invoke the `cloudconvert:references` command every minute in production environments.
- **Description:** This scheduling ensures the `cloudconvert:references` command runs automatically at a regular interval.
- **Impact:** Automates the invocation of the new video conversion command, maintaining up-to-date video status with minimal manual intervention.

5. **File: `app/Models/UserReference.php`**
- **Status:** Modified
- **Changes:** Updates the model to include new attributes `thumbnail` and `converted` in the `fillable` property and adds a relationship method to the `User` model.
- **Description:** These changes allow mass assignment of the new attributes and establish a relationship with the `User` model.
- **Impact:** Facilitates integration of new schema fields within the application, enabling streamlined data handling and retrieval.

6. **File: `app/Models/UserSetcardVideo.php`**
- **Status:** Modified
- **Changes:** Includes new attributes `thumbnail` and `converted` in the `fillable` property.
- **Description:** These adjustments allow mass assignment of `thumbnail` and `converted` fields in the `UserSetcardVideo` model.
- **Impact:** Enhances the model to handle new attributes transparently, ensuring compatibility with the updated schema.

By introducing these changes, the application can better manage video content, providing a more consistent and automated approach to video processing and storage, ultimately improving both backend efficiency and user experience.


---

# #175 Pull Request Overview: Feature Enhancement for Setcard Video Conversion

## Introduction
This pull request introduces a new feature to automate the process of converting user setcard videos to a specific resolution (360x640) and format (MP4) while applying a watermark. This enhancement improves the uniformity and branding of setcard videos on the platform. The changes span several areas, including the addition of new commands, service integrations, database migrations, and updates to existing controllers. These modifications aim to streamline video processing, enhance user experience, and maintain consistent content quality.

## Changes Overview

1. **File: `app/Console/Commands/CloudconvertSetcardvideo.php`**
- **Status:** Added
- **Changes:** Added a new console command `CloudconvertSetcardvideo` which converts user setcard videos to the specified format and resolution, adds a watermark, and updates the video record.
- **Description:** This command fetches videos marked as unconverted, converts them using the CloudConvert API, applies a watermark, saves the converted video and its thumbnail, updates the video record in the database, and deletes the original video. 
- **Impact:** Automates the video conversion process, ensuring all videos adhere to a standard format and branding, which can improve user experience and video consistency.

2. **File: `app/Services/CloudConvert.php`**
- **Status:** Added
- **Changes:** Implemented a new service `CloudConvert` to interface with the CloudConvert API for video processing.
- **Description:** This service handles the API interaction required for importing videos, converting them, applying watermarks, and exporting the final video along with a thumbnail. It manages task lifecycle and error handling during the process.
- **Impact:** Centralizes video conversion logic, simplifies command implementation, and promotes code reusability and maintainability.

3. **File: `database/migrations/2024_07_10_120227_add_converted_to_user_setcard_videos_table.php`**
- **Status:** Added
- **Changes:** Created a migration to add `thumbnail` and `converted` columns to the `user_setcard_videos` table.
- **Description:** This migration adds necessary columns to store the thumbnail path and conversion status of the videos.
- **Impact:** Extends the database schema to accommodate new functionality, enabling tracking of video conversion status and associated thumbnails.

4. **File: `app/Console/Kernel.php`**
- **Status:** Modified
- **Changes:** Scheduled the `cloudconvert:setcardvideo` command to run daily at 18:22 in the production environment.
- **Description:** This change automates the daily execution of the video conversion process, ensuring timely updates to user videos.
- **Impact:** Ensures regular and consistent processing of unconverted videos, reducing manual intervention and improving operational efficiency.

5. **File: `app/Http/Controllers/TaskController.php`**
- **Status:** Modified
- **Changes:** Added a newline for code formatting.
- **Description:** Minor formatting improvement with no functional impact.
- **Impact:** Enhances code readability and maintainability.

6. **File: `app/Http/Controllers/UserProfileController.php`**
- **Status:** Modified
- **Changes:** Updated the `video_upload` method to reset the `converted` status to `false` upon new video uploads.
- **Description:** Ensures any new or updated video uploads are marked for conversion by resetting the `converted` flag.
- **Impact:** Guarantees that all newly uploaded videos are processed appropriately for format and watermark application.

7. **File: `config/app_custom.php`**
- **Status:** Modified
- **Changes:** Added configurations for CloudConvert API details and new folder paths for storing processed videos and thumbnails.
- **Description:** These configurations enable the application to use the CloudConvert service and define storage paths for processed assets.
- **Impact:** Enhances configurability and environment-specific customization, supporting seamless integration and deployment.

Overall, these changes significantly enhance the platform's video handling capabilities, ensuring all setcard videos are consistently formatted, watermarked, and updated in a timely manner, thereby improving both user and administrative experiences.

---

# #173 Pull Request Overview: 

## Introduction
This pull request focuses on enhancing the "Order Details" page within the admin view by introducing sorting functionality for order applications. Previously, applications under an order were displayed without any specific order. With these changes, applications are now sorted by their status. This improvement is expected to benefit both administrators and users by providing a clearer overview of the order application statuses, which can enhance the decision-making process and provide a more organized display of information.

## Changes Overview

1. **File: `resources/views/admin/order/show.blade.php`**
- **Status:** Modified
- **Changes:**
  - Added a new section that sorts order applications based on their status.
  - Introduced a new `@php` block to sort applications by their status, with a specific priority order (`COMPLETED`, `APPROVED`, `REJECTED`, `CANCELED`, `APPLIED`).
  - Removed the display of the relative creation time for each application.
- **Description:**
  - Added a new heading for the "Applications" section to improve visibility and context.
  - Implemented sorting logic using a priority array within a `@php` block. This ensures that applications are displayed in a consistent and meaningful order, enhancing the usability of the page for administrators.
  - Removed the lines displaying how long ago the application was created ("diffForHumans()").
- **Impact:**
  - Clearer organization of order applications by status, providing an intuitive view for administrators.
  - Enhanced user interface by eliminating less relevant information (creation time), allowing for more focus on the status of applications. 
  - The removal of the relative creation time aims to streamline the information and reduce visual clutter.

The main objective of these changes is to make the order management process more efficient and user-friendly, leading to a smoother operational experience for the administrative staff.

---

# #171 Pull Request Overview
## Addition of Search Bar in Product Category Selection and Code Formatting Improvements

## Introduction
This pull request introduces updates to the product dashboard and product creation/editing views in terms of functionality and code formatting. Specifically, the changes focus on improving the user experience by adding a search bar to the product category selection dropdown and ensuring consistent and readable code formatting within the application's Blade templates. These modifications enhance user interaction, maintain code hygiene, and potentially reduce user frustration by making it easier to select product categories.

## Changes Overview

1. **File: `resources/lang/pt_br/dashboard.php`**
   - **Status:** Modified
   - **Changes:** Added a new localization string `'searchbar' => 'Procurar'`
   - **Description:** A new Portuguese translation for the term "Search" was added to support the new search functionality in the product category dropdown.
   - **Impact:** This change ensures that the user interface remains localized and user-friendly for Portuguese-speaking users.

2. **File: `resources/views/dashboard/business/product/create.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Added a search bar functionality to the category dropdown. 
     - Reformatted various code segments for better readability.
   - **Description:** 
     - The form input for selecting product categories now supports searching, enhancing the user experience by allowing users to easily find categories.
     - Code formatting adjustments ensure consistency and improve maintainability.
   - **Impact:** 
     - Users will have an easier time navigating and selecting product categories, making the product creation process more efficient.
     - Consistent code formatting makes future modifications and debugging more straightforward, fostering better collaboration among developers.

3. **File: `resources/views/dashboard/business/product/edit.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Added similar search functionality to the category dropdown as in the create view.
     - Made extensive code formatting changes to improve readability and maintainability.
   - **Description:** 
     - Like the product creation view, the edit view now also features a searchable product category dropdown.
     - The reformatting of code follows best practices for readability and future maintenance.
   - **Impact:** 
     - Enhances user experience by making category selection in the edit view as efficient as in the create view.
     - Maintains code quality and facilitates easier updates by ensuring consistent formatting.

---

# #170 New Deletion Feature for User References

## Introduction
This pull request introduces several updates with a primary focus on enhancing the profile references management feature. The most notable change is the addition of functionality to allow users to delete references from their profiles. This update also includes minor UI changes for better user experience and improved route handling. These changes improve the application's functionality by providing users more control over their profile content, enhancing security through proper resource management, and upgrading the user interface for a more intuitive experience.

## Changes Overview
1. **File: `app/Livewire/ProfileReferences.php`**
   - **Status:** Modified
   - **Changes:**
     - Added the `Storage` facade to handle file deletions.
     - Updated `updateVideoInformation` method to redirect to the references page.
     - Introduced a new `deleteReference` method to find and delete the reference and its associated video file from the S3 storage.
   - **Description:** The `deleteReference` method utilizes the `Storage` facade to remove video files from the S3 storage when a reference is deleted. This method ensures that both the database and the storage are updated accordingly.
   - **Impact:** This change allows users to delete their references along with associated video files, ensuring data consistency and freeing up storage space.

2. **File: `resources/views/admin/order/show.blade.php`**
   - **Status:** Modified
   - **Changes:**
     - Added `preload="auto"` and `controlsList="nodownload"` attributes to the video element.
   - **Description:** These attributes enhance the performance and security of video playback. `preload="auto"` starts loading the video as soon as the page loads, improving user experience, while `controlsList="nodownload"` prevents users from downloading the video.
   - **Impact:** Improved user experience with faster video loading and enhanced security by restricting video downloads.

3. **File: `resources/views/profile/profile-references.blade.php`**
   - **Status:** Modified
   - **Changes:**
     - Removed a redundant blank line.
     - Added a delete button with an associated `deleteReference` method call for each reference.
   - **Description:** The removal of the blank line is a minor cleanup for better code readability. The new delete button invokes the `deleteReference` method from `ProfileReferences.php`, enabling users to delete references directly from the UI.
   - **Impact:** Simplifies the user experience by allowing easy deletion of references directly from the profile, making the interface more interactive.

4. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:**
     - Added a new route definition for deleting references: `Route::delete('/referencias/{id}', [UserProfileController::class, 'references_delete'])->name('profile.references.delete');`
   - **Description:** This route links to a new controller method responsible for handling the deletion of profile references. The route uses the DELETE HTTP method, which is more appropriate for deletion operations.
   - **Impact:** Enhanced route handling ensures that reference deletions are processed correctly. This addition aligns with RESTful principles, improving the maintainability and scalability of the application.

By implementing these changes, the application benefits from improved functionality, enhanced user experience, and better resource management, all of which contribute to a more robust and user-friendly system.

---

# #169 Enhancements to Video Controls and Application Order in Various Views

## Introduction
This pull request introduces multiple updates across different parts of the application, primarily focusing on enhancing video playback controls and refining the order in which application records are displayed. The main changes can be categorized into two areas: 
- **User Experience Enhancements:** Improvements to video elements to disable downloading and ensure better load times, enhancing user interactivity and control.
- **Application Order Adjustment:** Modifications to the order processing logic to sort application records more intuitively.

These updates are important for maintaining a better and more secure user experience by controlling video content downloads while also ensuring that the application data is presented in a more user-friendly manner.

## Changes Overview
1. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** Reordered the application query to first sort by visibility and then by creation date.
- **Description:** The query modification now orders applications by their visibility status (visible applications first) and then by creation date, ensuring that users see the most relevant and visible applications at the top.
- **Impact:** Improves the relevance of data shown to users by prioritizing visible applications, enhancing user experience.

2. **File: `resources/views/admin/user/profile.blade.php`**
- **Status:** Modified
- **Changes:** Added attributes `preload="auto"` and `controlsList="nodownload"` to the video tag.
- **Description:** These enhancements ensure that the video preloads automatically and disables the download option, leading to better bandwidth management and increased security by preventing content downloading.
- **Impact:** Improves video loading experience and content protection.

3. **File: `resources/views/dashboard/business/order/applications.blade.php`**
- **Status:** Modified
- **Changes:** Added attributes `preload="auto"` and `controlsList="nodownload"` to the video tag.
- **Description:** Implemented to enhance video playback experience and prevent downloading, reflecting a consistent approach to video control across the dashboard.
- **Impact:** Enhanced video interaction and content security improvement.

4. **File: `resources/views/dashboard/components/order-files.blade.php`**
- **Status:** Modified
- **Changes:** Added attributes `preload="auto"` and `controlsList="nodownload"` to the video tag.
- **Description:** Similar to other changes, this modification ensures automatic video preload and disables download functionality, aligning with the video control standardization effort.
- **Impact:** Improved loading and enhanced content protection.

5. **File: `resources/views/dashboard/creator/references.blade.php`**
- **Status:** Modified
- **Changes:** Added attributes `preload="auto"` and `controlsList="nodownload"` to the video tag.
- **Description:** Automated preloading for smooth video playback and restricted download options, providing a consistent video experience across the platform.
- **Impact:** Better user experience with immediate video playback and restricted download abilities.

6. **File: `resources/views/dashboard/creator/task/view.blade.php`**
- **Status:** Modified
- **Changes:** Added attributes `preload="auto"` and `controlsList="nodownload"` to the video tag in two locations.
- **Description:** These updates ensure video files are preloaded and download options are disabled, enhancing interaction and security.
- **Impact:** Consistency in user experience and improved content protection.

7. **File: `resources/views/livewire/onboarding-form.blade.php`**
- **Status:** Modified
- **Changes:** Added attributes `preload="auto"` and `controlsList="nodownload"` to the video tag.
- **Description:** The attributes aim to provide smooth video interaction while restricting download capabilities, aligning the onboarding process with overall video enhancements.
- **Impact:** Smoother onboarding process with improved video handling.

8. **File: `resources/views/profile/profile-references.blade.php`**
- **Status:** Modified
- **Changes:** Added attributes `preload="auto"` and `controlsList="nodownload"` to the video tag.
- **Description:** The video elements across profile references are updated to preload and prevent download, standardizing video-related user experience.
- **Impact:** Consistent video playback experience and uniform content security measures.

9. **File: `resources/views/profile/profile-video-upload.blade.php`**
- **Status:** Modified
- **Changes:** Added attributes `preload="auto"` and `controlsList="nodownload"` to the video tag in two locations.
- **Description:** Updated to ensure videos are preloaded and that downloading is not an option, enhancing both the upload experience and content security.
- **Impact:** Better user interaction during the profile video upload with restricted download options.

---

# #168 Addition of Level 2 User Tracking and Display

## Introduction
This pull request introduces changes to track and display Level 2 users within the administration section of the application. The main focus lies in enhancing the user experience by providing comprehensive user statistics and improving the interface to manage different user levels more effectively. This update involves adding server-side logic to fetch Level 2 user data and updating the front-end to display this new category of users. As a result, administrators will have better insights and tools to manage users, particularly creators who have reached Level 2 status.

## Changes Overview

1. **File: `app/Http/Controllers/AdminController.php`**
- **Status:** Modified
- **Changes:** 
  - Added code to count Level 2 users.
  - `User::where('role', 'creator')->whereHas('data', function($query) { $query->where('checked', true)->where('level', 2); })->has('creatorDetails')->count();`
  - Update array returned to the view to include `level2Count`.
- **Description:** 
  - The changes enable the system to count and keep track of the number of Level 2 users. This extends the current functionality that already tracks other user levels.
- **Impact:** 
  - This will allow the administration panel to display the count of Level 2 users, providing administrators with a new metric to monitor user status and engagement.

2. **File: `resources/views/admin/user/levels.blade.php`**
- **Status:** Modified
- **Changes:**
  - Modified the grid layout to accommodate the new Level 2 user card: `grid-cols-3` to `grid-cols-4`.
  - Added a card to display Level 2 user statistics.
  - Included necessary HTML and Blade directives to fetch and display the Level 2 count.
  - Updated the user level description list to include Level 2 explanation.
  - Added a new tab for Level 2 users.
  - Extended the user table to display Level 2 users similarly to Level 1.
- **Description:**
  - The grid change (`grid-cols-4`) ensures the new Level 2 user card fits seamlessly in the existing layout.
  - The card structure is similar to other user level cards, ensuring a consistent look and feel.
  - User descriptions and tabs help administrators understand the new Level 2 user category and manage them effectively.
  - The new table handles display and management of Level 2 users, providing the same functional interface as other user levels.
- **Impact:**
  - User interface changes significantly improve the visualization of user levels on the admin dashboard.
  - Administrators gain the ability to view, manage, and filter Level 2 users, enhancing the overall user management capabilities of the platform.
  - This may necessitate updates to administrator training and documentation to cover the new functionalities.

These changes aim to enhance the administrative capabilities of the platform by providing more detailed user level insights and management options, thereby improving the overall administrative experience and system effectiveness.

---

# #166 New Detailed Order Overview Page for Admin

## Introduction

This pull request introduces a comprehensive new page in the Admin view dedicated to displaying detailed information about individual orders. The changes encompass:

1. **New Feature Addition**: A detailed order overview page that provides various information about the order, user, product, and applications linked to the order.
2. **UI Enhancements**: New visual components that enhance the user experience by structuring detailed information more clearly.
3. **Route Update**: New route to access individual order details in the Admin dashboard.

These modifications aim to improve the management experience for admins, offering a more detailed view of each order and facilitating better monitoring and user management.

## Changes Overview

1. **File: `resources/views/admin/order/show.blade.php`**
   - **Status:** Newly Added
   - **Changes:** An entirely new Blade view has been created.
   - **Description:** This file contains the HTML and Blade directives to show detailed information about a specific order, including user details, product information, and associated applications. Key features include:
     - Title and Header defining the order.
     - User Information Section: Displaying user first name, last name, email, phone, and status information.
     - Order Information: Details about the order, such as total price, duration, hooks, pictures, and additional creators.
     - Conditional Display: Order-specific details like title, language, video format, gender, age, and more.
     - Interactive Components: Options to expand/collapse long text data for better readability.
     - Applications linked to the order showcased with video previews and further options.
   - **Impact:**
     - Provides admins with a new, detailed view of each order.
     - Enhances data visibility and organization for improved admin decision-making.
     - Introduces a more interactive and user-friendly interface for managing order-related information.

2. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Added a new method `order_show` and its functionality.
   - **Description:** The method `order_show($uuid)` retrieves an order by its UUID and passes it to the new `admin/order/show` view for detailed rendering.
   - **Impact:**
     - Enables the backend to support fetching and displaying specific order details.
     - Enhances routing capabilities and tightly integrates with the new detailed order view.

3. **File: `resources/views/admin/order/index.blade.php`**
   - **Status:** Modified
   - **Changes:** Added a new button/link to view individual orders directly.
   - **Description:** 
     - Introduced a “View order” button next to each order entry on the order index page.
     - This button routes to the detailed order page for the selected order.
   - **Impact:**
     - Provides a quick navigation method for admins to access detailed order information.
     - Enhances usability by linking list and detail views directly.

4. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Added a new route definition.
   - **Description:** 
     - New route `admin/order/{uuid}` mapped to the `order_show` method in the AdminController.
   - **Impact:**
     - Implements the necessary backend route to access the detailed order view.
     - Completes the integration needed for navigating to the specific order details.

These changes introduce a crucial new feature to the admin dashboard, significantly enriching the order management capabilities by offering a granular, detailed perspective of each order. This leads to improved user satisfaction for admin users through enhanced insights and interactions within the admin panel.

---

# #165 Addition of "Checked" Feature to User Data

## Introduction
The pull request introduces several modifications across different files, primarily aimed at adding a "checked" state to user data. This includes the addition of new database columns, updates to controllers to manage this state, and alterations to various views and middleware. The main areas of change encompass feature additions, user experience enhancements, and database schema adjustments. These changes streamline the process of tracking and managing user verification statuses and incorporating this functionality into various parts of the application.

## Changes Overview
1. **File: `database/migrations/2024_07_08_131651_add_checked_column_to_user_data_table.php`**
   - **Status:** Added
   - **Changes:** Introduced a new migration to add `checked` (boolean) and `check_comment` (text, nullable) columns to the `user_data` table. Updated rows where `last_check_at` is not null to set `checked` to true.
   - **Description:** This migration aims to track whether user data has been verified. The `checked` column defaults to false, and `check_comment` allows for optional remarks.
   - **Impact:** Enhances the ability to mark and comment on user verification, potentially affecting queries and logic involving the `user_data` table.

2. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Added setting `checked` to true when changing user levels or checking user data.
   - **Description:** Reflects that user data has been reviewed by setting `checked` to true during user level changes.
   - **Impact:** Ensures that any changes to user levels or checks will automatically mark the user data as reviewed, improving data accuracy.

3. **File: `app/Http/Controllers/UserProfileController.php`**
   - **Status:** Modified
   - **Changes:** Sets `checked` to false when a user uploads a new video.
   - **Description:** This indicates that any new uploads need review, automatically flagging the user data for re-verification.
   - **Impact:** Helps maintain integrity by flagging new content for review, ensuring adherence to guidelines.

4. **File: `app/Http/Controllers/WebhookController.php`**
   - **Status:** Modified
   - **Changes:** Added the assignment of `orderstatus` to 'AGUARDANDO BRIEFING' on 'PAYMENT_CONFIRMED' events.
   - **Description:** Adds an order status update to provide more detailed tracking of payment statuses.
   - **Impact:** Improves payment tracking by adding specific statuses, aiding in better financial and order management.

5. **File: `app/Http/Middleware/CheckOnboarding.php`**
   - **Status:** Modified
   - **Changes:** Code refactoring for better readability.
   - **Description:** Improved code maintainability by consolidating conditions.
   - **Impact:** Ensures clear and maintainable middleware conditions, reducing potential logic errors.

6. **File: `app/Livewire/UpdateCreatorMessengerForm.php`**
   - **Status:** Modified
   - **Changes:** Changed validation rules for `country_code` and `phone_number` to be required instead of nullable.
   - **Description:** Ensures that essential contact information is always provided.
   - **Impact:** Enhances data completeness for user profiles, potentially impacting form submissions.

7. **File: `resources/lang/pt_br/dashboard.php`**
   - **Status:** Modified
   - **Changes:** Updated language to refine placeholder text and added new text entries.
   - **Description:** Provides clearer guidance to users on messages and options presented in the dashboard.
   - **Impact:** Improves user experience through more precise and user-friendly interface text.

8. **File: `resources/views/admin/user/levels.blade.php`**
   - **Status:** Modified
   - **Changes:** Significant changes in the user levels view including adding checks and hover-over tooltips for actions.
   - **Description:** Enhances the interface to show verification statuses and provides detailed actions.
   - **Impact:** Improves admin experience by adding meaningful visual cues and interactive elements, which aids in user management.

9. **File: `resources/views/auth/register.blade.php`**
   - **Status:** Modified
   - **Changes:** Made the `phone_number` field required.
   - **Description:** Ensures that newly registered users provide a phone number.
   - **Impact:** Enhances user data completeness upon registration, potentially increasing contactability.

10. **File: `resources/views/dashboard/creator/livewire/dashboard-tasks.blade.php`**
    - **Status:** Modified
    - **Changes:** Removed user company or name section.
    - **Description:** Streamlined task dashboard view by removing less critical information.
    - **Impact:** Simplifies the dashboard, focusing user attention on more relevant data.

11. **File: `resources/views/dashboard/creator/task/view.blade.php`**
    - **Status:** Modified
    - **Changes:** Adjusted layout elements, spacing, and text sizes for better readability.
    - **Description:** Improved UI/UX with better layout and visual hierarchy.
    - **Impact:** Enhances user experience by making task details clearer and easier to navigate.

12. **File: `resources/views/profile/update-creator-messenger-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Made `phone_number` field required.
    - **Description:** Ensures that creator profiles include contact information.
    - **Impact:** Enhances profile completeness, which is crucial for communication and service provisioning.

---

# #164 Temporary Disablement of User Data Update on Deletion

## Introduction
This pull request focuses on a minor adjustment to the `CustomDeleteUser` class within the application. The modification temporarily disables the updating of the `cpf_cnpj_value` when a user is deleted. This change ensures that the existing deletion workflow remains unaffected while potentially addressing known issues with updating user data during deletion. The impact of this change on the application's functionality is minimal, but the update might be important for debugging or development purposes. Moreover, this adjustment makes the code more robust by helping to prevent potential errors that might have been caused by the user data update logic.

## Changes Overview
1. **File: `app/Livewire/CustomDeleteUser.php`**
- **Status:** Modified
- **Changes:** 
    - Added comment syntax to disable the line retrieving user data and the corresponding conditional block that updates the `cpf_cnpj_value`.
    - The code block:
      ```php
      $userData = $user->data;
      if ($userData) {
          $userData->cpf_cnpj_value = 'deleted_' . $userData->cpf_cnpj_value;
          $userData->save();
      }
      ```
      has been commented out.
- **Description:** 
    - These changes were made to temporarily disable the functionality that updates the `cpf_cnpj_value` when a user is deleted. This may be aimed at debugging, resolving a bug, or avoiding errors related to this logic in the current state of the application.
- **Impact:** 
    - **Functionality:** No update will be performed on the `cpf_cnpj_value` of the user data due to deletion. This implies that the `cpf_cnpj_value` will remain unchanged rather than being prefixed with 'deleted_'.
    - **User Experience:** Users will continue to be logged out as expected upon deletion without any visible changes related to their `cpf_cnpj_value`.
    - **Development:** Developers should be aware that this logic is currently disabled and might need to be re-enabled after addressing the underlying issues prompting this change.

This modification is a behind-the-scenes change that does not impact end users directly but affects how the application handles user deletions internally.

---

# #163 Pull Request Overview: New Contract Creation Feature with Migration and PDF Generation

## Introduction
This pull request introduces a comprehensive feature for generating contracts for approved order applications. The main elements of the update include a new console command, database migration, new views for generating PDFs, and modifications to controllers and other supporting files. The changes significantly impact the application's functionality by automating contract creation and storage, enhancing the user experience with updated views, and improving the system's overall architecture. 

## Changes Overview

1. **File: `app/Console/Commands/OrderCreateContract.php`**
   - **Status:** Added
   - **Changes:** A new console command `OrderCreateContract` is introduced. It retrieves approved order applications that don't have a contract path, generates a PDF contract for each, and updates the contract path in the database.
   - **Description:** This addition automates contract creation for order applications, enhancing efficiency by programmatically fetching necessary data, generating PDFs, and saving them to AWS S3.
   - **Impact:** Improves the efficiency of contract generation and ensures consistency in data storage and retrieval.

2. **File: `database/migrations/2024_07_07_174407_add_contract_path_to_order_applications_table.php`**
   - **Status:** Added
   - **Changes:** A migration file that adds `contract_path` and `contract_data` columns to the `order_applications` table.
   - **Description:** These columns store the path to the generated contract and the contract data in JSON format respectively, crucial for contract management.
   - **Impact:** Enhances the database schema to support contract creation and storage functionalities.

3. **File: `resources/views/pdf/vertrag.blade.php`**
   - **Status:** Added
   - **Changes:** A new Blade view file for rendering the contract in a PDF format, utilizing various parameters such as business details, order details, and terms and conditions.
   - **Description:** This template is used by the PDF generation tool to create a professionally formatted contract document.
   - **Impact:** Provides a standardized format for contracts, improving the document’s presentation and consistency.

4. **File: `app/Console/Kernel.php`**
   - **Status:** Modified
   - **Changes:** Added a schedule for the new `order:create-contract` command to run every minute.
   - **Description:** Ensures the command runs automatically at regular intervals to process any outstanding order applications requiring contracts.
   - **Impact:** Automates the execution of contract creation, reducing manual intervention and ensuring timely processing.

5. **File: `app/Http/Controllers/OrderProcessController.php`**
   - **Status:** Modified
   - **Changes:** Added functionality to fetch IP information and update `contract_data` during the order application acceptance.
   - **Description:** Enhances the acceptance process by storing additional context-related data (e.g., IP information) relevant to the contract.
   - **Impact:** Provides more comprehensive data for contracts, which can be useful for security and validation purposes.

6. **File: `app/Http/Controllers/PublicPagesController.php`**
   - **Status:** Modified
   - **Changes:** Updated to include logic for rendering terms from markdown files and introduced a test route for PDF generation.
   - **Description:** Facilitates the retrieval and display of legal terms, and allows testing the PDF generation process.
   - **Impact:** Improves the management of legal documents and allows for easier testing of new features.

7. **File: `app/Models/OrderApplication.php`**
   - **Status:** Modified
   - **Changes:** Added `contract_path` and `contract_data` fields to the model’s fillable attributes.
   - **Description:** Ensures these fields can be mass-assigned when creating or updating `OrderApplication` records.
   - **Impact:** Facilitates automated updates to the `OrderApplication` model, supporting the contract creation workflow.

8. **File: `composer.json`**
   - **Status:** Modified
   - **Changes:** Added `spatie/laravel-pdf` package dependency.
   - **Description:** Adds a necessary library for generating PDFs based on Blade templates.
   - **Impact:** Enables PDF generation capabilities within the application, supporting new features.

9. **File: `package.json`**
   - **Status:** Modified
   - **Changes:** Added `puppeteer` dependency.
   - **Description:** Puppeteer is a required package for PDF functionalities and other document-related automations.
   - **Impact:** Provides tools necessary for rendering web content and generating PDFs.

10. **File: `resources/.DS_Store`**
    - **Status:** Modified
    - **Changes:** No notable changes.
    - **Description:** System file, possibly modified or re-indexed during development.
    - **Impact:** None.

11. **File: `resources/views/legal/terms.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated to dynamically render legal terms from markdown files.
    - **Description:** Synchronously updates the terms and conditions view to reflect content stored in markdown files.
    - **Impact:** Ensures that legal documents are easier to update and maintain.

12. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added a commented-out route for PDF testing.
    - **Description:** Provides an option to test the PDF generation feature.
    - **Impact:** Useful for developers during the testing phase of the new feature.

This comprehensive update enhances the capabilities and efficiency of the application regarding contract management and document generation. It introduces automated, scheduled tasks for contract creation, improves user experience through better data management, and ensures maintainable and scalable architecture with the addition of necessary dependencies and migrations.

---

# #162 Improved Payment Options and User Data Handling

## Introduction
This pull request introduces several enhancements to the payment system and user data handling within our application. The changes incorporate support for additional payment methods such as credit cards and debit cards, enhance the user experience by allowing the use of saved cards, and improve the overall robustness of the application by adding necessary data fields and refining the payment flow. These updates improve the application's functionality by making the checkout process more flexible and user-friendly, ensuring a seamless payment experience.

## Changes Overview
1. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** Added handling for `CREDIT_CARD` billing type within the `payment` method.
- **Description:** Ensures that when an order's billing type is `CREDIT_CARD`, the corresponding view is returned correctly.
- **Impact:** Allows users to proceed with credit card payments, enhancing the payment options available.

2. **File: `app/Http/Controllers/PaymentController.php`**
- **Status:** Modified
- **Changes:** 
  - Added support for `debit_card` payment method by treating it as `credit_card`.
  - Conditional logic to handle cobranca details based on billing type.
  - Redirects users to appropriate routes based on payment type with a special route for credit card payments.
- **Description:** Simplifies the payment method handling by converting `debit_card` to `credit_card` internally, adds robustness by handling cobranca details conditionally, and ensures users are correctly redirected.
- **Impact:** Enhances UX by providing appropriate payment flows for different billing types, thereby reducing payment-related issues and improving the checkout experience.

3. **File: `app/Http/Middleware/CheckUserAsaas.php`**
- **Status:** Modified
- **Changes:** Added `addressNumber` and `mobilePhone` fields.
- **Description:** Includes additional user data fields in the middleware to ensure comprehensive data synchronization.
- **Impact:** Improves data consistency and accuracy for user address and contact details, reducing potential issues with incomplete data.

4. **File: `app/Livewire/Business/CheckoutForm.php`**
- **Status:** Modified
- **Changes:** Added handling for saved cards and initialized `savedCards` during component mounting.
- **Description:** Allows users to use their saved credit cards, improving the convenience and speed of the checkout process.
- **Impact:** Enhances user experience by providing quicker payment options through the use of saved cards.

5. **File: `app/Models/User.php`**
- **Status:** Modified
- **Changes:** Changed relationship from `card` to `cards` to support multiple saved cards for a user.
- **Description:** Allows users to save multiple credit cards instead of just one.
- **Impact:** Increases flexibility in payment options, enabling users to manage several payment methods.

6. **File: `app/Services/PaymentService.php`**
- **Status:** Modified
- **Changes:** Enhanced `createCobranca` method to include additional information such as `description`, `externalReference`, and `callback`.
- **Description:** Improves payment processing by providing more detailed information and automatic redirection capabilities.
- **Impact:** Streamlines the payment process and ensures that transactions are more informative and user-friendly.

7. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** Added new language entries for card details-related strings.
- **Description:** Localizes new strings for additional card-related functionalities.
- **Impact:** Enhances user experience for Portuguese-speaking users by providing necessary translations.

8. **File: `resources/views/dashboard/business/order/checkout.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Added handling for `CREDIT_CARD` billing type.
  - Added button to redirect users to the external payment gateway for immediate payment.
- **Description:** Enhances the checkout view to handle credit card payments and provides an option to pay immediately via a link.
- **Impact:** Improves the checkout experience by providing an immediate payment option for credit card users.

9. **File: `resources/views/dashboard/business/order/livewire/checkout-form.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Adjusted logic for `credit_card` and `debit_card` payment methods.
  - Localized card detail related texts.
- **Description:** Refines the checkout form to handle both credit and debit card selections correctly and updates labels for better localization.
- **Impact:** Enhances the accuracy and localization of the checkout form, ensuring it is more user-friendly and intuitive.

---

# #161 Enhanced Validation and Localization in Onboarding and Content Creation Process

## Introduction
This pull request introduces several improvements to the validation mechanisms and localization within our application. These changes mainly consist of:
- Enhancements to validation checks for various file uploads.
- Updates to role-specific logic in the onboarding process.
- Amendments to the localization files for more accurate messaging.
- Minor adjustments to the UI and business logic to streamline the user experience.

## Changes Overview
1. **File: `app/Livewire/OnboardingForm.php`**
    - **Status:** Modified
    - **Changes:** Added conditional logic to check both 'creator' and 'business' roles with specific attributes.
    - **Description:** This modification ensures that users with a 'business' role but selecting CPF will be subjected to the same CPF validation as 'creator' users.
    - **Impact:** Enhances data integrity by ensuring appropriate validation checks are applied to different user roles.

2. **File: `app/Rules/FileSizeAvatar.php`**
    - **Status:** Modified
    - **Changes:** Added comprehensive validation to check file existence and readability before size validation.
    - **Description:** The file validation now includes checks for file existence and readability to prevent errors that occur when nonexistent or unreadable files are provided.
    - **Impact:** Improves robustness and reliability of avatar file uploads by preventing invalid file input.

3. **File: `app/Rules/FileSizeOrderImage.php`**
    - **Status:** Modified
    - **Changes:** Similar to avatar validation, added checks for file existence and readability.
    - **Description:** Prevents errors caused by missing or unreadable image files, ensuring only valid image uploads are processed.
    - **Impact:** Ensures smoother user experience and reduces potential upload errors.

4. **File: `app/Rules/FileSizeOrderVideo.php`**
    - **Status:** Modified
    - **Changes:** Added checks for file existence and readability before size validations.
    - **Description:** Ensures video uploads are validated for existence, readability, and size, enhancing the upload process's reliability.
    - **Impact:** Reduces errors related to file validation, improving the user experience.

5. **File: `app/Rules/FileSizeVideo.php`**
    - **Status:** Modified
    - **Changes:** Integrated additional checks for file existence and readability.
    - **Description:** Validation process was enhanced to include basic checks before size verification to prevent processing invalid files.
    - **Impact:** Provides better error handling, reducing potential user frustration during file uploads.

6. **File: `resources/lang/pt_br/validation.php`**
    - **Status:** Modified
    - **Changes:** Added new localization strings for avatar, image, and video filesizes.
    - **Description:** Updated the language file to include messages for new validation checks, ensuring users receive clear feedback in Portuguese.
    - **Impact:** Improves user communication and clarity by providing localized error messages.

7. **File: `resources/views/dashboard/business/order/livewire/checkout-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Adjusted the user data validation conditions and corrected a role-specific conditional check.
    - **Description:** The user data validation window was changed from 60 minutes to 15 minutes, refining the process for more timely updates.
    - **Impact:** Enhances security and ensures user data is accurately validated before proceeding with the order checkout process.

8. **File: `resources/views/dashboard/onboarding.blade.php`**
    - **Status:** Modified
    - **Changes:** Removed an unused script include.
    - **Description:** Cleaned up the code by removing an unnecessary script, improving the load efficiency of the onboarding page.
    - **Impact:** Slight enhancement in page speed and maintenance by eliminating unused code.

9. **File: `resources/views/legal/terms.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated various sections for clarity and added conditions related to paid ads and content rights.
    - **Description:** This update provides clearer terms regarding content creation, usage rights, and associated costs, especially for paid advertisements.
    - **Impact:** Ensures legal clarity and enhances user understanding of their rights and obligations when uploading content.

10. **File: `resources/views/livewire/onboarding-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Minor UI adjustment to a button element.
    - **Description:** Simplified button styling to ensure consistency across different themes.
    - **Impact:** Provides a more consistent and accessible UI experience for users.

---

# #160 Removal of Unused Code and Onboarding Check Enhancement

## Introduction
This pull request involves a significant cleanup of unused or redundant code and enhancements to the user onboarding process. The primary changes include the removal of the WATI webhook handler function and associated routes, deletion of outdated FAQ routes, and an added onboarding verification step to ensure business users complete the required onboarding process. These changes enhance the application's maintainability, streamline routing, and improve the user experience for business users by ensuring compulsory onboarding compliance.

## Changes Overview

1. **File: `app/Http/Controllers/WebhookController.php`**
   - **Status:** Modified
   - **Changes:** Removed the `wati_webhook` method.
   - **Description:** The `wati_webhook` method was eliminated, which handled incoming webhook requests from WATI and saved the payload to the database.
   - **Impact:** This change reduces the clutter in the controller by removing unused webhook handling logic, improving code maintainability.

2. **File: `app/Http/Middleware/CheckOnboarding.php`**
   - **Status:** Modified
   - **Changes:** Added an onboarding check for users with a 'business' role.
   - **Description:** The middleware now includes a condition that verifies if authenticated users with a 'business' role have completed their onboarding process. If not completed, the users are redirected to the onboarding route.
   - **Impact:** The change ensures that all business users complete the necessary onboarding steps before accessing other parts of the application, thereby enhancing the user experience and ensuring compliance.

3. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Removed several FAQ-related routes and the route for the WATI webhook.
   - **Description:** The routes responsible for handling CRUD operations on FAQ sections have been removed, as well as the route for handling WATI webhook events.
   - **Impact:** This cleanup reduces the number of obsolete routes, which simplifies route management and improves the maintainability and security of the application by reducing potential attack vectors.

---

# #159 New Features and Enhancements for Admin Order and Product Management

## Introduction
This pull request introduces significant updates to the admin panel, focusing on enhancing order and product management functionalities. The changes include the addition of new views for displaying orders and products, modifications to the `AdminController`, updates to middleware, and several UI improvements. These updates aim to provide a more intuitive and efficient user experience by integrating new features and simplifying data access and visualization.

## Changes Overview

1. **File: `resources/views/admin/order/index.blade.php`**
   - **Status:** Added
   - **Changes:** The new file contains a complete HTML structure for displaying a list of orders in the admin panel. It includes functionalities for displaying orders, their details, and associated actions.
   - **Description:** This new view lists all orders with essential details like user, product, status, and price. It also includes an expandable row for displaying additional order details.
   - **Impact:** This provides administrators with an enhanced capability to manage and view orders directly from the admin panel, leading to more efficient order tracking and management.

2. **File: `resources/views/admin/product/index.blade.php`**
   - **Status:** Added
   - **Changes:** The new file contains a complete HTML structure for displaying a list of products in the admin panel. It includes functionalities for displaying products, their categories, and associated actions.
   - **Description:** This new view lists all products with essential details like user, product title, category, and price. It also includes an expandable row for displaying additional product details and images.
   - **Impact:** This provides administrators with an enhanced capability to manage and view products directly from the admin panel, streamlining product management and oversight.

3. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Added `Order` and `Product` use statements. Refactored user index methods. Introduced `product_index` and `order_index` methods.
   - **Description:** New methods for fetching and displaying orders and products in the admin panel were added. Existing user-related methods were refactored for efficiency.
   - **Impact:** Enhances the controller's capabilities to manage orders and products, centralizing business logic for these actions and improving code maintainability.

4. **File: `app/Http/Middleware/TrackUserSource.php`**
   - **Status:** Modified
   - **Changes:** Added logic to normalize the `host` value to `direct` if it matches 'creatify.com.br'.
   - **Description:** Ensures that internal traffic from 'creatify.com.br' is tracked as 'direct' to avoid skewing source data.
   - **Impact:** Improves the accuracy of user source tracking, ensuring more reliable analytics data.

5. **File: `resources/lang/pt_br/admin.php`**
   - **Status:** Modified
   - **Changes:** Added new language entries for 'products' and 'orders'.
   - **Description:** Provides localized titles for the newly added product and order sections in Portuguese.
   - **Impact:** Ensures that the new admin functionalities are fully localized, catering to Portuguese-speaking users.

6. **File: `resources/views/admin/components/sidebar.blade.php`**
   - **Status:** Modified
   - **Changes:** Added new sidebar entries for 'products' and 'orders'.
   - **Description:** Integrates quick access links to the new product and order views, improving navigation within the admin panel.
   - **Impact:** Enhances the user experience by providing easy access to new functionalities, improving the overall workflow.

7. **File: `resources/views/admin/user/index.blade.php`**
   - **Status:** Modified
   - **Changes:** Updated user count and pagination handling.
   - **Description:** Switched from paginated lists to collections for user data display.
   - **Impact:** Simplifies data handling and improves performance by reducing the overhead associated with pagination.

8. **File: `resources/views/admin/user/profile.blade.php`**
   - **Status:** Modified
   - **Changes:** Updated to include new buttons and improved layout for product and order details.
   - **Description:** Enhanced the profile page to display associated products and orders with expandable details.
   - **Impact:** Provides a more comprehensive view of user-related data, supporting better decision-making and user interaction.

9. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Added routes for `product.index` and `order.index`.
   - **Description:** Defines new routes to handle requests for the new product and order views.
   - **Impact:** Extends the application routing capabilities to support new features, facilitating easier access and management.

These changes collectively enhance the admin panel's functionality, improving data management, user experience, and overall system architecture.

---

# #158 Headline:
Enhanced User Profile Management and User Interface in Admin Panel

## Introduction
This pull request introduces significant enhancements to the user profile management system and improves the user interface in the admin panel. These changes categorize users into different levels, streamline user status modifications, and offer a more detailed and navigable profile view for admins. Additionally, it rectifies previous routing issues and offers a consolidated approach to user status updates. These updates should improve the admin experience when managing user data, enhancing both functionality and user experience without compromising security.

## Changes Overview
1. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Added imports and logic for handling user reviews, combined user and order reviews, expanded user profile details, refined user status management, and updated return views.
   - **Description:** 
     - Integrated `OrderReview` and `UserReview` models to manage user reviews more efficiently by loading order and external reviews, then merging them into a single list.
     - Improved user profile detail extraction, checking for associated files, references, products, and orders to display more comprehensive information.
     - Simplified user status updates by merging `delete`, `ban`, and `activate` actions into a single `user_status_change` method.
     - Updated the user profile view to include all the new data points (reviews, files, references, products, orders).
   - **Impact:** Enhanced admin control and visibility over user data. More streamlined management of user statuses and profiles. Improved data integrity and user administration.

2. **File: `app/Models/User.php`**
   - **Status:** Modified
   - **Changes:** Adjusted relationships; renamed existing functions for clarity.
   - **Description:** Corrected the improperly named relationship methods (e.g., renamed `orders` to `products`, `reviews` to `files`, etc.) to align them with new data structures.
   - **Impact:** Ensures accurate data representation in models, leading to more reliable database operations and relationship handling in the application.

3. **File: `resources/views/admin/user/index.blade.php`**
   - **Status:** Modified
   - **Changes:** Updated table layout, removed redundant buttons, and ensured profile image and name link to the detailed user profile.
   - **Description:** Enhanced the admin user list interface by making user names and profile images clickable, linking to detailed user views. Removed the previous tooltip and modal structures for simplicity.
   - **Impact:** Improved navigability and user interface consistency. Reduces potential confusion and streamlines access to user profiles.

4. **File: `resources/views/admin/user/levels.blade.php`**
   - **Status:** Modified
   - **Changes:** Introduced tabbed navigation for user levels, enhanced the level management interface.
   - **Description:** Added tabs for quick switching between `Unchecked`, `Level 0`, and `Level 1` users. Provided better visual cues for user attributes and control buttons for level changes.
   - **Impact:** Improved usability in managing user levels and categorization. Enhances the admin's ability to quickly assess and manage users.

5. **File: `resources/views/admin/user/profile.blade.php`**
   - **Status:** Modified
   - **Changes:** Implemented a comprehensive profile layout with detailed sections on personal info, reviews, and actions.
   - **Description:** 
     - Detailed user information including name, status, contact info, social media accounts, and address details.
     - Displayed user-specific content including portfolio and reviews depending on user role (`creator`, `business`).
     - Added management buttons (activate, ban, delete) with modal confirmations.
   - **Impact:** Significantly improves the clarity and depth of user information available to admins, enabling more informed decision-making and user management.

6. **File: `resources/views/dashboard/business/order/applications.blade.php`**
   - **Status:** Modified
   - **Changes:** Corrected a broken link in the application view.
   - **Description:** Fixed link for creator profiles, ensuring it uses the correct user's nickname for navigation.
   - **Impact:** Ensures correct navigation for viewing user profiles from business order applications, enhancing usability.

7. **File: `resources/views/dashboard/creator/task/view.blade.php`**
   - **Status:** Modified
   - **Changes:** Fixed a formatting error.
   - **Description:** Corrected minor formatting issue to ensure consistency in the template.
   - **Impact:** Minor improvement in code quality and layout consistency.

8. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Updated route definitions for user status changes.
   - **Description:** Consolidated status change routes into a single versatile route handling `delete`, `ban`, and `activate` actions.
   - **Impact:** Simplifies routing and controller logic, enhancing maintainability and readability while ensuring flexibility in user status management. 

These changes collectively contribute to a more efficient, user-friendly, and secure admin user management system.

---

# #157 Overview: Custom User Deletion and Order Visibility Enhancements

## Introduction
This pull request introduces significant changes to the user account management and order visibility functionalities within the application. A new feature for custom user deletion has been added, modifying how user accounts are handled upon deletion. Additionally, enhancements have been made to the order visibility in various components, affecting both backend logic and user-facing interfaces. These changes improve user experience (UX) by ensuring better handling of user data and providing clearer visibility control of orders.

## Changes Overview
1. **File: `app/Livewire/CustomDeleteUser.php`**
- **Status:** Added
- **Changes:** Added a new Livewire component for custom user deletion functionality.
- **Description:** This new component allows users to delete their accounts securely by verifying their password. User email and status are updated to reflect deletion, and user data (e.g., CPF/CNPJ) is marked as deleted. The component also logs out the user post-deletion and redirects to the homepage.
- **Impact:** Enhances account management with more secure and robust deletion processes, ensuring user data privacy.

2. **File: `database/migrations/2024_07_05_173239_add_visible_to_orders_table.php`**
- **Status:** Added
- **Changes:** Added a migration file to include a `visible` boolean column in the `orders` table.
- **Description:** The `visible` column controls the visibility status of orders, defaulting to `false` (not visible).
- **Impact:** Provides greater flexibility and control over order visibility across the system, influencing various components that interact with order data.

3. **File: `resources/views/livewire/custom-delete-user.blade.php`**
- **Status:** Added
- **Changes:** Added a new Blade view file for the custom user deletion component.
- **Description:** This Blade template serves as a placeholder for the custom deletion interface, implying further UI elements will be integrated.
- **Impact:** Facilitates the integration of the custom user deletion UI into the front end.

4. **File: `app/Console/Commands/CreatorSendmailNewOrderAvailable.php`**
- **Status:** Modified
- **Changes:** Added checks for `visible` status in queries fetching orders for notifying creators.
- **Description:** Ensures that only visible orders trigger notifications to creators.
- **Impact:** Prevents unwanted notifications for orders marked as not visible, enhancing notification relevance and user experience.

5. **File: `app/Http/Controllers/DashboardController.php`**
- **Status:** Modified
- **Changes:** Added `visible` status checks in various queries fetching orders for dashboard display.
- **Description:** Modifies dashboard logic to account for visible orders only, ensuring accurate order counts and lists.
- **Impact:** Enhances dashboard accuracy and relevance by displaying only active and visible orders.

6. **File: `app/Http/Controllers/PublicPagesController.php`**
- **Status:** Modified
- **Changes:** Reformatted the query for fetching creator profiles but functionally unchanged.
- **Description:** Code reformatting for clarity and better maintainability.
- **Impact:** No immediate impact but improves code readability and maintainability.

7. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** Added a new translation string for profile preview functionality.
- **Description:** Supports new profile preview feature with appropriate translation.
- **Impact:** Enhances user experience for Portuguese-speaking users with relevant localization.

8. **File: `resources/views/dashboard/business/dashboard.blade.php`**
- **Status:** Modified
- **Changes:** Altered how creator applications are displayed, now filtering by application status and visibility.
- **Description:** Ensures only approved or applied and visible applications are shown in the dashboard, removing static image placeholders.
- **Impact:** Improves the relevance and accuracy of displayed creator applications, enhancing user experience.

9. **File: `resources/views/dashboard/business/order/applications.blade.php`**
- **Status:** Modified
- **Changes:** Updated the order application view to include user profile preview links and adjusted display logic for user details.
- **Description:** Adds functionality to view user profiles directly from the applications view.
- **Impact:** Enhances user interaction by providing quick access to creator profiles, improving usability.

10. **File: `resources/views/profile/delete-user-form.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted text color for consistency across themes.
- **Description:** Minor UI update to ensure consistent appearance with dark and light themes.
- **Impact:** Improves visual consistency and enhances the user interface.

11. **File: `resources/views/profile/settings.blade.php`**
- **Status:** Modified
- **Changes:** Updated to use the new custom delete user component in settings and removed comment-out code.
- **Description:** Integrates the custom delete user functionality within the profile settings.
- **Impact:** Provides a seamless experience for users managing their account settings, ensuring they can delete their accounts securely.

---

# #155 Enhancements to User Management and Improved Visibility Controls

## Introduction
This pull request introduces several updates aimed at enhancing user management within the administrative interface and improving visibility controls for order applications. These changes enhance the user experience, allow better administrative control, and improve the overall functionality and security of the application. The key areas of changes include the addition of new fields in the database, new migration scripts, updates to various controllers and views, and the introduction of error handling in various services. 

## Changes Overview

1. **File: `database/migrations/2024_07_01_104934_add_level_to_users.php`**
   - **Status:** Added
   - **Changes:** Adds new columns (`level`, `description`, `last_check_at`) to the `user_data` table.
   - **Description:** This migration adds fields to store user's level, description, and last check timestamp to improve user profile details.
   - **Impact:** Improves user profile management with more detailed information stored in the database.

2. **File: `database/migrations/2024_07_01_154834_add_show_to_order_application.php`**
   - **Status:** Added
   - **Changes:** Adds a new column `visible` to the `order_applications` table.
   - **Description:** This field will be used to manage the visibility of order applications.
   - **Impact:** Enhances control over which order applications are visible to users.

3. **File: `resources/views/admin/user/levels.blade.php`**
   - **Status:** Added
   - **Changes:** Adds a new blade template to show user levels.
   - **Description:** This view provides an interface to display and manage the levels of users.
   - **Impact:** Allows administrators to easily manage user levels through the user interface.

4. **File: `app/Console/Commands/BusinessSendmailNewApplications.php`**
   - **Status:** Modified
   - **Changes:** Adds a condition to check if the `visible` field is set to `1` when counting new applications.
   - **Description:** Ensures only visible applications are counted for sending notifications.
   - **Impact:** Prevents notifications being sent for non-visible applications, reducing unnecessary email traffic.

5. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Adds methods to manage user levels and updates existing return redirects.
   - **Description:** Facilitates the management of user levels and enhances user deletion, banning, and level changing functionalities.
   - **Impact:** Improves administrative control over user management and provides better feedback mechanisms for actions.

6. **File: `app/Http/Controllers/OrderProcessController.php`**
   - **Status:** Modified
   - **Changes:** Adds visibility checks to multiple methods and introduces error handling using try-catch blocks.
   - **Description:** Ensures that only visible applications are processed and provides error feedback during order deletions.
   - **Impact:** Improves robustness and error handling in order processing.

7. **File: `app/Http/Controllers/PublicPagesController.php`**
   - **Status:** Modified
   - **Changes:** Removes logging of errors in contact form submission.
   - **Description:** Minimizes logging verbosity for handled exceptions.
   - **Impact:** Keeps error logs cleaner by not logging handled exceptions.

8. **File: `app/Http/Middleware/CheckOnboarding.php`**
   - **Status:** Modified
   - **Changes:** Adds additional onboarding checks for users.
   - **Description:** Ensures creators complete all onboarding steps including profile photo and setcard video checks.
   - **Impact:** Enhances user onboarding process ensuring completeness before granting full access.

9. **File: `app/Http/Middleware/CheckUserAsaas.php`**
   - **Status:** Modified
   - **Changes:** Adds error handling for request exceptions.
   - **Description:** Provides user feedback in case of ASAAS check failures.
   - **Impact:** Improves error handling and user feedback.

10. **File: `app/Livewire/UpdateProfileForm.php`**
    - **Status:** Modified
    - **Changes:** Adds description field to the update profile form.
    - **Description:** Allows users to update their profile descriptions.
    - **Impact:** Enhances user profiles with a description field.

11. **File: `app/Models/OrderApplication.php`**
    - **Status:** Modified
    - **Changes:** Adds `visible` field to the fillable properties.
    - **Description:** Enables mass assignment for the `visible` attribute.
    - **Impact:** Improves flexibility in managing the visibility attribute.

12. **File: `app/Models/User.php`**
    - **Status:** Modified
    - **Changes:** Adds `status` field to the fillable properties.
    - **Description:** Enables mass assignment for the `status` attribute.
    - **Impact:** Enhances user management by allowing dynamic status updates.

13. **File: `app/Models/UserData.php`**
    - **Status:** Modified
    - **Changes:** Adds `level`, `description`, and `last_check_at` fields to the fillable properties.
    - **Description:** Enables mass assignment for new profile attributes.
    - **Impact:** Enhances user data model with additional profile details.

14. **File: `app/Services/FacebookConversionApiService.php`**
    - **Status:** Modified
    - **Changes:** Adds try-catch block for HTTP requests.
    - **Description:** Improves error handling for Facebook API calls.
    - **Impact:** Enhances service reliability by handling request exceptions properly.

15. **File: `app/Services/PaymentService.php`**
    - **Status:** Modified
    - **Changes:** Adds error handling for payment creation requests.
    - **Description:** Provides feedback upon payment processing failures.
    - **Impact:** Increases robustness and user feedback in the payment process.

16. **File: `app/Services/TikTokConversionApiService.php`**
    - **Status:** Modified
    - **Changes:** Removes error logging for TikTok event sending.
    - **Description:** Reduces logging verbosity by omitting handled exceptions.
    - **Impact:** Keeps log files cleaner.

17. **File: `resources/lang/pt_br/dashboard.php`**
    - **Status:** Modified
    - **Changes:** Adds new translations for missing avatar and payment failed messages.
    - **Description:** Updates localization file with additional key-value pairs for improved user guidance.
    - **Impact:** Enhances user experience for Portuguese-speaking users with more comprehensive messaging.

18. **File: `resources/lang/pt_br/profile.php`**
    - **Status:** Modified
    - **Changes:** Adds translation for the profile description field.
    - **Description:** Ensures consistent user messaging by localizing new fields.
    - **Impact:** Provides complete localization.

19. **File: `resources/views/admin/components/sidebar.blade.php`**
    - **Status:** Modified
    - **Changes:** Refactors the sidebar to include user levels navigation.
    - **Description:** Improves administrative navigation structure with nested user options.
    - **Impact:** Enhances admin panel usability.

20. **File: `resources/views/dashboard/business/order/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Removes unused table view logic.
    - **Description:** Simplifies the blade template by removing outdated order view logic.
    - **Impact:** Keeps the order index template lean and easier to maintain.

21. **File: `resources/views/dashboard/business/product/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Removes outdated product table view logic.
    - **Description:** Cleans up the product index template by removing unnecessary code.
    - **Impact:** Streamlines the product listing view for easier maintenance.

22. **File: `resources/views/profile/update-profile-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Adds description field to the profile update form template.
    - **Description:** Provides users with another field to describe themselves.
    - **Impact:** Improves user profiles by allowing more detailed self-descriptions.

23. **File: `resources/views/profile/update-profile-information-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Adds description field to the profile information form.
    - **Description:** Enables users to update their profile descriptions.
    - **Impact:** Enhances the profile update template by including the description field.

24. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Adds new routes to manage user levels.
    - **Description:** Introduces new endpoints for changing user levels.
    - **Impact:** Extends backend capabilities by allowing new level management routes.

These changes collectively enhance the system's manageability, robustness, and user experience, primarily by improving administrative control over user profiles and order application visibility.

---

# #154 Pull Request Overview

## Comprehensive Minification Configuration and Middleware Updates

## Introduction
This pull request brings significant enhancements to the application by optimizing resource handling through comprehensive minification configurations and middleware updates. The changes focus on the addition of a configuration file for handling various minification settings, updates to the controller and middleware to integrate these settings, and a corresponding update to the package dependencies. These improvements will enhance the application's efficiency by reducing resource size and potentially improving load times, thus providing a better user experience.

## Changes Overview
1. **File: `config/minify.php`**
- **Status:** Added
- **Changes:**
  - Added a new configuration file to manage blade view, asset, and HTML minification options.
  - Options include enabling minification, automatic semicolon insertion for CSS/JS, removal of HTML comments, JavaScript obfuscation, and directive replacements.
- **Description:** This file introduces fine-tuned control over the minification process, allowing developers to enable or disable various minification features easily and ensure certain routes or directives are handled appropriately.
- **Impact:** This change provides a centralized and extensive system to manage resource optimization, potentially improving the application's performance and load times, especially for users with slower network connections.

2. **File: `app/Http/Controllers/AdminController.php`**
- **Status:** Modified
- **Changes:**
  - Altered the `dashboard` method to exclude a specific range of user IDs (10000 to 10018) when counting total users.
- **Description:** This modification ensures that the user count excludes administrative or test accounts which fall between the given IDs, providing a more accurate count of regular users.
- **Impact:** The change improves the accuracy of user metrics displayed on the admin dashboard, which can influence administrative decisions and reporting.

3. **File: `app/Http/Kernel.php`**
- **Status:** Modified
- **Changes:**
  - Updated middleware array to replace `DipeshSukhia` package with `Fahlisaputra` middleware for minifying CSS, JavaScript, and Blade views.
- **Description:** This update shifts the application from the previously used HTML minification package to the new, possibly more robust `Fahlisaputra` minification middleware.
- **Impact:** The switch in minification middleware could bring improvements in how CSS, JavaScript, and Blade files are processed, potentially leading to enhanced performance. However, it might also require testing to ensure compatibility and functionality.

4. **File: `composer.json`**
- **Status:** Modified
- **Changes:**
  - Replaced the `dipeshsukhia/laravel-html-minify` package with `fahlisaputra/laravel-minify`.
- **Description:** Updates the project's dependencies to use the `fahlisaputra/laravel-minify` package, which is aligned with the new minification strategy defined in the updated config and middleware.
- **Impact:** This change ensures that the correct minification package is installed, removing reliance on the old package and thus avoiding potential conflicts. It also likely provides more comprehensive and secure minification features.

5. **File: `config/htmlminify.php`**
- **Status:** Removed
- **Changes:**
  - Completely removed the old configuration file for the `dipeshsukhia` minification package.
- **Description:** This deletion is part of the migration to the new `Fahlisaputra` minification middleware. By removing the old configuration, it streamlines the settings management to avoid confusion and redundancy.
- **Impact:** Cleans up obsolete configuration, reducing maintenance overhead and preventing misconfigurations. This helps ensure that the application is only using relevant and up-to-date configurations.

These updates collectively enhance the application's resource optimization strategy, leading to potential performance gains and a more efficient user experience.

---

# #153 Pull Request Summary

## Enhanced User Analytics and Frontend Refinements in Admin Dashboard

## Introduction
This pull request introduces significant changes aimed at enhancing user analytics and improving the frontend experience of the Admin Dashboard. Key updates include improved backend calculations for user statistics, finer control over HTML output, and the inclusion of essential libraries. The changes not only provide a clearer and more detailed view of user data but also refine the interface for better usability and performance.

## Changes Overview

1. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Added 20 lines of code, deleted 1 line.
   - **Description:** 
     - Enhanced the `dashboard` method to calculate and display daily and cumulative user registrations. The data is fetched and processed to exclude specific user IDs and grouped by date.
     - Introduced a total user count and cumulative user registration data to be passed to the view.
   - **Impact:**
     - Provides a more detailed and insightful user registration overview.
     - Allows for better decision-making based on user data trends.
     - Slightly increased the complexity of the controller logic.

2. **File: `config/htmlminify.php`**
   - **Status:** Modified
   - **Changes:** Modified 2 lines, added 2 lines.
   - **Description:** 
     - Updated the configuration to exclude all `admin.*` routes from HTML minification.
   - **Impact:**
     - Ensures that HTML minification does not affect admin routes, potentially preventing issues with rendering and debugging in the admin interface.

3. **File: `package.json`**
   - **Status:** Modified
   - **Changes:** Added 1 line.
   - **Description:** 
     - Added the `lodash` library version `^4.17.21` to dependencies.
   - **Impact:**
     - Allows the usage of the `lodash` library throughout the frontend, providing utility functions for common programming tasks.
     - Could slightly increase the application bundle size.

4. **File: `resources/views/admin/dashboard.blade.php`**
   - **Status:** Modified
   - **Changes:** Added 16 lines, deleted 89 lines.
   - **Description:** 
     - Simplified and redesigned the dashboard view to display total user count and a cumulative user registration chart.
     - Removed extensive HTML layout previously used for user statistics and replaced it with dynamic data rendering from the backend.
     - Incorporated JavaScript to dynamically generate charts with user data.
   - **Impact:**
     - Significantly improves the clarity and usefulness of the dashboard.
     - Reduces clutter on the dashboard view.
     - Ensures that the displayed data is dynamically generated and up-to-date.
     - Potentially better performance due to reduced static content.

By implementing these updates, the Admin Dashboard now offers improved data insights and enhanced frontend performance, providing a better user experience and more reliable data for administrative decision-making.

---

# #152 Headline

Addition and Update of Admin Views and Functionalities


## Introduction
This pull request includes significant updates to various components within the admin panel of the application. It introduces two new views for managing "bad words" and "emails," enhances existing functionalities, and refactors the admin interface to improve user experience and system consistency. The changes include new route definitions, controller actions, view templates, as well as modifications to existing JavaScript and CSS configurations.

## Changes Overview
1. **File: `resources/views/admin/badword/index.blade.php`**
- **Status:** Newly Added
- **Changes:** Added a new Blade template for managing bad words.
- **Description:** The file contains an interface for listing, adding, and deleting bad words. It includes markup for displaying a table of bad words with options to delete them and a modal form for adding new words.
- **Impact:** Adds a new feature for admin users to manage bad words used on the platform.

2. **File: `resources/views/admin/email/index.blade.php`**
- **Status:** Newly Added
- **Changes:** Added a new Blade template for managing emails.
- **Description:** This view includes a table listing emails along with their statuses, subjects, and creation dates. It facilitates email management within the application.
- **Impact:** Provides a new interface for admins to manage email statuses, improving administrative capabilities.

3. **File: `app/Http/Controllers/AdminController.php`**
- **Status:** Modified
- **Changes:** Added functions for managing bad words and emails, including listing, creating, and deleting bad words.
- **Description:** Extended the AdminController to include methods (`email_index`, `badword_index`, `badword_store`, `badword_delete`) to handle the new functionalities for bad words and email management.
- **Impact:** Enhances the application's backend to support the newly added admin functionalities.

4. **File: `package.json`**
- **Status:** Modified
- **Changes:** Added a new dependency `apexcharts`.
- **Description:** Includes `apexcharts` for data visualization purposes, which will assist in creating charts within the admin dashboard.
- **Impact:** Enhances data visualization capabilities in the admin panels, allowing more insightful data presentations.

5. **File: `resources/js/app.js`**
- **Status:** Modified
- **Changes:** Imports `apexcharts` and other necessary JavaScript dependencies.
- **Description:** This file now includes `ApexCharts` which is used for rendering data visualizations within the admin dashboard.
- **Impact:** Enables advanced chart visualizations in the admin dashboard, improving data presentation and analytics.

6. **File: `resources/lang/pt_br/admin.php`**
- **Status:** Modified
- **Changes:** Added translations for emails and bad words.
- **Description:** Provides the Portuguese translations for labels related to emails and bad words in the admin interface.
- **Impact:** Enhances the multilingual support of the application, making it more accessible to Portuguese-speaking users.

7. **File: `resources/views/admin/components/sidebar.blade.php`**
- **Status:** Modified
- **Changes:** Added links to the sidebar for accessing bad words and email management pages.
- **Description:** The sidebar now includes navigation links to the new admin views (`badword` and `email`).
- **Impact:** Improves navigation within the admin panel by making new features easily accessible.

8. **File: `resources/views/admin/dashboard.blade.php`**
- **Status:** Modified
- **Changes:** Enhanced the layout and added a data visualization section.
- **Description:** Updated dashboard to include a chart rendered by `ApexCharts`, and other UI enhancements.
- **Impact:** Provides a more interactive and data-driven dashboard for admins, facilitating better decision making.

9. **File: `resources/views/admin/user/index.blade.php`**
- **Status:** Modified
- **Changes:** Added new columns for user onboarding, reviews, and references.
- **Description:** The user management interface now shows additional information about user's onboarding status, reviews, and references.
- **Impact:** Offers more comprehensive insights into user data, aiding better user management and monitoring.

10. **File: `resources/views/layouts/admin.blade.php`**
- **Status:** Modified
- **Changes:** Refactored layout to include updated dependencies and better error handling.
- **Description:** The layout file was cleaned up, and the structure improved for better reusability and maintainability.
- **Impact:** Improves overall code quality and maintainability of the admin layout.

11. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** Added routes for managing bad words and emails.
- **Description:** Defined new routes to handle requests for managing bad words and emails in the admin panel.
- **Impact:** Integrates new functionality into the application's routing, allowing URLs to map to new admin actions.

12. **File: `tailwind.config.js`**
- **Status:** Modified
- **Changes:** Enabled charts feature in flowbite plugin.
- **Description:** Configured Tailwind CSS to include chart styles from `flowbite`.
- **Impact:** Adds necessary styles for data visualization components, ensuring consistent styling across the application.

13. **File: `resources/views/admin/blog/create.blade.php` (renamed)** 
- **Status:** Renamed
- **Changes:** Refactored Blade template for creating blog posts.
- **Description:** Improved structure and code cleanliness by migrating files under a unified directory structure for better organization.
- **Impact:** Enhances code maintainability and consistency.

14. **File: `resources/views/admin/blog/edit.blade.php` (renamed)**
- **Status:** Renamed
- **Changes:** Refactored Blade template for editing blog posts.
- **Description:** Improved directory structure and organization of files.
- **Impact:** Ensures structured and easy-to-navigate file system enhancing development efficiency.

15. **File: `resources/views/admin/blog/list.blade.php` (renamed)**
- **Status:** Renamed
- **Changes:** Refactored Blade template for listing blog posts.
- **Description:** Improved directory structure by moving files and updating namespace to follow the new convention.
- **Impact:** Improves maintainability and code readability.

16. **File: `resources/views/admin/faq/create.blade.php` (renamed, with changes)**
- **Status:** Renamed
- **Changes:** Refactored Blade template for creating FAQ posts and improved its layout.
- **Description:** Adjusted the code and enhanced styling for a consistent look and feel.
- **Impact:** Provides a better user experience for creating FAQ posts.

17. **File: `resources/views/admin/faq/edit.blade.php` (renamed, with changes)**
- **Status:** Renamed
- **Changes:** Refactored Blade template for editing FAQ posts.
- **Description:** Updated template structure and improved layout consistency.
- **Impact:** Simplifies editing FAQ posts with a more user-friendly interface.

18. **File: `resources/views/admin/faq/index.blade.php` (renamed, with changes)**
- **Status:** Renamed
- **Changes:** Refactored the FAQ index template.
- **Description:** Enhanced layout and improved the user interface for better navigation and usability.
- **Impact:** Simplifies managing FAQ posts and provides a more streamlined interface.

19. **Files: Removed several views in `resources/views/admin_old`**
- **Status:** Removed
- **Changes:** Removed outdated admin components and views.
- **Description:** These included old templates and components that have been refactored and migrated to new structured directories.
- **Impact:** Cleans up the codebase by removing obsolete and unused files, reducing clutter and potential confusion.

---

Overall, these changes introduce new functionalities for better managing content within the admin panel, enhance the user interface, and improve the performance and maintainability of the application.

---

# #151 Enhancements And Cleanup In Database Structure, Controllers, Middleware, and Views

## Introduction
This pull request focuses on the optimization and refinement of the project's database structure, controllers, middleware, and view files. Key changes include renaming and deleting certain database tables, modifying controller logic to remove redundant code, updating middleware to align with new data models, and enhancing UI components for better user experience. These changes collectively aim to streamline the code, reduce complexity, improve database management, and eliminate legacy code.

## Changes Overview
1. **File: `database/migrations/2024_06_29_102012_rename_and_delete_tables.php`**
   - **Status:** Added
   - **Changes:** Introduces a migration to rename `ceps`, `cnpjs`, and `cpfs` tables to `data_ceps`, `data_cnpjs`, and `data_cpfs`, respectively. Also deletes the `ceps_cities` and `ceps_states` tables.
   - **Description:** This change was made to standardize the table names for better clarity and organization. Deleting the `ceps_cities` and `ceps_states` tables was necessary as they are no longer in use.
   - **Impact:** Simplifies the database schema and removes unused tables, potentially improving query performance and maintainability.

2. **File: `database/migrations/2024_06_29_103557_update_user_data_and_delete_tables.php`**
   - **Status:** Added
   - **Changes:** Adds new columns `asaas_id` and `contaazul_id` to the `user_data` table and deletes the `design_views`, `user_conta_azuls`, and `user_asaas` tables.
   - **Description:** This change consolidates user-related data into a single table, making it easier to manage user information.
   - **Impact:** Reduces the number of database tables, thus simplifying data access and potentially improving performance.

3. **File: `app/Http/Controllers/OrderProcessController.php`**
   - **Status:** Modified
   - **Changes:** Removed the `change_view` function.
   - **Description:** The function was redundant following the removal of the `design_views` table.
   - **Impact:** Cleaner and more maintainable controller code with less obsolete logic.

4. **File: `app/Http/Controllers/ProductController.php`**
   - **Status:** Modified
   - **Changes:** Removed the `change_view` function.
   - **Description:** Similar to the `OrderProcessController`, this function became redundant and unnecessary.
   - **Impact:** Streamlined controller functionality.

5. **File: `app/Http/Controllers/WebhookController.php`**
   - **Status:** Modified
   - **Changes:** Updated references from `UserAsaas` to `UserData`.
   - **Description:** Aligns webhook processing with the new data model structure.
   - **Impact:** Ensures webhook functionality continues to operate correctly with the updated data model.

6. **File: `app/Http/Middleware/CheckUserAsaas.php`**
   - **Status:** Modified
   - **Changes:** Updated references from `UserAsaas` to `UserData`.
   - **Description:** Necessary updates to maintain middleware functionality.
   - **Impact:** Middleware will properly reference the new data structure.

7. **File: `app/Livewire/Admin/FormAddLead.php`**
   - **Status:** Modified
   - **Changes:** Updated references from `Ceps` to `DataCep`.
   - **Description:** Reflects the updated table and class names.
   - **Impact:** Ensures data fetching and manipulation align with the renamed model.

8. **File: `app/Livewire/Business/CheckoutForm.php`**
   - **Status:** Modified
   - **Changes:** Updated references from `Ceps` to `DataCep`.
   - **Description:** Keeps consistency with the new naming conventions.
   - **Impact:** Maintains functionality for the checkout process with the updated model.

9. **File: `app/Livewire/OnboardingForm.php`**
   - **Status:** Modified
   - **Changes:** Updated references from `Ceps`, `Cpf`, and `Cnpj` to `DataCep`, `DataCpf`, and `DataCnpj`.
   - **Description:** Ensures the onboarding process works with the revised models.
   - **Impact:** Smooth onboarding process using the newly named data structures.

10. **File: `app/Livewire/UpdateCreatorContactForm.php`**
    - **Status:** Modified
    - **Changes:** Updated references from `Ceps` to `DataCep`.
    - **Description:** Aligns contact form logic with the updated data model.
    - **Impact:** Correct data handling in the contact update form.

11. **File: `app/Models/User.php`**
    - **Status:** Modified
    - **Changes:** Removed relationships for `DesignView`, `UserContaAzul`, and `UserAsaas`.
    - **Description:** Since these models and tables are removed, their relationships were no longer needed.
    - **Impact:** Simplifies the User model.

12. **File: `app/Models/UserData.php`**
    - **Status:** Modified
    - **Changes:** Added `asaas_id` and `contaazul_id` attributes to the fillable list.
    - **Description:** Supports the newly added fields in the migration.
    - **Impact:** Allows mass assignment for the new fields in `UserData`.

13. **File: `app/Services/PaymentService.php`**
    - **Status:** Modified
    - **Changes:** Updated references from `UserAsaas` to `UserData`.
    - **Description:** Ensures the payment service aligns with the new data model.
    - **Impact:** Seamless processing of payments with updated references.

14. **File: `resources/lang/pt_br/dashboard.php`**
    - **Status:** Modified
    - **Changes:** Small language text update.
    - **Description:** Refined a message for better clarity.
    - **Impact:** Improved user experience through clearer messaging.

15. **File: `resources/views/admin/user/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Enhanced layout and added new information columns.
    - **Description:** Improved UI for the admin user index.
    - **Impact:** More comprehensive and user-friendly admin interface.

16. **File: `resources/views/dashboard/business/order/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Removed redundant view type switching code.
    - **Description:** Cleans up view logic.
    - **Impact:** Streamlined view without unnecessary components.

17. **File: `resources/views/dashboard/business/product/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Removed redundant view type switching code.
    - **Description:** Simplifies the product index view.
    - **Impact:** Cleaner component with reduced complexity.

18. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Removed routes related to view switching.
    - **Description:** Since view switching is deprecated, these routes were removed.
    - **Impact:** Cleaner routing file, reducing unnecessary routes.

19. **File: `app/Models/DataCep.php`**
    - **Status:** Renamed
    - **Changes:** Class name and table reference updated from `Ceps` to `DataCep`.
    - **Description:** Reflects the renaming in the migration.
    - **Impact:** Ensures model consistency with database schema.

20. **File: `app/Models/DataCnpj.php`**
    - **Status:** Renamed
    - **Changes:** Class name and table reference updated from `Cnpj` to `DataCnpj`.
    - **Description:** Completes the renaming process.
    - **Impact:** Consistent with the new database naming convention.

21. **File: `app/Models/DataCpf.php`**
    - **Status:** Renamed
    - **Changes:** Class name and table reference updated from `Cpf` to `DataCpf`.
    - **Description:** Finalizes the renaming to align with new standards.
    - **Impact:** Consistency across the application.

22. **File: `app/Models/DesignView.php`**
    - **Status:** Deleted
    - **Changes:** Removed entire file.
    - **Description:** The model is no longer required.
    - **Impact:** Reduces codebase bloat by removing unused models.

23. **File: `app/Models/UserAsaas.php`**
    - **Status:** Deleted
    - **Changes:** Removed entire file.
    - **Description:** Consolidated into `UserData`.
    - **Impact:** Simplifies data management by using a consolidated model.

24. **File: `app/Models/UserContaAzul.php`**
    - **Status:** Deleted
    - **Changes:** Removed entire file.
    - **Description:** Integrated fields into `UserData`.
    - **Impact:** Streamlined user-related data models.

25. **File: `app/Rules/ASAASRule.php`**
    - **Status:** Deleted
    - **Changes:** Removed entire file.
    - **Description:** No longer needed following model consolidation.
    - **Impact:** Cleans up unnecessary validation rules.

26. **File: `app/Rules/CONTAAZULRule.php`**
    - **Status:** Deleted
    - **Changes:** Removed entire file.
    - **Description:** Deprecated by model updates.
    - **Impact:** Reduces redundant code.

27. **File: `resources/views/components/button-view-type.blade.php`**
    - **Status:** Deleted
    - **Changes:** Removed entire file.
    - **Description:** No longer needed due to removal of view switching functionality.
    - **Impact:** Streamlined view components.

28. **File: `resources/views/dashboard/onboarding_old.blade.php`**
    - **Status:** Deleted
    - **Changes:** Removed entire file.
    - **Description:** An out-of-date onboarding component.
    - **Impact:** Reduces legacy code and potential confusion.

---

# #150 Summary of GitHub Pull Request

## Introduction
This pull request introduces several updates aimed at enhancing the functionality, user experience, and validation mechanisms within the application. These changes span across multiple files, primarily focusing on improving form validation, accommodating user input persistence, and enforcing specific requirement checks. The updates also ensure that critical fields are properly validated before data submission, which enhances both security and usability.

## Changes Overview

1. **File: `app/Livewire/OnboardingForm.php`**
   - **Status:** Modified
   - **Changes:** Reorganized validation checks for `cpf_cnpj_value`, added error setting for a missing profile photo, and enforced social media fields validation.
   - **Description:** 
     - Moved the `cpf_cnpj_value` validation to ensure errors are set before further checks.
     - Added conditions to check if a profile photo is missing, setting an appropriate error.
     - Included logic to ensure at least one social media field is filled out before updating personal details.
   - **Impact:** Enhances form reliability and user guidance by providing immediate feedback on required fields, thereby reducing the chances of incomplete or incorrect data submissions.

2. **File: `resources/lang/pt_br/profile.php`**
   - **Status:** Modified
   - **Changes:** Added a new language string for social media validation.
   - **Description:** Introduced the string `'min_one_required' => 'Pelo menos uma rede social deve ser informada.'` to accommodate the new validation rule.
   - **Impact:** Supports the new social media validation logic by providing user-friendly error messages in Portuguese, aiding non-English speaking users.

3. **File: `resources/views/auth/register.blade.php`**
   - **Status:** Modified
   - **Changes:** Ensured the persistence of old input values in the registration form and set the terms checkbox as required.
   - **Description:** 
     - Updated the inputs to retain values entered by users if the form submission fails and reloads.
     - Added the `required` attribute to the terms and policies agreement checkbox.
   - **Impact:** Improves the user experience by preventing loss of entered data on form reload and ensures compliance by making the terms agreement checkbox mandatory.

4. **File: `resources/views/livewire/onboarding-form.blade.php`**
   - **Status:** Modified
   - **Changes:** Removed the `required` attribute from the `apto` input, and added a section for displaying custom error messages for social media fields.
   - **Description:** 
     - The `apto` input (apartment field) is no longer mandatory.
     - Introduced an error display for social media validation, ensuring users are informed if no social media handle is provided.
   - **Impact:** Allows more flexibility for users without apartment details and enhances validation clarity for social media linkage requirements.

5. **File: `resources/views/livewire/onboarding_list.blade.php`**
   - **Status:** Modified
   - **Changes:** Streamlined the conditional check for user address details.
   - **Description:** Removed the check for `apto` (apartment) from the conditional statement that determines marking completion status.
   - **Impact:** Adjusts the completeness criteria for user address details, allowing users without apartment information to pass the check, thereby preventing unnecessary hindrances in the onboarding process.

These revisions collectively enhance the robustness and user-friendliness of the forms within the application, ensuring better data handling and user satisfaction.

---

# #149 Integration of Social Media Conversion API Services

## Introduction
This pull request introduces significant changes centered on the integration of the Conversion APIs for Facebook and TikTok into our application. These changes include a new middleware to send event data to social media platforms and updates to existing controllers and services to enhance data tracking and event reporting capabilities.

Main areas of changes include:
- New middleware for sending view content events to social media.
- Modification of controllers to support additional conversion tracking.
- Updates to service classes for better data handling and event submission.
- Clean-up and removal of redundant listener classes.

## Changes Overview

1. **File: `app/Http/Middleware/SendViewContentToSocialMedia.php`**
- **Status:** New
- **Changes:** Added a middleware to capture view content events and send them to Facebook and TikTok.
- **Description:** This middleware intercepts requests to specific routes, collects user data, sanitizes it, and sends event data to Facebook and TikTok Conversion APIs.
- **Impact:** Ensures that relevant user interactions are tracked and reported to social media platforms for analytics and marketing purposes.

2. **File: `app/Http/Controllers/PublicPagesController.php`**
- **Status:** Modified
- **Changes:** Added support for TikTok Conversion API; updated event data sent to Facebook.
- **Description:** Enhancements were made to better handle contact form submissions by sending data to both Facebook and TikTok for conversion tracking.
- **Impact:** Improved tracking of contact form submissions, offering a more comprehensive view of user engagements across platforms.

3. **File: `app/Http/Kernel.php`**
- **Status:** Modified
- **Changes:** Inclusion of the newly created `SendViewContentToSocialMedia` middleware in the global middleware stack.
- **Description:** Ensures that the new middleware is executed for incoming requests, facilitating the transmission of view content events.
- **Impact:** Seamlessly integrates social media event tracking across all relevant user interactions within the application.

4. **File: `app/Listeners/SendRegistrationToFacebook.php`**
- **Status:** Modified
- **Changes:** Refactored to remove redundant code for handling Facebook click and pixel ID cookies.
- **Description:** This refactor simplifies the listener logic, now leveraging the `FacebookConversionApiService` for these details directly.
- **Impact:** Streamlines the registration event handling, reducing potential points of failure and maintenance overhead.

5. **File: `app/Listeners/SendRegistrationToTikTok.php`**
- **Status:** Modified
- **Changes:** Minor formatting adjustments.
- **Description:** Small syntactical changes for consistency and readability.
- **Impact:** Ensures code consistency and maintainability without altering the core functionality.

6. **File: `app/Services/FacebookConversionApiService.php`**
- **Status:** Modified
- **Changes:** Added collection and inclusion of additional user data in the event payload.
- **Description:** Enhanced to include client IP address, user agent, and cookies `_fbc` and `_fbp` in the payload sent to Facebook.
- **Impact:** Provides more detailed and accurate user event data, which can improve the effectiveness of conversion tracking and analytics.

7. **File: `app/Services/TikTokConversionApiService.php`**
- **Status:** Modified
- **Changes:** Slight adjustment to event data formatting.
- **Description:** Small refinements to ensure event data conforms to expected structure.
- **Impact:** Enhances reliability of data sent to TikTok, ensuring adherence to expected API formats.

8. **File: `app/Listeners/SendViewContentToTikTok.php`**
- **Status:** Removed
- **Changes:** Deleted the redundant listener that handled view content events for TikTok.
- **Description:** With the introduction of the new middleware, this listener became obsolete and was removed.
- **Impact:** Simplifies the codebase by removing unnecessary components, reducing maintenance efforts, and potential for confusion.

These changes collectively enhance the application's capability to track and report user interactions to both Facebook and TikTok, providing valuable insights for marketing and analytics purposes. The introduction of the new middleware and enhancements to existing services and controllers ensure that user data is accurately captured and transmitted efficiently, improving both functionality and maintainability.

---

# #148 Implementing Database-Backed Bad Words Filtering

## Introduction
This pull request introduces a significant enhancement in the handling of inappropriate language within user messages by leveraging a new database-backed approach for bad words filtering. Specifically, it involves the addition of a new data model, a corresponding migration file, modifications to the message filtering service, and adjustments to the application middleware. These changes aim to create a more scalable and maintainable approach to filtering bad words. This implementation improves upon the previous hardcoded method by facilitating easier updates and expansions of the bad words list without altering the application's core code.

## Changes Overview
1. **File: `app/Models/DataBadWords.php`**
- **Status:** Added
- **Changes:** This file introduces a new Eloquent model named `DataBadWords`.
- **Description:** The `DataBadWords` model represents the `data_bad_words` table and includes the necessary configurations to map the `word` field as fillable. This model serves as the interface for querying and interacting with the bad words stored in the database.
- **Impact:** This change modularizes the bad words handling logic, allowing the application to dynamically fetch bad words from the database instead of using a hardcoded list.

2. **File: `database/migrations/2024_06_26_221829_create_data_bad_words_table.php`**
- **Status:** Added
- **Changes:** This migration file defines the structure of the `data_bad_words` table and seeds it with an initial list of bad words.
- **Description:** The `up` method creates a new table with columns `id`, `word` (which is set to be unique), and timestamps. It also inserts an initial set of bad words into the table. The `down` method drops the table if it exists.
- **Impact:** This provides the database schema and seed data necessary for the new dynamic bad words filtering mechanism, ensuring data persistence and easy updates of the bad words list.

3. **File: `app/Http/Kernel.php`**
- **Status:** Modified
- **Changes:** Adjusted the placement of the `TrackUserSource` middleware in the middleware stack.
- **Description:** The `TrackUserSource` middleware was removed from one stack and added to another, possibly for execution order optimization or context-specific reasons.
- **Impact:** While this change appears to be minor, it might have implications on how user tracking data is processed. It ensures that tracking operations occur in the appropriate middleware context.

4. **File: `app/Services/MessageFilterService.php`**
- **Status:** Modified
- **Changes:** Refactored to load bad words from the database using the new `DataBadWords` model instead of using a hardcoded array.
- **Description:** The constructor method now pulls the bad words from the `data_bad_words` table and populates the `$badWords` property. The rest of the filtering logic remains the same, replacing bad words, email addresses, and phone numbers in messages with asterisks.
- **Impact:** This update significantly enhances the flexibility and maintainability of the message filtering functionality. It ensures that updates to the bad words list can be made via database operations without requiring code modifications or redeployments.

These changes collectively transition the application to a more efficient, scalable, and maintainable approach for filtering inappropriate language, improving both the developer and user experience.

---

# #147 New Middleware to Track User Source and Database Enhancement

## Introduction
This pull request introduces significant updates aimed at enhancing user tracking and database infrastructure. A new middleware has been added to track the source of user traffic, which includes updates to the database schema and the user creation process. These changes will provide better insights into user acquisition sources, potentially aiding marketing and data analysis efforts. The main areas of change include:
- Addition of a new middleware for tracking user source.
- Modification of database schema to store user source data.
- Alterations to user creation logic to include the newly captured user source data.
- Inclusion of the new middleware in the application kernel for activation.

## Changes Overview
1. **File: `app/Http/Middleware/TrackUserSource.php`**
- **Status:** Added
- **Changes:** Entirely new file introduced with 43 lines of code.
- **Description:** This middleware checks the incoming request for query parameters (`partner`, `campaign`, or `utm_source`) or the referrer header to determine the source of the user. The identified source is then stored in the session under the key `user_source`. The middleware ensures it captures this data as early as possible in the request lifecycle.
- **Impact:** This change will enable the application to track the origins of its users more accurately, assisting in analytics and marketing efforts. It may, however, slightly increase the overhead in processing each request.

2. **File: `database/migrations/2024_06_26_215220_add_source_to_user_data_table.php`**
- **Status:** Added
- **Changes:** Adds a new column named `source` to the `user_data` table.
- **Description:** The migration script updates the `user_data` table to include a nullable `source` column after the `linkedin` field. It includes methods for both applying and reversing the migration.
- **Impact:** Modifying the schema to include user source data ensures that the information captured by the new middleware is persisted, allowing for future retrieval and analysis. This will have a direct benefit in understanding user acquisition but requires careful execution in production to avoid downtime or data issues.

3. **File: `app/Actions/Fortify/CreateNewUser.php`**
- **Status:** Modified
- **Changes:** Removed unused imports and added a single line to include the `source` field in the `UserData` creation array.
- **Description:** The changes streamline the user creation process by removing unnecessary dependencies (`GuzzleHttp\Client`, `GuzzleHttp\Exception\GuzzleException`, `Illuminate\Support\Facades\Log`) and ensure the user source, now tracked by the new middleware, is saved in the `user_data` table upon user creation.
- **Impact:** By including the source information in the user data at the time of account creation, the system ensures that valuable marketing information is recorded right from the start. Simplifying the imports also reduces potential points of failure and improves maintainability.

4. **File: `app/Http/Kernel.php`**
- **Status:** Modified
- **Changes:** Includes the newly created `TrackUserSource` middleware in the application’s global HTTP middleware stack.
- **Description:** Adds the `TrackUserSource` middleware to the list of middleware that the application runs on every request, ensuring that every incoming request passes through this new tracking mechanism.
- **Impact:** This ensures that the new tracking logic is applied globally across the application, providing comprehensive coverage. While it may slightly increase the request processing time, its placement in the global middleware stack ensures that it captures all potential user source data effectively.

This comprehensive set of changes collectively enhances the tracking and storage of user source data, providing valuable insights for marketing and user engagement strategies.

---

# #146 Addition of advertising pricing in orders and various improvements across system functionalities

## Introduction
This pull request introduces several significant changes and improvements across the codebase, targeting various aspects of the system functionalities. It primarily focuses on adding a new feature for advertising options in orders, enhancing security and logging mechanisms, and refining user interface elements and processes for better user experience. These changes are poised to improve the efficiency, usability, and scalability of the application.

## Changes Overview

1. **File: `database/migrations/2024_06_26_165303_add_ads_to_orders_table.php`**
    - **Status:** Added
    - **Changes:** A new migration file adding an `ads` column to the `orders` table.
    - **Description:** Introduces an integer column `ads` with a default value of 0, allowing for orders to include advertising options.
    - **Impact:** Enables the storage and management of advertising options associated with orders in the database.

2. **File: `app/Console/Commands/CreatorCheckWalletTransaction.php`**
    - **Status:** Modified
    - **Changes:** Adds logging functionality in place of error message output.
    - **Description:** Enhances existing command by logging errors when the transaction amount is greater than the balance pending, improving the system's error tracking and diagnosis capabilities.
    - **Impact:** Improved error logging for better monitoring and debugging.

3. **File: `app/Http/Controllers/OrderProcessController.php`**
    - **Status:** Modified
    - **Changes:** Added filtering of order status and integration of new advertising pricing logic in the order processing.
    - **Description:** Orders with a status of `CANCELADO` are excluded from the order list, and new ad pricing functionalities are incorporated during the order processing.
    - **Impact:** Enhanced order management and new ad pricing feature integration, improving the user’s ability to process and manage orders dynamically.

4. **File: `app/Http/Controllers/PublicPagesController.php`**
    - **Status:** Modified
    - **Changes:** Refactored to use a configuration-based approach for pricing plans instead of hardcoded values.
    - **Description:** Pricing plans are dynamically generated from a configuration file, improving flexibility in managing and updating pricing plans.
    - **Impact:** Simplifies modifications to pricing plans, allowing for easier updates and management.

5. **File: `app/Http/Controllers/WebhookController.php`**
    - **Status:** Modified
    - **Changes:** Added handling for the `PAYMENT_DELETED` event.
    - **Description:** Adds logic to handle payment deletion via webhooks, ensuring order status updates in response to such events.
    - **Impact:** Enhances webhook functionality to cover more payment-related events, keeping order statuses accurate and up-to-date.

6. **File: `app/Http/Middleware/CheckOrderCobrancaStatus.php`**
    - **Status:** Modified
    - **Changes:** Redirects based on additional order statuses (`DELETED`, `REFUNDED`, `CHARGEBACK`).
    - **Description:** Extends middleware to handle additional order statuses, improving response to different payment situations.
    - **Impact:** Improved handling of order statuses, enhancing user navigation and order status management.

7. **File: `app/Http/Middleware/CheckUserAsaas.php`**
    - **Status:** Modified
    - **Changes:** Adjustments in fetching user details for request body.
    - **Description:** Consolidates user data fetching to improve consistency and accuracy in data handling for Asaas user checks.
    - **Impact:** Increased data consistency and reduced potential for errors in user data checks.

8. **File: `app/Livewire/Business/OrderProcess.php`**
    - **Status:** Modified
    - **Changes:** Addition of advertising selection logic and pricing computation.
    - **Description:** Implements logic to handle ad selections within the order process, dynamically updating pricing based on selected ad options.
    - **Impact:** Enables dynamic updating of order details and pricing based on user selections, enhancing the order customization capabilities.

9. **File: `app/Models/Order.php`**
    - **Status:** Modified
    - **Changes:** Addition of `ads` to the fillable properties.
    - **Description:** Allows the `ads` attribute to be mass-assignable, facilitating easier updates and management of this attribute in the order model.
    - **Impact:** Simplifies updating the `ads` attribute, enhancing flexibility in order management.

10. **File: `config/app_custom.php`**
    - **Status:** Modified
    - **Changes:** Addition of `ads_pricing` configuration and updates to existing pricing configurations.
    - **Description:** Introduces configuration settings for advertising pricing and adjusts video pricing for various durations.
    - **Impact:** Enhanced pricing configuration management, enabling easier updates and additions of new pricing tiers and options.

11. **File: `resources/lang/pt_br/dashboard.php`**
    - **Status:** Modified
    - **Changes:** Added translation keys for new advertising related texts.
    - **Description:** Expanding language translations to support newly introduced advertising options.
    - **Impact:** Ensures new features are available and understandable in multiple languages, improving the user experience for non-English speakers.

12. **File: `resources/lang/pt_br/general.php`**
    - **Status:** Modified
    - **Changes:** Added and updated translation keys for various texts, especially related to pricing.
    - **Description:** Updates translations for more accurate and comprehensive language support for pricing plans and descriptions.
    - **Impact:** Better user communication and understanding through improved and complete translations.

13. **File: `resources/views/admin/user/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Added new display logic for user creator details.
    - **Description:** Adds visual indicators for user’s creator details readiness, improving UX for admin users.
    - **Impact:** Improved admin visibility on user details, aiding in better user management.

14. **File: `resources/views/components/pricing/pricing-child.blade.php`**
    - **Status:** Modified
    - **Changes:** Updates price formatting to ensure consistency.
    - **Description:** Ensures that all pricing values are displayed with consistent formatting.
    - **Impact:** Enhanced clarity and professionalism in price presentation.

15. **File: `resources/views/components/pricing/pricing-parent.blade.php`**
    - **Status:** Modified
    - **Changes:** Updates price formatting to ensure consistency.
    - **Description:** Ensures that all pricing values are displayed with consistent formatting.
    - **Impact:** Enhanced clarity and professionalism in price presentation.

16. **File: `resources/views/contact.blade.php`**
    - **Status:** Modified
    - **Changes:** Refines input and select elements within the contact form.
    - **Description:** Improves styling and user interaction with form fields, contributing to a better user experience.
    - **Impact:** Improved usability and aesthetic consistency of the contact form.

17. **File: `resources/views/dashboard/business/order/applications.blade.php`**
    - **Status:** Modified
    - **Changes:** Updates references to user data attributes.
    - **Description:** Ensures correct rendering of user data by fetching details from the correct attribute source.
    - **Impact:** Accurate display of user details, enhancing reliability of user information.

18. **File: `resources/views/dashboard/business/order/checkout.blade.php`**
    - **Status:** Modified
    - **Changes:** Addition of ad price display and improved counter logic for payment status checks.
    - **Description:** Displays pricing for ads if included in the order and improves the countdown timer for payment status verification.
    - **Impact:** Users have better visibility on order costs and improved feedback during payment processes.

19. **File: `resources/views/dashboard/business/order/livewire/process.blade.php`**
    - **Status:** Modified
    - **Changes:** Integrates advertising options into the order process interface.
    - **Description:** Visual components added for selecting and displaying advertising options during the order process.
    - **Impact:** Increased functionality and options available to users during order creation.

20. **File: `resources/views/dashboard/business/order/process.blade.php`**
    - **Status:** Modified
    - **Changes:** Passing ads data to the view.
    - **Description:** Ensures that ad options are available in the view for processing orders.
    - **Impact:** Facilitates the inclusion of ads in the order processing workflow.

21. **File: `resources/views/dashboard/components/header.blade.php`**
    - **Status:** Modified
    - **Changes:** Adjusts z-index property for better layering of header elements.
    - **Description:** Ensures header elements stack correctly in the visual hierarchy, preventing overlap issues.
    - **Impact:** Improved interface consistency and functionality.

22. **File: `resources/views/prices.blade.php`**
    - **Status:** Modified
    - **Changes:** Integrates new enterprise pricing plan and adjusts existing pricing plan layouts.
    - **Description:** Introduces a new enterprise pricing model, offering tailored solutions for larger customers.
    - **Impact:** Broadens the range of available pricing plans, catering to a wider audience.

23. **File: `app/Console/Commands/_OLD/UpdateUserDataOnboarding.php`**
    - **Status:** Renamed
    - **Changes:** Renames the file to indicate deprecation or historical reference.
    - **Description:** Marks this command as deprecated or retained for historical context, indicating it’s no longer actively used.
    - **Impact:** Clarifies codebase structure by distinguishing outdated commands.

---

# #145 Integrating GitHub Pull Request Automation and Minor Adjustments

## Introduction
This pull request introduces a new feature that automates the handling of GitHub pull requests that contain the term "wtd" in their body. The feature utilizes the OpenAI API to process these requests and update their content accordingly. In addition to this major enhancement, a few general improvements and modifications have been made across different parts of the application. This change primarily affects the application's internal processing and automation capabilities, with potential enhancements to user experience by ensuring pull request reviews are more informative and automated.

## Changes Overview
1. **File: `app/Console/Commands/GithubWTD.php`**
- **Status:** Added
- **Changes:** Added a new console command `GithubWTD`.
- **Description:** 
  - The new command checks for new GitHub pull requests with the body "wtd".
  - It fetches files from these pull requests, processes them through the OpenAI API, and updates the pull request body and `version.md` file with the response.
  - Includes handling of API interactions with GitHub and OpenAI, error logging, and processing logic to filter and sort files.
- **Impact:** 
  - Introduces an automated process for handling specific pull requests, reducing manual effort.
  - Ensures more consistent and detailed pull request descriptions.

2. **File: `app/Console/Commands/UserSendmail.php`**
- **Status:** Modified
- **Changes:** Updated the command description.
- **Description:** The command description was changed from a placeholder to a meaningful description: 'Send user emails.'
- **Impact:** 
  - Improves code clarity and documentation.
  - No functional impact on the system.

3. **File: `app/Console/Kernel.php`**
- **Status:** Modified
- **Changes:** Added scheduling for the new `github:what-the-difference` command.
- **Description:** 
  - Schedules the command to run every five minutes in the production environment.
  - Ensures regular execution to check for new pull requests.
- **Impact:** 
  - Enables automated and periodic execution of the new feature, ensuring timely updates to relevant pull requests.

4. **File: `app/Http/Controllers/WebhookController.php`**
- **Status:** Modified
- **Changes:** Added new imports and a new method for handling GitHub webhooks.
- **Description:** 
  - New method `github_webhook` handles incoming webhooks from GitHub and stores them in the database.
  - New imports to support HTTP client and logging functionalities.
- **Impact:** 
  - Adds the capability to handle GitHub webhook events, integrating them into the existing webhook processing system.
  - Ensures the new feature can capture and store the necessary data for further processing.

5. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** Added a route for GitHub webhook events.
- **Description:** 
  - New route `post('/webhook/github/events', [WebhookController::class, 'github_webhook'])` added.
  - Enables the application to receive and route GitHub webhook events to the appropriate controller method.
- **Impact:** 
  - Facilitates the integration of GitHub webhook events into the application.
  - Ensures proper routing and handling of push events needed for the new feature to operate correctly.

---

# #144 New Feature Addition and UI/UX Enhancements
  
## Introduction
This pull request introduces several new features and enhancements to the application's user interface and experience. The changes include adding new Blade templates for components, modifying existing views, updating configuration files, and improving CSS styling. These updates enhance the application's functionality, user experience, and visual consistency. The main areas of change are:

- New feature additions
- UI/UX enhancements
- Configuration updates

## Changes Overview
1. **File: `resources/views/components/button-view-type.blade.php`**
- **Status:** Added
- **Changes:** Added a new component that creates UI elements (buttons) to toggle between different view types (Table View and Grid View).
- **Description:** This new component allows users to switch between different viewing modes for displaying contents.
- **Impact:** Improves user experience by providing flexible view options.

2. **File: `resources/views/components/input-radio.blade.php`**
- **Status:** Added
- **Changes:** Added a new Blade component for rendering input radio buttons with specific styling.
- **Description:** This component streamlines the creation of styled radio buttons.
- **Impact:** Enhances consistency and reusability in UI elements.

3. **File: `config/app_custom.php`**
- **Status:** Modified
- **Changes:** Added configurations for social media URLs and removed unnecessary spaces.
- **Description:** The configuration updates include URLs for official social media accounts.
- **Impact:** Provides centralized management of social media links, ensuring easy updates and consistency.

4. **File: `resources/css/app.css`**
- **Status:** Modified
- **Changes:** Added utility classes to improve element styling, such as transition effects for buttons and tracking-wide for text.
- **Description:** Enhancements in CSS provide a more visually appealing and responsive design.
- **Impact:** Improves the visual consistency and performance of UI components across the application.

5. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** Updated translations for personal and address details.
- **Description:** Adjusted the terms to match the correct context in the dashboard interface.
- **Impact:** Increases clarity and accuracy of the translated user interface.

6. **File: `resources/lang/pt_br/profile.php`**
- **Status:** Modified
- **Changes:** Removed redundant text from contact subtitles.
- **Description:** Simplifies the contact section text.
- **Impact:** Enhances readability and conciseness in the user profile section.

7. **File: `resources/views/components/alert.blade.php`**
- **Status:** Modified
- **Changes:** Simplified the structure for including icons within alerts.
- **Description:** Removed nested `<div>` tags to streamline the code.
- **Impact:** Makes the alert component cleaner and easier to maintain.

8. **File: `resources/views/components/connected-account.blade.php`**
- **Status:** Modified
- **Changes:** Added a `max-w-lg` class to the outer `<div>` container.
- **Description:** Limits the maximum width of the connected account component.
- **Impact:** Ensures responsive design and appropriate scaling on larger screens.

9. **File: `resources/views/components/dialog-modal.blade.php`**
- **Status:** Modified
- **Changes:** Added dark mode styles for text and backgrounds.
- **Description:** Enhances the dialog modal's appearance in dark mode.
- **Impact:** Provides better visual consistency across light and dark themes.

10. **File: `resources/views/components/feedback.blade.php`**
- **Status:** Modified
- **Changes:** Overhauled the feedback form structure and styles.
- **Description:** Redesigned the feedback form for improved usability and visual appeal.
- **Impact:** Makes feedback submission easier and more intuitive for users.

11. **File: `resources/views/components/footer-homepage.blade.php`**
- **Status:** Modified
- **Changes:** Updated footer links and added social media icons.
- **Description:** Enhanced the footer with social media links, ensuring they use centralized configs.
- **Impact:** Ensures that the footer is informative and up-to-date with social media presence.

12. **File: `resources/views/components/menu-homepage.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted the gap size for the navbar menu items in large screens.
- **Description:** Ensures the menu items have appropriate spacing on larger screens.
- **Impact:** Enhances the menu's appearance and usability on larger displays.

13. **File: `resources/views/components/modal.blade.php`**
- **Status:** Modified
- **Changes:** Added dark mode styles for modal backgrounds.
- **Description:** Modifies the modal to support both light and dark themes.
- **Impact:** Ensures the modal displays consistently across different themes.

14. **File: `resources/views/components/secondary-button.blade.php`**
- **Status:** Modified
- **Changes:** Updated button styles for a more modern look.
- **Description:** Improved button styling to be more visually appealing and consistent.
- **Impact:** Enhances the user interface with updated and consistent button styles.

15. **File: `resources/views/components/section-title.blade.php`**
- **Status:** Modified
- **Changes:** Added a `text-pretty` class to section descriptions.
- **Description:** Updates styling for section titles, ensuring consistent typography.
- **Impact:** Improves readability and visual appeal of section titles.

16. **File: `resources/views/dashboard/business/dashboard.blade.php`**
- **Status:** Modified
- **Changes:** Various content and style updates to the business dashboard view.
- **Description:** Adjusted elements such as grid layouts, image handling, and order details.
- **Impact:** Provides a better-organized and visually appealing business dashboard.

17. **File: `resources/views/dashboard/business/order/applications.blade.php`**
- **Status:** Modified
- **Changes:** Refined the structure and styles for the order applications view.
- **Description:** Enhanced the order applications page with better alignment and component usage.
- **Impact:** Improves usability and consistency for users managing order applications.

18. **File: `resources/views/dashboard/business/order/checkout.blade.php`**
- **Status:** Modified
- **Changes:** Improved the styling and layout for the checkout page.
- **Description:** Ensured the checkout process is clear and visually appealing.
- **Impact:** Enhances the user experience during the checkout process.

19. **File: `resources/views/dashboard/business/order/index.blade.php`**
- **Status:** Modified
- **Changes:** Reorganized the order index view to better accommodate both table and grid views.
- **Description:** Updated the view toggle and overall layout for better user interaction.
- **Impact:** Provides users with flexible viewing options and a more organized display of orders.

20. **File: `resources/views/dashboard/business/order/livewire/process.blade.php`**
- **Status:** Modified
- **Changes:** Updated button styles within the process view.
- **Description:** Ensures buttons have consistent styling and improved accessibility.
- **Impact:** Enhances the visual consistency of interactive elements.

21. **File: `resources/views/dashboard/business/order/select_product.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted styles for the product selection view.
- **Description:** Ensures products are displayed consistently, with updated typography and layout.
- **Impact:** Improves the visual organization of product selection.

22. **File: `resources/views/dashboard/business/product/create.blade.php`**
- **Status:** Modified
- **Changes:** Enhanced the product creation form's structure and styling.
- **Description:** Improved inputs, labels, and section organization for better usability.
- **Impact:** Increases clarity and ease of use for product creation.

23. **File: `resources/views/dashboard/business/product/edit.blade.php`**
- **Status:** Modified
- **Changes:** Updated the product editing form to match the new creation form styles.
- **Description:** Ensures consistency between product creation and editing interfaces.
- **Impact:** Provides a seamless editing experience for users.

24. **File: `resources/views/dashboard/business/product/index.blade.php`**
- **Status:** Modified
- **Changes:** Reorganized and restyled the product index view for clarity.
- **Description:** Included a toggle for different view types (table and grid).
- **Impact:** Offers users flexible viewing options and a cleaner organization of products.

25. **File: `resources/views/dashboard/components/footer.blade.php`**
- **Status:** Modified
- **Changes:** Enhanced the footer with new styles and social media links.
- **Description:** Updated the footer to include icons for social media and centralized configuration usage.
- **Impact:** Ensures the footer is informative, modern, and easy to update.

---

# #143 Pull Request Overview: Enhanced User Onboarding and Simplified Middleware

## Introduction
This pull request introduces several substantial changes aimed at improving the user onboarding process and simplifying middleware and model structures. Key areas of enhancement include:

1. **New Features**: Introduction of new onboarding commands and middleware checks.
2. **Code Optimization**: Consolidation of user-related data models, removal of redundant middleware, and streamlining of user creation logic.
3. **User Experience Improvements**: Enhanced onboarding steps and validation, ensuring smoother user progression through the onboarding process.
4. **Security Enhancements**: Validation improvements for user data, particularly around personal information.

## Changes Overview

1. **File: `app/Console/Commands/UpdateUserDataOnboarding.php`**
   - **Status:** Added
   - **Changes:** Introduced a new command to update user onboarding status based on predefined conditions.
   - **Description:** This command iterates through all user data, updates names, and checks set conditions to advance onboarding stages.
   - **Impact:** Automates and ensures the consistency of the onboarding process for users.

2. **File: `app/Http/Middleware/CheckOnboarding.php`**
   - **Status:** Added
   - **Changes:** Middleware to check if the user's onboarding is complete.
   - **Description:** Redirects users to the onboarding page if their onboarding status is not 'done'.
   - **Impact:** Ensures users complete onboarding before accessing other application features.

3. **File: `app/Livewire/OnboardingForm.php`**
   - **Status:** Added
   - **Changes:** Comprehensive component for handling user onboarding steps and validation.
   - **Description:** Captures and validates user inputs across multiple onboarding steps, interfacing with external APIs for CPF/CNPJ validation.
   - **Impact:** Provides a guided and validated onboarding experience for users.

4. **File: `app/Livewire/OnboardingList.php`**
   - **Status:** Added
   - **Changes:** Component to handle the display of onboarding steps and their statuses.
   - **Description:** Renders the user's progress in onboarding with visual cues for each step.
   - **Impact:** Enhances user awareness of their progress in the onboarding workflow.

5. **File: `app/Actions/Fortify/CreateNewUser.php`**
   - **Status:** Modified
   - **Changes:** Optimized user creation process; added handling for phone number and country code.
   - **Description:** Removed legacy CPF/CNPJ validation, consolidating user-related data into the `UserData` model.
   - **Impact:** Simplifies user creation and ensures comprehensive handling of new user data.

6. **File: `app/Actions/Fortify/PasswordValidationRules.php`**
   - **Status:** Modified
   - **Changes:** Simplified password rules by removing confirmation requirements.
   - **Description:** Updated to relax password validation rules.
   - **Impact:** May reduce friction in password set-up during user registration.

7. **File: `app/Http/Controllers/DashboardController.php`**
   - **Status:** Modified
   - **Changes:** Refactored to remove redundant onboarding checks and streamline dashboard rendering.
   - **Description:** Removed detailed onboarding checks and implemented a simplified view render for dashboard and onboarding.
   - **Impact:** Simplifies controller logic and improves maintainability.

8. **File: `app/Http/Controllers/TaskController.php`**
   - **Status:** Modified
   - **Changes:** Removed onboarding checks from task view, apply, cancel, and progress actions.
   - **Description:** Ensures streamlined task-related actions without redundant onboarding validations.
   - **Impact:** Reduces unnecessary checks, improving response times and user experience.

9. **File: `app/Http/Controllers/UserProfileController.php`**
   - **Status:** Modified
   - **Changes:** Adjusted validation response for profile video upload and other methods.
   - **Description:** Fixed responses to ensure correct success status, removed duplicate checks.
   - **Impact:** Ensures correct status feedback to users on their profile updates.

10. **File: `app/Http/Kernel.php`**
    - **Status:** Modified
    - **Changes:** Updated middleware registration for onboarding.
    - **Description:** Removed old checking middleware and added new CheckOnboarding middleware.
    - **Impact:** Ensures appropriate middleware is applied to user requests.

11. **Files: `app/Http/Middleware/CheckUserAge.php`, `CheckUserContaAzul.php`**
    - **Status:** Removed
    - **Changes:** Deleted redundant middleware.
    - **Description:** Middleware logic now embedded within other existing middleware and consolidated checks.
    - **Impact:** Reduces codebase complexity and potential for middleware conflicts.

12. **File: `app/Livewire/Business/CheckoutForm.php`**
    - **Status:** Modified
    - **Changes:** Updated to use new UserData model.
    - **Description:** Ensures addressing and company details are sourced from the consolidated `UserData` model.
    - **Impact:** Simplifies data handling and enhances consistency.

13. **File: `app/Livewire/ProfileVideoUpload.php`**
    - **Status:** Modified
    - **Changes:** Added success alert and redirect for profile video update.
    - **Description:** Ensures users are informed and redirected appropriately post-update.
    - **Impact:** Enhances user experience by providing immediate feedback and navigation.

14. **File: `app/Models/User.php`**
    - **Status:** Modified
    - **Changes:** Removed redundant attributes and relationships; added new `UserData` relationship.
    - **Description:** Simplified user model to rely on `UserData` for extended user details.
    - **Impact:** Streamlines the user model, reducing redundancy and potential errors.

15. **Files: `app/Models/*` (Various Model Renames)**
    - **Status:** Renamed
    - **Changes:** Renamed `UserCnpj`, `UserCpf`, `UserAddress` to `Cnpj`, `Cpf`, `UserData`, respectively.
    - **Description:** Aligns model names with their new roles and database tables.
    - **Impact:** Improves clarity and maintains consistency across the codebase.

16. **File: `app/Providers/VariablesServiceProvider.php`**
    - **Status:** Modified
    - **Changes:** Updated role provision logic.
    - **Description:** Improved logic for injecting user role into views.
    - **Impact:** Ensures accurate role-based view rendering.

17. **File: `app/Services/FacebookConversionApiService.php`**
    - **Status:** Modified
    - **Changes:** Removed logging from API service.
    - **Description:** Cleanup to avoid unnecessary log clutter.
    - **Impact:** Keeps logs focused on essential information.

18. **File: `app/Rules/FileSize*` (Various File Size Rules)**
    - **Status:** Modified
    - **Changes:** Removed debug logging and improved validation checks.
    - **Description:** Cleaned up rule classes to ensure correct size validation without logging.
    - **Impact:** Improves performance and accuracy of file size validations.

19. **File: `app/Rules/CPFCNPJRule.php`**
    - **Status:** Removed
    - **Changes:** Deleted the custom CPF/CNPJ validation rule.
    - **Description:** This rule is no longer necessary due to the refactor.
    - **Impact:** Reduces redundant validation logic.

By implementing these changes, the application becomes more streamlined, efficient, and user-focused while maintaining strong data validation and user management capabilities.

---

# #137 Pull Request Description

## Headline
Implementation of Wallet Management System and Enhancements to Order Processing

## Introduction
This pull request introduces a new Wallet Management System for creators, enhancing the order processing workflow and integrating wallet functionality into the user interface. Among the key changes are the addition of console commands to check wallet transactions, new services for wallet and payout calculations, database migrations to support the new wallet structure, and user interface updates to display wallet information. These changes aim to streamline financial transactions for creators within the platform, ensuring accurate tracking of earnings and enhancing user experience by providing clear, accessible wallet data.

## Changes Overview

1. **File: `app/Console/Commands/CreatorCheckWalletTransaction.php`**
    - **Status:** Added
    - **Changes:** Introduced a new console command for checking wallet transactions and updating wallet balances accordingly.
    - **Description:** This new command retrieves all 'fulfilled' wallet transactions, validates if the pending balance is sufficient, and updates the wallet and transaction statuses. If not, an error message is displayed.
    - **Impact:** Simplifies the management and verification of wallet transactions, automating the updating process and ensuring the correct distribution of funds.

2. **File: `app/Services/PayoutCalculationService.php`**
    - **Status:** Added
    - **Changes:** Added a new service to calculate the payout amount for a given order, factoring in a percentage defined in the configuration.
    - **Description:** Handles the calculation of the payout amount for creators by applying the custom percentage defined in the application configuration.
    - **Impact:** Ensures that payout amounts are consistently calculated across different parts of the application, centralizing the logic for easier maintenance and updates.

3. **File: `app/Services/WalletService.php`**
    - **Status:** Added
    - **Changes:** Introduced a service to handle wallet-related operations, such as initiating and fulfilling orders.
    - **Description:** Manages wallet operations by updating balances and creating wallet transactions when an order is initiated or fulfilled.
    - **Impact:** Encapsulates wallet logic within a dedicated service, promoting a clean separation of concerns and enhancing code maintainability.

4. **File: `database/migrations/2024_06_18_124743_add_balance_pending_to_table_wallet.php`**
    - **Status:** Added
    - **Changes:** Added new columns (`balance_pending` and `total`) to the `wallets` table.
    - **Description:** These columns support tracking pending balances and overall earnings for the creators' wallets.
    - **Impact:** Provides a more granular view of wallet states by distinguishing between pending and available balances, and maintaining a cumulative total of earnings.

5. **File: `database/migrations/2024_06_18_125932_add_column_to_wallet_transaction.php`**
    - **Status:** Added
    - **Changes:** Added a `fulfilled_at` timestamp column to the `wallet_transactions` table.
    - **Description:** Enables tracking when a wallet transaction moves from 'initiated' to 'fulfilled'.
    - **Impact:** Improves transaction transparency by recording the fulfillment time, enhancing data accuracy for financial reporting and auditing.

6. **File: `database/migrations/2024_06_19_163223_add_payment_method_to_wallet_transactions_table.php`**
    - **Status:** Added
    - **Changes:** Added a `payment_method` column to the `wallet_transactions` table.
    - **Description:** Introduces the capability to record the payment method used for each transaction.
    - **Impact:** Enhances transaction details by including payment method information, valuable for analytics and user information.

7. **File: `resources/views/dashboard/creator/wallet.blade.php`**
    - **Status:** Added
    - **Changes:** Created a new view for displaying wallet information, including current balance, pending balance, and transaction history.
    - **Description:** Provides a user interface for creators to view their wallet balances and transaction history, with visual components for pending and available balances.
    - **Impact:** Enhances user experience by enabling creators to access detailed and organized financial information on their dashboard.

8. **File: `app/Http/Controllers/OrderProcessController.php`**
    - **Status:** Modified
    - **Changes:** Integrated the `WalletService` to handle wallet operations when orders are accepted or fulfilled.
    - **Description:** Refactored existing logic to use the newly created `WalletService` for better organization and code reuse.
    - **Impact:** Centralizes wallet-related logic and simplifies the order processing controller, making it easier to extend and maintain.

9. **File: `app/Http/Controllers/UserProfileController.php`**
    - **Status:** Modified
    - **Changes:** Added a new method to display the wallet view and integrated it into the user profile.
    - **Description:** Allows creators to access their wallet view directly from the profile section.
    - **Impact:** Improves navigation and accessibility for wallet information, contributing to a better user experience.

10. **File: `app/Models/User.php`**
    - **Status:** Modified
    - **Changes:** Added relationships to the `Wallet` and `WalletTransaction` models.
    - **Description:** Defines one-to-one and one-to-many relationships with the `Wallet` and `WalletTransaction` models.
    - **Impact:** Facilitates easier data retrieval and manipulation related to user finances within the application.

11. **File: `app/Models/WalletTransaction.php`**
    - **Status:** Modified
    - **Changes:** Added `payment_method` to the fillable attributes.
    - **Description:** Ensures the `payment_method` field can be mass-assigned.
    - **Impact:** Enhances the model's ability to handle additional transaction details flexibly.

12. **File: `resources/lang/pt_br/dashboard.php`**
    - **Status:** Modified
    - **Changes:** Added translations related to the wallet feature.
    - **Description:** Introduces Portuguese translations for the wallet interface, contributing to localization efforts.
    - **Impact:** Supports non-English-speaking users, improving accessibility and user experience for a broader audience.

13. **File: `resources/views/dashboard/components/header.blade.php`**
    - **Status:** Modified
    - **Changes:** Added wallet balance display for creators in the dashboard header.
    - **Description:** Provides a quick view of the creator's wallet balance directly in the dashboard header.
    - **Impact:** Enhances usability by allowing creators to see their balance at a glance, improving the overall user interface.

14. **File: `resources/views/dashboard/components/sidebar.blade.php`**
    - **Status:** Modified
    - **Changes:** Integrated a link to the wallet view in the sidebar for creators.
    - **Description:** Adds a convenient navigation option for accessing the wallet view.
    - **Impact:** Simplifies access to wallet information, enhancing the navigation experience within the dashboard.

15. **File: `resources/views/dashboard/creator/livewire/dashboard-tasks.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated payout calculation display to use the `PayoutCalculationService`.
    - **Description:** Ensures the correct payout amount is displayed, using the central calculation service.
    - **Impact:** Increases consistency and accuracy of financial data displayed to creators.

16. **File: `resources/views/dashboard/creator/task/view.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated earning potential display to use the `PayoutCalculationService`.
    - **Description:** Displays the correct potential earnings for creators using the centralized payout calculation logic.
    - **Impact:** Improves accuracy and consistency in displaying financial information to users.

17. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added routes for accessing wallet and payout views.
    - **Description:** Defines new routes to support wallet interactions and video uploads in user profiles.
    - **Impact:** Expands navigation options and functionalities available to creators, ensuring smooth access to new features.

This comprehensive update not only adds critical functionality for financial management but also enhances user experience and maintains code organization, making future updates and maintenance easier.

---


# #134 Minor Adjustments to Profile Video Upload and Setcard UI Logic

## Introduction
This pull request introduces small but significant changes to the user interface logic for the profile video upload and setcard sections of the application. These changes focus on refactoring the frontend code for improved element identification, better user interface operations, and overall code simplification. By addressing these aspects, the changes enhance the stability and maintainability of the file upload feature, which is critical for user experience.

## Changes Overview
1. **File: `resources/views/profile/profile-video-upload.blade.php`**
   - **Status:** Modified
   - **Changes:** Changed the `id` of a `<section>` element from `progress-area` to `progress-area`.
   - **Description:** The change involves modifying the ID of a section element related to displaying the progress of video uploads. This could indicate a refinement to reference or styling consistency in the UI components.
   - **Impact:** This minor change ensures the correct identification and operation of the progress section within the profile video upload process, potentially fixing or avoiding issues related to progress display inconsistencies.

2. **File: `resources/views/profile/setcard.blade.php`**
   - **Status:** Modified
   - **Changes:** Removed an event handler for the `change` event using jQuery and replaced it with a standard JavaScript event listener.
   - **Description:** This alteration eliminates redundant code and updates the event handling mechanism from jQuery to vanilla JavaScript. This improves the simplicity and readability of the file input change event.
   - **Impact:** The shift from jQuery to pure JavaScript can lead to slightly better performance and reduces dependency on jQuery for simple operations. This change also aligns with modern JavaScript practices, enhancing code maintainability and future-proofing the application.
```

---

# #133 Update Profile Video Upload and Setcard Scripts for Improved User Interface

## Introduction
This pull request includes modifications to the "profile-video-upload.blade.php" and "setcard.blade.php" files. The changes focus primarily on improving the user interface and the handling of file uploads. Specifically, there are updates to HTML elements and JavaScript event handling that enhance the user experience by fixing and refining the progress display area during file uploads.

## Changes Overview
1. **File: `resources/views/profile/profile-video-upload.blade.php`**
- **Status:** Modified
- **Changes:** A single line was updated to add an `id` attribute to a section element: 
  ```diff
  - <section class="rounded-md uploaded-area bg-creatify-bg dark:bg-neutral-700">
  + <section id="progress-area" class="rounded-md uploaded-area bg-creatify-bg dark:bg-neutral-700">
  ```
- **Description:** This change assigns an ID `progress-area` to the section element responsible for displaying the upload progress.
- **Impact:** It improves the accuracy and efficiency of JavaScript targeting this element, ensuring correct updates and manipulations during the upload process. This can streamline the user experience by clearly displaying upload progress to the users.

2. **File: `resources/views/profile/setcard.blade.php`**
- **Status:** Modified
- **Changes:** Nine lines were changed, including the following updates:
  - Removed reference to `uploaded-area`:
    ```diff
    - progressArea = document.getElementById("progress-area"),
    - uploadedArea = document.getElementById("uploaded-area");
    + progressArea = document.getElementById("progress-area");
    ```
  - Replaced old event listener syntax with a more modern handling:
    ```diff
    - form.addEventListener("click", () => {
    + fileInput.on("change", () => {
    ``` 
  - Removed lines altering the `uploaded-area`:
    ```diff
    - uploadedArea.innerHTML = "";
    - uploadedArea.classList.add("onprogress");
    + // uploadedArea.classList.remove("onprogress");
    ```
- **Description:** 
  These changes streamline the handling of file uploads by focusing solely on the `progress-area`. The removal of `uploaded-area` handling simplifies the code and reduces complexity related to the upload progress representation.
- **Impact:** These adjustments improve the maintainability and readability of the code, eliminating potential bugs or unclear logic associated with the `uploaded-area`. Additionally, updating the event listening mechanism is likely to make the script more robust and compatible with modern JavaScript practices, potentially enhancing overall performance and user interaction.

By focusing on critical updates to HTML elements and JavaScript logic, this pull request aims to enhance the user interface and user experience for file uploads, making the progress tracking clearer and the associated code more maintainable.

---

# #132 Addition of New View Component and Multiple Enhancements Across Files

## Introduction
This pull request primarily focuses on adding a new view component and making enhancements across various existing files. These changes bring about improved functionality, refined user experience, and more consistent styling across the application. The main areas of changes include:
- New component addition
- UI/UX enhancements
- Configuration updates
- Modifications for dark mode compatibility
- Code cleanup and improvements

## Changes Overview
1. **File: `resources/views/components/button-view-type.blade.php`**
- **Status:** New
- **Changes:** Introduced a new Blade component for toggling between table and grid view types.
- **Description:** This component generates buttons that allow users to switch between table and grid views.
- **Impact:** Enhances user experience by providing an easy way to toggle views on pages.

2. **File: `resources/views/components/input-radio.blade.php`**
- **Status:** New
- **Changes:** Added a new radio input component.
- **Description:** A customizable radio input element with specific styles for both light and dark themes.
- **Impact:** Streamlines the usage of radio inputs across different forms in the application.

3. **File: `config/app_custom.php`**
- **Status:** Modified
- **Changes:** Updated existing configurations and added new entries for official social media account URLs.
- **Description:** Enhanced API token management and added links to social media accounts.
- **Impact:** Provides better flexibility in configuring API tokens and improves the accessibility of social media links.

4. **File: `resources/css/app.css`**
- **Status:** Modified
- **Changes:** Added new utility classes for tracking-wide, transition effects, and button styling.
- **Description:** Improves the visual consistency and styling of buttons and general text appearance.
- **Impact:** Enhances overall user interface and experience.

5. **File: `resources/lang/pt_br/profile.php`**
- **Status:** Modified
- **Changes:** Removed redundant subtitles from the address section in the profile language file.
- **Description:** Simplifies the contact section's language for clarity.
- **Impact:** Cleaned up content making it more concise and easier to understand.

6. **File: `resources/views/components/alert.blade.php`**
- **Status:** Modified
- **Changes:** Updated alert component to adjust text sizes and removed unnecessary wrappers.
- **Description:** Improved the structure for responsiveness and readability.
- **Impact:** Makes alert messages more visually appealing and clear on various devices and screen sizes.

7. **File: `resources/views/components/connected-account.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted the maximum width of the component.
- **Description:** Ensures better layout control and consistency.
- **Impact:** Enhances the component's usability and appearance within different container sizes.

8. **File: `resources/views/components/dialog-modal.blade.php`**
- **Status:** Modified
- **Changes:** Added dark mode support and improved styling.
- **Description:** Ensures that the dialogs are properly styled in both light and dark themes.
- **Impact:** Enhances user experience for users who prefer dark mode.

9. **File: `resources/views/components/feedback.blade.php`**
- **Status:** Modified
- **Changes:** Comprehensive overhaul of the feedback form’s layout and functionality.
- **Description:** Improved the form's accessibility, responsiveness, and visual hierarchy.
- **Impact:** Makes the feedback form easier to use and more accessible across different devices.

10. **File: `resources/views/components/footer-homepage.blade.php`**
- **Status:** Modified
- **Changes:** Major redesign of the footer component, including adding dynamic links to social media from the configuration.
- **Description:** Enhances footer content with social media links, signup forms, and improved styling.
- **Impact:** Provides a more engaging and dynamic footer section.

11. **File: `resources/views/components/input.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted class attributes for text size consistency.
- **Description:** Standardizes input field text sizes.
- **Impact:** Ensures better readability and usability for input fields.

12. **File: `resources/views/components/label.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted class attributes for text size consistency.
- **Description:** Standardizes label text sizes.
- **Impact:** Ensures better readability and usability for labels.

13. **File: `resources/views/components/menu-homepage.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted navbar layout and flex properties.
- **Description:** Improved layout for better responsiveness and alignment.
- **Impact:** Enhances the header navigation experience.

14. **File: `resources/views/components/modal.blade.php`**
- **Status:** Modified
- **Changes:** Added dark mode support and adjusted background properties.
- **Description:** Ensures consistency of modals in dark theme scenarios.
- **Impact:** Improves the visual coherence of modal components.

15. **File: `resources/views/components/secondary-button.blade.php`**
- **Status:** Modified
- **Changes:** Improved button styling for better accessibility and visual appeal.
- **Description:** Adjusted classes for a more modern and usable design.
- **Impact:** Enhances the user interaction with secondary buttons.

16. **File: `resources/views/components/section-title.blade.php`**
- **Status:** Modified
- **Changes:** Added new styling class for section descriptions.
- **Description:** Improves the readability and styling of section titles.
- **Impact:** Provides a consistent appearance across different sections.

17. **File: `resources/views/dashboard/business/dashboard.blade.php`**
- **Status:** Modified
- **Changes:** Major overhauls, including adding dark mode support, text size adjustments, and enhanced responsiveness.
- **Description:** Ensures that the dashboard looks and performs well across devices and themes.
- **Impact:** Greatly enhances the user interface and functionality of the dashboard.

18. **File: `resources/views/dashboard/business/order/applications.blade.php`**
- **Status:** Modified
- **Changes:** Enhanced layout, added dynamic data displays, and improved responsiveness.
- **Description:** Improves the visual and functional interface for viewing and managing applications.
- **Impact:** Enriches user experience with a more intuitive and informative application management page.

19. **File: `resources/views/dashboard/business/order/checkout.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted heading sizes and improved input field consistency.
- **Description:** Makes the checkout process more streamlined and visually harmonious.
- **Impact:** Enhances the user experience during the checkout process.

20. **File: `resources/views/dashboard/business/order/index.blade.php`**
- **Status:** Modified
- **Changes:** Major upgrades including switching view toggle, improving layout, and enhancing table and grid views.
- **Description:** Provides a more flexible and user-friendly way of viewing orders.
- **Impact:** Greatly improves order management with clear and customizable views.

21. **File: `resources/views/dashboard/business/order/livewire/checkout-form.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted fonts sizes in the checkout form.
- **Description:** Ensures consistent text sizes and better readability.
- **Impact:** Enhances the overall user experience within the checkout form.

22. **File: `resources/views/dashboard/business/order/livewire/process.blade.php`**
- **Status:** Modified
- **Changes:** Added hover effects and dark mode support, refined buttons.
- **Description:** Enhances visual feedback and usability.
- **Impact:** Improves user interaction and accessibility.

23. **File: `resources/views/dashboard/business/order/select_product.blade.php`**
- **Status:** Modified
- **Changes:** Simplified layout by removing unnecessary view toggles and updated product display styles.
- **Description:** Provides a cleaner interface for product selection.
- **Impact:** Enhances usability and visual appeal of the product selection page.

24. **File: `resources/views/dashboard/business/product/create.blade.php`**
- **Status:** Modified
- **Changes:** Improved form layout, added hover effects, and updated alerts.
- **Description:** Makes the product creation process smoother and more aesthetically pleasing.
- **Impact:** Enhances the form usability with better styling and visual cues.

25. **File: `resources/views/dashboard/business/product/edit.blade.php`**
- **Status:** Modified
- **Changes:** Various text and styling adjustments for better consistency.
- **Description:** Improves the product editing experience by refining the UI.
- **Impact:** Ensures a seamless and coherent editing interface.

---

# #131 Additions of New Console Commands, Models, and Scheduling Updates for Improved User Interactions and Email Management

## Introduction
This pull request introduces significant enhancements and new features, focusing on email management, user experience improvements, and the expansion of the application’s architecture. Key areas updated include the addition of new console commands, livewire components and models, as well as updates to existing controllers, routes, and database migrations. These changes aim to improve user engagement through better email communication and provide more robust administrative tools.

## Changes Overview

1. **File: `app/Console/Commands/UserSendmail.php`**
   - **Status:** Added
   - **Changes:** Introduces a new console command to send emails to users with pending status and processes the email content.
   - **Description:** The command retrieves a batch of pending emails, processes each email’s HTML content to plain text, sends the email via the SMTP2Go service, logs the response, and updates status tables.
   - **Impact:** Automates the sending of user emails, ensuring email status updates and logging for better email management.

2. **File: `app/Livewire/ProfileReferences.php`**
   - **Status:** Added
   - **Changes:** New Livewire component to manage user profile references.
   - **Description:** Fetches user-specific references and displays them on the user’s profile page.
   - **Impact:** Enhances user profile pages by allowing users to view their references.

3. **File: `app/Livewire/PublicReviewForm.php`**
   - **Status:** Added
   - **Changes:** New Livewire component for users to submit reviews publicly.
   - **Description:** Allows users to provide reviews after validating whether the review invitation is still valid.
   - **Impact:** Streamlines the review process, encouraging user feedback and engagement.

4. **File: `app/Models/UserAdmin.php`**
   - **Status:** Added
   - **Changes:** New model for managing user admin-related settings and information.
   - **Description:** Contains admin-specific attributes like signature name and role.
   - **Impact:** Provides a structured way to manage and store user admin information.

5. **File: `app/Models/UserReview.php`**
   - **Status:** Added
   - **Changes:** New model to handle user reviews.
   - **Description:** Includes attributes like user ID, review content, rating, and status.
   - **Impact:** Enables the storage and retrieval of structured user reviews, facilitating better interaction tracking.

6. **File: `app/Models/UserReviewPending.php`**
   - **Status:** Added
   - **Changes:** New model to handle pending user reviews.
   - **Description:** Manages review invitations and their status.
   - **Impact:** Tracks the state of review invitations, improving the review solicitation process.

7. **File: `app/Models/UserSendmail.php`**
   - **Status:** Added
   - **Changes:** New model for managing user-specific email sends.
   - **Description:** Stores email details and status for each user email send operation.
   - **Impact:** Centralizes the management of user email communication, improving traceability and accountability.

8. **File: `app/Notifications/Creator/ReviewInvitation.php`**
   - **Status:** Added
   - **Changes:** New notification for sending review invitations via SMTP2Go.
   - **Description:** Formats and sends review invitation emails to specified users.
   - **Impact:** Enhances user engagement by facilitating review solicitations through email notifications.

9. **File: `database/migrations/2024_06_14_172909_add_social_media_columns_to_user_social_media_table.php`**
   - **Status:** Added
   - **Changes:** Adds new social media columns to the user social media table.
   - **Description:** Adds fields for Twitter, YouTube, LinkedIn, and Facebook.
   - **Impact:** Expands the social media capabilities of the platform, enabling users to link additional social media profiles.

10. **File: `database/migrations/2024_06_14_183352_create_user_reviews_table.php`**
    - **Status:** Added
    - **Changes:** Creates a new table for storing user reviews.
    - **Description:** The table includes fields for review content, rating, status, and timestamps.
    - **Impact:** Provides a dedicated storage solution for user reviews, enhancing data organization and retrieval efficiency.

11. **File: `database/migrations/2024_06_14_193244_create_user_review_pendings_table.php`**
    - **Status:** Added
    - **Changes:** Creates a new table for pending user reviews.
    - **Description:** Manages review invitations and pending statuses.
    - **Impact:** Improves the review process by tracking pending review invitations.

12. **File: `database/migrations/2024_06_14_205210_add_email_to_user_reviews_table.php`**
    - **Status:** Added
    - **Changes:** Adds an email field to the user reviews table.
    - **Description:** Ensures that each review is associated with an email address for identification.
    - **Impact:** Enhances the detail and traceability of user reviews.

13. **File: `app/Actions/Fortify/CreateNewUser.php`**
    - **Status:** Modified
    - **Changes:** Adds nickname generation for new users.
    - **Description:** Automatically generates a lowercase nickname based on the user’s name and a random number.
    - **Impact:** Simplifies the nickname assignment process, ensuring unique and consistent nicknames for new users.

14. **File: `app/Console/Commands/LeadSendmail.php`**
    - **Status:** Modified
    - **Changes:** Updates the lead email send console command for batch processing.
    - **Description:** Fetches a configurable batch of pending lead emails for processing and sending.
    - **Impact:** Improves the efficiency of sending lead emails by processing them in batches.

15. **File: `app/Console/Kernel.php`**
    - **Status:** Modified
    - **Changes:** Updates the kernel scheduling for the new user email send command.
    - **Description:** Schedules both lead and user email sends to run every five minutes.
    - **Impact:** Ensures timely and periodic sending of both lead and user emails, enhancing communication consistency.

16. **File: `app/Http/Controllers/AdminController.php`**
    - **Status:** Modified
    - **Changes:** Several additions including settings management for user admins, sending user-specific emails, and validation.
    - **Description:** Enhances the admin functionality for managing user-specific settings and email communications.
    - **Impact:** Provides admins with better tools for managing user engagements and communications.

17. **File: `app/Http/Controllers/DashboardController.php`**
    - **Status:** Modified
    - **Changes:** Adjusts the logic of personal details completeness check.
    - **Description:** Includes new social media fields in the completeness check.
    - **Impact:** Ensures comprehensive monitoring of user profile completion status.

18. **File: `app/Http/Controllers/PublicPagesController.php`**
    - **Status:** Modified
    - **Changes:** Adds routes and functionalities for review writing and creator profile display.
    - **Description:** Forwards invitations to write reviews and displays creator profiles based on nicknames.
    - **Impact:** Enhances public user interactions by facilitating reviews and showcasing creator profiles.

19. **File: `app/Http/Controllers/UserProfileController.php`**
    - **Status:** Modified
    - **Changes:** Adds methods for handling review invitations, review submissions, and profile previews.
    - **Description:** Manages new functionalities for user reviews and the handling of video references.
    - **Impact:** Enriches user profile management with additional review and video reference functionalities.

20. **File: `app/Http/Middleware/VerifyCsrfToken.php`**
    - **Status:** Modified
    - **Changes:** Adds new routes to the CSRF exclusion list.
    - **Description:** Includes video upload and references routes in the CSRF token exclusion list.
    - **Impact:** Ensures uninterrupted processing of specific video-related and webhook routes.

21. **File: `app/Livewire/Business/OrderProcess.php`**
    - **Status:** Modified
    - **Changes:** Adjusts the discount application logic in order processing.
    - **Description:** Updates total calculation logic after applying discount codes.
    - **Impact:** Ensures accurate calculation and application of discounts for business orders.

22. **File: `app/Livewire/Creator/UserProfile.php`**
    - **Status:** Modified
    - **Changes:** Updates user profile display to include both internal and external reviews and references.
    - **Description:** Combines different sources of reviews into a unified display for user profiles.
    - **Impact:** Provides users with a comprehensive view of their reviews and references, enhancing their profile completeness.

23. **File: `app/Livewire/ProfileVideoUpload.php`**
    - **Status:** Modified
    - **Changes:** Minor update for aligning video upload functionality.
    - **Description:** Ensures video upload functionality follows the updated schema and logic.
    - **Impact:** Maintains consistency and reliability in profile-related video uploads.

24. **File: `app/Livewire/UpdateCreatorMessengerForm.php`**
    - **Status:** Modified
    - **Changes:** Adds new social media fields for update.
    - **Description:** Synchronizes new social media fields with the user profile update form.
    - **Impact:** Enhances the social media linking capabilities for user profiles.

25. **File: `app/Livewire/UpdateCreatorPayoutForm.php`**
    - **Status:** Modified
    - **Changes:** Improves pay-out detail validation logic.
    - **Description:** Ensures proper validation for various payout formats before updating.
    - **Impact:** Improves accuracy and consistency in user payout details management.

26. **File: `app/Models/Order.php`**
    - **Status:** Modified
    - **Changes:** Adds relationship to coupon codes.
    - **Description:** Enables linking of orders to their respective coupon codes.
    - **Impact:** Enhances the tracking and application of discounts in orders.

27. **File: `app/Models/User.php`**
    - **Status:** Modified
    - **Changes:** Adds relationships to handle multiple new components.
    - **Description:** Includes relationships for user references, reviews, and pending reviews.
    - **Impact:** Enhances the user model’s capabilities in managing and retrieving complex user-related data.

28. **File: `app/Models/UserReference.php`**
    - **Status:** Modified
    - **Changes:** Minor update to clarify the video field.
    - **Description:** Adds comment to the video field for clarification.
    - **Impact:** Improves code readability and maintainability for the development team.

29. **File: `app/Models/UserSocialMedia.php`**
    - **Status:** Modified
    - **Changes:** Adds new social media handle fields.
    - **Description:** Synchronizes with migration updates to include Twitter, YouTube, LinkedIn, and Facebook.
    - **Impact:** Expands the range of social media handles that can be stored for each user.

30. **File: `config/app_custom.php`**
    - **Status:** Modified
    - **Changes:** Introduces configurations for batching newsletter sends and folders for reference videos.
    - **Description:** Adds configurations for managing email batch sizes and file storage paths.
    - **Impact:** Improves the flexibility and manageability of email communication and file storage.

---

# #130 New Email Notification System for Creators

## Introduction
This pull request introduces a significant new feature to the application: an email notification system for creators when a new order is available. The implementation includes the addition of new console commands, notification logic, database schema updates, and language file modifications. These changes aim to enhance user experience by ensuring that creators are promptly notified of new opportunities, improving engagement and efficiency. Additionally, there are some refactorings and renamings in the console commands to maintain consistency and clarity. Other changes include the cleanup of redundant language files and minor modifications to existing functionalities.

## Changes Overview

1. **File: `app/Console/Commands/CreatorSendmailNewOrderAvailable.php`**
   - **Status:** Added
   - **Changes:** New console command to send an email to creators when a new order is available.
   - **Description:** This command checks for new orders that have not been notified to the creators, sends notifications, and updates the order's 'notified' status once the notifications are sent.
   - **Impact:** Ensures creators are immediately informed about new orders, improving response times and engagement.

2. **File: `app/Notifications/Creator/NewOrderAvailable.php`**
   - **Status:** Added
   - **Changes:** Notification class to handle sending emails using the Smtp2GoChannel.
   - **Description:** This class constructs the email details, including the subject, headline, subtitle, content, action button, and additional information tailored to the creator receiving the notification.
   - **Impact:** Facilitates communication and ensures that creators receive prompt and clear notifications about new orders.

3. **File: `database/migrations/2024_06_14_160728_add_notified_to_orders_table.php`**
   - **Status:** Added
   - **Changes:** Migration file to add a 'notified' boolean column to the 'orders' table.
   - **Description:** This column tracks whether an order has been notified to the creators.
   - **Impact:** Helps in managing the state of order notifications, ensuring notifications are not sent multiple times for the same order.

4. **File: `resources/views/emails/order/new-order-available.blade.php`**
   - **Status:** Added
   - **Changes:** Blade template for the new order available email.
   - **Description:** This file defines the structure and content of the email notification sent to creators, including the image, title, subtitle, content, action link, and additional information.
   - **Impact:** Ensures email notifications are well-structured and visually appealing, improving the likelihood of recipient engagement.

5. **File: `app/Console/Commands/LeadSendmail.php`**
   - **Status:** Modified
   - **Changes:** Minor modifications to the command signature and description.
   - **Description:** Updated the command signature to 'sendmail:lead-emails' and provided a clearer description.
   - **Impact:** Improves readability and consistency in the command-line tools.

6. **File: `app/Console/Kernel.php`**
   - **Status:** Modified
   - **Changes:** Schedule modifications to include the new command and adjust existing command timings.
   - **Description:** Added scheduling for the new 'creator:sendmail-new-order-available' command and organized other scheduled commands for clarity.
   - **Impact:** Ensures the new notification system runs automatically at specified times, maintaining regular updates to creators without manual intervention.

7. **File: `resources/lang/pt_br/auth.php`**
   - **Status:** Modified
   - **Changes:** Modified language strings related to business terminology.
   - **Description:** Updated terminology from 'Empresa' to 'Marca' for consistency with the recent business branding focus.
   - **Impact:** Improves clarity and consistency in the user interface for Portuguese-speaking users.

8. **File: `resources/lang/pt_br/email.php`**
   - **Status:** Modified
   - **Changes:** Added new email notifications strings and updated existing ones.
   - **Description:** New strings are added to support the new notification email for new orders available.
   - **Impact:** Ensures all necessary language support is in place for sending clear and concise email notifications to users.

9. **File: `resources/lang/pt_br/general.php`**
   - **Status:** Modified
   - **Changes:** Updated several general language strings to align with branding changes.
   - **Description:** Changed 'Empresa' to 'Marca' in various sections to reflect the new branding direction.
   - **Impact:** Maintains consistency and ensures the application uses the correct terminology throughout the user interface.

10. **File: `resources/views/dashboard/creator/dashboard.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated content to reflect terminology change from 'Empresa' to 'Marca'.
    - **Description:** Adjusted text to ensure consistent branding throughout the creator dashboard.
    - **Impact:** Enhances user experience by maintaining a consistent and clear brand message.

11. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Route modification for business registration.
    - **Description:** Redirects old business registration URL to the new 'marca' registration URL.
    - **Impact:** Ensures users trying to access the old URL are seamlessly redirected to the correct, updated route.

12. **File: `app/Console/Commands/SendmailNewApplications.php`**
    - **Status:** Renamed
    - **Changes:** Renamed to `BusinessSendmailNewApplications.php` and updated the class and command signature.
    - **Description:** Refactoring the class and command name for clarity and consistency.
    - **Impact:** Improves codebase maintainability and readability by having clear, descriptive command names.

13. **File: `app/Console/Commands/SendmailSetcardVideoMissing.php`**
    - **Status:** Renamed
    - **Changes:** Renamed to `CreatorSendmailSetcardVideoMissing.php` and updated the class and command signature.
    - **Description:** Refactoring for better clarity and consistency with other command names.
    - **Impact:** Simplifies understanding and usage of console commands within the codebase.

14. **File: `app/Console/Commands/UpdateCouponStatus.php`**
    - **Status:** Renamed
    - **Changes:** Renamed to `OrderUpdateCouponStatus.php` and updated the class and command signature.
    - **Description:** This change aligns the command file names and signatures for better consistency.
    - **Impact:** Helps maintain a clear and organized codebase.

15. **File: `public/sitemap.xml`**
    - **Status:** Removed
    - **Changes:** Entire file deleted.
    - **Description:** The removal likely indicates a change in how sitemaps are handled or generated.
    - **Impact:** May affect search engine optimization (SEO) if a replacement sitemap strategy is not implemented.

16. **File: `resources/lang/en/auth.php`**
    - **Status:** Removed
    - **Changes:** Entire file deleted.
    - **Description:** The removal suggests a cleanup of unused or redundant translation files.
    - **Impact:** Potential reduction in localization maintenance burden, assuming these translations are no longer needed.

17. **File: `resources/lang/en/pagination.php`**
    - **Status:** Removed
    - **Changes:** Entire file deleted.
    - **Description:** Cleanup of redundant or unused language files.
    - **Impact:** Simplifies the localization fileset, reducing potential confusion.

18. **File: `resources/lang/en/passwords.php`**
    - **Status:** Removed
    - **Changes:** Entire file deleted.
    - **Description:** Indicates a cleanup of unused or redundant translation files.
    - **Impact:** Reduced maintenance and possible minor reduction in application size.

19. **File: `resources/lang/en/validation.php`**
    - **Status:** Removed
    - **Changes:** Entire file deleted.
    - **Description:** Indicates comprehensive cleanup of redundant language resources.
    - **Impact:** Easier maintenance and potentially less confusion within the development team regarding unused resources.

20. **File: `resources/lang/pt_br copy.json`**
    - **Status:** Removed
    - **Changes:** Entire file deleted.
    - **Description:** Cleanup of what seems to be a redundant or mistakenly duplicated language file.
    - **Impact:** Reduces clutter in the codebase, enhancing maintainability.

---

# #128 New Automated Email Send-out System for Leads

## Introduction
This pull request introduces a new automated system to send emails to leads. The main goal is to enhance the application's functionality by allowing scheduled and manual email dispatches for pending messages. This feature adds a significant improvement to user experience by automating a repetitive task, ensuring emails are sent on time. It also bolsters overall system architecture with new database models and views to support this functionality.

## Changes Overview

1. **File: `app/Console/Commands/LeadSendmail.php`**
   - **Status:** Added
   - **Changes:** A new console command `send:lead-emails` is created to automate the email sending process for leads.
   - **Description:** This command retrieves pending email entries (`LeadSendmail`), processes each one by removing unnecessary HTML elements, and sends the email using the SMTP2Go API. It also logs the status and saves the webhook response and email statuses.
   - **Impact:** Automates the sending of pending lead emails, reducing manual intervention, and integrating into the system's schedule.

2. **File: `app/Models/LeadSendmail.php`**
   - **Status:** Added
   - **Changes:** Introduced a new `LeadSendmail` model with necessary relationships and fillable attributes.
   - **Description:** Represents the structure needed to store and manage pending lead emails in the database.
   - **Impact:** Provides a data structure for storing pending email tasks, facilitating automation.

3. **File: `database/migrations/2024_06_13_190248_create_lead_sendmails_table.php`**
   - **Status:** Added
   - **Changes:** A migration script to create the `lead_sendmails` table in the database.
   - **Description:** Defines the schema for the `lead_sendmails` table which includes foreign keys and necessary fields for email descriptions and statuses.
   - **Impact:** Sets up the database infrastructure necessary to store lead emails, critical for the new email-sending feature.

4. **File: `resources/views/admin/lead/sendmail.blade.php`**
   - **Status:** Added
   - **Changes:** A new Blade view for the email send-out interface in the admin panel.
   - **Description:** Provides a user interface for administrators to create and send emails to specific leads or lists of leads.
   - **Impact:** Enhances user experience by providing an administrative UI to control the sending of emails.

5. **File: `app/Console/Kernel.php`**
   - **Status:** Modified
   - **Changes:** Registered the new command to be executed every minute.
   - **Description:** Ensures the `send:lead-emails` command runs automatically and frequently to process pending emails.
   - **Impact:** Integrates the email sending process into the application's regular schedule, automating a previously manual task.

6. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Modified
   - **Changes:** Added methods to handle email sending to leads and lists from the admin interface.
   - **Description:** Allows admin users to send emails directly to specified leads or lead lists via the UI and stores these tasks as pending emails.
   - **Impact:** Improves admin control over email dispatches, enhancing functionality and user experience.

7. **File: `resources/views/admin/lead/index.blade.php`**
   - **Status:** Modified
   - **Changes:** UI updates to integrate the new send email functionality.
   - **Description:** Enhanced to allow administrators to trigger the sending of emails to specific leads from the listing page.
   - **Impact:** Provides convenient access to email sending features directly from the lead list view.

8. **File: `resources/views/admin/lead/lists.blade.php`**
   - **Status:** Modified
   - **Changes:** Integrated send email buttons for lead lists.
   - **Description:** Adds a button to send emails to all leads in a list.
   - **Impact:** Simplifies the process of sending bulk emails to groups of leads.

9. **File: `resources/views/layouts/admin.blade.php`**
   - **Status:** Modified
   - **Changes:** Added styles and scripts necessary for the email editor.
   - **Description:** Ensures the text editor for composing emails has the required CSS and JavaScript.
   - **Impact:** Improves the user interface for composing and sending emails, enhancing usability.

10. **File: `resources/views/layouts/partials/head.blade.php`**
    - **Status:** Modified
    - **Changes:** Various SEO and favicon meta tags updates.
    - **Description:** Ensures up-to-date and comprehensive metadata for SEO and site branding.
    - **Impact:** Improves site metadata, benefiting SEO and user experience.

11. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added routes for the new send email functionality.
    - **Description:** Defines new routes for initiating the email send-out process from the admin panel.
    - **Impact:** Integrates the new email functionality into the application's routing system, providing necessary endpoints for the new features.

---

# #127 New Functionality for Lead Management in Admin Panel

## Introduction
This pull request introduces significant changes to the admin panel by adding comprehensive lead management capabilities. The update encapsulates new feature additions, database migrations, UI enhancements, and improvements in the backend logic to support lead operations. The changes enhance the application's functionality by allowing efficient management of leads, improve user experience through a new user interface for lead additions and listings, and ensure a more robust and scalable architecture.

## Changes Overview

1. **File: `app/Livewire/Admin/FormAddLead.php`**
   - **Status:** Added
   - **Changes:** Introduced a new Livewire component for adding leads, including fields for category, list, name, company, email, phone, website, and various address components. Includes methods to handle form submission, address fetching through an external API, and lead creation in the database.
   - **Description:** This file contains the logic required to add a new lead. It processes the input fields, handles API calls to fetch address details, and saves the lead data in the respective tables.
   - **Impact:** Adds the capability to create leads from the admin panel, enhancing user experience and allowing administrators to manage leads right from the interface.

2. **File: `app/Models/Lead.php`**
   - **Status:** Added
   - **Changes:** Defined the `Lead` model with Eloquent relationships to emails, phones, addresses, notes, and websites.
   - **Description:** This model represents the lead entity in the database.
   - **Impact:** Central to the lead management system, linking various lead details through defined relationships.

3. **File: `app/Models/LeadAddress.php`**
   - **Status:** Added
   - **Changes:** Defined the `LeadAddress` model with fields like lead_id, address, street, city, state, zip, etc.
   - **Description:** This model contains address details related to a lead.
   - **Impact:** Supports the addition and association of address information with leads.

4. **File: `app/Models/LeadEmail.php`**
   - **Status:** Added
   - **Changes:** Defined the `LeadEmail` model with fields like lead_id, email, label, and primary flag.
   - **Description:** Handles the email addresses associated with leads.
   - **Impact:** Enables linking multiple email addresses with a single lead.

5. **File: `app/Models/LeadList.php`**
   - **Status:** Added
   - **Changes:** Defined the `LeadList` model with fields like name and description.
   - **Description:** Represents different lists to categorize leads.
   - **Impact:** Helps categorize and manage leads through predefined lists.

6. **File: `app/Models/LeadNote.php`**
   - **Status:** Added
   - **Changes:** Introduced the `LeadNote` model with fields including lead_id, note text, and created_by.
   - **Description:** Stores notes related to a lead.
   - **Impact:** Facilitates detailed logs and notes for each lead.

7. **File: `app/Models/LeadPhone.php`**
   - **Status:** Added
   - **Changes:** Defined the `LeadPhone` model with fields like lead_id, phone number, label, and primary flag.
   - **Description:** Manages phone numbers linked to leads.
   - **Impact:** Improves lead contact management by allowing multiple phone numbers to be associated with a lead.

8. **File: `app/Models/LeadWebsite.php`**
   - **Status:** Added
   - **Changes:** Created the `LeadWebsite` model with fields like lead_id, URL, and label.
   - **Description:** Stores website URLs associated with leads.
   - **Impact:** Provides a way to store and manage websites related to leads.

9. **File: `database/migrations/2024_06_12_111721_create_leads_table.php`**
   - **Status:** Added
   - **Changes:** Migration for creating the `leads` table with fields for category, name, company, source, other, and lead_lists.
   - **Description:** Sets up the main leads table to store lead data.
   - **Impact:** Establishes the foundational structure for lead management.

10. **File: `database/migrations/2024_06_12_111744_create_lead_lists_table.php`**
    - **Status:** Added
    - **Changes:** Migration to create the `lead_lists` table with fields for name and description.
    - **Description:** Creates a table to store lead lists for categorization.
    - **Impact:** Supports dynamic lead categorization.

11. **File: `database/migrations/2024_06_12_112530_create_lead_notes_table.php`**
    - **Status:** Added
    - **Changes:** Migration to create the `lead_notes` table with fields for lead_id, note, and created_by.
    - **Description:** Table to store notes related to leads.
    - **Impact:** Enhances the ability to track additional information related to leads.

12. **File: `database/migrations/2024_06_12_112629_create_lead_addresses_table.php`**
    - **Status:** Added
    - **Changes:** Migration to create the `lead_addresses` table with various address-related fields.
    - **Description:** Sets up a table for storing address information linked to leads.
    - **Impact:** Supports the addition and maintenance of address data for leads.

13. **File: `database/migrations/2024_06_12_113658_create_lead_emails_table.php`**
    - **Status:** Added
    - **Changes:** Migration to create the `lead_emails` table with fields for lead_id, email, label, and primary flag.
    - **Description:** Creates a table to manage email addresses associated with leads.
    - **Impact:** Enables the storing and retrieval of multiple email addresses for a single lead.

14. **File: `database/migrations/2024_06_12_113826_create_lead_phones_table.php`**
    - **Status:** Added
    - **Changes:** Migration to create the `lead_phones` table with fields for lead_id, phone, label, and primary flag.
    - **Description:** Establishes a table for managing lead phone numbers.
    - **Impact:** Facilitates linking multiple phone numbers to leads, improving contact management.

15. **File: `database/migrations/2024_06_12_113900_create_lead_websites_table.php`**
    - **Status:** Added
    - **Changes:** Migration to create the `lead_websites` table with fields for lead_id, URL, and label.
    - **Description:** Builds a table to store website URLs linked to leads.
    - **Impact:** Allows for detailed tracking of lead-related websites.

16. **File: `database/migrations/2024_06_12_122317_add_lead_id_to_email_statuses_table.php`**
    - **Status:** Added
    - **Changes:** Migration to add a nullable foreign key lead_id to the `email_statuses` table.
    - **Description:** Modifies the existing email statuses table to associate emails with leads.
    - **Impact:** Improves email handling by linking statuses to specific leads.

17. **File: `database/migrations/2024_06_12_153626_create_lead_tempfiles_table.php`**
    - **Status:** Added
    - **Changes:** Migration to create `lead_tempfiles` table with fields like user_id, name, path, category, and status.
    - **Description:** Sets up a table to store temporary lead import files.
    - **Impact:** Facilitates the uploading and processing of lead data files.

18. **File: `database/migrations/2024_06_13_170822_rename_name_column_in_lead_tempfiles_table.php`**
    - **Status:** Added
    - **Changes:** Migration to rename the `name` column to `list_id` in `lead_tempfiles` table.
    - **Description:** Updates the schema to better reflect the usage of the column.
    - **Impact:** Clarifies the purpose of the field, enhancing data organization.

19. **File: `resources/views/admin/components/form-add-lead.blade.php`**
    - **Status:** Added
    - **Changes:** Blade template for the livewire component to render the form for adding a lead.
    - **Description:** Contains form fields for lead creation, leveraging Blade directives and Livewire bindings.
    - **Impact:** Improves UX by providing a user-friendly form for administrators to add new leads.

20. **File: `resources/views/admin/lead/add.blade.php`**
    - **Status:** Added
    - **Changes:** Blade template for the view to add a new lead.
    - **Description:** Wraps the form component within the admin layout.
    - **Impact:** Ensures new UI consistency for lead addition.

21. **File: `app/Actions/Fortify/CreateNewUser.php`**
    - **Status:** Modified
    - **Changes:** Minor formatting and comment adjustments to improve code clarity.
    - **Description:** Enhances the documentation and clarity within the user creation logic.
    - **Impact:** Improves maintainability and readability of the codebase.

22. **File: `app/Http/Controllers/AdminController.php`**
    - **Status:** Modified
    - **Changes:** Added new methods for managing leads, including listing, adding, uploading, mapping, and importing leads.
    - **Description:** Extends the admin functionalities to cover lead management, utilizing various Lead models and views.
    - **Impact:** Enhances admin capabilities, streamlining lead management workflows.

23. **File: `composer.json`**
    - **Status:** Modified
    - **Changes:** Added "phpoffice/phpspreadsheet" as a new dependency.
    - **Description:** Includes the PhpSpreadsheet library to handle lead file imports.
    - **Impact:** Enables the processing of Excel and CSV files for lead data management.

24. **File: `resources/lang/pt_br/admin.php`**
    - **Status:** Modified
    - **Changes:** Updated the Portuguese language file to include translations for new lead-related titles.
    - **Description:** Ensures translated strings are available for the new lead management interface.
    - **Impact:** Improves internationalization support.

25. **File: `resources/views/admin/components/menu.blade.php`**
    - **Status:** Modified
    - **Changes:** Link update to point to the new admin dashboard route.
    - **Description:** Adjusts navigation to reflect route changes.
    - **Impact:** Ensures consistency and correct navigation within the admin panel.

26. **File: `resources/views/admin/components/sidebar.blade.php`**
    - **Status:** Modified
    - **Changes:** Added new sidebar entries for lead management, including sections for lead list, upload, and addition.
    - **Description:** Enhances the sidebar to provide quick navigation to lead management features.
    - **Impact:** Improves overall user navigation and accessibility to new lead features.

27. **File: `app/Http/Controllers/UserController.php`**
    - **Status:** Removed
    - **Changes:** Deleted the `UserController`.
    - **Description:** Consolidated user management functionality into `AdminController` for better organization.
    - **Impact:** Simplifies controller structures and avoids redundancy.

This collection of changes comprehensively enhances the lead management capabilities within the admin panel, providing a robust system for classification, addition, and maintenance of leads. The new UI elements and backend logic cater to a streamlined and efficient lead management workflow.



---


# #126 Automated Email Notification and User Management Updates

## Introduction
This pull request introduces multiple updates and new features to enhance email notification capabilities and user management in the application. The primary objective is to automate email notifications to users for missing setcard videos, improve the facilitation of payouts, and update the administration interface to improve user experience and navigation. These changes impact the application by adding new console commands, notification handlers, database migrations, and improved localization. The updates are categorized as follows:
- New feature additions
- Layout and UI updates
- User notification enhancements
- Database schema adjustments

## Changes Overview
1. **File: `app/Console/Commands/SendmailSetcardVideoMissing.php`**
- **Status:** Added
- **Changes:** Introduces a new console command that sends notifications to creators who have not yet uploaded their setcard videos.
- **Description:** This command queries all users with the role of 'creator' and checks if their setcard video is missing. It then sends an email notification using the `SetcardVideoMissing` notification to users who need to upload their videos.
- **Impact:** Automates the notification process, ensuring that creators are reminded to complete their profiles.

2. **File: `app/Notifications/Creator/SetcardVideoMissing.php`**
- **Status:** Added
- **Changes:** Adds a new notification class designed to send emails via the `Smtp2Go` channel to creators missing their setcard video.
- **Description:** Defines the notification message details and email template for the missing setcard video.
- **Impact:** Enhances communication with users, ensuring important steps like uploading setcard videos are completed.

3. **File: `database/migrations/2024_06_08_131743_add_payoutformat_to_user_payout_details_table.php`**
- **Status:** Added
- **Changes:** Introduces a new database migration to add the `payoutformat` column in the `user_payout_details` table.
- **Description:** Supports different payout formats such as email, phone number, CPF (Brazilian ID), etc.
- **Impact:** Adds more flexibility in handling various payout methods for users.

4. **File: `database/migrations/2024_06_10_180530_add_subject_to_email_statuses_table.php`**
- **Status:** Added
- **Changes:** Adds a new `subject` column to the `email_statuses` table via a migration.
- **Description:** Ensures that the subject of the email is stored along with email status details.
- **Impact:** Enhances record-keeping and email tracking capabilities.

5. **File: `resources/lang/pt_br/admin.php`**
- **Status:** Added
- **Changes:** Adds Portuguese localization for the admin dashboard.
- **Description:** Provides translated strings for various sections of the admin panel.
- **Impact:** Improves accessibility for Portuguese-speaking users.

6. **File: `resources/views/admin/user/index.blade.php`**
- **Status:** Added
- **Changes:** Introduces a new blade view for displaying user information in the admin panel.
- **Description:** Lists users with various details and provides an interface for admin activities.
- **Impact:** Enhances the admin’s ability to manage and oversee users effectively.

7. **File: `app/Channels/Smtp2GoChannel.php`**
- **Status:** Modified
- **Changes:** Adds a line to save the subject of the email in the email status.
- **Description:** Updates the Smtp2GoChannel to store the email subject in the database for better tracking.
- **Impact:** Improves the detailed logging and metadata available for sent emails.

8. **File: `app/Console/Commands/SendmailNewApplications.php`**
- **Status:** Modified
- **Changes:** Corrects a namespace for the `NewApplications` notification.
- **Description:** Ensures the correct namespace is used for importing the `NewApplications` notification class.
- **Impact:** Fixes potential notification sending issues due to incorrect namespace.

9. **File: `app/Console/Kernel.php`**
- **Status:** Modified
- **Changes:** Schedules the new `sendmail:setcard-video-missing` command to run every six hours.
- **Description:** Ensures periodic reminders are sent to users who need to upload their setcard videos.
- **Impact:** Enhances automation and consistency in user communication.

10. **File: `app/Http/Controllers/AdminController.php`**
- **Status:** Modified
- **Changes:** Adds methods for the admin dashboard and user index.
- **Description:** Facilitates the rendering of new admin dashboard views and user management pages.
- **Impact:** Improves admin functionalities and system navigation.

11. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** Updates namespace references for order-related notifications.
- **Description:** Ensures notifications are sent using the correct namespaces.
- **Impact:** Fixes potential issues in the notification system related to orders.

12. **File: `app/Listeners/SendWelcomeEmailToCreator.php`**
- **Status:** Modified
- **Changes:** Updates the namespaces for welcome notifications.
- **Description:** Corrects the namespaces to ensure welcome emails to creators and businesses are sent correctly.
- **Impact:** Ensures accurate delivery of welcome emails.

13. **File: `app/Livewire/UpdateCreatorPayoutForm.php`**
- **Status:** Modified
- **Changes:** Adds support for various payout formats and validates them.
- **Description:** Ensures payout detail inputs are correctly validated and formatted.
- **Impact:** Enhances user experience by guiding them through the payout information correctly.

14. **File: `app/Models/UserPayoutDetails.php`**
- **Status:** Modified
- **Changes:** Adds the `payoutformat` field to the fillable attributes.
- **Description:** Allows mass assignment of the new `payoutformat` field.
- **Impact:** Supports additional payout formats in the system.

15. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** Updates translations and changes some terms related to the dashboard.
- **Description:** Corrects and improves Portuguese translations.
- **Impact:** Ensures better localization and user understanding.

16. **File: `resources/lang/pt_br/email.php`**
- **Status:** Modified
- **Changes:** Adds new email templates and updates existing ones for notifications.
- **Description:** Provides detailed and localized email templates for user notifications.
- **Impact:** Improves communication quality with users.

17. **File: `resources/lang/pt_br/profile.php`**
- **Status:** Modified
- **Changes:** Updates various profile-related translations and payout information.
- **Description:** Enhances the profile section with improved localization.
- **Impact:** Provides a better user experience for Portuguese-speaking users.

18. **File: `resources/lang/pt_br/validation.php`**
- **Status:** Modified
- **Changes:** Updates phone number validation example and other related messages.
- **Description:** Ensures validation messages are clear and accurate.
- **Impact:** Improves the user’s ability to understand validation errors.

19. **File: `resources/views/admin/components/menu.blade.php`**
- **Status:** Modified
- **Changes:** Simplifies and reorganizes the admin menu layout.
- **Description:** Enhances user experience and navigation within the admin panel.
- **Impact:** Makes the admin interface more intuitive and user-friendly.

20. **File: `resources/views/admin/components/sidebar.blade.php`**
- **Status:** Modified
- **Changes:** Adjusts the sidebar structure and adds additional menu items.
- **Description:** Improves the navigation within the admin panel by providing a more organized sidebar with clear sections.
- **Impact:** Enhances overall usability for admin users.

21. **File: `resources/views/admin/dashboard.blade.php`**
- **Status:** Modified
- **Changes:** Updates the dashboard layout to reflect new statistics and widgets.
- **Description:** Provides a more detailed and interactive dashboard for admin users.
- **Impact:** Offers better insights and actionable information for administrators.

22. **File: `app/Livewire/MenuAdmin.php`**
- **Status:** Renamed to `app/Livewire/Admin/Menu.php`
- **Changes:** Adjusted namespace to reflect the new folder structure.
- **Description:** Organizes admin-related components under the same namespace for better code management.

23. **File: `app/Livewire/SidebarAdmin.php`**
- **Status:** Renamed to `app/Livewire/Admin/Sidebar.php`
- **Changes:** Adjusted namespace to reflect the new folder structure.
- **Description:** Ensures the proper organization of admin components.

24. **File: `app/Notifications/NewApplications.php`**
- **Status:** Renamed to `app/Notifications/Business/NewApplications.php`
- **Changes:** Adjusted namespace for better organization.
- **Description:** Maintains orderly and logical namespace structure for notifications.

25. **File: `app/Notifications/OrderCompleted.php`**
- **Status:** Renamed to `app/Notifications/Business/OrderCompleted.php`
- **Changes:** Adjusted namespace for better organization.

26. **File: `app/Notifications/WelcomeBusiness.php`**
- **Status:** Renamed to `app/Notifications/Business/WelcomeBusiness.php`
- **Changes:** Adjusted namespace for better organization.

27. **File: `app/Notifications/ApplicationApproved.php`**
- **Status:** Renamed to `app/Notifications/Creator/ApplicationApproved.php`
- **Changes:** Adjusted namespace for better organization.

28. **File: `app/Notifications/WelcomeCreator.php`**
- **Status:** Renamed to `app/Notifications/Creator/WelcomeCreator.php`
- **Changes:** Adjusted namespace for better organization.

29. **File: `resources/views/admin_old/blog/create.blade.php`**
- **Status:** Renamed from `resources/views/admin/blog/create.blade.php`
- **Changes:** Changed layout component to `x-adminold-layout` to differentiate from updated admin layout.
- **Description:** Uses the old admin layout for the blog create view.

30. **File: `resources/views/admin_old/blog/edit.blade.php`**
- **Status:** Renamed from `resources/views/admin/blog/edit.blade.php`
- **Changes:** Changed layout component to `x-adminold-layout`.
- **Description:** Uses an old admin layout for the blog edit view.


---

# #125 Update to Improve SEO, Accessibility, and User Experience

## Introduction
In this pull request, several updates and modifications have been made to enhance the application's functionality, security, user experience, and overall architecture. The main areas of changes include SEO optimization, accessibility improvements, and user interface adjustments. These changes are aimed at improving the visibility of the site in search engines, ensuring the application is more accessible to users with disabilities, and providing a better user experience.

## Changes Overview

1. **File: `resources/lang/pt_br/auth.php`**
- **Status:** Modified
- **Changes:** Added a new translation key `'title2' => 'Registre-se'`.
- **Description:** A new key was added to provide an additional translation for the register title.
- **Impact:** This addition can help display different titles in various contexts, improving the flexibility of the application.

2. **File: `resources/views/blog/index.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Updated the `alt` attribute for post images to use the post title.
  - Updated the `alt` attribute for the author’s profile image to use the author's first name.
- **Description:** These changes improve SEO by providing meaningful `alt` text to images, which aids search engine indexing and improves accessibility for screen readers.
- **Impact:** Enhanced SEO and improved accessibility for users utilizing screen readers.

3. **File: `resources/views/blog/single-page.blade.php`**
- **Status:** Modified
- **Changes:**
  - Modified the `metaDescription` slot to utilize the post’s SEO description.
  - Commented out the `metaKeywords` slot with placeholder text.
- **Description:** This change allows for dynamic meta descriptions based on post content, enhancing the SEO of individual blog pages.
- **Impact:** Better SEO performance for individual posts which can translate to higher search engine rankings.

4. **File: `resources/views/components/password-revealer.blade.php`**
- **Status:** Modified
- **Changes:**
  - Added meaningful `alt` text ("Eye" and "Eye Slash") to the password reveal/hide icons.
- **Description:** The update provides appropriate `alt` attributes to the icons, which improves accessibility.
- **Impact:** Enhanced usability for visually impaired users who rely on screen readers.

5. **File: `resources/views/index.blade.php`**
- **Status:** Modified
- **Changes:**
  - Updated the `alt` attribute for the latest post images to use the post title.
  - Updated the `alt` attribute for the author’s profile image to use the author's first name.
- **Description:** Similar to the changes in the blog index, these updates improve SEO and accessibility by providing meaningful `alt` text.
- **Impact:** Improved SEO and better accessibility for visually impaired users.

6. **File: `resources/views/register.blade.php`**
- **Status:** Modified
- **Changes:**
  - Dynamically set the page title using translation keys and config values within a PHP block.
- **Description:** This adjustment allows for a dynamic and translated page title for the registration page, which improves the user experience for non-English users.
- **Impact:** Enhanced internationalization support with more descriptive and locale-specific page titles.

These updates collectively enhance the application’s functionality and user experience significantly by prioritizing SEO and accessibility features. The changes are backward-compatible and should not interfere with existing functionalities.

---

# #124 Sitemap Update for Daily Frequency and High Priority

## Introduction
This pull request involves a modification to the `GenerateSitemap` command in the application's console commands. Specifically, it enhances the sitemap generation process to set a daily update frequency and a high priority for the URLs included in the sitemap. These changes aim to improve the discoverability and relevance of the application's web pages to search engines, ultimately benefiting SEO efforts.

## Changes Overview

1. **File: `app/Console/Commands/GenerateSitemap.php`**
   - **Status:** Modified
   - **Changes:** Added three lines to set the change frequency and priority of sitemap URLs.
   - **Description:** 
     - The new code sets the change frequency of URLs to daily using `$url->setChangeFrequency(Url::CHANGE_FREQUENCY_DAILY);`.
     - It also sets the priority of the URLs to 0.8 with `$url->setPriority(0.8);`.
   - **Impact:** 
     - **SEO Improvement:** By indicating to search engines that the site's content is updated daily, search engines are more likely to visit and index the site regularly.
     - **Priority Setting:** Assigning a higher priority to the URLs can direct search engines to consider these URLs as more significant compared to others with lower priority, potentially improving their ranks in search results.
     - **Code Maintainability:** The changes are small and localized, minimizing potential for conflicts or issues with existing functionality.

---

# #123 Improved Website Sitemap, Asset Path Updates, and Code Enhancements

## Introduction
This pull request introduces several key updates aimed at improving our website's SEO, user experience, and maintainability of the codebase. A new sitemap is added to better index our pages, multiple updates are made to the application to ensure consistency in asset references, and an enhancement to the current sitemap generation command.

## Changes Overview

1. **File: `public/sitemap.xml`**
- **Status:** Added
- **Changes:** Addition of an XML file containing sitemap information for various URLs within the website.
- **Description:** This sitemap includes URL entries for pages like the homepage, login, register, and several blog posts.
- **Impact:** Enhances our search engine optimization (SEO) by helping search engines crawl and index various pages effectively.

2. **File: `app/Console/Commands/GenerateSitemap.php`**
- **Status:** Modified
- **Changes:** Updates include refactoring the sitemap generation logic, excluding specific paths like `/register` and the homepage, and directly adding a URL for `/registrar-criador`.
- **Description:** Streamlines the process for generating the sitemap, ensuring that unneeded routes like OAuth and the homepage are not included, and programmatically adds an important route.
- **Impact:** These changes ensure more relevant and targeted pages are included in the sitemap, further improving SEO and crawl efficiency.

3. **File: `resources/views/components/application-mark.blade.php`**
- **Status:** Modified
- **Changes:** Updated image source paths to move from the root to the `/img` directory.
- **Description:** Standardizes the asset paths to ensure all image references consistently use the `/img` directory, potentially making asset management easier.
- **Impact:** Improves consistency in how assets are referenced and may reduce the likelihood of broken links.

4. **File: `resources/views/components/authentication-card-logo.blade.php`**
- **Status:** Modified
- **Changes:** Updated paths of logo images to reflect the new structure under the `/img` directory.
- **Description:** Ensures the dark mode and light mode logos are correctly referenced.
- **Impact:** Enhances the user interface by ensuring that the logos are correctly displayed.

5. **File: `resources/views/emails/layout.blade.php`**
- **Status:** Modified
- **Changes:** Updated the email logo image path to point to the `/img` directory.
- **Description:** Adjusts the email layout to reflect the new path structure for embedded images.
- **Impact:** Ensures that email layouts remain consistent and that images load correctly for recipients.

6. **File: `resources/views/errors/503.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted the logo path in the 503 error page to use the `/img` directory.
- **Description:** Updates the image path used during the 503 Service Unavailable error page.
- **Impact:** Guarantees that the correct branding is used even when the site is down, providing a consistent user experience.

7. **File: `resources/views/layouts/errors.blade.php`**
- **Status:** Modified
- **Changes:** Changed the logo image path to use the new `/img` directory.
- **Description:** Ensures the correct image path is used in the main error layout file.
- **Impact:** Maintains consistent branding and reduces the likelihood of broken images in error states.

8. **File: `resources/views/register.blade.php`**
- **Status:** Modified
- **Changes:** Updates the registration page to point to the new logo paths in the `/img` directory.
- **Description:** Aligns the registration page's image paths with the new structured directory.
- **Impact:** Enhances user experience by ensuring all images are correctly referenced and displayed.

9. **File: `resources/views/vendor/mail/html/layout.blade.php`**
- **Status:** Modified
- **Changes:** Updated the email template to use new image paths under `/img`.
- **Description:** Adjusts the email templates to maintain consistency in image references.
- **Impact:** Enhances branding within email communications ensuring the images are correctly shown.

In summary, these changes focus on optimizations for search engine indexing, consistent asset referencing across the application, and a slight enhancement to the sitemap generation command to make it more efficient and targeted.

---

# #122 Pull Request Summary

## Improved Profile Photo Handling and UI Enhancements

## Introduction
This pull request includes several updates focusing on improving profile photo handling and enhancing the user interface in specific areas of the application. The changes made aim to provide a better experience for users by ensuring that profile photos are correctly displayed and default placeholders are generated when necessary. This also includes some minor optimizations in the use of avatar images in various UI components, enhancing the visual consistency and functionality.

## Changes Overview
1. **File: `app/Models/User.php`**
   - **Status:** Modified
   - **Changes:** 
     - Added a new method `defaultProfilePhotoUrl` to generate a default profile photo URL if no profile photo is provided.
   - **Description:** 
     - The `defaultProfilePhotoUrl` method constructs a URL to a service that generates placeholder images based on the user's first and last name.
   - **Impact:** 
     - Ensures that every user has a profile photo even if they have not uploaded one, improving the visual consistency across the application.

2. **File: `resources/js/crispChat.js`**
   - **Status:** Modified
   - **Changes:** 
     - Simplified the logic by always setting the user's avatar with `Crisp.user.setAvatar(window.user.avatar)`.
   - **Description:** 
     - Removed the conditional check and redundant code, making sure the avatar setting logic is consistent.
   - **Impact:** 
     - Streamlines avatar handling in the Crisp chat integration, ensuring that the avatar is always set correctly.

3. **File: `resources/views/blog/index.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Updated the profile image element's class to use `flex-shrink-0` for better handling of object sizing.
   - **Description:** 
     - Changed the CSS class from `flex-none` to `flex-shrink-0` and added `object-cover` to ensure the profile images are displayed correctly within their container.
   - **Impact:** 
     - Enhances the visual appearance of author profile photos in blog posts, ensuring they are displayed consistently.

4. **File: `resources/views/layouts/partials/head.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Enhanced the script that sets the window user object to include a default avatar path if none exists.
   - **Description:** 
     - The script now assigns a fallback avatar image from the assets if the user's profile photo path is not set.
   - **Impact:** 
     - Ensures that even users without a custom uploaded profile picture have an avatar shown in the UI, improving user experience.

5. **File: `resources/views/profile/avatar-upload.blade.php`**
   - **Status:** Modified
   - **Changes:** 
     - Adjusted the default profile photo URL to dynamically incorporate the user's first and last name.
     - Simplified condition checks related to the profile photo uploader.
   - **Description:** 
     - The changes ensure that the default avatar URL includes the correct user name parameters and refactor the conditions for previewing the profile picture.
   - **Impact:** 
     - Improves the accuracy and consistency of profile photo displays, both default and user-uploaded, making the avatar upload component more reliable and user-friendly.

These changes collectively enhance the consistency and reliability of user profile photo handling across various parts of the application, providing a better end-user experience and maintaining the visual integrity of the application's UI elements.

---

# #121 Addition of Crisp Chat Webhook Handler and User Avatar Integration

## Introduction
This pull request introduces multiple significant changes to the application, including a new webhook handler, enhancements to the user chat functionalities, and minor UI adjustments. These changes are categorized under new feature additions and UI/UX enhancements. The key areas affected include webhook integration, user profile handling in Crisp Chat, and conditional UI display logic. 

## Changes Overview
1. **File: `app/Http/Controllers/WebhookController.php`**
- **Status:** Modified
- **Changes:** Added a new method `crisp_webhook` to handle POST requests.
   ```php
   public function crisp_webhook(Request $request)
   {
       $data = $request->all();

       Webhook::create([
           'source' => 'crisp.chat',
           'webhook' => json_encode($data),
       ]);
   }
   ```
- **Description:** The changes add a new endpoint for handling Crisp Chat webhook events, saving received data into the database.
- **Impact:** Enhances the system's ability to interact with Crisp Chat by logging webhook events, improving monitoring and integrations with third-party services.

2. **File: `resources/js/crispChat.js`**
- **Status:** Modified
- **Changes:** Added logic to set the user's avatar in Crisp Chat if it exists.
   ```javascript
   if (window.user.avatar) {
       Crisp.user.setAvatar(window.user.avatar);
   }
   ```
- **Description:** Enhanced the Crisp Chat user initialization by including the user's avatar to provide a more personalized chat experience.
- **Impact:** Improves user interaction and experience on the chat platform by displaying the user's avatar, contributing to personalized communications.

3. **File: `resources/views/dashboard/creator/dashboard.blade.php`**
- **Status:** Modified
- **Changes:** Changed the condition for open orders display from fewer than 5 to fewer than 1.
   ```php
   @if ($openorders < 1)
   ```
- **Description:** Adjusted the condition to show a specific UI element only when there are no open orders.
- **Impact:** Improves UX by ensuring that the element is displayed only when truly relevant (no open orders), potentially reducing unnecessary UI clutter.

4. **File: `resources/views/layouts/partials/head.blade.php`**
- **Status:** Modified
- **Changes:** Updated the embedded JavaScript to include the user's avatar URL.
   ```javascript
   <script>window.user={... ,avatar:"{{ Storage::disk('s3')->url(Auth::user()->profile_photo_path) }}"};</script>
   ```
- **Description:** The script was modified to pass the user's avatar URL, retrieved from the S3 storage, to the global `user` object.
- **Impact:** Ensures that the user's avatar can be used throughout the application, improving integration with third-party services like Crisp Chat.

5. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** Added a route for handling Crisp Chat webhook events.
   ```php
   Route::post('/webhook/crisp/events', [WebhookController::class, 'crisp_webhook']);
   ```
- **Description:** The new route points to the `crisp_webhook` method in the `WebhookController`.
- **Impact:** Expands the application's webhook handling capabilities, allowing it to process events from Crisp Chat, thereby enhancing interoperability with external services.

---

# #120 Update to Pricing Information in PublicPagesController

## Introduction
This pull request involves a minor yet impactful change to the pricing information within the application's frontend. Specifically, there is an update to the pricing details displayed on the public-facing pages of the application. This change aims to reflect the new pricing strategy and ensure that potential customers receive the most accurate and recent information. By modifying the price value in the controller, the application now presents the updated cost for a service plan, which is crucial for maintaining transparency and trust with users.

## Changes Overview
1. **File: `app/Http/Controllers/PublicPagesController.php`**
- **Status:** Modified
- **Changes:** The `price` attribute for a 30-minute duration in the controller has been updated from `119` to `199`.
- **Description:** The single change within this file updates the price of a specific service plan. This adjustment seems to reflect a new pricing model or correction of previously incorrect data.
- **Impact:** This modification impacts the public-facing pricing page, ensuring that customers see the new price. This change is critical for accurate billing and can affect current sales and customer satisfaction as it directly influences their purchasing decision. It also maintains alignment with the company's updated pricing strategy, which might have implications for revenue and market positioning.

Overall, by reviewing and merging this pull request, the team ensures the latest pricing is accurately represented, avoiding potential misunderstandings or miscommunications with users.

---

# #119 Simplification of Route Definitions in `web.php`

## Introduction
This pull request focuses on simplifying the route definitions in the `web.php` file for the application's public pages. The primary change involves the removal of environment-specific conditional statements which previously altered the routing behavior based on the application's environment (production or otherwise). This modification aims to streamline the routing logic, thereby making the codebase cleaner, easier to manage, and consistent across different environments. 

## Changes Overview
1. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:**
  - Removed the conditional statement that checked whether the application was in production.
  - Unified the route definition for the root URL (`'/'`) to always route to the `index` method of the `PublicPagesController`.
- **Description:**
  - Previously, the routing logic for the root URL varied based on the application's environment. If the environment was set to production, the root URL would show a 503 error page. Otherwise, it would route to the `index` method of the `PublicPagesController`.
  - The new logic simplifies this to always use the `index` method of the `PublicPagesController`, regardless of the environment.
- **Impact:**
  - **Functionality:** This change ensures that the root URL always shows the public index page, eliminating the special case for the production environment.
  - **Code Maintainability:** Removing environment-specific conditions simplifies the routing logic, making the codebase easier to read and maintain.
  - **User Experience:** Users will no longer encounter a 503 error page in the production environment when accessing the root URL, providing a more consistent user experience across environments.

---

# #118 Addition of Crisp Chat Integration and UI Improvements on Dashboard

## Introduction
This pull request includes the integration of the Crisp Chat SDK to enhance customer support functionalities alongside some updates to the user interface on the dashboard particularly for the creator dashboard views. The changes encapsulate new feature additions primarily for improved user engagement through chat functionality, and minor modifications for better user experience handling jobs and job statuses. These improvements will likely have impacts on user satisfaction due to the added communication channel and improved clarity in UI components.

## Changes Overview

1. **File: `resources/js/crispChat.js`**
   - **Status:** Added
   - **Changes:** New file with Crisp SDK initialization and user data setup.
   - **Description:**
     - Imported the Crisp SDK.
     - Configured Crisp with application key.
     - Set user-related information (UUID, email, name, role) if a user is authenticated.
   - **Impact:**
     - Introduces a new chat capability for logged-in users, providing them immediate access to support.
     - User-specific data helps in personalizing the support interaction.

2. **File: `package.json`**
   - **Status:** Modified
   - **Changes:** Added Crisp SDK dependency.
   - **Description:**
     - Included `"crisp-sdk-web": "^1.0.25"` in the `dependencies` section.
   - **Impact:**
     - Ensures that the Crisp SDK is available for use within the project, enabling the new chat functionalities.

3. **File: `resources/js/app.js`**
   - **Status:** Modified
   - **Changes:** Imported the new `crispChat.js` file.
   - **Description:**
     - Added the Crisp Chat integration script to the main application JavaScript file.
   - **Impact:**
     - Ensures that the chat functionalities are loaded whenever the app's JavaScript is executed, activating the chat feature across the application where needed.

4. **File: `resources/views/dashboard/creator/dashboard.blade.php`**
   - **Status:** Modified
   - **Changes:** Enhanced UI components and messaging.
   - **Description:**
     - Added a dropdown for tab selection on smaller screens.
     - Adjusted conditional logic to display messages based on job count thresholds.
     - Included motivating and informative message for users with less than 5 open orders, as opposed to the previous plain message.
   - **Impact:**
     - Improves the responsiveness and user-friendliness of the dashboard.
     - Provides clarity and encouragement to users, potentially increasing their engagement and retention.

5. **File: `resources/views/layouts/partials/head.blade.php`**
   - **Status:** Modified
   - **Changes:** Introduced user data script for authenticated users.
   - **Description:**
     - Added a script block that sets up a global `window.user` object with authenticated user’s data.
   - **Impact:**
     - Facilitates the Crisp SDK and possibly other scripts to access user information easily, improving personalization of services and user experience.

---

# #117 Allow Orders with Status 'CONCLUÍDO' to Access Progress Route

## Introduction
This pull request modifies the logic within the `OrderProcessController` to enhance the functionality of order handling by allowing orders that are marked as "CONCLUÍDO" (completed) to access the progress route. Previously, only orders with the status "EM PRODUÇÃO" (in production) could access this route. This change aims to improve user experience and workflow for order management by expanding the access conditions. It ensures that completed orders can also follow the same process route without encountering unnecessary restrictions.

## Changes Overview
1. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:**
  ```diff
  -        if ($order->status === 'EM PRODUÇÃO') {
  +        if ($order->status === 'EM PRODUÇÃO' || $order->status === 'CONCLUÍDO') {
  ```
- **Description:** 
  - The condition in the if-statement has been expanded.
  - Previously, only orders with the status 'EM PRODUÇÃO' (in production) could be redirected to the `orders.progress` route.
  - Now, orders with the status 'CONCLUÍDO' (completed) are also included.
  
- **Impact:**
  - **User Experience:** Enhances user experience by allowing broader access to the order progress page. Users can now track the progress even after the order is completed.
  - **Functionality:** Provides seamless transition and access after order completion, ensuring users are not restricted unnecessarily.
  - **Workflow Improvement:** Assists in better tracking and management of the order lifecycle from production to completion.

---

# #116 Pull Request Overview: Update Order Processing Conditions in OrderProcessController

## Introduction
This pull request includes a small but critical change aimed at improving the logic governing order processing within the `OrderProcessController`. By updating the conditions that determine whether an order can be progressed, the enhancement ensures that only orders with specific statuses can proceed, thereby enhancing the application's reliability and accuracy in order handling. 

## Changes Overview
1. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** Updated the condition check in the `progress` method to include a new status `'CONCLUÍDO'`.
    ```diff
    - if ($order->status != 'EM PRODUÇÃO' && $order->status != 'ESCOLHA O CRIADOR') {
    + if ($order->status != 'CONCLUÍDO' && $order->status != 'EM PRODUÇÃO' && $order->status != 'ESCOLHA O CRIADOR') {
    ```
- **Description:** The condition to check order statuses was enhanced by adding `CONCLUÍDO` to ensure that orders in this new status are also processed correctly. This allows the system to differentiate more precisely between orders that require action and those that do not.
- **Impact:** 
   - **Functionality:** Enhances the accuracy of order progress conditions, preventing orders that are 'CONCLUÍDO' from incorrectly triggering further processing actions.
   - **User Experience:** Users will experience fewer errors and a smoother operation flow when processing orders that are completed.
   - **System Reliability:** Reduces the risk of logical errors in order processing, ensuring better system stability and more predictable behavior.

---

# #115 Rename and Standardize Database Models, Adjust Model Properties, and Improve UI Consistency

## Introduction
This pull request entails several key modifications spanning database migrations, model adjustments, and user interface enhancements. The primary changes involve renaming and standardizing database model names for consistency, updating model properties to align with the new database schema, refining the translations within the application, and enhancing the UI for better usability. These changes ensure uniform database naming conventions, improve code maintainability, and enhance the user experience by providing clearer feedback and consistent layout adjustments.

## Changes Overview
1. **File: `database/migrations/2024_06_07_125230_rename_users_paymentdetails_to_users_cards.php`**
- **Status:** Added
- **Changes:** This migration script renames several tables in the database to standardize and simplify the naming conventions.
- **Description:** The script renames tables such as `users_paymentdetails` to `user_cards`, `users_address` to `user_addresses`, and other similar table renames.
- **Impact:** The renaming strengthens the consistency and readability of table names, making it easier to manage and maintain. It also affects any model or code references to these tables, requiring updates to ensure proper functionality.

2. **File: `app/Models/BlogPost.php`**
- **Status:** Modified
- **Changes:** Added `protected $table = 'blog_posts';` and updated the `$fillable` property.
- **Description:** Ensuring the model explicitly defines the table it references and updating the fields that can be mass assigned.
- **Impact:** Increases the clarity by explicitly setting the table and protects against mass assignment vulnerabilities.

3. **File: `app/Models/Contact.php`**
- **Status:** Modified
- **Changes:** Added `protected $table = 'contacts';`
- **Description:** Specifies the associated table for this model.
- **Impact:** Enhances clarity and avoids potential issues if Laravel's default naming convention is different.

4. **File: `app/Models/DesignView.php`**
- **Status:** Modified
- **Changes:** Added `protected $table = 'design_views';`
- **Description:** Specifies the table association explicitly.
- **Impact:** Reduces ambiguity and potential errors related to table naming assumptions.

5. **File: `app/Models/Faq.php`**
- **Status:** Modified
- **Changes:** Added `protected $table = 'faqs';`
- **Description:** Explicitly states the table for the `Faq` model.
- **Impact:** Improves code readability and maintainability.

6. **File: `app/Models/NewsletterSubscriber.php`**
- **Status:** Modified
- **Changes:** Updated table name in `protected $table = 'newsletter_subscribers';`
- **Description:** Reflects the renaming of the table in the migration script.
- **Impact:** Ensures the model operates correctly with the renamed table.

7. **File: `app/Models/OrderCobranca.php`**
- **Status:** Modified
- **Changes:** Updated table name to `protected $table = 'order_cobrancas';`
- **Description:** Aligns with new database naming conventions.
- **Impact:** Maintains functionality with the renamed table.

8. **File: `app/Models/User.php`**
- **Status:** Modified
- **Changes:** Updated payment relationship to reference `UserCard` instead of `UserPaymentDetail`.
- **Description:** Reflects the renaming of the related model.
- **Impact:** Ensures relational integrity and accurate model relationships.

9. **File: `app/Models/UserAddress.php`**
- **Status:** Modified
- **Changes:** Updated table name to `protected $table = 'user_addresses';`
- **Description:** Follows standardized naming conventions.
- **Impact:** Maintains the correct association with the renamed table.

10. **File: `app/Models/UserAsaas.php`**
- **Status:** Modified
- **Changes:** Updated table name to `protected $table = 'user_asaas';`
- **Description:** Aligns model with new table names.
- **Impact:** Ensures model functionality with renamed database tables.

11. **File: `app/Models/UserCnpj.php`**
- **Status:** Modified
- **Changes:** Updated table name to `protected $table = 'user_cnpjs';`
- **Description:** Reflects table renaming for consistency.
- **Impact:** Guarantees proper model-table association.

12. **File: `app/Models/UserContaAzul.php`**
- **Status:** Modified
- **Changes:** Updated table name to `protected $table = 'user_conta_azuls';`
- **Description:** Corresponding changes to support new naming scheme.
- **Impact:** Maintains accurate references to the database.

13. **File: `app/Models/UserCpf.php`**
- **Status:** Modified
- **Changes:** Updated table name to `protected $table = 'user_cpfs';`
- **Description:** Matches new naming conventions.
- **Impact:** Ensures continued functionality with the renamed table.

14. **File: `app/Models/UserPayoutDetails.php`**
- **Status:** Modified
- **Changes:** Updated table name to `protected $table = 'user_payout_details';`
- **Description:** Aligns with the standardized naming.
- **Impact:** Corrects the table reference following the renaming migration.

15. **File: `app/Models/UserSetcardVideo.php`**
- **Status:** Modified
- **Changes:** Updated table name to `protected $table = 'user_setcard_videos';`
- **Description:** Adjusts to the new database table name.
- **Impact:** Prevents issues due to incorrect table references.

16. **File: `app/Models/UserSocialMedia.php`**
- **Status:** Modified
- **Changes:** Updated table name to `protected $table = 'user_social_media';`
- **Description:** Reflects the table's renaming.
- **Impact:** Maintains model integrity and functionality.

17. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** Multiple updates to translation strings.
- **Description:** Provides more accurate and user-friendly messages in the UI.
- **Impact:** Enhances the user experience for Portuguese-speaking users.

18. **File: `resources/views/dashboard/business/order/applications.blade.php`**
- **Status:** Modified
- **Changes:** Improved blade template for applications, including messages for no applications and language adjustments.
- **Description:** Provides a more informative interface when no applications are present.
- **Impact:** Offers better user guidance and enhances the interface.

19. **File: `resources/views/dashboard/business/order/livewire/briefing.blade.php`**
- **Status:** Modified
- **Changes:** UI refinements for the briefing section.
- **Description:** Improved alignment and usability of elements.
- **Impact:** Better user experience with clearer UI elements.

20. **File: `resources/views/dashboard/business/order/livewire/modal-briefing.blade.php`**
- **Status:** Modified
- **Changes:** Minor adjustments for improved UI consistency.
- **Description:** Enhances the modal's layout and functionality.
- **Impact:** Provides clearer, more intuitive interactions.

21. **File: `resources/views/dashboard/components/order-chat.blade.php`**
- **Status:** Modified
- **Changes:** Adjusted message and icon displays.
- **Description:** Ensures consistent naming and better display logic.
- **Impact:** Clearer communication and improved user interface elements.

22. **File: `resources/views/dashboard/creator/dashboard.blade.php`**
- **Status:** Modified
- **Changes:** Added and reorganized tabs and sections related to orders.
- **Description:** Improved structure and user feedback for different order states.
- **Impact:** Better navigation and clearer understanding of order statuses for users.

23. **File: `resources/views/dashboard/creator/task/progress.blade.php`**
- **Status:** Modified
- **Changes:** Enhanced user feedback and added progress tracking details.
- **Description:** Improved feedback mechanisms and better progress indicators.
- **Impact:** Users receive more timely and clear updates on task progress.

24. **File: `resources/views/layouts/partials/head.blade.php`**
- **Status:** Modified
- **Changes:** Added Crisp chat client script.
- **Description:** Integrates Crisp chat for better user communication.
- **Impact:** Enhanced customer support capabilities through live chat.

25. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** Removed unnecessary newline characters.
- **Description:** Minor cleanup for better readability.
- **Impact:** No functional impact, just improved code cleanliness.

26. **File: `app/Models/UserCard.php`** (formerly `UserPaymentDetail.php`)
- **Status:** Renamed
- **Changes:** Renamed class from `UserPaymentDetail` to `UserCard` and updated the table name accordingly.
- **Description:** Reflects the updated table name and standardizes model naming.
- **Impact:** Ensures the model correctly references the new table name, maintaining data integrity and application functionality.

---

# #114 Title: Enhancement of Profile UI and Refactoring Form-Section Component

## Introduction
This pull request primarily focuses on enhancing the user interface of the profile section and refactoring the form-section component in our application. The changes aim to improve the visual presentation and code maintainability, ensuring a more robust and intuitive user experience. Key areas affected by these changes include the profile form, the static profile update section, and the visibility logic within form sections. These updates are designed to enhance user interaction with the system while ensuring code clarity and maintainability.

## Changes Overview

1. **File: `resources/views/components/form-section.blade.php`**
    - **Status:** Modified
    - **Changes:** Added a conditional wrapper around the `x-section-title` component to prevent rendering empty title and description slots unless they are provided.
    - **Description:** The `x-section-title` component is now conditionally rendered only if the title and description are not empty. This eliminates unnecessary rendering of empty elements, thereby improving the clarity and efficiency of the UI.
    - **Impact:** This change enhances the code's readability and ensures that the UI remains clean and intuitive by not displaying empty title and description sections, which improves user experience by reducing visual clutter.

2. **File: `resources/views/profile/setcard.blade.php`**
    - **Status:** Modified
    - **Changes:** Added a new subtitle and descriptive text sections, and included conditional rendering for the profile photo upload component.
    - **Description:** New subsections such as a subtitle and a descriptive paragraph have been integrated at the top of the profile setcard, providing explicit guidance and context to users while they update their profile. Moreover, conditional rendering for the profile photo upload is incorporated by checking if the application manages profile photos using Laravel Jetstream.
    - **Impact:** These UI enhancements lead to a better user experience by providing clear instructions and context. The conditional profile photo upload ensures that only applicable users (based on the application's settings) see the option, thereby simplifying the interface and reducing potential confusion.

3. **File: `resources/views/profile/update-profile-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Removed subtitle and description slots from the `x-form-section` component and adjusted padding styles.
    - **Description:** By removing redundant slots for subtitles and descriptions, the form component is simplified, reducing unnecessary complexity. Padding styles have been refined to maintain consistent spacing, resulting in a cleaner and more organized UI.
    - **Impact:** The simplification aids in the maintenance of the form section's codebase and ensures a consistent user interface. Adjusting the padding styles contributes to a more visually appealing layout, which can enhance user satisfaction and engagement.

These changes collectively aim to refine the application's user interface, making it more user-friendly and maintainable while also improving the overall performance by reducing unnecessary component renders.

---

# #113 Simplification and Refinement of Profile Management and Removal of Deprecated Price Controller

## Introduction
This pull request primarily focuses on the following key areas:
- Code refinement and simplification of the `UpdateProfileForm` component.
- UI/UX improvement in the header by refining the user data sent to the analytics script.
- Removal of outdated or unnecessary code and features.
- Enhancement to user experience by removing redundant components.

 This update touches crucial parts of the profile management where simplicity and efficiency were priorities. The changes not only improve code readability but also streamline some processes, potentially resulting in enhanced application performance and maintenance.

## Changes Overview
1. **File: `app/Livewire/UpdateProfileForm.php`**
  - **Status:** Modified
  - **Changes:** Removed the try-catch block and streamlined the update process.
  - **Description:** 
    - Simplified the `updateInformation` method by removing the try-catch block. 
    - The exception handling was removed, assuming that the validation will prevent any potential errors that need catching.
  - **Impact:** This modification could improve code readability and maintainability, but potential runtime errors related to user data updates will no longer be caught and handled gracefully, potentially affecting the user experience in certain situations.

2. **File: `resources/views/layouts/partials/head.blade.php`**
  - **Status:** Modified
  - **Changes:** Consolidated the data parameters for the analytics script into a single line.
  - **Description:** 
    - The script's custom parameters related to user data were made more concise and integrated into a one-liner, without altering the actual data being sent, just improving the code clarity.
  - **Impact:** This change primarily impacts code readability and maintainability with a minor indirect impact on performance due to the reduction in line count.

3. **File: `resources/views/profile/update-profile-form.blade.php`**
  - **Status:** Modified
  - **Changes:** Removed the conditional block managing profile photos using Laravel Jetstream.
  - **Description:** 
    - The section of the code that dealt with profile photo management via Laravel Jetstream was entirely removed.
    - This might be an effort to deprecate the use of Jetstream for profile photos or to streamline the profile update interface.
  - **Impact:** Users will no longer see options related to profile photo management in the profile form. This could streamline user interactions by focusing strictly on textual updates but may require compensatory photo management elsewhere in the system.

4. **File: `app/Http/Controllers/PriceController.php`**
  - **Status:** Deleted
  - **Changes:** The whole file was removed.
  - **Description:** 
    - The `PriceController.php` file which contained hardcoded structure for different pricing plans was entirely removed.
    - This likely indicates the obsolescence of this controller or its absorption into another part of the system that handles pricing dynamically.
  - **Impact:** This deletion will remove any direct route or functionality depending on this controller. The system must ensure any dependencies are addressed prior to rollout to prevent breaking changes.

Overall, the changes in this pull request simplify and cleanse the codebase, enhancing maintainability and potentially the efficiency of critical profile-related functionalities, albeit with implications on error handling and user interaction features.

---

# #112 Improved Error Handling and Enhanced Analytics Integration

## Introduction
This pull request introduces important updates to the application's profile management and analytics integration features. The changes focus on enhancing error handling during profile updates and providing richer analytics data by including user-specific information in the tracking script. These improvements will increase the robustness of our application and provide deeper insights into user behavior.

## Changes Overview
1. **File: `app/Livewire/UpdateProfileForm.php`**
- **Status:** Modified
- **Changes:** Added a `try-catch` block to handle exceptions during profile information updates.
  ```php
  try {
      $this->validate();
      $updateData = [
          'firstname' => $this->firstname,
          'lastname' => $this->lastname,
          'birthday' => $this->birthday,
          'gender' => $this->gender ?? null,
      ];
      $user = User::find(Auth::id());
      $user->update($updateData);
      $this->mount();
      $this->alert('success', __('profile.setcard.savedprofile'));
  } catch (\\Exception $e) {
      $this->alert('error', $e->getMessage());
  }
  ```
- **Description:** 
  - Previously, the method attempted to update user information without any error handling. If an error occurred during validation or updating the database, the application could crash or behave unpredictably.
  - By adding a `try-catch` block around the code, exceptions are now caught, and an appropriate error message is displayed to the user.
- **Impact:**
  - **Improved Reliability:** User experience is more predictable and stable, as the application will handle errors gracefully.
  - **User Feedback:** Users will receive specific error messages, which can help in troubleshooting and improving the overall experience.

2. **File: `resources/views/layouts/partials/head.blade.php`**
- **Status:** Modified
- **Changes:** Updated the analytics script to include custom parameters when a user is authenticated.
  ```blade
  <script defer src="https://85analytics.com/pixel/qI1bCul7XcqMbwvr"
      @auth
      data-custom-parameters='{
          "uuid": "{{ auth()->user()->uuid }}",
          "role": "{{ auth()->user()->role }}",
          "name": "{{ auth()->user()->name }}", 
          "email": "{{ auth()->user()->email }}",
      }'
      @endauth
  ></script>
  ```
- **Description:** 
  - The analytics script now dynamically injects user-specific data (UUID, role, name, and email) into the script's `data-custom-parameters` attribute if the user is authenticated.
  - This change enriches the information sent to the analytics service, allowing for more detailed tracking and analysis of authenticated users.
- **Impact:**
  - **Enhanced Analytics:** Provides deeper insights into user behavior and demographics, which can help inform business decisions and improve user engagement.
  - **Privacy Considerations:** Since more detailed user information is now sent to the analytics service, it is crucial to ensure compliance with data privacy regulations and obtain user consent where necessary.

---

# #111 Pull Request Description

## Headline
Enhancement to Profile Update Mechanism in UpdateProfileForm Component

## Introduction
This pull request introduces a modification in the `UpdateProfileForm` Livewire component to improve the functionality following user profile updates. Specifically, it addresses the need to reset the component state after a user's profile information is successfully updated. This enhancement aims to provide a better user experience by making sure the displayed information is immediately consistent with the saved changes. 

## Changes Overview
1. **File: `app/Livewire/UpdateProfileForm.php`**
- **Status:** Modified
- **Changes:**
  - Added a call to the `mount` method immediately after the user profile data is updated.
  - This results in the component being reinitialized right after a profile update.
- **Description:** 
  - The `mount` method is invoked to reset the component’s state and ensure that any dynamic data displayed in the component reflects the freshly updated profile information.
  - Adds two new lines within the `updateInformation` method:
    ```php
    $this->mount();
    ```
- **Impact:**
  - **Functionality:** The profile update flow should be more robust, ensuring that displayed data is always up-to-date immediately after changes are made.
  - **User Experience:** Users will experience a seamless update mechanism where changes are instantly reflected in their profile view, thereby reducing any confusion arising from stale data.
  - **System Re-initialization:** The additional call to the `mount` method means the component is reinitialized, which might slightly increase the processing time but ensures data integrity and consistency. 

The discussed changes are minimal but ensure a significant improvement in how users perceive updates by instantly reflecting changes, thereby enhancing the overall user experience.

---

# #110 Removal of 'CheckOnboardingStatus' Middleware from Kernel

## Introduction
This pull request involves a modification to the `Kernel.php` file in the application. The change specifically focuses on the removal of the 'CheckOnboardingStatus' middleware from the application's global HTTP middleware stack. This update could have multiple implications, including streamlining the request lifecycle and potentially altering the behavior related to user onboarding processes.

## Changes Overview
1. **File: `app/Http/Kernel.php`**
- **Status:** Modified
- **Changes:** Removed 'CheckOnboardingStatus' from the middleware stack.
    ```diff
    -        'CheckOnboardingStatus' => \App\Http\Middleware\CheckOnboardingStatus::class,
    ```
- **Description:** The middleware `CheckOnboardingStatus` has been removed from the list of middleware that the application uses globally. This means that any logic that `CheckOnboardingStatus` middleware handled will no longer be automatically applied to incoming HTTP requests.
- **Impact:** This change could streamline the request lifecycle by reducing the number of middleware checks for each request. However, it could also mean that certain verification steps related to onboarding will not be executed unless they are implemented elsewhere in the application's flow. This might impact new users' flow or any functionality dependent upon the onboarding status of the user.

---

# #109 Feature Additions and Enhancements for Improved Profile Updates, Order Management, and User Reviews

## Introduction
This pull request introduces several new features and enhancements to the application, focusing on profile management, order processing, user feedback, and UI/UX improvements. The main areas of changes include adding functionality for updating user profiles, managing orders and transactions, implementing new user review systems, enhancing the pricing plans display, and updating validation scripts for inputs. These changes are expected to improve the overall user experience, streamline order processing, and ensure better data integrity.

## Changes Overview

1. **File: `app/Livewire/UpdateProfileForm.php`**
- **Status:** Added
- **Changes:** Created a new Livewire component `UpdateProfileForm`.
- **Description:** This file contains functionality for updating user profile information including first name, last name, birthday, and gender.
- **Impact:** It allows users to update profile details directly from the application interface, enhancing the user experience.

2. **File: `app/Models/OrderReview.php`**
- **Status:** Added
- **Changes:** Introduced new model `OrderReview`.
- **Description:** This model represents user reviews on orders including fields like `order_id`, `user_id`, `review`, `rating`, and others.
- **Impact:** Provides structured data for handling order reviews which can be used for feedback and improving service quality.

3. **File: `app/Models/Wallet.php`**
- **Status:** Added
- **Changes:** Introduced the `Wallet` model.
- **Description:** This model captures user wallet details such as `user_id`, `balance`, `currency`, `status`, and timestamps for various status changes.
- **Impact:** Facilitates financial transactions and balance management features for users.

4. **File: `app/Models/WalletTransaction.php`**
- **Status:** Added
- **Changes:** Introduced the `WalletTransaction` model.
- **Description:** This model handles individual transactions related to the user’s wallet.
- **Impact:** Supports logging and tracking of all wallet transactions.

5. **File: `database/migrations/2024_06_06_215130_create_order_reviews_table.php`**
- **Status:** Added
- **Changes:** Created a new database migration for `order_reviews`.
- **Description:** Defines the schema for the `order_reviews` table, including foreign keys and various fields.
- **Impact:** Sets up the database structure necessary for managing order reviews.

6. **File: `database/migrations/2024_06_07_014439_create_wallets_table.php`**
- **Status:** Added
- **Changes:** Created a new database migration for `wallets`.
- **Description:** Defines the schema for the `wallets` table.
- **Impact:** Essential for storing wallet-related information.

7. **File: `database/migrations/2024_06_07_014445_create_wallet_transactions_table.php`**
- **Status:** Added
- **Changes:** Created a new database migration for `wallet_transactions`.
- **Description:** Defines the schema for the `wallet_transactions` table.
- **Impact:** Establishes the structure needed for recording wallet transactions.

8. **File: `public/js/jquery-3.7.1.min.js`**
- **Status:** Added
- **Changes:** Added minified jQuery library.
- **Description:** This JavaScript library is necessary for various front-end functionalities.
- **Impact:** Improves client-side scripting and interactivity within the application.

9. **File: `public/js/validateInputHigher50.js`**
- **Status:** Added
- **Changes:** Introduced a script to validate input values ensuring they do not exceed 50.
- **Description:** Helps maintain data integrity by enforcing input constraints.
- **Impact:** Prevents users from entering values higher than allowed.

10. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** Added functionality to handle wallet balance updates and transactions when an order is accepted.
- **Description:** Integrates wallet management into the order processing workflow.
- **Impact:** Ensures accurate financial transactions and balance updates upon order acceptance.

11. **File: `app/Http/Controllers/PublicPagesController.php`**
- **Status:** Modified
- **Changes:** Enhanced the `price` method to include detailed plans with descriptions and features.
- **Description:** Provides a better user experience by displaying detailed pricing plans.
- **Impact:** Likely to improve conversion rates by clarifying the benefits of each plan.

12. **File: `app/Http/Controllers/TaskController.php`**
- **Status:** Modified
- **Changes:** Added new methods for handling video and image uploads with validation.
- **Description:** Manages file uploads more effectively with additional constraints.
- **Impact:** Enhances the reliability and security of file uploads.

13. **File: `app/Livewire/OrderChat.php`**
- **Status:** Modified
- **Changes:** Included functionality for submitting order reviews.
- **Description:** Allows users to review orders directly from the chat interface.
- **Impact:** Facilitates more integrated and immediate user feedback.

14. **File: `app/Models/Order.php`**
- **Status:** Modified
- **Changes:** Added a relationship with `OrderReview`.
- **Description:** Connects orders with their respective reviews.
- **Impact:** Streamlines the retrieval and display of order reviews.

15. **File: `app/Models/OrderFiles.php`**
- **Status:** Modified
- **Changes:** Included `Str` utility for generating random strings.
- **Description:** Utilizes Laravel helpers for string operations.
- **Impact:** Improves consistency and reliability in file naming.

16. **File: `app/Models/User.php`**
- **Status:** Modified
- **Changes:** Added relationships to user-related models such as orders, applications, and reviews.
- **Description:** Enriches the user model with more associations.
- **Impact:** Facilitates better data management and retrieval.

17. **File: `resources/js/app.js`**
- **Status:** Modified
- **Changes:** Removed jQuery import as it was added separately.
- **Description:** Cleaned up redundant imports.
- **Impact:** Optimizes the overall script loading process.

18. **File: `resources/js/passwordReveal.js`**
- **Status:** Modified
- **Changes:** Cleaned up unnecessary comments.
- **Description:** Improves code readability.
- **Impact:** Simplifies future maintenance.

19. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** Added new translations related to reviews.
- **Description:** Supports localized user review functionalities.
- **Impact:** Enhances user experience for Portuguese-speaking users.

20. **File: `resources/views/components/menu-homepage.blade.php`**
- **Status:** Modified
- **Changes:** Fixed a CSS class for improved UI consistency.
- **Description:** Minor UI tweak for better visual consistency.
- **Impact:** Improves the aesthetic quality of the homepage header.

21. **File: `resources/views/dashboard/business/order/livewire/process.blade.php`**
- **Status:** Modified
- **Changes:** Updated input validation to use `validateInputHigher50` instead of `validateInputHigher100`.
- **Description:** Adjusts the UI to constrain maximum input values to 50.
- **Impact:** Enforces the new input constraints visually.

22. **File: `resources/views/dashboard/business/order/process.blade.php`**
- **Status:** Modified
- **Changes:** Updated the script for validating input values to the new constraints.
- **Description:** Ensures the validation script matches the updated business logic.
- **Impact:** Prevents users from entering values beyond the allowed limits within the order process.

23. **File: `resources/views/dashboard/business/order/progress.blade.php`**
- **Status:** Modified
- **Changes:** Enhanced review submission and display along with some UI improvements.
- **Description:** Allows users to submit reviews and view them in a more interactive manner.
- **Impact:** Improves user engagement by integrating reviews into the order progress.

24. **File: `resources/views/dashboard/components/order-chat.blade.php`**
- **Status:** Modified
- **Changes:** Incorporated the new review system within the order chat component.
- **Description:** Displays and manages user reviews directly within the chat.
- **Impact:** Enhances the order review process and provides immediate feedback options.

25. **File: `resources/views/dashboard/creator/task/progress.blade.php`**
- **Status:** Modified
- **Changes:** Added enhanced file upload progress tracking and error handling.
- **Description:** Improved the reliability and user experience of file uploads.
- **Impact:** Users can more effectively upload and track the status of their files.

26. **File: `resources/views/errors/404.blade.php`**
- **Status:** Modified
- **Changes:** Removed redundant analytics scripts.
- **Description:** Cleaned up unnecessary scripts for error pages.
- **Impact:** Improves page load times and privacy on error pages.

27. **File: `resources/views/errors/503.blade.php`**
- **Status:** Modified
- **Changes:** Removed unnecessary analytics scripts.
- **Description:** Streamlined the error page by removing unnecessary scripts.
- **Impact:** Ensures faster page loads and reduced external dependencies.

28. **File: `resources/views/layouts/errors.blade.php`**
- **Status:** Modified
- **Changes:** Removed unnecessary analytics scripts.
- **Description:** Cleaned up error layout by removing extra scripts.
- **Impact:** Enhances efficiency and reduces potential security risks.

29. **File: `public/js/validateInputHigher100.js`**
- **Status:** Deleted
- **Changes:** Removed the old validation script for input values higher than 100.
- **Description:** Obsolete due to new input validation limits.
- **Impact:** Eliminates redundancy and potential confusion regarding input validation constraints.

These changes collectively enhance the application's functionality, security, user experience, and maintainability.

---

# #108 Pull Request Overview:
## Title:
Enhancements and Bug Fixes for Order Checkout and Profile Update Components

## Introduction
This pull request introduces several significant changes aimed at enhancing and fixing components related to the order checkout and profile update processes in our web application. The primary changes span modifications to the live order processing views, profile updating forms, and routing endpoints. These updates aim to improve overall functionality, user experience, and ensure a more consistent routing scheme. Key areas of modification include:
- Updating the order checkout form routing for accuracy and consistency.
- Enhancing the profile information update form for better user clarity and additional functionality.
- Adjusting route definitions to better adhere to naming conventions and improve maintainability.

## Changes Overview
1. **File: `resources/views/dashboard/business/order/livewire/process.blade.php`**
- **Status:** Modified
- **Changes:** Updated form action route from `orders.checkout` to `orders.checkout.store`.
- **Description:** The form action previously pointed to a generic checkout route (`orders.checkout`) but has now been specified to `orders.checkout.store` to align with the updated route definitions.
- **Impact:** This change ensures that the order checkout form submits to the correct endpoint, enhancing the reliability and predictability of the checkout process.

2. **File: `resources/views/profile/update-profile-information-form.blade.php`**
- **Status:** Modified
- **Changes:** Reorganized and improved the profile update form, increasing the number of lines from 101 to 103 with the addition and deletion of texts.
- **Description:** The changes involve restructuring the profile update form to enhance readability and user interaction. This includes wrapping the form within a new `<div>`, reordering DOM elements, and implementing additional features like gender selection.
- **Impact:** This update significantly improves the user experience when updating profile information by making the form more intuitive and visually appealing. It ensures that all necessary fields and options are readily accessible and properly labeled.

3. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** Changed the name for the POST checkout route from `checkout` to `checkout.store`.
- **Description:** This change clarifies the role of the route by accurately reflecting its action, which is to store checkout information. This aligns with RESTful routing conventions.
- **Impact:** This change enhances route clarity and maintainability, ensuring that developers can easily understand the purpose of each route, reducing the likelihood of routing-related bugs.

These changes collectively aim to streamline the checkout process, improve the user interface for profile updates, and enhance overall code maintainability through better routing conventions.

---

# #107 Pull Request Description

## Headline
Improvements in Input Validation, Localization, and Backup Notifications Management

## Introduction
This pull request encompasses a variety of updates related to input validation, localization, routing configuration, and backup notifications within the application. The aim of the changes is to improve application functionality by adding more robust input validation mechanisms and streamline some navigational routes. Additionally, modifications to configuration files improve the alignment of localization efforts, and better management of backup notifications fosters more efficient monitoring of backup statuses.

## Changes Overview

1. **File: `public/js/validateInputHigher100.js`**
    - **Status:** Added
    - **Changes:** Added JavaScript function `validateInputHigher100`.
    - **Description:** This function limits any input value to a maximum of 100. If the input exceeds 100, it automatically sets it back to 100.
    - **Impact:** Enhances input validation, preventing values higher than 100, likely reducing potential user errors.

2. **File: `public/js/validateInputLower1.js`**
    - **Status:** Added
    - **Changes:** Added JavaScript function `validateInputLower1`.
    - **Description:** This function ensures that any input value remains at a minimum of 1. If the input is below 1, it automatically sets it to 1.
    - **Impact:** Improves input validation, avoiding inputs less than 1, thus increasing application reliability.

3. **File: `app/Providers/FortifyServiceProvider.php`**
    - **Status:** Modified
    - **Changes:** Implemented a custom view for user registration in the Fortify boot method.
    - **Description:** Added a new custom view function for user registration.
    - **Impact:** Allows more flexibility and customization in rendering the user registration view, contributing to a better user experience.

4. **File: `config/backup.php`**
    - **Status:** Modified
    - **Changes:** Commented out multiple backup notification classes and updated email addresses.
    - **Description:** Temporarily disabled several backup notification configurations and changed the email addresses for mail notifications.
    - **Impact:** These changes suggest a refined focus on specific backup notifications as well as aligning certain email settings for improved notification management.

5. **File: `resources/lang/pt_br/dashboard.php`**
    - **Status:** Modified
    - **Changes:** Updated various labels and text translations.
    - **Description:** Changed translations around the "applications" concept to "inscrições" to ensure correctness and consistency.
    - **Impact:** Improved localization accuracy and relevance in the user interface for Brazilian Portuguese.

6. **File: `resources/views/auth/login.blade.php`**
    - **Status:** Modified
    - **Changes:** Corrected the route name from `register` to `registrar`.
    - **Description:** Changed the route in the login page to correctly point to the registration page.
    - **Impact:** Ensures proper navigation from the login page to the registration page, enhancing user experience.

7. **File: `resources/views/components/menu-homepage.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated the route name from `register` to `registrar`.
    - **Description:** Fixed the navigation link in the homepage menu to direct users to the correct registration route.
    - **Impact:** Prevents dead links and improves user navigation on the homepage.

8. **File: `resources/views/dashboard/business/order/applications.blade.php`**
    - **Status:** Modified
    - **Changes:** Adjusted styling classes.
    - **Description:** Modified a class removing unnecessary `uppercase` styling.
    - **Impact:** Minor UI adjustment potentially improving readability.

9. **File: `resources/views/dashboard/business/order/checkout.blade.php`**
    - **Status:** Modified
    - **Changes:** Enhanced the interval check on order status using POST method and CSRF token for improved security.
    - **Description:** Refactored the interval script to POST request with appropriate security headers and reduced the interval time.
    - **Impact:** Added security while dynamically checking order status, improving real-time user experience.

10. **File: `resources/views/dashboard/business/order/livewire/checkout-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Removed z-index in the peer class for input radios.
    - **Description:** Cleaned up CSS class attributes for better maintainability.
    - **Impact:** Minor UI cleanup without significant functional changes.

11. **File: `resources/views/dashboard/business/order/livewire/process.blade.php`**
    - **Status:** Modified
    - **Changes:** Added validation scripts and updated input type and validation calls.
    - **Description:** Added higher and lower input validation scripts and changed input types to `number` with min and max constraints.
    - **Impact:** Improved user input validation and enhanced user interface to reflect valid input ranges, reducing input errors.

12. **File: `resources/views/dashboard/business/order/process.blade.php`**
    - **Status:** Modified
    - **Changes:** Included additional JS script sources for input validation.
    - **Description:** Added script sources for input validation to support newly implemented functions.
    - **Impact:** Ensures the input validation scripts are properly loaded and functional across the relevant views.

13. **File: `resources/views/index.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated registration route in the homepage hero section.
    - **Description:** Adjusted the navigation link to the correct registration route.
    - **Impact:** Ensures seamless navigation for users from the homepage hero section to the registration page.

14. **File: `resources/views/layouts/homepage.blade.php`**
    - **Status:** Modified
    - **Changes:** Corrected the signup link route.
    - **Description:** Changed the route from `register` to `registrar`.
    - **Impact:** Prevents navigation errors and ensures route consistency.

15. **File: `resources/views/profile/profile-video-upload.blade.php`**
    - **Status:** Modified
    - **Changes:** Optimized code, enhanced button ids, and adjusted overlays.
    - **Description:** Refactored event listeners and buttons for pausing video tips.
    - **Impact:** Enhances usability by ensuring intuitive user interactions with modal elements.

16. **File: `resources/views/profile/setcard.blade.php`**
    - **Status:** Modified
    - **Changes:** Refined multiple sections of progress bar HTML.
    - **Description:** Improved layout and structure for file upload progress bar.
    - **Impact:** Provides a clearer and more consistent display of progress to users during file uploads.

17. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Adjusted route names and changed order status check from GET to POST route.
    - **Description:** Refined several routes for consistent naming and switched status check to a more secure POST method.
    - **Impact:** Improves route consistency, navigation, and enhances security by using appropriate HTTP methods.

18. **File: `resources/lang/vendor/backup/en/notifications.php`**
    - **Status:** Deleted
    - **Changes:** Removed entire file with backup notifications in English.
    - **Description:** Deleted the obsolete notifications language file.
    - **Impact:** Cleans up outdated or unnecessary files reducing clutter.

19. **File: `resources/lang/vendor/backup/pt_br/notifications.php`**
    - **Status:** Deleted
    - **Changes:** Removed the entire file with backup notifications in Brazilian Portuguese.
    - **Description:** Deleted the outdated notifications language file similar to the English version.
    - **Impact:** Enhances maintainability by removing redundant files.

These changes introduce important input validation enhancements, refine route management, improve user interface localization, and optimize the backup notification configuration. All stakeholders, especially developers and QA engineers, should review the changes in detail to ensure they align with overall application architecture and user requirements.

---

# #106 Summary of Pull Request Changes

## Introduction
This pull request introduces several modifications across multiple files in the project. These changes focus on improving functionality and user experience, particularly in areas of order handling and UI consistency. Notably, some UUID-generating logic has been moved between models for proper functionality, and there are several user interface tweaks to enhance visual coherence and interaction feedback. The modifications are categorized under code improvements, UI/UX enhancements, and minor cleanups.

## Changes Overview
1. **File: `app/Models/OrderDetail.php`**
    - **Status:** Modified
    - **Changes:** Removed the boot method responsible for setting UUIDs.
    - **Description:** The UUID generation logic that was in the `creating` event hook inside the `boot` method has been removed.
    - **Impact:** This change will stop the automatic assignment of UUIDs to `OrderDetail` models, potentially affecting any functionality depending on UUIDs for these models.

2. **File: `app/Models/OrderFiles.php`**
    - **Status:** Modified
    - **Changes:** Added a boot method to generate UUIDs during the creation of `OrderFiles`.
    - **Description:** Introduced UUID assignment logic in the `creating` event hook inside the `boot` method for the `OrderFiles` model.
    - **Impact:** This change ensures that UUIDs are generated for `OrderFiles` models, which can be essential for maintaining unique file references.

3. **File: `resources/views/dashboard/creator/task/progress.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated the progress bar style by changing the color classes.
    - **Description:** Changed the progress bar's fill color class from `bg-blue-600` to a project-specific custom color `bg-creatify-2`.
    - **Impact:** This change will affect the visual representation of the progress bar, making it consistent with the project's design guidelines.

4. **File: `resources/views/profile/profile-video-upload.blade.php`**
    - **Status:** Modified
    - **Changes:** 
        - Replaced `<x-secondary-button>` with `<x-button>` for video change buttons.
        - Corrected file type descriptions and cleaned up unnecessary text.
        - Commented out an unused or redundant `x-slot` section.
    - **Description:** These changes fix button styling issues, improve the clarity of text, and clean up the code structure.
    - **Impact:** Enhances user experience by providing consistent and clearer UI elements and descriptions.

5. **File: `resources/views/profile/setcard.blade.php`**
    - **Status:** Modified
    - **Changes:** 
        - Updated the styling of progress and uploaded file display areas.
        - Changed progress bar color classes to custom project-specific colors.
    - **Description:** Adjusted the styling for increased visual consistency and better alignment with project-specific design aesthetics.
    - **Impact:** Improved visual coherence making UI elements more consistent and aesthetically pleasing.



---

# #105 New Feature Addition to Newsletter Subscription and Various System Enhancements

## Introduction
This pull request primarily introduces a new feature that adds users who contact through the contact form to the newsletter subscription list. Meanwhile, it also includes various other enhancements that improve the middleware handling of API requests, the form handling within the checkout process, and the aesthetics and functionality of the profile video upload interface. These changes aim to provide a better user experience, improve the robustness of form submissions, and ensure the accurate transmission of data through middleware processes.

## Changes Overview
1. **File: `app/Http/Controllers/PublicPagesController.php`**
   - **Status:** Modified
   - **Changes:** Added `NewsletterSubscriber` model to handle newsletter subscriptions. Updated the `contact_store` method to create a new record in the `newsletter_subscribers` table when a contact form is submitted.
   - **Description:** This change ensures that every user who submits a contact form is automatically subscribed to the newsletter using their email address.
   - **Impact:** Improves user retention by allowing seamless subscription to the newsletter, enhancing the overall user engagement with the platform.

2. **File: `app/Http/Middleware/CheckUserAsaas.php`**
   - **Status:** Modified
   - **Changes:** Replaced the `'json'` option with `'body'` and manually encoded the request payload to JSON format.
   - **Description:** This modification might have been made to circumvent some issues with encoding or to ensure consistency in how the payload is sent.
   - **Impact:** Ensures correct data format during transmission, preventing potential data handling errors on the receiving end (Asaas API).

3. **File: `app/Livewire/Business/CheckoutForm.php`**
   - **Status:** Modified
   - **Changes:** Added condition to check for the existence of the `estado` key in `$data` array before assigning a state.
   - **Description:** This update prevents potential errors that could occur if the `estado` key does not exist in the response data.
   - **Impact:** Increases the robustness of the form handling, ensuring that the absence of certain data does not cause the application to crash or misbehave.

4. **File: `app/Services/PaymentService.php`**
   - **Status:** Modified
   - **Changes:** Similar to the changes in `CheckUserAsaas.php`, replaced the `'json'` option with `'body'` and manually encoded the request payload to JSON format.
   - **Description:** Ensures the proper sending of the payment request payload by manually managing the JSON encoding.
   - **Impact:** Improves the reliability of payment-related API calls, preventing potential issues with incorrectly formatted payloads.

5. **File: `resources/views/profile/profile-video-upload.blade.php`**
   - **Status:** Modified
   - **Changes:** Added `id` attributes to the progress and uploaded areas. Some changes appear to be accidental and should be reviewed (e.g., "dsflkjdflkdsflkdsjflkdsjfldsjfjldsjfljdsfjdlkjk" text).
   - **Description:** The addition of `id` attributes aims to facilitate a more precise targeting of HTML elements for JavaScript operations.
   - **Impact:** Enhances the accuracy of DOM manipulations for video uploads, though accidental changes should be reviewed and corrected to avoid unintended issues.

6. **File: `resources/views/profile/setcard.blade.php`**
   - **Status:** Modified
   - **Changes:** Extensive updates to the file upload progress/interface, including a more detailed and user-friendly progress bar and more information display during upload operations.
   - **Description:** These modifications significantly enhance the user experience by providing clearer and more detailed feedback during the video upload process.
   - **Impact:** Improves the usability and accessibility of the file upload process, leading to a smoother user experience and potentially increasing user satisfaction and engagement.

The updates included in this pull request mainly focus on enhancing user engagement, improving data handling robustness, and upgrading the UI/UX for critical functionalities like contact management and file uploads. These enhancements collectively aim to provide a smoother, more reliable user experience across the platform.

---

# #104 Update API Token and Improve Video Upload UI for Better User Experience

## Introduction
This pull request encompasses two main changes: an update to the API tokens for the Asaas service in a configuration file and a minor UI change in the profile video upload section. The configuration change aims to enhance security by updating the token used to interact with the Asaas API, ensuring that current and secure credentials are employed. The UI adjustment in the video upload template is intended to improve the user interface, making it more visually appealing and user-friendly. These changes collectively enhance both the security framework and the user experience of the application.

## Changes Overview
1. **File: `config/app_custom.php`**
- **Status:** Modified
- **Changes:** Updated the `asaas_token` used for the Asaas API based on the environment.
- **Description:** The `asaas_token` was modified to ensure the application uses a new, secure token for both production and sandbox environments.
- **Impact:** This change enhances the security of the application by utilizing updated and presumably more secure API tokens. Users interacting with the Asaas service will now do so using current API tokens, reducing the risk of unauthorized access.

2. **File: `resources/views/profile/profile-video-upload.blade.php`**
- **Status:** Modified
- **Changes:** Added `<br>` tag after the closing `h3` tag in the profile video upload template.
- **Description:** This change was made to improve the layout of the video upload section by adding a line break after the section header, ensuring better spacing and visual separation in the UI.
- **Impact:** This small UI enhancement improves the readability and user experience of the profile video upload page, potentially making it easier for users to navigate and interact with video uploading features.

---

# #103 Add Event Broadcasting, Detailed Task Management, and File Handling Improvements

## Introduction
This pull request introduces several significant updates to the application, involving the addition of new features, improvements to user experience (UX), and enhancements to backend processes. The changes focus on event broadcasting for real-time updates, refined task management for creators, new file handling mechanisms, and consolidation of PR controllers. These updates aim to enhance the overall functionality, security, user experience, and maintainability of the application. Specific areas of improvement include new event broadcasting for messaging, file handling for orders, improved task management, and admin functionalities.

## Changes Overview

1. **File: `app/Events/MessageSent.php`**
   - **Status:** Added
   - **Changes:** Introduced an event class `MessageSent` to handle message broadcasting.
   - **Description:** The `MessageSent` event class, implements `ShouldBroadcast` for real-time message sending, with methods to determine the broadcast channels and additional broadcast data.
   - **Impact:** Improves the messaging feature by enabling real-time updates, enhancing user communication.

2. **File: `app/Livewire/Creator/DashboardFinishedTasks.php`**
   - **Status:** Added
   - **Changes:** Created a Livewire component to list finished tasks for creators.
   - **Description:** Manages the display logic for tasks that are finished by querying orders from the database and listing them based on user interactions.
   - **Impact:** Enhances creator's dashboard by providing better visibility and management of finished tasks.

3. **File: `app/Livewire/OrderFiles.php`**
   - **Status:** Added
   - **Changes:** Created a Livewire component to manage order files.
   - **Description:** Handles file management for an order, including file retrieval and status updates, filtering based on user roles and views.
   - **Impact:** Improves file handling by allowing better organization and status tracking of files associated with orders.

4. **File: `app/Http/Controllers/DashboardController.php`**
   - **Status:** Modified
   - **Changes:** Updated methods to include counting of finished orders and status-based ordering.
   - **Description:** Refined to handle fetching of active and finished orders more efficiently using `whereIn` clauses.
   - **Impact:** Provides enhanced data accuracy for the creator's dashboard, leading to better task management.

5. **File: `app/Http/Controllers/FAQController.php`**
   - **Status:** Modified
   - **Changes:** Removed the `faqs` method, keeping only the `list` method.
   - **Description:** Simplified the FAQController by removing the redundant method and consolidating functionality.
   - **Impact:** Reduces application complexity, making it easier to maintain the FAQ page.

6. **File: `app/Http/Controllers/OrderProcessController.php`**
   - **Status:** Modified
   - **Changes:** Added detailed file handling operations and status updates for orders.
   - **Description:** Enhanced to support file review and approval, order status updates based on file completion, and downloading of files from AWS S3 storage.
   - **Impact:** Significantly improves order processing and file management, ensuring better workflow and user interaction.

7. **File: `app/Http/Controllers/PriceController.php`**
   - **Status:** Modified
   - **Changes:** Added comprehensive plan details with pricing and features.
   - **Description:** Expanded to define various pricing plans, including descriptions and feature lists.
   - **Impact:** Provides detailed and structured pricing information to users, enhancing the subscription experience.

8. **File: `app/Http/Controllers/TaskController.php`**
   - **Status:** Modified
   - **Changes:** Added methods for file deletion, and video uploads, and enhanced task progress tracking.
   - **Description:** Enhanced to support various task operations including file uploads and deletions, and tracking unread messages.
   - **Impact:** Improves task management functionalities, providing creators with more control and feedback on their work progress.

9. **File: `app/Http/Controllers/UserProfileController.php`**
   - **Status:** Modified
   - **Changes:** Updated validation rules for file uploads.
   - **Description:** Improved file size validation for avatars and videos by using renamed and more specific validation classes.
   - **Impact:** Enhances profile update mechanisms, ensuring better file management and validation.

10. **File: `app/Http/Controllers/WebhookController.php`**
   - **Status:** Modified
   - **Changes:** Streamlined webhook handling for various events.
   - **Description:** Now supporting detailed transaction logging for payment events and email status tracking.
   - **Impact:** Enhances backend reliability and traceability for payment and email processing.

11. **File: `app/Livewire/Business/ModalBriefing.php`**
   - **Status:** Modified
   - **Changes:** Added the `$view` property.
   - **Description:** Minor enhancement to support different views in the modal.
   - **Impact:** Increases flexibility in how briefing modals are displayed.

12. **File: `app/Livewire/Creator/DashboardActiveTasks.php`**
   - **Status:** Modified
   - **Changes:** Updated methods to use `Auth` facade for retrieving the user ID.
   - **Description:** Improves task querying by utilizing `whereIn` for fetching active tasks.
   - **Impact:** Enhances performance and readability of code, ensuring more accurate task listings.

13. **File: `app/Livewire/Creator/DashboardAppliedTasks.php`**
   - **Status:** Modified
   - **Changes:** Same as changes in `DashboardActiveTasks` for user ID retrieval.
   - **Description:** Similar improvements as the active tasks component.
   - **Impact:** Consistent user ID handling across components, leading to more reliable task management.

14. **File: `app/Livewire/Creator/DashboardOpenTasks.php`**
   - **Status:** Modified
   - **Changes:** Same as changes in `DashboardActiveTasks` for user ID retrieval.
   - **Description:** Similar improvements as the active tasks component.
   - **Impact:** Ensures reliability in querying open tasks for creators.

15. **File: `app/Livewire/OrderChat.php`**
   - **Status:** Modified
   - **Changes:** Added broadcasting, message sending, and a file handling mechanism.
   - **Description:** Enhanced to support real-time messaging through event broadcasting and improved file handling for chats.
   - **Impact:** Significantly improves the chat feature by introducing real-time updates and better file management within messages.

16. **File: `app/Models/Order.php`**
   - **Status:** Modified
   - **Changes:** Added a new relationship method for order files.
   - **Description:** Improves model relationships, making it easier to access files related to an order.
   - **Impact:** Enhances data models, leading to more maintainable and efficient database querying.

17. **File: `app/Models/OrderChat.php`**
   - **Status:** Modified
   - **Changes:** Added relationships with users for more detailed chat information.
   - **Description:** Improves how chat messages are connected to users.
   - **Impact:** Provides more detailed and context-rich data for chat messages.

18. **File: `app/Models/OrderDetail.php`**
   - **Status:** Modified
   - **Changes:** Added UUID generation.
   - **Description:** Automatically assigns UUIDs when creating new order details.
   - **Impact:** Ensures unique identification of order details, improving data integrity and referencing.

19. **File: `app/Models/OrderFiles.php`**
   - **Status:** Modified
   - **Changes:** Added new fields and relationships for better file handling.
   - **Description:** Enhances file model with additional fields like `type`, `read_at`, `sent_at`, etc., and relationships with orders and users.
   - **Impact:** Improves management and querying of order files, leading to more robust file handling capabilities.

20. **File: `app/Rules/CONTAAZUlRule.php`**
   - **Status:** Modified
   - **Changes:** Removed commented-out code.
   - **Description:** Cleaned up the rule class by removing unused code.
   - **Impact:** Enhances readability and maintainability of code.

21. **File: `app/Rules/CPFCNPJRule.php`**
   - **Status:** Modified
   - **Changes:** Same as `CONTAAZUlRule`.
   - **Description:** Cleaned up the rule class by removing unused code.
   - **Impact:** Ensures cleaner and more maintainable code.

22. **File: `app/Http/Controllers/AdminController.php`**
   - **Status:** Renamed from `BlogPostController` with major additions
   - **Changes:** Consolidated multiple admin-related functionalities such as contact management, blog management, and FAQ management.
   - **Description:** This controller now handles different aspects of admin functionalities by encapsulating all related actions in one controller.
   - **Impact:** Improves the structure and organization of controllers in the application, making it easier to manage admin-related actions.

23. **File: `app/Http/Controllers/PublicPagesController.php`**
   - **Status:** Renamed and consolidated from multiple controllers including `ContactController`, `IndexController`, `LegalPagesController`, and `RegisterController`.
   - **Changes:** Combined multiple public-facing controller actions into one.
   - **Description:** Now handles actions such as rendering the home page, showing blog posts, handling contact forms, and more.
   - **Impact:** Streamlines handling of public pages and reduces redundant code in the application.

24. **File: `app/Rules/FileSizeAvatar.php`**
   - **Status:** Renamed from `FileSize`
   - **Changes:** Name change to be more specific to its function.
   - **Description:** No functional changes, only a rename to improve code readability.
   - **Impact:** Makes it clearer what the rule validates, enhancing code maintainability.

25. **File: `app/Http/Controllers/BlogPostPublicController.php`**
   - **Status:** Removed
   - **Changes:** Merged functionality into `PublicPagesController`.
   - **Description:** Consolidated functionality for public blog post actions.
   - **Impact:** Reduces redundancy and improves controller organization.

26. **File: `app/Http/Controllers/IndexController.php`**
   - **Status:** Removed
   - **Changes:** Merged functionality into `PublicPagesController`.
   - **Description:** Consolidated functionality for rendering the index page.
   - **Impact:** Reduces redundancy and improves controller organization.

27. **File: `app/Http/Controllers/LegalPagesController.php`**
   - **Status:** Removed
   - **Changes:** Merged functionalities into `PublicPagesController`.
   - **Description:** Consolidated functionality for rendering legal pages.
   - **Impact:** Reduces redundancy and improves controller organization.

28. **File: `app/Http/Controllers/RegisterController.php`**
   - **Status:** Removed
   - **Changes:** Merged functionalities into `PublicPagesController`.
   - **Description:** Consolidated functionality for handling registrations.
   - **Impact:** Reduces redundancy and improves controller organization.

29. **File: `app/Livewire/OrderChatForm.php`**
   - **Status:** Removed
   - **Changes:** Merged functionalities into `OrderChat`.
   - **Description:** Consolidated all chat-related functionalities into one component.
   - **Impact:** Streamlines chat operations and reduces complexity by having one component handle all related tasks.

These changes collectively improve the application's performance, maintainability, and user experience, laying a solid foundation for future enhancements.

---

# #101 New Tracking System for Active Orders: User Interface and Database Enhancements

## Introduction
This pull request introduces several significant updates and additions aimed at enhancing the tracking and management of active orders in the system. These changes include additions to the user interface, updates to database migrations, the introduction of new models, and adjustments to existing controllers. The new features and updates are expected to improve the user experience by adding functionalities for viewing and managing active tasks, enhancing the chat interface, and modifying database schemas to support new data requirements. The changes also introduce better status tracking and provide more detailed visual cues for users.

## Changes Overview
1. **File: `app/Livewire/Creator/DashboardActiveTasks.php`**
    - **Status:** Added
    - **Changes:** New Livewire component created for managing active tasks on the creator’s dashboard, includes methods `loadMore` to increase task count, and `render` to display tasks.
    - **Description:** This file was introduced to provide creators with an interface for viewing and managing their active tasks directly from their dashboard.
    - **Impact:** Enhances the user interface by allowing creators to manage and track more tasks efficiently.

2. **File: `app/Models/OrderFiles.php`**
    - **Status:** Added
    - **Changes:** New model for handling order files with attributes such as `order_id`, `user_id`, `path`, `name`, `extension`, `size`, `read`, and `status`.
    - **Description:** Created to manage file uploads and associations with orders, ensuring a clear and structured way to handle order-related files.
    - **Impact:** Improves file management within orders, supporting better user interactions with order attachments.

3. **File: `database/migrations/2024_05_28_132529_create_order_files_table.php`**
    - **Status:** Added
    - **Changes:** Database migration to create the `order_files` table with fields for `order_id`, `user_id`, file details, and status.
    - **Description:** This migration adds a new table to store files related to orders, facilitating improved data organization and storage capabilities.
    - **Impact:** Enhances the database schema by supporting additional data related to order files, leading to a more robust data handling structure.

4. **File: `database/migrations/2024_05_28_133348_change_product_images_table_name.php`**
    - **Status:** Added
    - **Changes:** Migration to rename `products_images` table to `product_files`.
    - **Description:** Renaming was done to better align with the new model conventions and handle broader file types, not limited to images.
    - **Impact:** Enhances data clarity and supporting future proofing by broadening scope beyond images.

5. **File: `resources/js/chatPage.js`**
    - **Status:** Added
    - **Changes:** JavaScript file added for managing chat page interactions, including automatic scrolling features.
    - **Description:** Enhances the chat functionality by enabling automatic scrolling and improving overall user experience in the chat interface.
    - **Impact:** Improves the usability of the chat interface, providing a smoother and more intuitive user experience.

6. **File: `resources/views/dashboard/creator/task/progress.blade.php`**
    - **Status:** Added
    - **Changes:** New blade file added for displaying task progress with detailed HTML structure and dynamic content.
    - **Description:** Introduces a comprehensive interface for creators to track task progress with enhanced visual and interactive elements.
    - **Impact:** Significantly improves the user interface for task management, offering detailed and organized views.

7. **File: `app/Http/Controllers/DashboardController.php`**
    - **Status:** Modified
    - **Changes:** Added logic to track active orders along with open and applied orders.
    - **Description:** Updates to enhance order tracking by adding support for new active orders state.
    - **Impact:** Improves dashboard functionality, providing more comprehensive order management for better user insights.

8. **File: `app/Http/Controllers/ProductController.php`**
    - **Status:** Modified
    - **Changes:** Replaced references from `ProductImage` to `ProductFiles`.
    - **Description:** Aligns the product controller with the new `ProductFiles` model for better handling of product-related files.
    - **Impact:** Ensures consistency and accuracy in file handling within product management.

9. **File: `app/Http/Controllers/TaskController.php`**
    - **Status:** Modified
    - **Changes:** Added methods to redirect approved applications to progress page and handling order progress route.
    - **Description:** Enhances the task controller by adding new functionalities for handling task progress and application status.
    - **Impact:** Improves task handling processes and user navigation within the application.

10. **File: `app/Livewire/Creator/DashboardAppliedTasks.php` and `DashboardOpenTasks.php`**
    - **Status:** Modified
    - **Changes:** Updated views to `dashboard-tasks` blade for consistency.
    - **Description:** Simplifies the view files usage by consolidating into a general task display component.
    - **Impact:** Maintains consistency and reduces redundancy in code implementation.

11. **File: `app/Livewire/OrderChat.php`**
    - **Status:** Modified
    - **Changes:** Added logic for loading and marking messages, handling chat applications.
    - **Description:** Enhances the chat functionality by adding dynamic message updates and application message handling.
    - **Impact:** Improves the real-time messaging experience and context awareness within chats.

12. **File: `app/Livewire/OrderChatForm.php`**
    - **Status:** Modified
    - **Changes:** Added event dispatch after message creation.
    - **Description:** Ensures the chat form dynamically updates upon sending messages.
    - **Impact:** Enhances interactivity and responsiveness in chat components.

13. **Files: `app/Models/Order.php`, `Product.php`**
    - **Status:** Modified
    - **Changes:** Updated relationships from `ProductImage` to `ProductFiles`.
    - **Description:** Aligns with new table structure.
    - **Impact:** Ensures model integrity and consistency.

14. **Files: `resources/js/app.js`, `resources/lang/pt_br/dashboard.php`, `profile.php`, `errors/404.blade.php`**
    - **Status:** Modified
    - **Changes:** Various text updates, UI modifications, and JS file imports to support new features.
    - **Description:** Language updates for clarity, UI improvements, and additional script functionalities.
    - **Impact:** Enhances localization, UI usability, and feature support across the application.

15. **Files: `resources/views/blog/index.blade.php`, `single-page.blade.php`, `components/menu-homepage.blade.php`**
    - **Status:** Modified
    - **Changes:** Added trims for text, updated blog formatting.
    - **Description:** Improves blog interface and text management.
    - **Impact:** Better user experience and readability.

16. **File: `resources/views/dashboard/business/order/progress.blade.php`**
    - **Status:** Modified
    - **Changes:** Major restructuring with additional features for business order progress views.
    - **Description:** Significant enhances business-side order progress tracking.
    - **Impact:** Provides enriched controls and visibility for business users.

17. **File: `resources/views/dashboard/components/order-chat.blade.php`**
    - **Status:** Modified
    - **Changes:** Added condition-based views for different user types within the chat.
    - **Description:** Customizes chat views based on user role (business or creator).
    - **Impact:** Improves user-specific experiences in the chat interface.

18. **File: `app/Models/ProductFiles.php`**
    - **Status:** Renamed from `ProductImage.php`
    - **Changes:** Updated file name and class references.
    - **Description:** Renames model to reflect broader file handling capabilities.
    - **Impact:** Supports extended file management functionalities for future use cases.

19. **Blade Files: Consolidation and Deletion**
    - **Files Renamed/Merged/Removed:** `resources/views/dashboard/creator/livewire/dashboard-tasks.blade.php` consolidated views; `dashboard-open-tasks.blade.php` removed.
    - **Description:** Cleaned up redundant views and merged similar functionalities.
    - **Impact:** Streamlines codebase and maintains cleaner file structure.

These changes collectively enhance the functionality, user experience, and maintainability of the application, providing users with better tools and interfaces for managing and tracking their tasks and orders.

---

# #100 Pull Request Description

## Introduction
This pull request is focused on a comprehensive overhaul of the 404 error page template. The 404 page serves as a vital part of user experience when navigating broken or non-existent links. This update aligns the page with modern web standards, improves accessibility, and enhances aesthetic appeal. The changes include HTML structure modifications, inclusion of meta tags, favicon links, font imports, analytics integration, and updated content presentation. These improvements not only modernize the page's appearance but also contribute to better performance and usability.

## Changes Overview
1. **File: `resources/views/errors/404.blade.php`**
   - **Status:** Modified
   - **Changes:**
     - Removed the old Blade template inheritance `@extends('layouts.errors')` and related sections for title and body.
     - Reconstructed the page structure with a traditional HTML5 doctype and tags.
     - Implemented meta tags for character set, viewport, CSRF token, favicon links for various devices, and theme color.
     - Added links for favicon images of different sizes and a manifest file for web application.
     - Integrated external font "Figtree" from `fonts.bunny.net`.
     - Included Vite for handling CSS and JS assets.
     - Conditional script inclusion for different analytics setups based on the environment (production).
     - Updated the body tag class to style the background and text color of the page.
     - Encapsulated content within a main tag with flexbox styles for better responsiveness.
     - Added a new message and link back to the home page within a more stylized container.
     - Included an image asset to enhance the visual appeal.
   - **Description:** The changes were made to improve the overall user experience when encountering a 404 error. The legacy Blade extended layout was replaced with a standalone HTML structure to allow finer control over the document structure and styling. Favicon links ensure that a recognizable icon is displayed across different devices. The new meta tags improve compliance with web standards and enhance the page's SEO and accessibility. Additionally, the integration with Vite allows for better management of styles and scripts.
   - **Impact:** These changes modernize the 404 page, making it more visually appealing and user-friendly. The added responsiveness ensures a consistent user experience across various devices. Also, integrating analytics scripts can provide valuable insights into how often users encounter 404 errors, aiding in future improvements. Performance enhancements may also result from the optimized assets handling via Vite.

Overall, these modifications will significantly enhance the aesthetic and functional aspects of the 404 error page, aligning it with contemporary web design practices.

---

# #99 Enhancing Data Management in BriefingView

## Introduction
This pull request focuses on refining the data handling within the Business BriefingView component. It introduces improvements in the data update process to ensure consistency and better error handling. Specifically, these changes affect how order details are updated and how validation errors are managed. This helps to enhance the functionality of the application by improving the reliability of data operations and user feedback. 

## Changes Overview
1. **File: `app/Livewire/Business/BriefingView.php`**
- **Status:** Modified
- **Changes:** 
  - Replaced direct `OrderDetail::updateOrCreate` call with an assignment to `$orderDetail`.
  - Adjusted the validation for `photoDescription` to check against `$orderDetail->photo_requirements` instead of a local variable.
- **Description:**  
  - Previously, the `OrderDetail::updateOrCreate` method was called directly without storing its result. The revised code now assigns the result to `$orderDetail`, which is then used in subsequent operations.
  - Initially, the validation checked if `photoDescription` was empty. This has been corrected to check against `$orderDetail->photo_requirements` to ensure the order's photo requirements are properly validated.
- **Impact:** 
  - **Functionality:** Assigning the result of `updateOrCreate` to `$orderDetail` ensures that the updated or newly created order details can be accessed immediately for further operations. 
  - **User Experience:** Enhanced validation provides users with more accurate error messages, which can prevent potential confusion and improve user satisfaction.
  - **Data Integrity:** These changes help maintain consistency in how order details are managed and validated, reducing the likelihood of data discrepancies.

---

# #98 Addition of Email Notifications and Order Management Enhancements

## Introduction

This pull request introduces several notable changes that enhance the notification system, improve order management, and refine user interaction within the application. Key enhancements include new email notification features for order applications, the addition of Livewire components for real-time interactivity with orders and chats, and numerous improvements to the application's structures and functionalities. These updates aim to improve the application's architecture, elevate the user experience, and optimize operational workflows.

## Changes Overview

1. **File: `app/Console/Commands/SendmailNewApplications.php`**
- **Status:** Added
- **Changes:** Implemented a command to notify the business owner when new applications for an order are received.
- **Description:** This command queries orders with a specific status and sends email notifications if there are new, uninformed applications. It updates the application's status to informed.
- **Impact:** Enhances communication by ensuring business owners are promptly informed about new applications, improving response times and engagement.

2. **File: `app/Livewire/Business/ModalBriefing.php`**
- **Status:** Added
- **Changes:** Introduced a Livewire component to handle order briefings.
- **Description:** This file sets up a Livewire component that renders a view for order briefings.
- **Impact:** Streamlines the process of viewing and updating order briefings, making it more interactive and real-time for users.

3. **File: `app/Livewire/OrderChat.php`**
- **Status:** Added
- **Changes:** Added a Livewire component for order chat functionality.
- **Description:** Fetches and displays the chat messages exchanged between users and creators related to an order.
- **Impact:** Improves communication flow by allowing real-time chat interactions within the order management interface.

4. **File: `app/Livewire/OrderChatForm.php`**
- **Status:** Added
- **Changes:** Introduced a form component for sending messages in an order chat.
- **Description:** Enables users to send and validate messages, then adds them to the chat.
- **Impact:** Enhances user experience by providing a real-time, interactive platform for communication.

5. **File: `app/Models/OrderChat.php`**
- **Status:** Added
- **Changes:** Created a model for order chat messages.
- **Description:** Defines the structure and fields for storing chat messages related to orders.
- **Impact:** Establishes a database structure for persisting order chats, facilitating better tracking and retrieval of messages.

6. **File: `app/Notifications/ApplicationApproved.php`**
- **Status:** Added
- **Changes:** Notification class for informing users when their application is approved.
- **Description:** Implements email notifications using a custom SMTP channel to notify users of approved applications.
- **Impact:** Enhances communication by keeping users informed about the status of their applications.

7. **File: `app/Notifications/NewApplications.php`**
- **Status:** Added
- **Changes:** Notification class for informing users about new applications.
- **Description:** Sends email notifications when new applications for an order are received.
- **Impact:** Ensures timely notifications, allowing users to manage applications more efficiently.

8. **File: `database/migrations/2024_04_27_234641_add_informed_to_order_applications_table.php`**
- **Status:** Added
- **Changes:** Adds a new column to track informed applications.
- **Description:** Updates the `order_applications` table to include an `informed` status boolean.
- **Impact:** Permits better tracking of application statuses, contributing to more efficient application processing.

9. **File: `database/migrations/2024_05_15_135434_create_order_chats_table.php`**
- **Status:** Added
- **Changes:** Creates a new table for storing order chat messages.
- **Description:** Establishes the database schema for the `order_chats` table, including necessary fields and relationships.
- **Impact:** Facilitates the storage and management of order-related chat messages, enabling related features.

10. **File: `app/Console/Kernel.php`**
- **Status:** Modified
- **Changes:** Scheduled new console commands, including sending email notifications.
- **Description:** Updates the kernel to include a schedule for sending notification emails every six hours.
- **Impact:** Automates the notification process, ensuring notifications are sent in a timely manner without manual intervention.

11. **File: `app/Http/Controllers/BlogPostPublicController.php`**
- **Status:** Modified
- **Changes:** Adjusted method and view handling for blog posts.
- **Description:** Updated route handling and view naming conventions to improve clarity and organization.
- **Impact:** Refines the structure and readability of the code, making it easier to maintain and extend.

12. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** Significant updates including adding notifications and refactoring views.
- **Description:** Enhanced order processing by adding user notifications for application approvals and reorganizing views for better maintainability.
- **Impact:** Improves the user experience by providing timely updates and clearer code structure for developers.

13. **File: `app/Http/Controllers/ProductController.php`**
- **Status:** Modified
- **Changes:** Refined view routes and storage paths.
- **Description:** Reorganized view paths and updated image storage locations from `public` to `storage`.
- **Impact:** Enhances the code organization and security by moving user-uploaded files to a more appropriate storage location.

14. **File: `app/Http/Controllers/TaskController.php`**
- **Status:** Modified
- **Changes:** Updated view paths for task management.
- **Description:** Adjusted the task controller to point to newly organized view files.
- **Impact:** Improves maintainability and logical organization of task-related views.

15. **File: `app/Http/Controllers/UserProfileController.php`**
- **Status:** Modified
- **Changes:** Updated avatar upload paths from `public` to `storage`.
- **Description:** Enhanced security and organization for user profile pictures by using the `storage` path.
- **Impact:** Improves security for user-uploaded assets and aligns with best practices for file handling.

16. **File: `app/Livewire/Business/BriefingView.php`**
- **Status:** Modified
- **Changes:** Corrected path for a view related to briefings.
- **Description:** Refactored the path to align with the new structure.
- **Impact:** Enhances code maintainability and clarity.

17. **File: `app/Livewire/Business/CheckoutForm.php`**
- **Status:** Modified
- **Changes:** Corrected path for checkout form view.
- **Description:** Updated the path to ensure consistency and clarity.
- **Impact:** Maintains logical structure and simplifies further development.

18. **File: `app/Livewire/Business/UploadImages.php`**
- **Status:** Modified
- **Changes:** Moved upload images' view path.
- **Description:** Updated the path to align with the new structure.
- **Impact:** Improves maintainability and organization of view files.

19. **File: `app/Notifications/OrderCompleted.php`**
- **Status:** Modified
- **Changes:** Updated view path for order completion emails.
- **Description:** Adjusted the path ensuring it points to the correct email view.
- **Impact:** Ensures users receive the correct email format when an order is completed.

20. **File: `config/app_custom.php`**
- **Status:** Modified
- **Changes:** Minor configuration changes to improve functionality and security.
- **Description:** Updated tokens and file paths to switch based on environment.
- **Impact:** Enhances security by using different tokens for different environments and refines configuration for better functionality.

21. **File: `public/robots.txt`**
- **Status:** Modified
- **Changes:** Added sitemap link to the robots.txt file.
- **Description:** Ensures that search engines are informed about the sitemap location.
- **Impact:** Improves search engine optimization (SEO) by providing search engines with easier access to the sitemap.

22. **File: `resources/css/app.css`**
- **Status:** Modified
- **Changes:** Added styling for thin scrollbars.
- **Description:** Enhances the visual appearance of the application by improving scrollbar aesthetics.
- **Impact:** Improves the overall user interface and user experience.

23. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** Added new translations for the dashboard section.
- **Description:** Enhanced localization support by adding new language strings.
- **Impact:** Provides a better user experience for Portuguese-speaking users.

24. **File: `resources/lang/pt_br/email.php`**
- **Status:** Modified
- **Changes:** Added new email-related translations.
- **Description:** Enhanced localization for email notifications.
- **Impact:** Improves communication clarity with local users by providing emails in their preferred language.

25. **File: `app/Livewire/Business/OrderProcess.php`**
- **Status:** Renamed
- **Changes:** Renamed file and adjusted view path for order processing.
- **Description:** Renamed for better clarity and alignment with naming conventions.
- **Impact:** Enhances the logical organization and clarity of the Livewire components.

26. **File: `app/Livewire/Creator/DashboardAppliedTasks.php`**
- **Status:** Renamed
- **Changes:** Moved to the creator namespace and reassigned view path.
- **Description:** Ensures a more organized namespace structure for creator-specific components.
- **Impact:** Improves maintainability and navigability of the code.

27. **File: `app/Livewire/Creator/DashboardOpenTasks.php`**
- **Status:** Renamed
- **Changes:** Moved to the creator namespace and updated view path.
- **Description:** Refactored for better organization and clarity.
- **Impact:** Facilitates easier maintenance and clearer separation of concerns within the codebase.

These changes collectively improve the core functionalities and build a more robust and user-friendly application.

---

# #97 Enhancing Order Management and Notification System

## Introduction
This pull request introduces significant enhancements to the order management system. The updates include:
- A new notification feature to inform users when an order is completed.
- Numerous changes to the order processing logic, including improved error handling and order status management.
- Improvements in the user interface for better management of creator applications for orders.
- Language and UI adjustments to ensure clear and consistent communication.

These changes aim to improve user experience, enhance system reliability, and ensure timely notifications, which will make the platform more robust and user-friendly.

## Changes Overview

1. **File: `app/Notifications/OrderCompleted.php`**
- **Status:** Added
- **Changes:** A new notification class that sends an email via the Smtp2Go service when an order is completed.
- **Description:** This class is responsible for notifying users about their completed orders using the Smtp2Go email service. The notification includes a subject, headline, and other content relevant to the order.
- **Impact:** Ensures users are promptly informed about the status of their orders, enhancing communication and user satisfaction.

2. **File: `resources/views/emails/order-completed.blade.php`**
- **Status:** Added
- **Changes:** A new email template for the order completion notification.
- **Description:** This template structures the email content provided by the `OrderCompleted` notification class, including subject, headline, and other order information.
- **Impact:** Provides a visually consistent and informative email to users, improving the notification system's effectiveness.

3. **File: `app/Http/Controllers/DashboardController.php`**
- **Status:** Modified
- **Changes:** Adjustments to filter orders based on their status and applications.
- **Description:** The changes refine how orders are fetched and filtered, ensuring only relevant orders (based on new status terminology) are displayed.
- **Impact:** Improves accuracy in displaying order statuses, which enhances user navigation and order management.

4. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** Extensive updates to handle order processing, including new methods for managing creator applications and improved error handling.
- **Description:** Enhancements involve rigorous checks for order existence, user authorization, and updated logic for handling various order statuses. New methods allow closing, opening, accepting, and rejecting creator applications.
- **Impact:** Enhances the robustness of order processing and creator management, reduces potential errors, and improves system stability.

5. **File: `app/Http/Controllers/TaskController.php`**
- **Status:** Modified
- **Changes:** Change in order/task status check logic.
- **Description:** Adjusted the status checks to align with the new terminology 'ESCOLHA O CRIADOR'.
- **Impact:** Maintains consistency in order status terminology throughout the system, preventing conflicts and confusion.

6. **File: `app/Http/Controllers/WebhookController.php`**
- **Status:** Modified
- **Changes:** Update order statuses based on webhook events.
- **Description:** Ensures the order statuses are correctly updated based on webhook events from payment services, with added conditions for specific events like payment refunds and chargebacks.
- **Impact:** Ensures accuracy in order statuses based on real-time payment events, enhancing reliability.

7. **File: `app/Livewire/DashboardAppliedTasks.php`**
- **Status:** Modified
- **Changes:** Update status filters in order queries.
- **Description:** Adjustments ensure that the order queries match the new status terminology.
- **Impact:** Reduces inconsistencies in order display and improves the clarity of user interfaces related to task management.

8. **File: `app/Livewire/DashboardOpenTasks.php`**
- **Status:** Modified
- **Changes:** Similar to above, modifications align with new status terminology.
- **Description:** Ensures the correct orders are fetched based on the updated statuses.
- **Impact:** Similar to above, enhances the reliability of task management features.

9. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** Added new language lines for various notifications and user interactions.
- **Description:** Provides the necessary translations for new features and changes.
- **Impact:** Ensures that the application remains user-friendly for Portuguese-speaking users by keeping the language files up to date.

10. **File: `resources/lang/pt_br/email.php`**
- **Status:** Modified
- **Changes:** Added new translation lines for order completion email notifications.
- **Description:** Ensures the order completion notification email is well-understood by Portuguese-speaking users.
- **Impact:** Maintains clear communication with users in their preferred language.

11. **File: `resources/views/dashboard/business/dashboard.blade.php`**
- **Status:** Modified
- **Changes:** Adjust display logic for orders based on the new status terminology.
- **Description:** Upgraded the user interface to handle new order statuses appropriately.
- **Impact:** Enhances the user experience by accurately reflecting the state of each order.

12. **File: `resources/views/dashboard/business/order_applications.blade.php`**
- **Status:** Modified
- **Changes:** Extensive updates to handle creator applications more effectively.
- **Description:** Improved UI components for managing and displaying creator applications for orders, including actions to open/close applications and accept/reject creators.
- **Impact:** Provides a better and clearer user interface for managing creator applications, improving the workflow for users managing orders.

13. **File: `resources/views/dashboard/components/creator/dashboard-applied-tasks.blade.php`**
- **Status:** Modified
- **Changes:** Simplified the content by removing unnecessary code.
- **Description:** Streamlined the template to focus on core functionality.
- **Impact:** Reduces clutter in the codebase, making it easier to maintain.

14. **File: `resources/views/dashboard/components/creator/dashboard-open-tasks.blade.php`**
- **Status:** Modified
- **Changes:** Similar to applied tasks, simplified the content.
- **Description:** Ensures consistency and maintainability.
- **Impact:** Clean, manageable code consistent with system updates.

15. **File: `resources/views/dashboard/creator/task.blade.php`**
- **Status:** Modified
- **Changes:** Adjustments in the task details view to reflect the new status logic.
- **Description:** Ensures that the right tasks and statuses are displayed to users.
- **Impact:** Prevents confusion and ensures accurate task details are displayed.

16. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** Route additions and middleware adjustments.
- **Description:** New routes for managing creator applications and streamlined middleware for order processes.
- **Impact:** Introduces new capabilities in routing and access control which enhances feature management and security.

---

# #96 Introduction of Event-Driven Welcome Email System for User Roles

## Introduction
This pull request introduces an enhancement to the application by implementing a new event-driven mechanism that sends targeted welcome emails to users. When users verify their email addresses, they will now receive welcome emails tailored to their roles—either "creator" or "business." This functionality aims to improve the user experience by providing immediate engagement and relevant information upon account verification. The key areas of changes include adding a new listener for the email verification event, modifying existing notification classes, and updating the event service provider's configuration.

## Changes Overview
1. **File: `app/Listeners/SendWelcomeEmailToCreator.php`**
   - **Status:** Added
   - **Changes:** 
     - Created a new event listener class `SendWelcomeEmailToCreator`.
     - The class listens for the `Verified` event and sends different notifications to users based on their role.
   - **Description:** 
     - This file introduces a new event listener that handles the `Verified` event. If a user's email is verified, the listener checks the user's role and sends a corresponding welcome email using `Notification::sendNow()`.
     - This implementation differentiates between two types of users: "creator" and "business." Depending on the role, it uses either `WelcomeCreator` or `WelcomeBusiness` notification classes.
   - **Impact:**
     - Improves user engagement by sending welcome emails immediately upon email verification.
     - Ensures tailored communication, making the user feel recognized and valued based on their role.
     - Adds new dependencies on the `Verified` event and the `Notification` facade within the application.

2. **File: `app/Notifications/WelcomeBusiness.php`**
   - **Status:** Modified
   - **Changes:**
     - Added a new placeholder `subject` in the email view.
   - **Description:**
     - This minor change adds a `subject` attribute to the data passed to the email view, which uses the translated welcome subject.
     - This ensures consistency in the email content and allows easier customization of email subjects.
   - **Impact:**
     - Enhances the customization of the welcome email for business users.
     - No significant architectural impact but improves flexibility in email rendering.

3. **File: `app/Notifications/WelcomeCreator.php`**
   - **Status:** Modified
   - **Changes:**
     - Added a new placeholder `subject` in the email view.
   - **Description:**
     - Similar to the modification in `WelcomeBusiness.php`, this change includes a `subject` attribute to be used in the email template for creators.
   - **Impact:**
     - Improves the customization and personalization of the welcome email for creators.
     - No major architectural changes but enhances email content management.

4. **File: `app/Providers/EventServiceProvider.php`**
   - **Status:** Modified
   - **Changes:**
     - Added the import statement for `SendWelcomeEmailToCreator` and modified the event listener mapping to include the `Verified` event.
   - **Description:**
     - This update registers the `SendWelcomeEmailToCreator` event listener to respond to the `Verified` event.
     - Ensures that when the `Verified` event is triggered, the corresponding listener is invoked to handle it.
   - **Impact:**
     - Integrates the new event listener within the existing event service provider framework.
     - Ensures that the application reacts appropriately to email verification events.
     - Slightly increases the complexity of the `EventServiceProvider` but significantly boosts email engagement functionality.

---

# #95 Introduction of Transaction Model and Database Migration for Webhook Integrations

## Introduction
This pull request introduces significant changes to the transaction processing capabilities of our application. The primary focus lies on adding a new `Transaction` model, creating a corresponding database migration, and updating the `WebhookController` to handle transaction records more effectively. These changes enhance our ability to manage financial transactions resulting from webhook events, thereby improving the overall robustness and functionality of the transaction management system.

Main areas of change include:
- **New Feature Additions:** Introduction of `Transaction` model and database migration.
- **Controller Updates:** Modifications to `WebhookController` to incorporate the new `Transaction` model.
- **Data Management Enhancements:** Improved handling and storage of transaction-related data received from webhooks.

## Changes Overview
1. **File: `app/Models/Transaction.php`**
- **Status:** Added
- **Changes:** Added a new `Transaction` model with properties such as `user_id`, `provider`, `event`, `provider_id`, `customer_id`, `value`, etc. The model uses the `HasFactory` trait and declares the corresponding database table as 'transactions'.
- **Description:** The new `Transaction` model encapsulates all the necessary fields relevant to a transaction, offering a structured way to handle and store transaction data. This change is crucial to better manage incoming transaction data and to allow easy interaction with the database.
- **Impact:** This establishes a new foundation for transaction management within the application, providing a consistent and reusable way to interact with transaction data. Future enhancements or features related to transactions will be easier to implement.

2. **File: `database/migrations/2024_04_25_230551_create_transactions_table.php`**
- **Status:** Added
- **Changes:** Introduced a migration script to create the 'transactions' table in the database with all necessary fields such as `user_id`, `provider`, `event`, `provider_id`, `customer_id`, `value`, etc.
- **Description:** This migration sets up the database structure necessary to store the transaction records. It includes the definition of various fields and their data types, ensuring that all critical transaction details are captured and stored correctly.
- **Impact:** The database structure will now support transaction data, allowing the application to persist and query transaction details effectively. This change enhances the stability and reliability of transaction-related operations within the system.

3. **File: `app/Http/Controllers/WebhookController.php`**
- **Status:** Modified
- **Changes:** Updated the `asaas_cobranca` method to create a new transaction record using the `Transaction` model. The webhook handling logic has been extended to parse incoming data and store relevant transaction details. Additional `use` statements for the `Transaction` model, `UserAsaas` model, and `Carbon\Carbon` were included. Removed unnecessary comments in the `smtp2go_webhook` method.
- **Description:** These updates allow the `WebhookController` to handle incoming webhook data and store it as transaction records. Specifically, the `asaas_cobranca` method now creates `Transaction` entries using the provided data. The removal of redundant comments also improves code readability.
- **Impact:** Enhanced transaction tracking and management by incorporating the new `Transaction` model directly within the webhook processing logic. This ensures accurate and timely recording of transaction data, contributing to better financial and operational reporting. The refactored code also improves maintainability and clarity.

Overall, these changes ensure a more robust transaction handling mechanism within the application, aligning with the goal of improving data management and operational efficiency.

---

# #94 Pull Request Overview

## Introduction

This pull request implements a significant feature enhancement for the business order management dashboard. It introduces a new interface for viewing and managing order applications, refines existing order processing functions, and updates user interface elements for improved user experience. These changes collectively impact the functionality and usability of the application, allowing users to better manage order workflows and interact with creator applications effectively. The key areas of changes include new feature additions for order applications, updates to order processing logic, user interface improvements, and localization updates.

## Changes Overview

1. **File: `resources/views/dashboard/business/order_applications.blade.php`**
- **Status:** Added
- **Changes:** 
  - Introduced a new Blade view template for displaying order applications.
  - Implemented header, video playback, user information, modal pop-ups for application details, and various UI components.
- **Description:** 
  - This new file introduces the user interface layout for viewing order applications. It includes functionalities like video playback for application previews, user profile display, and modal dialogs for detailed application interactions.
- **Impact:** 
  - Enhances the order management capabilities by allowing users to view and manage applications directly. This improves the efficiency and usability of the dashboard.

2. **File: `resources/views/dashboard/business/order_task.blade.php`**
- **Status:** Added
- **Changes:** 
  - Created a basic layout for future task-related functionalities.
- **Description:** 
  - This file sets up a scaffold for task management within the dashboard.
- **Impact:** 
  - Prepares the application for future additions related to task management, potentially improving workflow management.

3. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** 
  - Added logic to handle new order statuses and operations related to viewing and managing order applications.
  - Introduced methods to ensure proper order status checks and redirects.
- **Description:** 
  - These changes involve managing the new order statuses and ensuring that operations like deletion and payment processing are correctly handled based on the order state.
- **Impact:** 
  - Enhances the robustness and correctness of order-related operations, ensuring that only valid state transitions are allowed.

4. **File: `app/Livewire/Business/BriefingView.php`**
- **Status:** Modified
- **Changes:** 
  - Removed status update logic.
- **Description:** 
  - This adjustment ensures that status updates are handled exclusively within the `OrderProcessController`.
- **Impact:** 
  - Centralizes status management, reducing redundancy and potential errors.

5. **File: `app/Models/OrderApplication.php`**
- **Status:** Modified
- **Changes:** 
  - Added relationships to `Order` and `User` models.
- **Description:** 
  - The file now includes methods to define the ORM relationships between order applications, orders, and users.
- **Impact:** 
  - Facilitates better data handling and querying capabilities, enhancing the interaction with connected models.

6. **File: `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** 
  - Added new language keys related to application functionalities.
- **Description:** 
  - Introduces localized strings for new UI components, such as application titles and button labels.
- **Impact:** 
  - Improves the application's localization, ensuring new features are also available in Portuguese.

7. **File: `resources/views/dashboard/business/dashboard.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Revised the dashboard layout, simplified columns, and updated logic for displaying orders.
- **Description:** 
  - The modifications streamline the dashboard layout, making it more readable and functional. It filters and sorts orders based on their statuses.
- **Impact:** 
  - Enhances user experience by providing a clearer and more organized overview of orders.

8. **File: `resources/views/dashboard/business/order_finished.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Updated the redirection link to navigate to the new order applications page.
- **Description:** 
  - Adjustments ensure users are directed to the appropriate section upon completing order processes.
- **Impact:** 
  - Improves navigation flow, enhancing usability.

9. **File: `resources/views/dashboard/components/header.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Improved user profile image handling, ensuring it is appropriately styled.
- **Description:** 
  - Minor UI tweaks to ensure profile images are displayed correctly.
- **Impact:** 
  - Enhances the visual consistency of the user interface.

10. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** 
  - Added new routes and grouped middleware for better route management.
- **Description:** 
  - The routing updates include adding paths for viewing order applications and structuring middleware for better security and functionality.
- **Impact:** 
  - Ensures correct routing and access control for the new features, enhancing overall application security and organization.

This pull request adds valuable features and improves existing functionalities, making the order management process more efficient and user-friendly. The new order applications interface, in particular, stands out as a significant advancement.

---

# #92 New Onboarding and Task Management Features

## Introduction
This pull request introduces a range of enhancements and new features focused on improving the user onboarding experience and task management functionalities. The changes involve adding new components, updating models and controllers, and tweaking user interface elements. These enhancements aim to provide a more intuitive and seamless experience for users, assisting them in completing their profiles efficiently and managing their tasks more effectively. The main areas of changes include new feature additions in the onboarding process, user experience (UX) improvements in displaying tasks, and modifications in the database schema to support these functionalities.

## Changes Overview
1. **File: `app/Livewire/DashboardAppliedTasks.php`**
   - **Status:** Added
   - **Changes:** New Livewire component to manage and display applied tasks.
   - **Description:** This file introduces a class `DashboardAppliedTasks` that manages loading and displaying tasks that the user has applied for and allows loading more tasks.
   - **Impact:** Enhances user experience by providing a dedicated section for applied tasks, allowing users to easily track their task applications.

2. **File: `app/Livewire/DashboardOpenTasks.php`**
   - **Status:** Added
   - **Changes:** New Livewire component to manage and display open tasks.
   - **Description:** Similar to the applied tasks component, this class `DashboardOpenTasks` handles loading and displaying open tasks, with functionality to load more tasks.
   - **Impact:** Improved task management by distinguishing between applied and open tasks, facilitating better user navigation and interaction.

3. **File: `app/Models/OrderApplication.php`**
   - **Status:** Added
   - **Changes:** Introduction of a new model to manage order applications.
   - **Description:** The `OrderApplication` model tracks details of user applications for orders, including status, timestamps, and related messages.
   - **Impact:** Provides a structured way to manage and query order applications, integral to the new task management and tracking features.

4. **File: `database/migrations/2024_04_22_221421_create_order_applications_table.php`**
   - **Status:** Added
   - **Changes:** New migration file to create `order_applications` table.
   - **Description:** Defines the schema for the new `order_applications` table, including foreign keys and timestamps.
   - **Impact:** Ensures the database is structured to support order applications, crucial for the new task-tracking functionalities.

5. **File: `database/migrations/2024_04_22_221800_change_order_table_names.php`**
   - **Status:** Added
   - **Changes:** Migration to rename various order-related tables for consistency.
   - **Description:** Updates table names to a more standardized format, ensuring consistency and clarity in database schema.
   - **Impact:** Simplifies database management and improves readability and consistency across the schema.

6. **File: `resources/views/dashboard/components/creator/dashboard-applied-tasks.blade.php`**
   - **Status:** Added
   - **Changes:** New blade view for displaying applied tasks.
   - **Description:** Presents a grid layout for displaying user-applied tasks with relevant details and action buttons.
   - **Impact:** Enhances user interface, providing a dedicated space for users to view their applied tasks.

7. **File: `resources/views/dashboard/components/creator/dashboard-open-tasks.blade.php`**
   - **Status:** Added
   - **Changes:** New blade view for displaying open tasks.
   - **Description:** Similar to the applied tasks view, this presents open tasks that the user can apply for.
   - **Impact:** Improves user experience by clearly separating tasks that are available for application from those already applied for.

8. **File: `resources/views/dashboard/creator/onboarding.blade.php`**
   - **Status:** Added
   - **Changes:** New onboarding blade view.
   - **Description:** Guides new users through completing their onboarding steps, ensuring all necessary details are provided.
   - **Impact:** Streamlines the onboarding process, helping new users quickly complete their profiles and start using the platform effectively.

9. **File: `app/Http/Controllers/DashboardController.php`**
   - **Status:** Modified
   - **Changes:** Added logic for checking onboarding completion and fetching task counts.
   - **Description:** Updates to handle new onboarding checks and task count retrievals, adapting the dashboard view accordingly.
   - **Impact:** Provides a smoother onboarding process and a more informative dashboard, aiding user navigation and task management.

10. **File: `app/Http/Controllers/OrderProcessController.php`**
    - **Status:** Modified
    - **Changes:** Updated model references and additional check for order status.
    - **Description:** Changes reflect model name updates and include order status checks before proceeding with order processes.
    - **Impact:** Prevents unauthorized access or actions on orders, enhancing security and data integrity.

11. **File: `app/Http/Controllers/TaskController.php`**
    - **Status:** Modified
    - **Changes:** Added logic for task application, cancellation, and onboarding checks.
    - **Description:** Enhances task application and management capabilities, ensuring users can apply for and manage tasks effectively.
    - **Impact:** Facilitates better task management, enhancing user engagement and activity on the platform.

12. **File: `app/Http/Controllers/UserProfileController.php`**
    - **Status:** Modified
    - **Changes:** Minor updates to handle profile photo uploads more effectively.
    - **Description:** Adjustments ensure proper handling and storage of user profile photos.
    - **Impact:** Enhances profile management, contributing to a more polished user experience.

13. **File: `app/Http/Kernel.php`**
    - **Status:** Modified
    - **Changes:** Addition of a new middleware for onboarding status checks.
    - **Description:** Registers `CheckOnboardingStatus` middleware that ensures users complete onboarding steps before accessing certain features.
    - **Impact:** Secures the platform by guiding new users to complete their profiles, improving user data completeness and integrity.

14. **File: `app/Livewire/Business/BriefingView.php`**
    - **Status:** Modified
    - **Changes:** Updated model references to match new table names.
    - **Description:** Aligns existing functionality with new database schema for briefing views.
    - **Impact:** Ensures consistency and proper function post-database schema changes.

15. **File: `app/Models/Order.php`**
    - **Status:** Modified
    - **Changes:** Added relationship for order applications.
    - **Description:** Introduces a new relationship between orders and applications.
    - **Impact:** Facilitates querying and managing order applications more efficiently.

16. **File: `app/Models/OrderCobranca.php`, `OrderCobrancaBoleto.php`, `OrderCobrancaPix.php`**
    - **Status:** Modified
    - **Changes:** Table name updates for consistency.
    - **Description:** Reflects updates from the schema change migration.
    - **Impact:** Ensures models align with the updated database schema, maintaining functional integrity.

17. **File: `resources/lang/pt_br/dashboard.php`, `general.php`**
    - **Status:** Modified
    - **Changes:** Added new translations for onboarding and task management.
    - **Description:** New and updated language entries to support new features.
    - **Impact:** Ensures multilingual readiness of the application, enhancing accessibility for more users.

18. **File: `resources/views/dashboard/business/briefing-view.blade.php`, `order_finished.blade.php`, `creator/dashboard.blade.php`, `creator/task.blade.php`**
    - **Status:** Modified
    - **Changes:** UI updates and new component integrations for better task and onboarding management.
    - **Description:** UI and UX improvements to accommodate new features and improve overall user experience.
    - **Impact:** Provides a more engaging and user-friendly interface, boosting user satisfaction and engagement.

19. **File: `resources/views/layouts/app.blade.php`**
    - **Status:** Modified
    - **Changes:** Enhanced alert handling for success and error messages.
    - **Description:** Updates how alerts are presented, ensuring they are noticeable and informative.
    - **Impact:** Improves user feedback mechanisms, aiding user navigation and action confirmations.

20. **File: `resources/views/profile/avatar-upload.blade.php`**
    - **Status:** Modified
    - **Changes:** Interface improvements for profile photo uploads.
    - **Description:** Adjustments to layout and interaction elements for better user experience.
    - **Impact:** Enhances the process of setting up profile photos, contributing to a more polished profile setup experience.

21. **File: `app/Models/OrderDetail.php`**
    - **Status:** Renamed
    - **Changes:** Class and table name updates for consistency.
    - **Description:** Reflects changes from schema migration, aligning model names with updated table names.
    - **Impact:** Ensures model and table name alignment, maintaining consistency and avoid potential conflicts.

These comprehensive changes collectively improve the onboarding process, provide clearer task management, and refine the user interface, significantly enhancing the overall experience and functionality of the application.

---

# #91 Migration and Notification System Update

## Introduction
This pull request introduces significant changes to the migration and notification aspects of the application. The main areas of improvements include:
- A new database migration script to modify the `html_body` column in the `email_statuses` table.
- Transition from the standard `Mail` notification channel to a custom `Smtp2GoChannel` for various notification classes.
- Updates to email templates to accommodate content and structural changes.
- Enhanced localization strings.

These changes aim to improve the application's flexibility with email content, optimize the notification system, and enhance user experience.

## Changes Overview
1. **File: `database/migrations/2024_04_22_151209_change_html_body_column_in_email_statuses_table.php`**
   - **Status:** Added
   - **Changes:** Added a new migration script to change the `html_body` column type in the `email_statuses` table from `string` to `longText`.
   - **Description:** This migration updates the database schema to allow for longer HTML content within emails, enhancing flexibility for email formatting and content.
   - **Impact:** This change ensures emails with rich HTML content are accommodated without truncation, potentially improving communication quality.

2. **File: `resources/views/emails/blank-message.blade.php`**
   - **Status:** Added
   - **Changes:** Added a new Blade template for a blank email message layout.
   - **Description:** The template extends an existing layout and sections for the title and content, ensuring consistency across emails using this template.
   - **Impact:** Simplifies email content management and maintains a consistent format for email communications.

3. **File: `app/Notifications/ContactReceived.php`**
   - **Status:** Modified
   - **Changes:** 
     - Implemented the `ShouldQueue` interface.
     - Changed the notification channel from `mail` to `Smtp2GoChannel`.
     - Updated the email content structure.
   - **Description:** Transition to using a custom email delivery channel and queuing for improved handling of email notifications.
   - **Impact:** Enhances reliability and flexibility of email deliveries, and improves performance through queuing.

4. **File: `app/Notifications/CustomResetPassword.php`**
   - **Status:** Modified
   - **Changes:** 
     - Added the `Smtp2GoChannel`.
     - Implemented changes to transform method signatures for the new channel.
   - **Description:** Adjusts password reset notifications to utilize the new email channel.
   - **Impact:** Consistent email handling, improved performance and reliability.

5. **File: `app/Notifications/CustomVerifyEmail.php`**
   - **Status:** Modified
   - **Changes:** 
     - Integrated `Smtp2GoChannel`.
     - Altered method names and signatures.
   - **Description:** Update verification emails to use `Smtp2GoChannel`.
   - **Impact:** Enhances email verification reliability and processing.

6. **File: `app/Notifications/FeedbackReceived.php`**
   - **Status:** Modified
   - **Changes:** 
     - Update to queued handling (`ShouldQueue` implementation).
     - Change notification channel to `Smtp2GoChannel`.
   - **Description:** Streamlines feedback notifications with the new email channel and improves handling through queuing.
   - **Impact:** Improves user feedback processing and reliability of notifications.

7. **File: `app/Notifications/WelcomeBusiness.php`**
   - **Status:** Modified
   - **Changes:**
     - Notification channel switched to `Smtp2GoChannel`.
     - Updated related method signatures.
   - **Description:** Utilizes `Smtp2GoChannel` for business welcome emails, optimizing the delivery method.
   - **Impact:** Boosts email delivery reliability for welcome messages.

8. **File: `app/Notifications/WelcomeCreator.php`**
   - **Status:** Modified
   - **Changes:**
     - Transition to using `Smtp2GoChannel`.
     - Updated respective method signatures.
   - **Description:** Facilitates creator welcome emails via the new `Smtp2GoChannel`.
   - **Impact:** Enhances the consistency and performance of email notifications.

9. **File: `resources/lang/pt_br/email.php`**
   - **Status:** Modified
   - **Changes:** 
     - Updated email content localization strings.
     - Changed structure to align with new email layout.
   - **Description:** Localization strings were adjusted to ensure compatibility with the new email templates and content structure.
   - **Impact:** Guarantees localized emails appear correctly and cohesively with new templates.

10. **File: `resources/views/emails/layout.blade.php`**
    - **Status:** Modified
    - **Changes:** Adjusted template placeholders to replace `@yield` with dynamic content using `{!! . . . !!}`.
    - **Description:** Enables dynamic content insertion for better control over email presentation.
    - **Impact:** Ensures that email layouts dynamically present content based on localization and specific content requirements.

---

# #90 Overview of Changes in Pull Request

## Title
Update User Validation to Check for Unique CPF/CNPJ in Users Table

## Introduction
This pull request focuses on refining the user creation validation process by adjusting the uniqueness checks for CPF (Cadastro de Pessoas Físicas) and CNPJ (Cadastro Nacional da Pessoa Jurídica). Instead of validating the uniqueness against separate tables (`users_cpf` and `users_cnpj`), the updated code validates the unique CPF and CNPJ values directly within the `users` table. This change is intended to streamline the database schema management and ensure consistent implementation of uniqueness checks for user identification numbers.

## Changes Overview
1. **File: `app/Actions/Fortify/CreateNewUser.php`**
- **Status:** Modified
- **Changes:** Updated the validation logic for CPF and CNPJ to ensure the uniqueness is checked within the `users` table.
  ```diff
  - 'cpf' => ['required', 'unique:users_cpf'],
  + 'cpf' => ['required', 'unique:users,cpf_cnpj_value'],
  - 'unique:users_cnpj',
  + 'unique:users,cpf_cnpj_value',
  ```
- **Description:** The CPF and CNPJ uniqueness checks have been modified. Previously, the code verified the uniqueness of CPF against the `users_cpf` table and CNPJ against the `users_cnpj` table. With this update, the validation now checks the `users` table's `cpf_cnpj_value` column for both CPF and CNPJ entries. This ensures that the new user creation process directly validates against the primary `users` table.
- **Impact:** These changes will centralize the unique identifier checks to a single table, potentially simplifying database management and improving data consistency. It's important to ensure that `users` table indexing and column structure support this new validation rule to prevent any adverse effects on performance during user creation. This change will also require current and future data migrations to properly reflect these updated validation requirements.

---

# #89 Addition of SweetAlert2 Notifications and Code Refactor

## Introduction
This pull request introduces the SweetAlert2 (`swal`) library to enhance the user notification system with animated toast messages and refactors the existing JavaScript and CSS codebase to streamline alert configuration and improve maintainability. The main areas of change include new feature additions for customizable alerts, consolidation of JavaScript files for better modularity, and integration of custom styles for toast notifications.

## Changes Overview

1. **File: `resources/js/swalConfig.js`**
   - **Status:** Added
   - **Changes:**
     - Imports SweetAlert2 and `animate.css` libraries.
     - Initializes and configures a toast notification system using SweetAlert2.
     - Sets up event listeners to trigger these toasts on specific user actions (e.g., button click).
   - **Description:** A new JavaScript configuration file was created to centralize the setup of SweetAlert2 (swal) toast notifications. This file imports the necessary libraries, configures toast options such as position, animation, and auto-close timer, and defines a custom class for different toast themes.
   - **Impact:** Improves the user experience with better visual feedback via well-styled and animated toast notifications. Enhances maintainability by isolating swal configuration into a dedicated file.

2. **File: `resources/css/app.css`**
   - **Status:** Modified
   - **Changes:**
     - Adds new styles for SweetAlert2 toast container.
     - Refines styles for error toast messages.
   - **Description:** Custom CSS was added to provide a better look and feel for toast notifications, ensuring that the application's design remains consistent and visually appealing.
   - **Impact:** Ensures visual consistency in toast notifications across the application, enhancing user experience.

3. **File: `resources/js/app.js`**
   - **Status:** Modified
   - **Changes:**
     - Removes SweetAlert2 import and configuration from this file.
     - Imports the newly created `swalConfig.js`.
     - Minor cleanup and restructuring for improved code organization.
   - **Description:** Refactored to offload SweetAlert2 configuration to `swalConfig.js`, reducing clutter and improving modularity in the main application JavaScript file.
   - **Impact:** Enhances code organization and maintainability by separating configuration concerns. Simplifies the `app.js` file.

4. **File: `resources/js/passwordReveal.js`**
   - **Status:** Modified
   - **Changes:**
     - Refactored to run after the DOM content is loaded.
     - Removes jQuery import as it is no longer necessary within this file.
   - **Description:** Adjustments ensure that the password reveal functionality initializes correctly after the DOM is fully loaded, promoting better performance and reliability.
   - **Impact:** Enhances the reliability of the password reveal feature, ensuring it functions as expected without dependency issues.

5. **File: `resources/views/dashboard/business/checkout.blade.php`**
   - **Status:** Modified
   - **Changes:**
     - Refactors inline JavaScript into scoped push stacks for better Laravel blade handling.
     - Updates the implementation to use the newly configured SweetAlert2 mixin for showing toasts on certain user actions like copying PIX or boleto codes.
   - **Description:** Moves inline scripts into @push stacks to adhere to Laravel blade's best practices, ensuring scripts are only included when necessary. Incorporates the new swal mixin introduced in `swalConfig.js` for toast notifications.
   - **Impact:** Enhances code organization within blade files and ensures that toast notifications are consistent in design and behavior across the application. 

These changes collectively enhance the application's frontend functionality, improve the user experience with more engaging notifications, and make the codebase more maintainable.

---

# #88 Improved Form Handling in Registration Page

## Introduction
This pull request focuses on enhancing the registration page's form handling mechanism for an improved user experience and better data handling. The changes involve refining the use of old input values to ensure that previously entered data is retained when the registration form reloads. Key modifications include adjustments to input fields for name, lastname, birthday, email, password, and password confirmation, as well as removing the ‘required’ attribute from the terms checkbox and making adjustments to the registration button.

## Changes Overview
1. **File: `resources/views/auth/register.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Updated the `value` attribute in input fields for `name`, `lastname`, `birthday`, and `email` to handle old input values properly.
  - Removed the `required` attribute from the `password`, `password_confirmation`, and `terms` fields.
  - Uncommented and refactored the primary registration button and commented out the alternative button.
- **Description:** 
  - The `value` attributes in the input fields now include a check for existing input values (`$input['fieldname']`) and default to an empty string if none exist. This change helps retain user input values upon form submission failures, enhancing the user experience by preventing users from re-entering data.
  - Removing the `required` attribute from the `password`, `password_confirmation`, and `terms` fields shifts validation responsibilities to backend logic, ensuring the form validation is robust and comprehensive. 
  - The primary registration button is now uncommented and active, while the alternative button is commented out, reflecting a design or functional choice shift.
- **Impact:**
  - **Usability:** Users benefit from a smoother registration experience since previously entered data is maintained upon form reload, reducing frustration.
  - **Validation:** Validation now relies more on backend checks, reducing chances of frontend bypassing and improving data integrity.
  - **User Interface:** The adjustments to button rendering and checkbox requirements reflect a cleaner, more user-friendly interface while avoiding mandatory field blocking flow disruptions.

This pull request significantly improves the data handling and user interface of the registration feature, enhancing overall user satisfaction and preventing data loss during form submissions.

---

# #87 Updated Avatar Upload Workflow and UI Adjustments in User Profile Module

## Introduction
This pull request primarily focuses on enhancing the avatar upload functionality within the user profile module. The changes aim to improve the user experience by updating the image processing workflow and removing some redundant interface behaviors. The updates include modifications to the `UserProfileController` to integrate a more robust image manager, adjustments to the image path handling to ensure better file organization, and minor UI tweaks to prevent unnecessary refresh calls. These changes collectively help in ensuring a smoother, more efficient user interaction and streamlined backend processes when handling user avatars.

## Changes Overview

1. **File: `app/Http/Controllers/UserProfileController.php`**
   - **Status:** Modified
   - **Changes:**
     - Added import for `Intervention\Image\Drivers\Gd\Driver as Gd`.
     - Updated logic in the `avatar_upload` method:
       - Changed the image manager instantiation to use `Gd` driver.
       - Modified variable names for better clarity (`$avatar` to `$imageFile`, etc.).
       - Updated the destination path logic to check and create directories if they do not exist.
       - Optimized image resizing logic to maintain aspect ratio.
       - Adjusted handling of file paths to align with new directory structure.
   - **Description:** These changes were made to improve the avatar image processing workflow by utilizing the `Gd` driver for better compatibility and performance. Directory checks and creations ensure no missing directories cause errors. The improvements aim to streamline the process, secure accurate file handling, and maintain the correct aspect ratio during resizing.
   - **Impact:**
     - Enhances compatibility and performance of image processing.
     - Prevents issues related to missing directories.
     - Improves overall robustness of the avatar upload feature.

2. **File: `app/Livewire/AvatarUpload.php`**
   - **Status:** Modified
   - **Changes:** Commented out the `dispatch('refresh-nav')` line inside the `deleteProfilePhoto` method.
   - **Description:** This line was responsible for dispatching a navigation refresh event, which has been identified as redundant and thus commented out to avoid unnecessary operations.
   - **Impact:**
     - Slightly improves the performance by avoiding redundant UI updates.
     - Reduces potential flickering or delays in the user interface.

3. **File: `resources/views/profile/setcard.blade.php`**
   - **Status:** Modified
   - **Changes:** Removed the `Livewire.dispatch('refresh-nav');` line from the success callback function.
   - **Description:** Similar to the modification in `AvatarUpload.php`, this line was removed to prevent redundant navigation refresh events upon successful avatar dispatch.
   - **Impact:**
     - Provides a cleaner and more efficient user interface experience.
     - Helps in reducing unnecessary refresh actions, leading to a smoother user interaction.

These changes collectively enhance both backend functionality and front-end user experience when dealing with avatar uploads and profile updates.

---

# #86 New "Coming Soon" Page and Various UI/UX Enhancements

## Introduction
This pull request introduces a new "Coming Soon" page and incorporates several UI and UX improvements across various sections of the application. These changes enhance user interaction, specifically within forms and error message displays, and add a new route for the 503 error page. Key areas impacted include the newsletter subscription functionality, general form validation, error handling, and UI components for login and verification views. 

The primary changes involve:
- Addition of a new feature: "Coming Soon" page.
- UI/UX enhancements for better error message handling and form interactions.
- Localization updates for error messages.
- Minor backend adjustments to support the new functionalities.

## Changes Overview
1. **File: `app/Livewire/ComingSoonPage.php`**
- **Status:** Added
- **Changes:** Added a Livewire component for handling "Coming Soon" page functionalities, including newsletter subscriptions.
- **Description:** This new class uses Livewire to create reactive, dynamic user experiences. It includes methods to handle the newsletter subscription form submissions, validate input, and provide user feedback.
- **Impact:** Introduces new dynamic functionality to the upcoming "Coming Soon" page enabling user engagement even before the site is fully launched.

2. **File: `resources/views/errors/newsletter-form.blade.php`**
- **Status:** Added
- **Changes:** Added a Blade template for rendering the newsletter subscription form within the "Coming Soon" page.
- **Description:** This view file provides the HTML structure and Livewire directives to facilitate the newsletter subscription functionality with responsive design and interactive elements.
- **Impact:** Enhances user experience by providing an interactive and reactive subscription form.

3. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** Added a minor code change involving additional spacing and a new line within the `completed` method.
- **Description:** This modification improves code readability without altering existing functionalities.
- **Impact:** None significant on functionality but improves the code maintainability.

4. **File: `app/Livewire/FooterHomepage.php`**
- **Status:** Modified
- **Changes:** Added validation for missing email input in the newsletter subscription function.
- **Description:** Ensures that the user receives appropriate feedback if the email field is left empty, improving form validation.
- **Impact:** Improves user experience by providing clear error messages and preventing invalid form submissions.

5. **File: `resources/lang/pt_br/general.php`**
- **Status:** Modified
- **Changes:** Added a new language line for `email_missing` error message in the Portuguese language file.
- **Description:** Introduces a new localized error message for missing email input.
- **Impact:** Enhances localization support, ensuring that users receive error messages in their preferred language.

6. **File: `resources/views/auth/forgot-password.blade.php`**
- **Status:** Modified
- **Changes:** Updated the session status message display with dismissible alerts and improved styles.
- **Description:** Replaced plain text alerts with a UI-enhanced, dismissible alert box to improve error display aesthetics and user experience.
- **Impact:** Improves user interaction by providing a more engaging and visually appealing error message display.

7. **File: `resources/views/auth/login.blade.php`**
- **Status:** Modified
- **Changes:** Enhanced the session status message display similar to the forgot password view with dismissible alerts.
- **Description:** Improved the design and functionality of error messages using a consistent, dismissible alert component.
- **Impact:** Consistent with other form views, it provides a better user experience through improved visual feedback and interaction.

8. **File: `resources/views/auth/verify-email.blade.php`**
- **Status:** Modified
- **Changes:** Updated the session status message display for email verification with a dismissible alert component.
- **Description:** Similar to other auth views, this change introduces a styled, dismissible alert to inform the user about email verification link status.
- **Impact:** Enhances the UI/UX by providing clear and aesthetically improved feedback mechanisms.

9. **File: `resources/views/components/footer-homepage.blade.php`**
- **Status:** Modified
- **Changes:** Updated the newsletter subscription form with new class and error message handling.
- **Description:** Improved the input fields and error handling in the footer newsletter form for better user experience.
- **Impact:** Results in a more cohesive and user-friendly footer component with clear feedback mechanisms.

10. **File: `resources/views/components/validation-errors.blade.php`**
- **Status:** Modified
- **Changes:** Enhanced the validation error messages display with a new dismissible alert UI component.
- **Description:** Improved the presentation of validation errors using a consistent, dismissible alert box to enhance UI consistency.
- **Impact:** Improves user interactions by providing visually appealing and clear validation messages.

11. **File: `resources/views/errors/503.blade.php`**
- **Status:** Modified
- **Changes:** Rewritten to provide a more user-friendly and interactive design during maintenance mode.
- **Description:** Converted the old layout to a new standalone HTML structure, significantly enhancing the user experience during maintenance periods by providing clear and engaging communication.
- **Impact:** Users are better informed and engaged even when the site is down for maintenance.

12. **File: `resources/views/layouts/errors.blade.php`**
- **Status:** Modified
- **Changes:** Added production-specific analytics scripts.
- **Description:** Ensured analytics scripts are only loaded in a production environment.
- **Impact:** Improves performance and tracks error page views only in relevant environments to provide meaningful data without impacting development.

13. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** Added a new route for a custom 503 error page.
- **Description:** Introduces a new route to handle and display the custom maintenance page.
- **Impact:** Provides users with a friendly and informative page during maintenance periods, ensuring continuity of communication.

---

# #85 Pull Request Overview

## Introduction
This pull request introduces significant changes to the application, encompassing new feature additions, security improvements, and configuration adjustments. The most notable changes include the addition of a `TaskController` for managing tasks, extensive configuration settings for various APIs and service pricing, multiple migrations for updating the database schema, and various updates across controllers, Livewire components, middleware, and views. These changes collectively aim to enhance the application's functionality, ensure better security practices, and offer a more robust and configurable user experience.

## Changes Overview

1. **File: `app/Http/Controllers/TaskController.php`**
   - **Status:** Added
   - **Changes:** New controller class added, with a method to view tasks by UUID.
   - **Description:** Introduces end-point for viewing task details.
   - **Impact:** Allows users to view specific tasks, enhancing task management.

2. **File: `config/app_custom.php`**
   - **Status:** Added
   - **Changes:** New custom configuration file created with settings for API tokens, pricing information, and available options.
   - **Description:** Consolidates various custom settings into a single configuration file.
   - **Impact:** Simplifies management of custom configurations and improves maintainability.

3. **File: `database/migrations/2024_03_30_171805_add_number_and_shipping_number_to_users_address.php`**
   - **Status:** Added
   - **Changes:** Migration to add `number` and `shipping_number` columns to `users_address` table.
   - **Description:** Enhances user address details by including more specific information fields.
   - **Impact:** Improves accuracy of address data stored in the database.

4. **File: `database/migrations/2024_04_05_211051_set_default_value_for_gender_in_orders_details_table.php`**
   - **Status:** Added
   - **Changes:** Migration to set default value for `gender` column in `orders_details` table.
   - **Description:** Ensures a default value is provided for `gender`, enhancing data consistency.
   - **Impact:** Prevents null values in gender field, ensuring consistent data entries.

5. **File: `app/Actions/Fortify/CreateNewUser.php`**
   - **Status:** Modified
   - **Changes:** Changed configuration reference for `cpfcnpj_token` to use `app_custom`.
   - **Description:** Updates to follow the new custom configuration structure.
   - **Impact:** Ensures API tokens are fetched from the correct configuration file.

6. **File: `app/Console/Commands/ContaAzulGetAccessToken.php`**
   - **Status:** Modified
   - **Changes:** Changed configuration references for ContaAzul client details to use `app_custom`.
   - **Description:** Aligns with the new consolidated configuration.
   - **Impact:** Uniform configuration management improves maintainability.

7. **File: `app/Http/Controllers/DashboardController.php`**
   - **Status:** Modified
   - **Changes:** Added fetching and passing of orders and products to the dashboard views.
   - **Description:** Enhances dashboard functionality by displaying more data.
   - **Impact:** Provides users with detailed information on their dashboard, improving the overall user experience.

8. **File: `app/Http/Controllers/OrderProcessController.php`**
   - **Status:** Modified
   - **Changes:** Reworked logic to fetch pricing and hooks configuration from `app_custom`.
   - **Description:** Streamlines the process configuration updates using the new consolidated configuration.
   - **Impact:** More robust and flexible handling of pricing and hooks information.

9. **File: `app/Http/Controllers/WebhookController.php`**
   - **Status:** Modified
   - **Changes:** Adjusted status translations for Asaas webhook handling.
   - **Description:** Updates status values to more descriptive translations for payment events.
   - **Impact:** Improves clarity and localization of payment statuses.

10. **File: `app/Http/Middleware/CheckUserAsaas.php`**
    - **Status:** Modified
    - **Changes:** Updated references to Asaas URLs and tokens to use `app_custom`.
    - **Description:** Aligns middleware to fetch configuration from the new custom config.
    - **Impact:** Ensures middleware uses the correct API endpoints and tokens.

11. **File: `app/Livewire/Business/BriefingView.php`**
    - **Status:** Modified
    - **Changes:** Adjusted to fetch video formats and languages from `app_custom`.
    - **Description:** Fetches configurations more dynamically using the consolidated settings file.
    - **Impact:** Enhances flexibility in handling different video formats and languages.

12. **File: `app/Livewire/Business/OrderProcessView.php`**
    - **Status:** Modified
    - **Changes:** Adjusted photo price reference to use `app_custom`.
    - **Description:** Consistent usage of new custom configuration for pricing.
    - **Impact:** Unified configuration handling.

13. **File: `app/Livewire/UpdateCreatorContactForm.php`**
    - **Status:** Modified
    - **Changes:** Added support for new address fields, updated validation rules.
    - **Description:** Updates Livewire component to handle additional address fields.
    - **Impact:** Improves user data accuracy and form validation.

14. **File: `app/Models/UserAddress.php`**
    - **Status:** Modified
    - **Changes:** Added new `number` and `shipping_number` fields.
    - **Description:** Updates the model to reflect the new database schema.
    - **Impact:** Ensures the UserAddress model supports the latest field additions.

15. **File: `app/Rules/CONTAAZULRule.php`**
    - **Status:** Modified
    - **Changes:** Changed CPF/CNPJ token reference to `app_custom`.
    - **Description:** Aligns rule validation to use the new configuration structure.
    - **Impact:** Improved consistency and maintainability of rule validations.

16. **File: `app/Rules/CPFCNPJRule.php`**
    - **Status:** Modified
    - **Changes:** Changed CPF/CNPJ token reference to `app_custom`.
    - **Description:** Aligns rule validation to use the new configuration structure.
    - **Impact:** Improved consistency and maintainability of rule validations.

17. **File: `app/Services/PaymentService.php`**
    - **Status:** Modified
    - **Changes:** Changed Asaas token and URL references to use `app_custom`.
    - **Description:** Updates service to accommodate new configurations.
    - **Impact:** Ensures the service utilizes the correct API information.

18. **File: `config/app.php`**
    - **Status:** Modified
    - **Changes:** Removed custom configuration settings.
    - **Description:** Deprecated old configuration settings now moved to `app_custom`.
    - **Impact:** Reduces redundancy in the configuration files.

19. **File: `resources/lang/pt_br/dashboard.php`**
    - **Status:** Modified
    - **Changes:** Added new translations and updated existing ones for the dashboard.
    - **Description:** Expands and refines language support for the Portuguese dashboard.
    - **Impact:** Enhances user experience for Portuguese-speaking users.

20. **File: `resources/lang/pt_br/profile.php`**
    - **Status:** Modified
    - **Changes:** Added and updated translations for profile management.
    - **Description:** Improves localization of profile-related messages.
    - **Impact:** Improves clarity and user experience.

21. **File: `resources/lang/pt_br/validation.php`**
    - **Status:** Modified
    - **Changes:** Added new phone validation message.
    - **Description:** Provides a clearer example for phone number validation.
    - **Impact:** Prevents user input errors with more descriptive validation messages.

22. **File: `resources/views/components/connected-account.blade.php`**
    - **Status:** Modified
    - **Changes:** Adjusted provider display name for LinkedIn.
    - **Description:** Fixes an issue where the full provider name was shown, now displays a user-friendly name.
    - **Impact:** Enhances readability and user-friendliness of account connections.

23. **File: `resources/views/dashboard/business/briefing-view.blade.php`**
    - **Status:** Modified
    - **Changes:** Update to display selected language name correctly from `app_custom`.
    - **Description:** Improves language selection display logic using the new configuration.
    - **Impact:** Better user experience in language selection fields.

24. **File: `resources/views/dashboard/business/checkout.blade.php`**
    - **Status:** Modified
    - **Changes:** Dynamic fetching of video and hook pricing from `app_custom`.
    - **Description:** Uses new configuration for displaying pricing dynamically.
    - **Impact:** More accurate and maintainable pricing display logic.

25. **File: `resources/views/dashboard/business/dashboard.blade.php`**
    - **Status:** Modified
    - **Changes:** Added new open and closed orders tabs, new stat displays.
    - **Description:** Enhances dashboard view with additional information and better structure.
    - **Impact:** Provides more insights and better user interface for business users.

26. **File: `resources/views/dashboard/business/products.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated product image alt attribute.
    - **Description:** Enhanced accessibility by providing better alternative text for images.
    - **Impact:** Improved accessibility for visually impaired users.

27. **File: `resources/views/dashboard/creator/dashboard.blade.php`**
    - **Status:** Modified
    - **Changes:** Added new sections for job management and stats.
    - **Description:** Enhances the creator dashboard with more detailed job and stat displays.
    - **Impact:** Provides a better overview and interaction for creators.

28. **File: `config/app_pricing.php`**
    - **Status:** Removed
    - **Changes:** Deleted the old pricing configuration file.
    - **Description:** Deprecated old pricing configurations now incorporated into `app_custom`.
    - **Impact:** Reduces redundancy and centralizes pricing configurations.

This comprehensive set of changes aims to streamline application management, enhance user experience, improve data accuracy, and strengthen overall functionality.

---

# #84 New Order Briefing Feature with Detailed Management

## Introduction
This pull request introduces several new features and modifications related to the order briefing process and its management in the application. The primary changes include the addition of new models, components, and migration files for handling order details more efficiently. These changes aim to improve the user experience for managing order briefings, enhance the security around order deletion, and extend the application's overall architecture to better support future enhancements. 

The main areas of changes include:
- **New Feature Additions:** New Livewire component for order briefing view, new model for Order Details.
- **Database Updates:** New migrations to create and modify order details table.
- **Controller Updates:** Enhancements to the OrderProcessController for handling order details.
- **Package Updates:** Updates to the dependencies in `package.json` to include a new range slider library and an upgrade of TinyMCE.

## Changes Overview

1. **File: `app/Livewire/Business/BriefingView.php`**
- **Status:** Added
- **Changes:** Introduction of a new Livewire component for the order briefing view.
- **Description:** This new component includes properties and methods for handling various details associated with an order, such as title, language, video format, visual descriptions, and more. It also includes dummy data for steps and creators, as well as methods to update order details.
- **Impact:** This change will allow users to view and update various aspects of an order briefing dynamically within the application, improving usability and data management.

2. **File: `app/Models/OrderDetails.php`**
- **Status:** Added
- **Changes:** Introduction of a new model for Order Details.
- **Description:** This model defines the attributes and relationships for the order details, including title, language, video format, sequence, topics, call-to-action (CTA), visual descriptions, and acceptance criteria.
- **Impact:** This model serves as a single source of truth for order briefing details, making it easier to manage and retrieve these details across the application.

3. **File: `database/migrations/2024_03_17_205928_create_order_details_table.php`**
- **Status:** Added
- **Changes:** Migration to create the `orders_details` table.
- **Description:** This migration defines the schema for the `orders_details` table, specifying columns for order ID, title, language, video format, sequence, topics, CTA, visual descriptions, acceptance criteria, gender, age range, and further requirements.
- **Impact:** Establishing this table is crucial for storing detailed information about each order, enabling complex querying and data management.

4. **File: `database/migrations/2024_03_26_193521_set_default_max_age_in_orders_details.php`**
- **Status:** Added
- **Changes:** Migration to modify the default value of the `max_age` column in `orders_details`.
- **Description:** Changes the default value of the `max_age` column from '40+' to '40'.
- **Impact:** This change standardizes the age criteria format, making data consistency and validation simpler.

5. **File: `database/migrations/2024_04_07_180930_add_photo_requirements_to_orders_details_table.php`**
- **Status:** Added
- **Changes:** Migration to add the `photo_requirements` column to the `orders_details` table.
- **Description:** Adds a text column for specifying photo requirements for an order.
- **Impact:** By including photo requirements, the detailed briefing provides more comprehensive guidance for order creators, enhancing clarity and expectation management.

6. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** Added error handling for non-existent orders and enhanced functions to include order details.
- **Description:** Updates include validating the existence of an order before attempting deletion and adding retrieval of order details in the briefing process.
- **Impact:** These changes enhance the security and robustness of the order management process, reducing the risk of errors and unauthorized actions.

7. **File: `app/Models/Order.php`**
- **Status:** Modified
- **Changes:** Added a one-to-one relationship to the OrderDetails model.
- **Description:** A new method `details` has been added to define the relationship between the Order and OrderDetails models.
- **Impact:** This relationship allows for easier retrieval and management of order details directly from an Order instance, promoting cleaner and more efficient code.

8. **File: `package.json`**
- **Status:** Modified
- **Changes:** Added `ion-rangeslider` dependency and upgraded `tinymce` version.
- **Description:** The `ion-rangeslider` library has been included for improved UI components, and `tinymce` has been upgraded from version 6.8.0 to 7.0.0 for better features and security fixes.
- **Impact:** These updates will enhance the visual and functional aspects of the application, providing users with a more sophisticated editing experience and additional UI capabilities.

---

# #83 New Password Visibility Toggle Feature Implemented

## Introduction
This pull request adds a new feature to the application, allowing users to toggle the visibility of their passwords on various authentication pages (login, register, confirm password, and reset password). The changes primarily include JavaScript and Blade template modifications to introduce a clickable icon that reveals or hides the password. This feature enhances user experience by making it easier for users to input and verify their passwords. Additionally, minor formatting improvements have been made to ensure consistency across the forms.

## Changes Overview
1. **File: `resources/js/passwordReveal.js`**
- **Status:** Added
- **Changes:** Introduced a new JavaScript file that provides the functionality to toggle password visibility.
- **Description:** 
  - The script uses jQuery to handle click events on elements with the `data-toggle-password` attribute.
  - It switches the input type between 'password' and 'text' and toggles visibility of the corresponding icons.
- **Impact:** 
  - Enhances user experience by allowing users to see their password when typing.
  - Minimal effect on page load time and performance.

2. **File: `resources/views/components/password-revealer.blade.php`**
- **Status:** Added
- **Changes:** Added a new Blade component to render the toggle button with icons for showing and hiding the password.
- **Description:** 
  - The component handles the button rendering and associates it with the password input field using the `data-toggle-password` attribute.
- **Impact:** 
  - Encourages reusability and cleaner code by separating the password reveal button into a component.

3. **File: `resources/js/app.js`**
- **Status:** Modified
- **Changes:** Imported the new `passwordReveal.js` script.
- **Description:** 
  - Ensures the password reveal functionality is included in the main application script.
- **Impact:**
  - Seamlessly integrates the new feature into the existing application setup.

4. **File: `resources/views/auth/confirm-password.blade.php`**
- **Status:** Modified
- **Changes:** Included the new password revealer component for the password input field.
- **Description:** 
  - Adds the eye icon to toggle password visibility on the confirm password page.
- **Impact:**
  - Improves user experience for confirming passwords.

5. **File: `resources/views/auth/login.blade.php`**
- **Status:** Modified
- **Changes:** Included the new password revealer component for the password input field and minor formatting updates.
- **Description:** 
  - Adds the eye icon to toggle password visibility on the login page.
  - Ensures consistent label formatting.
- **Impact:** 
  - Enhances user experience for logging in.

6. **File: `resources/views/auth/register.blade.php`**
- **Status:** Modified
- **Changes:** Included the new password revealer component for both password and password confirmation fields and minor formatting updates.
- **Description:** 
  - Adds the eye icon to toggle visibility for both password fields on the registration page.
  - Ensures consistent label formatting.
- **Impact:** 
  - Improves user experience when creating a new account.

7. **File: `resources/views/auth/reset-password.blade.php`**
- **Status:** Modified
- **Changes:** Included the new password revealer component for both password and password confirmation fields and minor formatting updates.
- **Description:** 
  - Adds the eye icon to toggle visibility for both password fields on the reset password page.
  - Ensures consistent label formatting.
- **Impact:** 
  - Enhances user experience when resetting their password.

Overall, the changes in this pull request significantly improve the user experience by adding a commonly expected feature for password input fields and maintaining code consistency across the application.

---

# #81 Enhanced User Registration with Multi-API Utilization and Database Schema Update

## Introduction
This pull request introduces significant updates to the user registration process by adding an additional API source for validating CNPJ numbers and adjusting the database schema for improved flexibility. The main changes are focused on improving the reliability of data fetched for CNPJ validation and allowing nullable categories in the products database, ensuring smoother operations and enhanced data integrity. 

The changes include:
- **New Feature Addition:** Dual API support for CNPJ validation.
- **Database Schema Update:** Making the `category_id` column in the `products` table nullable and changing its delete behavior.

## Changes Overview
1. **File: `app/Actions/Fortify/CreateNewUser.php`**
   - **Status:** Modified
   - **Changes:** 158 changes, with 103 additions and 55 deletions.
   - **Description:** 
     - Added support to fetch CNPJ data from an additional API (BrasilAPI).
     - Introduced logic to decide between the original API and the new API based on the availability and success of the responses.
     - Refactored code to handle different response structures from the two APIs.
     - Adjusted the validation logic and user creation process to accommodate new data fields provided by BrasilAPI.
   - **Impact:** 
     - Improved reliability and redundancy in validating CNPJ numbers.
     - Reduced possibility of relying on a single point of failure by having an alternative data source.
     - Ensured consistent user experience while creating new users regardless of which API responds successfully.

2. **File: `database/migrations/2024_02_18_055204_add_category_id_to_products_table.php`**
   - **Status:** Modified
   - **Changes:** 6 changes, with 4 additions and 2 deletions.
   - **Description:** 
     - Made the `category_id` column in the `products` table nullable.
     - Changed the foreign key constraint on `category_id` to `NO ACTION` on delete instead of setting the default.
   - **Impact:**
     - Allows products to exist without being associated with any category, improving flexibility in product management.
     - Prevents unintended changes from cascading deletions, thus preserving existing product data integrity more effectively.

These updates are geared towards improving the overall system's robustness and flexibility, ensuring that user data is accurately validated and database operations are more resilient.

---

# #80 Added Coupon Handling and Improved Order Processing

## Introduction
This pull request adds functionalities to handle discounts via coupons in the order processing system. The changes include migration to add a new field in the orders table, logic to apply and remove coupons, and UI updates for various order-related views. These enhancements aim to improve user experience by allowing the users to apply, manage, and view coupon discounts directly within the order processing flow. There are also improvements in the backend to ensure the order totals are correctly updated based on coupons and other order items.

## Changes Overview
1. **File: `database/migrations/2024_03_08_034338_add_coupon_amount_fields_to_orders_table.php`**
   - **Status:** Added
   - **Changes:** Added a new migration file to include a `coupon_amount` column in the `orders` table with data type `decimal(10, 2)` and a default value of 0.
   - **Description:** This migration allows storing the applied coupon amount in the database.
   - **Impact:** The database schema is modified to include a new column to store coupon discount amounts which will be essential for further order processing logic.

2. **File: `app/Livewire/Business/OrderProcessView.php`**
   - **Status:** Modified
   - **Changes:** Added logic to:
     - Apply coupons.
     - Reapply coupons if they were previously applied.
     - Calculate discounted prices.
     - Update the order totals based on coupons and other order details.
   - **Description:** This update introduces the ability to handle coupon codes and discounts within the `OrderProcessView` component, enhancing order processing.
   - **Impact:** Users can apply coupons to their orders, see instant feedback on discounts, and visualize the updated totals, improving overall user experience and order accuracy.

3. **File: `app/Models/Coupon.php`**
   - **Status:** Modified
   - **Changes:** Added scopes:
     - `isApplicableToUser`
     - `isValid`
     - `isCanBeUsed`
   - **Description:** These scopes help to filter and validate coupons based on user applicability, validity, and usage.
   - **Impact:** This ensures only applicable, valid, and usable coupons are processed, thereby preventing misuse and errors.

4. **File: `app/Models/Order.php`**
   - **Status:** Modified
   - **Changes:** Added properties:
     - `coupon`
     - `coupon_amount`
     - `additional_creators`
     - `total`
   - **Description:** These additions support storing coupon-related details directly within the `Order` model.
   - **Impact:** Enables handling and reflecting coupon data in the order records, facilitating accurate order tracking and processing.

5. **File: `resources/lang/pt_br/dashboard.php`**
   - **Status:** Modified
   - **Changes:** Added translation for `discount`.
   - **Description:** Provides the Portuguese translation for “Discount Total”.
   - **Impact:** Improves localization and user interface for Portuguese-speaking users.

6. **File: `resources/views/components/pricing/pricing-parent.blade.php`**
   - **Status:** Modified
   - **Changes:** Minor CSS adjustment (`ml-12 -mt-3`).
   - **Description:** Adjusts styling for better layout presentation.
   - **Impact:** Enhances UI presentation and consistency.

7. **File: `resources/views/dashboard/business/order-process-view.blade.php`**
   - **Status:** Modified
   - **Changes:** Refactoring of the order process view HTML and integration of coupon handling UI components.
   - **Description:** Modularized the view for better maintainability and added input fields, buttons, and messages for coupon application.
   - **Impact:** Improved user interface for order processing with coupon management options.

These changes collectively introduce improved functionality for handling discount coupons in the application, enhance the order processing user interface, and ensure that the system's backend can support these new features reliably.

---

# #79 Introduction

This update introduces several refinements to the Product management system within the application. These modifications enhance the code structure, consistency, and user experience when managing products. Key features include: refactored controllers, improved UI for editing products, and adjustments to route definitions for better maintainability.

## Changes Overview

### Product Controller

1. **File: `app/Http/Controllers/ProductController.php`**
   - **Status:** Modified
   - **Changes:**
       - Reformatted code for consistency.
       - Adjusted the method for deleting images to use request parameters.
   - **Description:** Enhances code readability and maintains consistent formatting across methods.
   - **Impact:** Simplifies the logic for handling product image deletions and improves overall code maintainability.

   ```php
   <?php

   namespace App\Http\Controllers;

   use App\Models\Product;
   use App\Models\ProductImage;
   use Illuminate\Http\Request;
   use Illuminate\Support\Facades\Auth;

   class ProductController extends Controller
   {
       public function list()
       {
           $products = Product::where('user_id', Auth::id())
               ->orderBy('created_at', 'desc')
               ->get();

           return view('dashboard.business.products', [
               'products' => $products
           ]);
       }

       public function save_new_product(Request $request)
       {
           $product = new Product();
           $product->title = $request->productname;
           $product->category_id = $request->category;
           $product->description = $request->description;
           $product->price = $request->price;
           $product->pronounciation = $request->pronounciation;
           $product->save();

           if ($request->hasFile('images')) {
               foreach ($request->file('images') as $file) {
                   $name = time() . '_' . $file->getClientOriginalName();
                   $filePath = $file->storeAs('productimages', $name, 's3');

                   $productImage = new ProductImage();
                   $productImage->user_id = Auth::id();
                   $productImage->product_id = $product->id;
                   $productImage->image = $filePath;
                   $productImage->save();
               }
           }

           if ($request->filled('redirection') && !Str::contains($request->redirection, 'criar-produto')) {
               return redirect($request->redirection)->with('success', __('dashboard.products.create_success'));
           } else {
               return redirect()->route('products.view')->with('success', __('dashboard.products.create_success'));
           }
       }

       public function edit_product($uuid)
       {
           $product = Product::where('uuid', $uuid)->first();

           return view('dashboard.business.edit_product', [
               'product' => $product
           ]);
       }

       public function delete_image()
       {
           $imageid = request('imageid');
           $image = ProductImage::findOrFail($imageid);

           if (Auth::id() != $image->user_id) {
               return redirect()->back()->with('error', __('auth.notauthorized'));
           }

           $image->delete();

           return redirect()->route('products.view')->with('success', __('dashboard.products.delete_image_success'));
       }

       public function save_edit_product($uuid, Request $request)
       {
           $product = Product::where('uuid', $uuid)->first();
           $product->title = $request->productname;
           $product->category_id = $request->category;
           $product->description = $request->description;
           $product->price = $request->price;
           $product->pronounciation = $request->pronounciation;
           $product->save();

           if (request()->hasFile('images')) {
               foreach (request()->file('images') as $file) {
                   $name = time() . '_' . $file->getClientOriginalName();
                   $filePath = $file->storeAs('productimages', $name, 's3');

                   $productImage = new ProductImage();
                   $productImage->user_id = Auth::id();
                   $productImage->product_id = $product->id;
                   $productImage->image = $filePath;
                   $productImage->save();
               }
           }

           if ($request->filled('redirection') && !Str::contains($request->redirection, 'criar-produto')) {
               return redirect($request->redirection)->with('success', __('dashboard.products.edit_success'));
           } else {
               return redirect()->route('products.view')->with('success', __('dashboard.products.edit_success'));
           }
       }

       public function delete_product($uuid)
       {
           $product = Product::where('uuid', $uuid)->first();
           if (Auth::id() == $product->user_id) {
               $product->delete();
           }

           return redirect()->route('products.view')->with('success', __('dashboard.products.delete_success'));
       }
   }
   ```

### Edit Product Blade

2. **File: `resources/views/dashboard/business/edit_product.blade.php`**
   - **Status:** Modified
   - **Changes:**
       - Reformatted HTML structure for better readability.
       - Improved accessibility and UI consistency.
       - Added JavaScript functionality to delete images using an updated route.
   - **Description:** Enhances the user interface for editing products by improving the layout and interactivity.
   - **Impact:** Provides a cleaner and more user-friendly experience when managing product data and images.

   ```blade
   <x-app-layout>
       <x-slot name="title">
           {{ __('dashboard.products.edit') }} - {{ config('app.name', 'Creatify') }}
       </x-slot>

       <div class="p-2 space-y-5 sm:p-5 md:pt-5">
           <div class="flex flex-col justify-center p-5 bg-white border border-gray-200 shadow-sm rounded-xl dark:bg-neutral-800 dark:border-neutral-700">
               <div class="relative h-full rounded-xl">
                   <div class="inset-0 w-full h-full">
                       <h2 class="mt-5 mb-10 text-4xl font-bold text-center text-gray-900 dark:text-neutral-200">
                           {{ __('dashboard.products.edit') }}
                       </h2>

                       <form action="{{ route('products.save_edit_product', ['uuid' => $product->uuid]) }}" class="flex flex-col" method="POST" enctype="multipart/form-data">
                           @csrf
                           @method('POST')
                           <input type="hidden" name="redirection" value="{{ old('redirection', request()->headers->get('referer')) }}" readonly>

                           <div class="max-w-screen-xl gap-16 px-4 pb-8 mx-auto lg:grid lg:grid-cols-2 lg:pb-16 lg:px-6">
                               <div class="col-span-2 lg:col-span-1">
                                   <div class="mb-6">
                                       <x-label for="productname" class="flex items-start gap-1 dark:text-neutral-200">
                                           {{ __('dashboard.products.name') }}
                                           <span class="text-rose-600">*</span>
                                       </x-label>
                                       <x-input id="productname" class="block w-full mt-1" type="text" name="productname" :value="$product->title" required :placeholder="__('dashboard.products.name_text')" />
                                   </div>
                                   <div class="mb-6">
                                       <x-label for="category" class="flex items-start gap-1 dark:text-neutral-200">
                                           {{ __('dashboard.products.category') }}
                                           <span class="text-rose-600">*</span>
                                       </x-label>
                                       <div class="relative mt-1">
                                           <select id="category" name="category" data-hs-select='{"placeholder": "{{ __('dashboard.products.category_text') }}", "toggleTag": "<button type=\"button\"></button>", "toggleClasses": "hs-select-disabled:pointer-events-none hs-select-disabled:opacity-50 relative py-2 px-4 pe-9 flex text-nowrap w-full cursor-pointer bg-white border border-stone-200 rounded-lg text-start text-sm text-stone-800 focus:outline-none focus:ring-2 focus:ring-creatify-2 dark:bg-neutral-800 dark:border-neutral-700 dark:text-neutral-200 dark:focus:outline-none dark:focus:ring-1 dark:focus:ring-neutral-600", "dropdownClasses": "mt-2 z-50 w-full min-w-[140px] max-h-[300px] overflow-y-auto z-50 p-1 space-y-0.5 bg-white rounded-xl shadow-[0_10px_40px_10px_rgba(0,0,0,0.08)] dark:bg-neutral-900", "optionClasses": "hs-selected:bg-stone-100 dark:hs-selected:bg-neutral-800 py-2 px-4 w-full text-sm text-stone-800 cursor-pointer hover:bg-stone-100 rounded-lg focus:outline-none focus:bg-stone-100 dark:bg-neutral-900 dark:hover:bg-neutral-800 dark:text-neutral-200 dark:focus:bg-neutral-800", "optionTemplate": "<div class=\"flex justify-between items-center w-full\"><span data-title></span><span class=\"hidden hs-selected:block\"><svg class=\"flex-shrink-0 w-3.5 h-3.5 text-stone-800 dark:text-neutral-200\" xmlns=\"http:.w3.org/2000/svg\" width=\"24\" height=\"24\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><polyline points=\"20 6 9 17 4 12\"/></svg></span></div>"}' class="hidden" required>
                                               @foreach ($productcategories as $category)
                                                   <option value="{{ $category->id }}" {{ $product->category_id == $category->id ? 'selected' : '' }}>{{ $category->name }}</option>
                                               @endforeach
                                           </select>
                                           <div class="absolute top-1/2 end-2.5 -translate-y-1/2">
                                               <svg class="flex-shrink-0 w-3.5 h-3.5 text-stone-500" xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
                                                 <path d="m7 15 5 5 5-5" />
                                                 <path d="m7 9 5-5 5 5" />
                                               </svg>
                                           </div>
                                       </div>
                                   </div>
                                   <div class="mb-6">
                                       <x-label for="description" class="flex items-start gap-1 dark:text-neutral-200">
                                           {{ __('dashboard.products.description') }}
                                           <span class="text-rose-600">*</span>
                                       </x-label>
                                       <textarea id="description" name="description" class="block w-full px-4 py-3 mt-1 text-sm border-gray-200 rounded-lg rounded-b-none focus:border-creatify-2 focus:ring-creatify-2 dark:bg-neutral-800 dark:border-neutral-700 dark:text-neutral-200 dark:placeholder:text-neutral-500 dark:focus:outline-none dark:focus:ring-1 dark:focus:ring-neutral-600" rows="5" placeholder="{{ __('dashboard.products.description_text') }}" required>{{ $product->description }}</textarea>
                                       <div class="hs-accordion-group">
                                           <div class="border border-t-0 dark:border-neutral-700 hs-accordion bg-creatify-bg dark:bg-neutral-700 rounded-b-md border-creatify-2" id="hs-basic-with-title-and-arrow-stretched-heading-one">
                                               <span class="inline-flex items-center justify-between w-full p-3 font-semibold text-gray-800 rounded-lg cursor-pointer hs-accordion-toggle hs-accordion-active:text-blue-600 gap-x-3 text-start hover:text-gray-500 disabled:opacity-50 disabled:pointer-events-none dark:hs-accordion-active:text-blue-500 dark:text-gray-200 dark:hover:text-gray-400 dark:focus:outline-none dark:focus:text-gray-400" aria-controls="hs-basic-with-title-and-arrow-stretched-collapse-one">
                                                   <div class="inline-flex items-center gap-2">
                                                       <img src="/img/svgs/hand-wavy.svg" class="w-5 h-5" alt="">
                                                       <p class="text-sm font-medium text-gray-900 dark:text-neutral-200">
                                                           {{ __('dashboard.products.no_idea') }}
                                                       </p>
                                                   </div>
                                                   <svg class="block hs-accordion-active:hidden size-4" xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
                                                     <path d="m6 9 6 6 6-6" />
                                                   </svg>
                                                   <svg class="hidden hs-accordion-active:block size-4" xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
                                                     <path d="m18 15-6-6-6 6" />
                                                   </svg>
                                               </span>
                                               <div id="hs-basic-with-title-and-arrow-stretched-collapse-one" class="hs-accordion-content hidden w-full overflow-hidden transition-[height] duration-300 px-6 pb-4" aria-labelledby="hs-basic-with-title-and-arrow-stretched-heading-one">
                                                   <p class="text-sm text-gray-800 dark:text-gray-200">
                                                       {{ __('dashboard.products.no_idea_text') }}
                                                   </p>
                                               </div>
                                           </div>
                                       </div>
                                   </div>
                                   <div class="gap-6 lg:grid lg:grid-cols-2">
                                       <div class="col-span-2 xl:col-span-1">
                                           <x-label for="price" class="flex items-end gap-1">
                                               {{ __('dashboard.products.price') }}
                                               <p class="mb-1 text-xs text-gray-400">
                                                   ({{ __('dashboard.products.optional') }})
                                               </p>
                                           </x-label>
                                           <span class="w-full relative before:text-gray-700 before:content-['R$'] before:absolute before:top-1/2 before:left-3 block before:-translate-y-1/2 before:font-bold before:dark:text-neutral-200">
                                               <x-input id="price" class="block w-full mt-1 pl-9" type="text" name="price" maxlength="6" :value="$product->price" placeholder="0,00" oninput="isPrice(this.value, this.id)" />
                                           </span>
                                           <div class="mt-2">
                                               <p class="text-sm text-gray-400">
                                                   {{ __('dashboard.products.price_text') }}
                                               </p>
                                           </div>
                                       </div>
                                       <div class="col-span-2 mb-6 xl:col-span-1">
                                           <x-label for="pronounciation" class="flex items-end gap-1 dark:text-neutral-200">
                                               {{ __('dashboard.products.pronounce') }}
                                               <p class="mb-1 text-xs text-gray-400">
                                                   ({{ __('dashboard.products.optional') }})
                                               </p>
                                           </x-label>
                                           <x-input id="pronounciation" class="block w-full mt-1" type="text" name="pronounciation" :value="$product->pronounciation" :placeholder="__('dashboard.products.pronounce_text')" />
                                       </div>
                                   </div>
                               </div>
                               <div class="col-span-2 lg:col-span-1">
                                   <div class="flex flex-col overflow-hidden bg-white border shadow-sm mt-9 border-stone-200 rounded-xl dark:bg-neutral-800 dark:border-neutral-700">
                                       <div class="flex items-center justify-between px-5 py-3 border-b gap-x-5 border-stone-200 dark:border-neutral-700">
                                           <h2 class="inline-block font-semibold text-stone-800 dark:text-neutral-200">
                                               {{ __('dashboard.products.upload_images') }}
                                           </h2>
                                       </div>
                                       <div class="p-5 space-y-4">
                                           <div class="grid grid-cols-2 gap-3 md:grid-cols-4">
                                               @foreach($product->images as $image)
                                                   <div id="dismiss-img{{ $image->id }}" class="relative">
                                                       <div class="relative flex-shrink-0 w-full overflow-hidden rounded-xl h-44">
                                                           <img class="absolute top-0 object-cover w-full h-full start-0 rounded-xl" src="{{ $image->image }}">
                                                       </div>
                                                       <div class="absolute z-10 top-2 end-2">
                                                           <button type="button" class="w-7 h-7 inline-flex justify-center items-center gap-x-1.5 font-medium text-sm rounded-full border border-stone-200 bg-white text-stone-600 shadow-sm hover:bg-stone-50 disabled:opacity-50 disabled:pointer-events-none focus:outline-none focus:bg-stone-50 dark:bg-neutral-800 dark:border-neutral-700 dark:text-neutral-400 dark:hover:bg-neutral-700 dark:focus:bg-neutral-700" data-hs-remove-element="#dismiss-img{{ $image->id }}">
                                                               <svg class="flex-shrink-0 w-4 h-4" xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M18 6 6 18" /><path d="m6 6 12 12" /></svg>
                                                           </button>
                                                       </div>
                                                   </div>
                                               @endforeach
                                           </div>
                                           <div class="flex items-center justify-center w-full">
                                               <label for="images" class="flex flex-col items-center justify-center w-full h-[19rem] bg-white border border-dashed cursor-pointer border-stone-300 rounded-xl dark:hover:bg-bray-800 dark:bg-neutral-800 dark:border-neutral-600 hover:bg-gray-50 dark:hover:border-gray-500 dark:hover:bg-gray-600">
                                                   <div class="flex flex-col items-center justify-center pt-5 pb-6">
                                                       <svg class="w-16 mx-auto text-stone-400 dark:text-neutral-400" width="70" height="46" viewBox="0 0 70 46" fill="none" xmlns="http://www.w3.org/2000/svg">
                                                           <path d="M6.05172 9.36853L17.2131 7.5083V41.3608L12.3018 42.394

---

# #78 Introduction

This update refines the feedback submission system, focusing on better file handling and validation for feedback image uploads. The `FeedbackController` now uses a customized storage path for images, while the `Feedback` Livewire component is simplified to remove redundant validation steps and ensure cleaner code.

## Changes Overview

### Feedback Controller

1. **File: `app/Http/Controllers/FeedbackController.php`**
   - **Status:** Modified
   - **Changes:**
      - Adjusted the storage path for feedback image uploads to `feedbackimages`.
   - **Description:** Specifies a more appropriate directory for storing feedback-related images.
   - **Impact:** Keeps uploaded feedback images organized within the storage system.

   ```php
   <?php

   namespace App\Http\Controllers;

   use Illuminate\Support\Facades\Storage;
   use Illuminate\Http\Request;

   class FeedbackController extends Controller
   {
       public function storeImage(Request $request){
           if ($request->hasFile('image')) {
               $path = $request->file('image')->store('feedbackimages');
               $url = Storage::url($path);
               return response()->json(['path' => $url]);
           }
           return response()->json(['error' => 'File not found.'], 400);
       }
   }
   ```

### Livewire Feedback Component

2. **File: `app/Livewire/Feedback.php`**
   - **Status:** Modified
   - **Changes:**
      - Removed duplicate validation call not necessary in this context.
   - **Description:** Simplifies the feedback submission process by removing redundant validation.
   - **Impact:** Enhances code clarity and performance by avoiding unnecessary actions.

   ```php
   <?php

   namespace App\Livewire;

   use Illuminate\Notifications\Notifiable;
   use App\Notifications\FeedbackReceived;
   use Illuminate\Support\Facades\Notification;
   use Illuminate\Support\Facades\Auth;
   use Livewire\Component;
   use Livewire\Features\SupportFileUploads\WithFileUploads;
   use Jantinnerezo\LivewireAlert\LivewireAlert;

   class Feedback extends Component
   {
       use LivewireAlert;
       use Notifiable;
       public $firstname;
       public $lastname;
       public $email;
       public $feedbackmessage;
       public $feedbackimage;
       public $imagePath;
       public $user;
       protected $rules = [
           'feedbackimage' => 'required',
           'feedbackmessage' => 'required|string',
       ];
       protected $listeners = ['imageUploaded' => 'setImage'];

       public function setImage($newName)
       {
           $this->feedbackimage = $newName;
       }

       public function mount(){
           $this->user = Auth::user();
       }

       public function submitFeedback(){
           $data = [
               'firstname' => $this->user->firstname,
               'lastname' => $this->user->lastname,
               'email' => $this->user->email,
               'role' => $this->user->role,
               'feedbackimage' => $this->feedbackimage,
               'feedbackmessage' => $this->feedbackmessage,
           ];

           Notification::route('mail', env('MAIL_FROM_ADDRESS'))
                         ->notify(new FeedbackReceived($data));
           $this->dispatch('feedback-send'); 
           $this->alert('success', 'Mail enviado');
           $this->feedbackimage = '';
           $this->reset(['firstname', 'lastname', 'email', 'feedbackimage', 'feedbackmessage']);
       }

       public function render()
       {
           return view('components.feedback');
       }
   }
   ```

### Feedback Form UI

3. **File: `resources/views/components/feedback.blade.php`**
   - **Status:** Modified
   - **Changes:**
      - Tweaked the AJAX upload URL to use a named route.
      - Formatting improvements for consistency and readability.
   - **Description:** Enhances the feedback image upload handling and ensures better maintainability.
   - **Impact:** Provides a cleaner experience for managing and displaying feedback-related functionalities.

   ```blade
   class="block p-2.5 w-full text-sm text-gray-900 bg-gray-50 rounded-lg border border-gray-300 focus:ring-blue-500 focus:border-blue-500 dark:bg-gray-600 dark:border-gray-500 dark:placeholder-gray-400 dark:text-white dark:focus:ring-blue-500 dark:focus:border-blue-500"
   id="imagePath" type="file" />
   <span class="hidden" id="loader-image">
       <svg aria-hidden="true" role="status" class="inline w-4 h-4 text-white me-3 animate-spin" viewBox="0 0 100 101" fill="none" xmlns="http://www.w3.org/2000/svg">
           <!-- SVG Path -->
       </svg> Loading...
   </span>
   <input id="feedbackimage" type="hidden" wire:model="feedbackimage" />
   ```

### Web Routes

4. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Updated the route path and added a named route for feedback image uploads.
   - **Description:** Simplifies route handling and improves URL management.
   - **Impact:** Ensures easier maintenance and better route organization for feedback-related actions.

   ```php
   <?php

   use Illuminate\Support\Facades\Route;
   use App\Http\Controllers\UserProfileController;
   use App\Http\Controllers\OrderProcessController;
   use App\Http\Controllers\DashboardController;
   use App\Http\Controllers\FeedbackController;
   use App\Http\Controllers\PaymentController;
   use App\Http\Controllers\PriceController;
   use App\Http\Controllers\ProductController;

   Route::post('/feedback/upload/image', [FeedbackController::class, 'storeImage'])->name('feedback.upload.image');

   // Other routes...
   ```

### Summary
These updates provide a more streamlined and efficient feedback mechanism, enhancing the user experience for submitting feedback while ensuring the backend processes are well-organized and maintainable. The modifications cater to feedback image handling, form validation improvements, and a more consistent structural approach.

---

# #77 Introduction

This update introduces a feedback submission system where users can provide feedback along with an optional image upload. A new `FeedbackController` and a `Feedback` Livewire component have been added to handle this functionality. The system also includes handling and sending notifications for received feedback. Various UI and structure changes have been made to support this feature.

## Changes Overview

### New Feedback Controller

1. **File: `app/Http/Controllers/FeedbackController.php`**
    - **Status:** Added
    - **Changes:**
        - A new method `storeImage` to handle image uploads via AJAX and return the image URL.
    - **Description:** Handles the storage of feedback images.
    - **Impact:** Allows users to upload images as part of their feedback submissions, returning the image URL to be stored.

    ```php
    <?php

    namespace App\Http\Controllers;
    use Illuminate\Support\Facades\Storage;
    use Illuminate\Http\Request;

    class FeedbackController extends Controller
    {
        public function storeImage(Request $request){
            if ($request->hasFile('image')) {
                $path = $request->file('image')->store('public/images');
                $url = Storage::url($path);
                return response()->json(['path' => $url]);
            }
            return response()->json(['error' => 'File not found.'], 400);
        }
    }
    ```

### New Livewire Feedback Component

2. **File: `app/Livewire/Feedback.php`**
    - **Status:** Added
    - **Changes:**
        - Handles form submission, image upload, and sending notifications.
    - **Description:** Manages the feedback process, including form data and user interaction.
    - **Impact:** Enables users to provide feedback with optional images which are then emailed to the support team.

    ```php
    <?php

    namespace App\Livewire;
    use Illuminate\Notifications\Notifiable;
    use App\Notifications\FeedbackReceived;
    use Illuminate\Support\Facades\Notification;
    use Illuminate\Support\Facades\Auth;
    use Livewire\Component;
    use Livewire\Features\SupportFileUploads\WithFileUploads;
    use Jantinnerezo\LivewireAlert\LivewireAlert;

    class Feedback extends Component
    {
        use LivewireAlert;
        use Notifiable;
        public $firstname;
        public $lastname;
        public $email;
        public $feedbackmessage;
        public $feedbackimage;
        public $imagePath;
        public $user;
        protected $rules = [
            'feedbackimage' => 'required',
            'feedbackmessage' => 'required|string',
        ];
        protected $listeners = ['imageUploaded' => 'setImage'];

        public function setImage($newName)
        {
            $this->feedbackimage = $newName;
        }

        public function mount(){
            $this->user = Auth::user();
        }

        public function submitFeedback(){
            $this->validate();
            $data = [
                'firstname' => $this->user->firstname,
                'lastname' => $this->user->lastname,
                'email' => $this->user->email,
                'role' => $this->user->role,
                'feedbackimage' => $this->feedbackimage,
                'feedbackmessage' => $this->feedbackmessage,
            ];

            Notification::route('mail', env('MAIL_FROM_ADDRESS'))
                ->notify(new FeedbackReceived($data));
            $this->dispatch('feedback-send'); 
            $this->alert('success', 'Mail enviado');
            $this->feedbackimage = '';
            $this->reset(['firstname', 'lastname', 'email', 'feedbackimage', 'feedbackmessage']);
        }

        public function render()
        {
            return view('components.feedback');
        }
    }
    ```

### New Notification Class

3. **File: `app/Notifications/FeedbackReceived.php`**
    - **Status:** Added
    - **Changes:**
        - Sends an email notification when feedback is received.
    - **Description:** Emails the feedback details to the support team.
    - **Impact:** Automates the notification process for received feedback.

    ```php
    <?php

    namespace App\Notifications;

    use Illuminate\Bus\Queueable;
    use Illuminate\Contracts\Queue\ShouldQueue;
    use Illuminate\Notifications\Messages\MailMessage;
    use Illuminate\Notifications\Notification;

    class FeedbackReceived extends Notification
    {
        use Queueable;
        private $data;

        public function __construct($data)
        {
            $this->data = $data;
        }

        public function via(object $notifiable): array
        {
            return ['mail'];
        }

        public function toMail(object $notifiable): MailMessage
        {
            return (new MailMessage)
                ->greeting(__('email.FeedbackReceived.greeting'))
                ->line(__('email.FeedbackReceived.line1', ['first_name' => $this->data['firstname']]))
                ->line(__('email.FeedbackReceived.line2', ['last_name' => $this->data['lastname']]))
                ->line(__('email.FeedbackReceived.line3', ['email' => $this->data['email']]))
                ->line(__('email.FeedbackReceived.line4', ['role' => $this->data['role']]))
                ->line(__('email.FeedbackReceived.line5', ['feedbackimage' => $this->data['feedbackimage']]))
                ->line(__('email.FeedbackReceived.line6', ['message' => $this->data['feedbackmessage']]))
                ->line('');
        }
    }
    ```

### Feedback Form UI

4. **File: `resources/views/components/feedback.blade.php`**
    - **Status:** Added
    - **Changes:**
        - Includes HTML and JavaScript for the feedback modal and form.
    - **Description:** Provides UI for feedback submission, including image upload and form input handling.
    - **Impact:** Enables users to submit feedback through a modal interface.

    ```blade
    <div wire:ignore id="feedback-modal" tabindex="-1" aria-hidden="true" class="hidden overflow-y-auto overflow-x-hidden fixed top-0 right-0 left-0 z-50 justify-center items-center w-full md:inset-0 h-[calc(100%-1rem)] max-h-full">
        <div class="relative w-full max-w-2xl max-h-full p-4">
            <div class="relative bg-white rounded-lg shadow dark:bg-gray-700">
                <div class="flex items-center justify-between p-4 border-b rounded-t md:p-5 dark:border-gray-600">
                    <h3 class="text-xl font-semibold text-gray-900 dark:text-white">
                        {{ __('dashboard.feedback.title') }}
                    </h3>
                    <button type="button" class="inline-flex items-center justify-center w-8 h-8 text-sm text-gray-400 bg-transparent rounded-lg hover:bg-gray-200 hover:text-gray-900 ms-auto dark:hover:bg-gray-600 dark:hover:text-white" data-modal-toggle="feedback-modal">
                        <svg class="w-3 h-3" aria-hidden="true" xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 14 14">
                            <path stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="m1 1 6 6m0 0 6 6M7 7l6-6M7 7l-6 6"/>
                        </svg>
                        <span class="sr-only">Close modal</span>
                    </button>
                </div>
                <form wire:submit.prevent="submitFeedback">
                    <div class="p-4 space-y-4 md:p-5">
                        <div class="grid sm:grid-cols-2 gap-y-1.5 sm:gap-y-0 sm:gap-x-5 border-t border-gray-200 sm:py-2 first:border-t-0 dark:border-neutral-700">
                            <div class="sm:col-span-12 xl:col-span-12">
                                <div class="sm:col-span-4 xl:col-span-3 2xl:col-span-2">
                                    <x-label for="feedbackmessage" value="{{ __('dashboard.feedback.message') }}" />
                                </div>
                                <div class="sm:col-span-8 xl:col-span-4">
                                    <textarea id="feedbackmessage" rows="4" wire:model="feedbackmessage" 
                                        class="block p-2.5 w-full text-sm text-gray-900 bg-gray-50 rounded-lg border border-gray-300 focus:ring-blue-500 focus:border-blue-500 dark:bg-gray-600 dark:border-gray-500 dark:placeholder-gray-400 dark:text-white dark:focus:ring-blue-500 dark:focus:border-blue-500" 
                                        placeholder="{{ __('dashboard.feedback.message_text') }}">
                                    </textarea>                    
                                    <x-input-error for="feedbackmessage" class="mt-1" />
                                </div>
                            </div>
                            <div class="sm:col-span-12 xl:col-span-12">
                                <div class="sm:col-span-4 xl:col-span-3 2xl:col-span-2">
                                    <x-label for="feedbackimage" value="{{ __('dashboard.feedback.upload_screenshot') }}" />
                                </div>
                                <div class="sm:col-span-8 xl:col-span-4">
                                    <input id="imagePath" type="file" class="block w-full mt-1" />
                                    <span class="hidden" id="loader-image">
                                        <svg aria-hidden="true" role="status" class="inline w-4 h-4 text-white me-3 animate-spin" viewBox="0 0 100 101" fill="none" xmlns="http://www.w3.org/2000/svg">
                                            <path d="M100 50.5908C100 78.2051 77.6142 100.591 50 100.591C22.3858 100.591 0 78.2051 0 50.5908C0 22.9766 22.3858 0.59082 50 0.59082C77.6142 0.59082 100 22.9766 100 50.5908ZM9.08144 50.5908C9.08144 73.1895 27.4013 91.5094 50 91.5094C72.5987 91.5094 90.9186 73.1895 90.9186 50.5908C90.9186 27.9921 72.5987 9.67226 50 9.67226C27.4013 9.67226 9.08144 27.9921 9.08144 50.5908Z" fill="#E5E7EB"/>
                                            <path d="M93.9676 39.0409C96.393 38.4038 97.8624 35.9116 97.0079 33.5539C95.2932 28.8227 92.871 24.3692 89.8167 20.348C85.8452 15.1192 80.8826 10.7238 75.2124 7.41289C69.5422 4.10194 63.2754 1.94025 56.7698 1.05124C51.7666 0.367541 46.6976 0.446843 41.7345 1.27873C39.2613 1.69328 37.813 4.19778 38.4501 6.62326C39.0873 9.04874 41.5694 10.4717 44.0505 10.1071C47.8511 9.54855 51.7191 9.52689 55.5402 10.0491C60.8642 10.7766 65.9928 12.5457 70.6331 15.2552C75.2735 17.9648 79.3347 21.5619 82.5849 25.841C84.9175 28.9121 86.7997 32.2913 88.1811 35.8758C89.083 38.2158 91.5421 39.6781 93.9676 39.0409Z" fill="currentColor"/>
                                        </svg> Loading...
                                    </span>
                                    <input id="feedbackimage" type="hidden" wire:model="feedbackimage" />
                                    <x-input-error for="feedbackimage" class="mt-1" />
                                </div>
                            </div>
                        </div>
                    </div>
                    <div class="p-4 border-t border-gray-200 rounded-b text-end md:p-5 dark:border-gray-600">
                        <button data-modal-hide="feedback-modal" type="button" class="py-2.5 px-5 ms-3 text-sm font-medium text-gray-900 focus:outline-none bg-white rounded-lg border border-gray-200 hover:bg-gray-100 hover:text-blue-700 focus:z-10 focus:ring-4 focus:ring-gray-100 dark:focus:ring-gray-700 dark:bg-gray-800 dark:text-gray-400 dark:border-gray-600 dark:hover:text-white dark:hover:bg-gray-700">
                            {{ __('dashboard.feedback.cancel') }}
                        </button>
                        <button type="submit" id="feeback-button" class="text-white bg-blue-700 hover:bg-blue-800 focus:ring-4 focus:outline-none focus:ring-blue-300 font-medium rounded-lg text-sm px-5 py-2.5 text-center dark:bg-blue-600 dark:hover:bg-blue-700 dark:focus:ring-blue-800">
                            {{ __('dashboard.feedback.send') }}
                        </button>
                    </div>
                </form>
            </div>
        </div>
    </div> 

    @script
    <script>
        document.getElementById('imagePath').addEventListener('change', function() {
            var file = this.files[0];
            var formData = new FormData();
            formData.append('image', file);
            var csrfToken = document.querySelector('meta[name="csrf-token"]').getAttribute('content');
            if(file){
                document.getElementById("feeback-button").disabled = true;
                var imagePathInput = document.getElementById("imagePath").style.display = "none";
                var loaderImage = document.getElementById("loader-image");
                loaderImage.classList.remove('hidden');
                $.ajax({
                    url: '/upload/feedback/image',
                    method: 'POST',
                    data: formData,
                    processData: false,
                    contentType: false,
                    headers: {
                    'X-CSRF-TOKEN': csrfToken
                    },
                    success: function(response) {
                        var imagePath = response.path;
                        document.getElementById('feedbackimage').value = imagePath;
                        document.getElementById("feeback-button").disabled = false;
                        loaderImage.classList.add('hidden');
                        var imagePathInput = document.getElementById("imagePath").style.display = "block";
                        Livewire.dispatch('imageUploaded', [imagePath]);
                    },
                    error: function(xhr, status, error) {
                        console.error(error);
                    }
                });
            }
        });
        $wire.on('feedback-send', () => {
            document.querySelector('[data-modal-hide="feedback-modal"]').click();
            document.getElementById('imagePath').value = '';
        });
    </script>
    @endscript
    ```

### New Language Lines

5. **File: `resources/lang/pt_br/dashboard.php`**
    - **Status:** Modified
    - **Changes:** Added new language lines for feedback-related text.
    - **Impact:** Localizes the feedback form.

    ```php
    'feedback' => [
        'title' => 'Enviar Feedback',
        'message' => 'Mensagem',
        'message_text' => 'Como podemos melhorar?',
        'upload_screenshot' => 'Faça upload de uma captura de tela',
        'cancel' => 'Cancelar',
        'send' => 'Enviar Feedback',
        'success' => 'Feedback enviado com sucesso',
    ],
    ```

6. **File: `resources/lang/pt_br/email.php`**
    - **Status:** Modified
    - **Changes:** Added new language lines for feedback notification emails.
    - **Impact:** Localizes the feedback notification emails sent to the support team.

    ```php
    'FeedbackReceived' => [
        'greeting' => 'Nova solicitação de contato',
        'line1' => 'Nome: :first_name',
        'line2' => 'Sobrenome: :last_name',
        'line3' => 'E-mail: :email',
        'line4' => 'Papel: :role',
        'line5' => 'Image: :feedbackimage',
        'line6' => 'Mensagem: :message',
    ],
    ```

### Footer Updates

7. **File: `resources/views/components/footer-homepage.blade.php`**
    - **Status:** Modified
    - **Changes:**
        - Renamed `email` to `newsLetteremail` to avoid conflicts.
    - **Impact:** Fixes variable conflicts, enhancing the newsletter subscription form functionality.

    ```blade
    <input type="email" wire:model="newsLetteremail" name="newsLetteremail" id="newsLetter" class="block w-full p-3 pl-10 text-sm text-gray-900 border rounded-l-lg dark:text-white placeholder:text-gray-400 focus:ring-0 focus:border-creatify-3 subscribe-input-field dark:bg-neutral-800" placeholder=" " autocomplete="username" />
    <x-label for="newsLetteremail" class="bg-white subscribe-input-label dark:bg-neutral-800" value="{{ __('general.footer.enter') }}" />
    @error('newsLetteremail')
    <span class="text-left text-red-500" style="position: absolute; width: 100%; left: 0;">{{ $message }}</span>
    @enderror
    ```

### Added Feedback Link in Layout

8. **Files: `resources/views/dashboard/components/header.blade.php`**, **`resources/views/layouts/admin.blade.php`**, **`resources/views/layouts/app.blade.php`**
    - **Status:** Modified
    - **Changes:** Added modal trigger links for the feedback form.
    - **Impact:** Provides quick access to the feedback form from main navigation areas.

    ```blade
    <a class="flex px-3 py-2 text-sm text-gray-800 rounded-lg hover:cursor-pointer gap-x-3 hover:bg-gray-100 focus:outline-none focus:bg-gray-100 dark:text-neutral-300 dark:hover:bg-neutral-800 dark:focus:bg-neutral-800"
       data-modal-target="feedback-modal" data-modal-toggle="feedback-modal">
       <!-- Icon and text here -->
    </a>
    ```

### Web Routes

9. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added route for storing feedback images

---

# #76 Introduction

This update primarily focuses on enhancing the user experience by integrating animated alerts using the SweetAlert2 library and Animate.css for smoother animations. Additionally, some handling logic inside the `AvatarUpload` class, and configurations in the `LivewireAlert` settings have been optimized to support the new alert system. The CSS and JavaScript files have been adjusted to reflect these changes.

## Changes Overview

### JavaScript Imports and Initializations

1. **File: `resources/js/app.js`**
    - **Status:** Modified
    - **Changes:**
        - Imported `animate.css`.
        - Imported and initialized `SweetAlert2` with customized configurations.
        - Implemented a sample toast trigger for SweetAlert2.
    - **Description:** Adds support for animated alerts and initializes a global instance of SweetAlert2.
    - **Impact:** Provides a modernization to the UX with animated alerts.

    ```javascript
    import 'animate.css';
    import Swal from "sweetalert2";
    
    const swalToastTheme = [
        'swal-toast-warning', 
        'swal-toast-success', 
        'swal-toast-error', 
        'swal-toast-question', 
        'swal-toast-info'
    ];
    
    const Toast = Swal.mixin({
        padding: "8px",
        toast: true,
        timerProgressBar: true,
        position: "bottom-end",
        showClass: {
            popup: `
            animate__animated
            animate__slideInRight
            animate__fast
            `
        },
        hideClass: {
            popup: `
            animate__animated
            animate__slideOutRight
            animate__fast
            `
        },
        showConfirmButton: false,
        timer: 5000,
    })

    $('#triggerSwal').on('click', function() {
        Toast.fire({
            title: "Auto close alert!",
            html: "I will close in <b></b> milliseconds.",
            didOpen: () => {
                const timer = Swal.getPopup().querySelector("b");
                let timerInterval = setInterval(() => {
                    timer.textContent = `${Swal.getTimerLeft()}`;
                }, 100);
            },
            customClass: {
                popup: 'swal-toast-error',
            }
        });
    });
    ```

### Livewire Alert Configuration

2. **File: `config/livewire-alert.php`**
    - **Status:** Modified
    - **Changes:**
        - Changed alert `position`, and added show/hide class attributes for animation effects.
    - **Description:** Configures `LivewireAlert` to support customizable SweetAlert2 settings with animations.
    - **Impact:** Ensures toasts exhibit smooth animations on display and hide operations.

    ```php
    return [
        'alert' => [
            'position' => 'bottom-end',
            'timer' => 3000,
            'toast' => true,
            'text' => null,
            'showCancelButton' => false,
            'showConfirmButton' => false,
            'timerProgressBar' => true,
            'showClass' => (object)[
                'popup' => 'animate__animated animate__slideInRight animate__fast'
            ],
            'hideClass' => (object)[
                'popup' => 'animate__animated animate__slideOutRight animate__fast'
            ],
        ],
        // Other configurations...
    ];
    ```

### AvatarUpload Logic Update

3. **File: `app/Livewire/AvatarUpload.php`**
    - **Status:** Modified
    - **Changes:**
        - Enhanced the `sweetAlertResponse` method to support custom class options.
    - **Description:** Allows the sweet alerts to have custom classes for more detailed styling.
    - **Impact:** Enables the possibility to customize the alert styling per type.

    ```php
    public function sweetAlertResponse($icon, $message)
    {
        $options = [
            'customClass' => (object)[
                'popup' => 'swal-toast-'.$icon,
            ],
        ];
        $this->alert($icon, __($message), $options);
    }
    ```

### CSS Styling for Alerts

4. **File: `resources/css/app.css`**
    - **Status:** Modified
    - **Changes:** Added custom classes for different alert types to be used by SweetAlert2.
    - **Description:** Styles SweetAlert2 toasts based on their type (success, error, warning, etc.).
    - **Impact:** Ensures a visually consistent and appealing alert system.

    ```css
    .swal-toast-error {
        @apply text-rose-500 !bg-rose-50 dark:text-rose-50 dark:!bg-rose-800
    }

    .swal-toast-error .swal2-timer-progress-bar-container .swal2-timer-progress-bar {
        @apply !bg-rose-500 dark:!bg-rose-50
    }

    .swal-toast-success {
        @apply text-green-500 !bg-green-50 dark:text-green-50 dark:!bg-green-800
    }

    .swal-toast-success .swal2-timer-progress-bar-container .swal2-timer-progress-bar {
        @apply !bg-green-500  dark:!bg-green-50
    }
    ```

### Package Configuration

5. **Files: `tailwind.config.js`, `package.json`**
    - **Status:** Modified
    - **Changes:**
        - Added relevant paths to Tailwind CSS configuration.
        - Included `animate.css` in the package configuration.
    - **Description:** Ensures Tailwind CSS processor picks up the required paths and includes the necessary packages.
    - **Impact:** Enables smooth integration of the newly added packages and paths into the ecosystem.

    ```json
    "dependencies": {
        "@alpinejs/collapse": "^3.13.5",
        "@alpinejs/focus": "^3.13.2",
        "alpinejs": "^3.13.5",
        "animate.css": "^4.1.1",
        // Other dependencies...
    }
    ```
    ```javascript
    content: [
        './vendor/laravel/jetstream/**/*.blade.php',
        './storage/framework/views/*.php',
        './resources/views/**/*.blade.php',
        './resources/js/**/*.js',
        "./node_modules/flowbite/**/*.js",
        "./node_modules/preline/dist/*.js",
    ]
    ```

### Summary

This set of changes significantly improves user feedback mechanisms by introducing animated alerts with SweetAlert2, leveraging Animate.css for smooth display/hide transitions, and enabling custom alert classes for better styling control. These changes enhance the overall user experience in web interactions by adding a layer of sophistication and responsiveness.

---

# #75 Introduction

This update includes changes to the `ContactController` and the contact form view to incorporate Google's reCAPTCHA validation. Additionally, some minor refactoring has been done to improve code efficiency and structure.

## Changes Overview

### Contact Controller Updates

1. **File: `app/Http/Controllers/ContactController.php`**
    - **Status:** Modified
    - **Changes:** Added reCAPTCHA validation, fixed improper usage of data retrieval, and streamlined the return statements.
    - **Description:** Ensures that form submissions are validated using reCAPTCHA and simplifies the retrieval of request data.
    - **Impact:** Enhances form security and ensures proper storage of user's IP address, timezone, and country.

    ```php
    public function store(Request $request) {
        try {
            $data = $request->validate([
                recaptchaFieldName() => recaptchaRuleName(),
                'first_name' => 'required|string|max:255',
                'last_name'  => 'required|string|max:255',
                'company'    => 'sometimes|string|max:255',
                'email'      => 'required|email|max:255',
                'message'    => 'required|string',
                'phone_number' => 'required|string|max:255',
            ]);

            $data = $request->all();
            $data['phone_number'] = $data['countrycode'] . $data['phone_number'];
            $data['ip_address'] = $request->ip();
            $data['policy'] = $request->input('policy') == 'on' ? 1 : 0;

            $contact = Contact::create($data);

            Notification::route('mail', env('MAIL_FROM_ADDRESS'))->notify(new ContactReceived($data));
            return redirect()->route('contact.view')->with('success', __('validation.custom.messagesent'));

        } catch (\Exception $e) {
            Log::error($e->getMessage());
            return redirect()->back()->with('error', 'validation.custom.messageerror');
        }
    }
    ```

### Contact Form View Updates

2. **File: `resources/views/contact.blade.php`**
    - **Status:** Modified
    - **Changes:**
        - Added the `@csrf` token inside the form for security.
        - Fixed the `id` attribute for the form.
    - **Description:** Ensures CSRF protection for the form submission and corrects the form layout.
    - **Impact:** Enhances security and correctness of the contact form implementation.

    ```html
    <div class="relative p-8 bg-white rounded-lg shadow-lg dark:bg-dark-2 sm:p-12">
        <form action="{{ route('contact.store') }}" method="POST" id="{{ getFormId() }}">
            @csrf
            @if ($errors->any())
                <div class="alert alert-danger">
                    <ul>
                        @foreach ($errors->all() as $error)
                            <li>{{ $error }}</li>
                        @endforeach
                    </ul>
                </div>
            @endif
            <div class="grid grid-cols-1 gap-x-8 gap-y-6 sm:grid-cols-2">
                <div>
                    <label for="first_name" class="block text-sm font-semibold leading-6 text-gray-900">First Name</label>
                    <input type="text" name="first_name" id="first_name" class="block w-full mt-1 border-gray-300 rounded-md">
                </div>
                <!-- More form fields... -->
            </div>
        </form>
    </div>
    ```

### Summary

These changes significantly improve the security and correctness of the contact form by incorporating reCAPTCHA validation and fixing issues related to data handling and form structure.

---

# #74 Enhancements to 2FA Input and HTML Email Adjustments

## Introduction

This pull request focuses on improving the UX for Two-Factor Authentication (2FA) and enhancing the HTML email templates. Specifically, it modifies the 2FA input fields for better user interaction and updates email templates for more consistent styling and usage.

## Changes Overview

### Stylesheet Adjustments

1. **File: `resources/css/app.css`**
    - **Status:** Modified
    - **Changes:**
        - Adjusted the padding inline for the `.authpage-input-field` class.
    - **Description:** The new styles make the padding adjustments more reusable with Tailwind classes.
    - **Impact:** Simplifies and standardizes padding for input fields.

    ```css
    .authpage-input-field {
        @apply pl-10 pr-5;
        height: 45px;
        ...
    }
    ```

### Script Enhancements

2. **File: `resources/js/app.js`**
    - **Status:** Modified
    - **Changes:**
        - Added functionality for handling the pin input on the 2FA challenge page using the `HSPinInput` from Preline.
    - **Description:** The new script dynamically handles the input of the 2FA code.
    - **Impact:** Enhances user experience by providing a more interactive and user-friendly input method for the 2FA codes.

    ```javascript
    import { HSPinInput } from "preline/dist/preline.js";
    window.addEventListener('load', () => {
        const path = window.location.pathname;
        const segments = path.split('/');
        if (segments[1] == 'two-factor-challenge') {
            const el = HSPinInput.getInstance('#pin-input');
            const inputTarget = document.querySelector('.__input2FaChallenge');
            el.on('completed', ({ currentValue }) => {
                inputTarget.value = currentValue.join('');
            });
        }
    });
    ```

### Auth Two-Factor Challenge View

3. **File: `resources/views/auth/two-factor-challenge.blade.php`**
    - **Status:** Modified
    - **Changes:**
        - Updated to include pin input fields using Tailwind and Preline for better input handling.
    - **Description:** Replaced the text input for the 2FA code with a more interactive pin input.
    - **Impact:** Provides a visually appealing and user-friendly input method for entering 2FA codes.

    ```html
    <form class="space-y-6" method="POST" action="{{ route('two-factor.login') }}">
        @csrf

        <div x-show="! recovery">
            <div class="flex items-center justify-center gap-2 sm:gap-3" data-hs-pin-input id="pin-input">
                <input autofocus type="number" class="!size-10 sm:!size-14 authpage-input-field text-center sm:!p-4 !p-2" placeholder="●" data-hs-pin-input-item>
                ...
            </div>
            <div class="hidden authpage-input-container">
                <input type="text" inputmode="numeric" name="code" id="code" class="authpage-input-field __input2FaChallenge" placeholder=" " autofocus x-ref="code" autocomplete="one-time-code">
                <x-label for="code" class="bg-white authpage-input-label dark:bg-neutral-800" value="{{ __('auth.2fa.code') }}">
            </div>
        </div>
        ...
    </form>
    ```

### Summary

These changes significantly enhance the user experience for 2FA by making input fields more interactive and intuitive. Furthermore, the adjustments to the email HTML ensure a consistent design that aligns with the overall application styling.

---

# #73 Adding and Modifying Email Templates and Notification Formatting

## Introduction

This pull request introduces new email layouts and templates, modifying the existing notifications to use these new designs. The updates ensure a consistent visual style and improve the user experience when interacting with the system via email.

## Changes Overview

### Email Templates

1. **File: `resources/views/emails/layout.blade.php`**
    - **Status:** Added
    - **Changes:** A new comprehensive email layout template with sections for header, content, action buttons, and footer. 
    - **Description:** The template standardizes the structure for all outgoing emails, ensuring a consistent look and feel.
    - **Impact:** Provides a reusable layout for different types of email communications.

    ```html
    <!-- HTML template for the email layout -->
    ```

2. **File: `resources/views/emails/reset-password.blade.php`**
    - **Status:** Added
    - **Changes:** A new specific template for reset password emails.
    - **Description:** Utilizes the new layout to format reset password notifications.
    - **Impact:** Ensures that reset password notifications are visually consistent with other email communications.

    ```html
    @extends('emails.layout')
    ...
    ```

3. **File: `resources/views/emails/verify-email.blade.php`**
    - **Status:** Added
    - **Changes:** A new specific template for verify email notifications.
    - **Description:** Utilizes the new layout to format email verification notifications.
    - **Impact:** Ensures that email verification notifications follow the new standardized email format.

    ```html
    @extends('emails.layout')
    ...
    ```

### Notification Classes

4. **File: `app/Notifications/CustomResetPassword.php`**
    - **Status:** Modified
    - **Changes:** Updated to use the new reset-password email template.
    - **Description:** Integrates the fresh layout to ensure the reset password notifications are using the latest design.
    - **Impact:** Enhances the user interface for reset password emails.

    ```php
    $mailMessage = (new MailMessage)
        ->subject(__('email.ResetPassword.subject'))
        ->view('emails.reset-password', [
            'url' => $url,
            'subtitle' => __('email.ResetPassword.subtitle'),
            'content' => __('email.ResetPassword.content'),
            ...
        ]);
    ```

5. **File: `app/Notifications/CustomVerifyEmail.php`**
    - **Status:** Modified
    - **Changes:** Updated to use the new verify-email email template.
    - **Description:** Integrates the fresh layout to ensure the email verification notifications are using the latest design.
    - **Impact:** Enhances the user interface for email verification notifications.
    
    ```php
    $mailMessage = (new MailMessage)
        ->subject(__('email.VerifyEmail.subject'))
        ->view('emails.verify-email', [
            'url' => $url,
            'subtitle' => __('email.VerifyEmail.subtitle'),
            'content' => __('email.VerifyEmail.content'),
            ...
        ]);
    ```

### Language Translation Files

6. **File: `resources/lang/pt_br/email.php`**
    - **Status:** Modified
    - **Changes:** Adjusted the text for new templates.
    - **Description:** Updated email message translations to match the new structure of the emails.
    - **Impact:** Ensures localized content is appropriately structured for the new email templates.

    ```php
    'VerifyEmail' => [
        'subject' => 'Verifique seu endereço de e-mail',
        'subtitle' => 'Você criou sua conta com sucesso.',
        ...
    ],
    'ResetPassword' => [
        'subject' => 'Redefinir senha',
        'subtitle' => 'Recebemos sua solicitação para alterar sua senha.',
        ...
    ],
    ```

### Other Modifications

7. **File: `resources/views/vendor/mail/html/button.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated to match the new button styling in the email template.
    - **Impact:** Ensures that action buttons in emails follow the new design guidelines.

    ```html
    <table border="0" cellpadding="0" cellspacing="0" width="100%" class="tableButton">
        ...
    </table>
    ```

8. **File: `resources/views/vendor/mail/html/layout.blade.php`**
    - **Status:** Modified
    - **Changes:** Streamlined the email layout to match the new holistic layout template.
    - **Impact:** Provides consistency across all email communications by utilizing a centralized layout template.

9. **File: `resources/views/vendor/mail/html/panel.blade.php`**
    - **Status:** Modified
    - **Changes:** Simplified the panel layout to align with the new template.
    - **Impact:** Ensures panels in emails are consistent with the new design.

    ```html
    {{ Illuminate\Mail\Markdown::parse($slot) }}
    ```

10. **File: `resources/views/vendor/mail/html/subcopy.blade.php`**
    - **Status:** Modified
    - **Changes:** Adjusted the subcopy section to follow the new layout style.
    - **Impact:** Improves the readability and consistency for email subcopy sections.

    ```html
    <table border="0" cellpadding="0" cellspacing="0" width="100%" class="tableDescription">
        ...
    </table>
    ```

11. **File: `resources/views/vendor/notifications/email.blade.php`**
    - **Status:** Modified
    - **Changes:** Enhanced the notification email template to follow updated formatting guidelines.
    - **Impact:** Ensures that notification emails look professional and are consistently formatted.

    ```html
    {{ __('email.subcopy', ['actionText' => $actionText]) }}<br>
    ...
    ```

## Impact and Summary

This series of changes will improve the consistency, aesthetics, and user experience of all email communications sent from the application. By standardizing the templates and using a new layout, users will receive visually coherent emails that align with the application's branding and provide clear, professional information.

---

# #72 Renaming LinkedIn Provider for Social Login

## Introduction

This pull request makes essential configuration changes to enable social login via LinkedIn using OpenID Connect. Previously, the application was using a standard LinkedIn OAuth2 provider. The changes involve updating the configuration to use `linkedin-openid` instead of `linkedin`.

## Changes Overview

### Configuration Files

1. **File: `config/services.php`**
    - **Status:** Modified
    - **Changes:** Updated the LinkedIn OAuth2 provider key to `linkedin-openid`.
    - **Description:** This modification ensures the application uses LinkedIn's OpenID Connect for authentication.
    - **Impact:** Changes how LinkedIn authentication details are fetched and processed.
    
    ```php
    ...
    'linkedin-openid' => [
        'client_id' => env('LINKEDIN_CLIENT_ID'),
        'client_secret' => env('LINKEDIN_CLIENT_SECRET'),
        'redirect' => env('LINKEDIN_REDIRECT_URI'),
    ],
    ...
    ```
    
2. **File: `config/socialstream.php`**
    - **Status:** Modified
    - **Changes:** Switched the provider from `Providers::linkedin()` to `Providers::linkedinOpenId()`.
    - **Description:** This change integrates LinkedIn using OpenID Connect within the Socialstream configuration.
    - **Impact:** Adapts the social authentication flow to match the OpenID Connect protocol for LinkedIn.
    
    ```php
    ...
    'providers' => [
        Providers::google(),
        Providers::facebook(),
        Providers::linkedinOpenId(),
        // Providers::twitterOAuth2(),
    ],
    ...
    ```

## Impact on the System

### Functionality
- **Enhancement:** Improves the application’s authentication capabilities by adopting LinkedIn OpenID Connect, providing more secure and standardized authentication.
- **Backward Compatibility:** The change is not backward compatible. Users need to update their environment variables and ensure the new redirect URIs and client credentials are correctly set up for OpenID Connect.

### User Experience
- **Login Experience:** Users will experience a seamless authentication process using their LinkedIn credentials, leveraging the enhanced security features of OpenID Connect.
- **Configuration:** Administrators will need to update the LinkedIn application configuration in LinkedIn's developer portal to use OpenID Connect, including updating the `client_id`, `client_secret`, and `redirect` URIs.

These updates bring the application in line with modern authentication standards, enhancing security and reliability for users logging in with LinkedIn.

---

# #71 Addition of E-commerce Payment Processing and Order Management

## Introduction

This pull request introduces comprehensive changes to integrate payment processing and order management within the platform. Key features include support for multiple billing types (e.g., Pix, Boleto, and credit card), webhook handling for payment status updates, and order status monitoring. These updates significantly enhance the application’s capability to manage orders and process payments efficiently.

## Changes Overview

### New Controllers

1. **File: `app/Http/Controllers/PaymentController.php`**
    - **Status:** Added
    - **Changes:** Added logic to handle payments, including creating billing requests based on the chosen payment method.
    - **Description:** This controller interacts with the `PaymentService` to process payments and manages the saving of billing information.
    - **Impact:** Adds the ability to process payments and handle payment-specific data storage.
    
    ```php
    ...
    public function pay(Request $request, $uuid)
    {
        $order = Order::where('uuid', $uuid)->firstOrFail();
        $billingType = $request->input('payment_method');
        $cobrancaResponse = $this->paymentService->createCobranca($uuid, $billingType);

        if ($cobrancaResponse['status'] === 'PENDING') {
            ...
            return redirect()->route('orders.payment', $uuid);
        } else {
            return redirect()->route('orders.checkout', $uuid)->with('error', __('dashboard.checkout.payment_failed'));
        }
    }
    ...
    ```

2. **File: `app/Http/Controllers/WebhookController.php`**
    - **Status:** Added
    - **Changes:** Provides webhook endpoint to handle callbacks from payment gateways (e.g., Asaas).
    - **Description:** Updates `Order` and `OrderCobranca` statuses based on the payment event received from the payment provider.
    - **Impact:** Enables real-time updates of payment status, ensuring that the order workflow is accurately maintained.

    ```php
    ...
    public function asaas_cobranca(Request $request)
    {
        $data = $request->all();
        Webhook::create(['source' => 'asaas.com', 'webhook' => json_encode($data)]);
        // Update order and payment status based on the event
        $event = $data['event'];
        if (isset($status)) {
            $order_cobranca = OrderCobranca::where('cobranca_id', $data['payment']['id'])->first();
            if ($order_cobranca) {
                $order_cobranca->update(['status' => $status]);
                Order::where('id', $order_cobranca->order_id)->update(['status' => $status]);
            }
            return response()->json(['message' => 'Cobranca successfully updated']);
        }
        return response()->json(['message' => 'Webhook received successfully']);
    }
    ...
    ```

### New Middleware

3. **File: `app/Http/Middleware/CheckOrderCobrancaStatus.php`**
    - **Status:** Added
    - **Changes:** Middleware to check the status of the order payment and redirect based on the status.
    - **Description:** Ensures that users are guided through the correct workflow based on the current status of their order payment.
    - **Impact:** Provides a streamlined user experience by ensuring users are always directed to the appropriate page based on their order status.

    ```php
    ...
    public function handle($request, Closure $next)
    {
        $uuid = $request->route('uuid');
        $order = Order::where('uuid', $uuid)->first();
        $orderCobranca = OrderCobranca::where('order_id', $order->id)->first();
        if ($orderCobranca) {
            if ($orderCobranca->status === 'PENDING') {
                return redirect()->route('orders.payment', $uuid);
            } elseif ($orderCobranca->status === 'RECEIVED') {
                return redirect()->route('orders.briefing', $uuid);
            }
        }
        return $next($request);
    }
    ...
    ```

### New Models and Services

4. **Files: `app/Models/*`**
    - **Status:** Added
    - **Changes:** Added multiple models (OrderCobranca, OrderCobrancaPix, OrderCobrancaBoleto, Webhook) to manage billing information and webhook data.
    - **Description:** These models are used to store detailed billing information for different payment methods and log incoming webhooks.
    - **Impact:** Facilitates organized storage and retrieval of billing and webhook data.

5. **File: `app/Services/PaymentService.php`**
    - **Status:** Added
    - **Changes:** Service to handle the interaction with the payment provider (Asaas).
    - **Description:** Manages the creation and retrieval of billing information from Asaas.
    - **Impact:** Encapsulates the logic related to payment interactions, making the controller code cleaner and more maintainable.

    ```php
    ...
    public function createCobranca($orderUuid, $billingType) {
        // Logic to create a billing request with Asaas
    }
    
    public function getCobrancaDetails($paymentId, $type) {
        // Logic to retrieve billing details for specific payment type
    }
    ...
    ```

### Database Migrations

6. **Files: `database/migrations/*`**
    - **Status:** Added
    - **Changes:** Migrations for the new models (OrderCobranca, OrderCobrancaPix, etc.).
    - **Description:** Creates the necessary database tables to store billing information, payment statuses, and webhook logs.
    - **Impact:** Supports the new payment processing and order management features by providing the required data structures.

### Blade Templates and Routes

7. **File: `resources/views/dashboard/business/*`**
    - **Changes:** Added and modified templates to support the new payment workflow and status displays.
    - **Description:** Provides the user interface for checking out, viewing payment status, and interacting with orders.
    - **Impact:** Extends the frontend to provide end-users with necessary views to manage their purchases and payments.

    ```blade
    ...
    <form action="{{ route('orders.payment_process', ['uuid' => $order->uuid]) }}" method="post" class="flex flex-col gap-5">
        @csrf
        ...
    </form>
    ...

    @if($order_cobranca->billing_type === 'PIX')
      // Display PIX specific information
    @elseif($order_cobranca->billing_type === 'BOLETO')
      // Display Boleto specific information
    @endif
    ...
    ```

8. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Registered new routes for handling payments and webhooks.
    - **Description:** Integrates new endpoints to facilitate payment processing and webhook handling.
    - **Impact:** Extends the application's API surface to accommodate the new payment and order management functionalities.

    ```php
    ...
    Route::get('/pedido/{uuid}/finalizar', [OrderProcessController::class, 'checkout'])->middleware('CheckUserAsaas', 'CheckUserContaAzul', 'CheckOrderCobrancaStatus')->name('orders.checkout');
    Route::post('/pedido/{uuid}/pagamento', [PaymentController::class, 'pay'])->name('orders.payment_process');
    Route::post('/webhook/asaas/cobranca', [WebhookController::class, 'asaas_cobranca']);
    ...
    ```

### Additional Modifications

9. **Localization, CSS, and JavaScript Adjustments**
    - **Status:** Modified
    - **Changes:** Updated language files, custom styles for checkboxes, and JavaScript for enhancing user interactions with payment functionalities.
    - **Description:** Ensures that all new features are adequately localized and provide a seamless user experience.
    - **Impact:** Improves usability and accessibility for non-English users and ensures an aesthetically consistent interface.

    ```js
    ...
    import JsBarcode from 'jsbarcode';  // Used for rendering barcodes on boleto payments
    window.JsBarcode = JsBarcode;
    ...
    ```

These comprehensive changes introduce a robust system for managing orders and processing payments, enhancing the platform’s functionality and user experience.

---

# #70 Implementation and Enhancement of reCAPTCHA with Custom Checkbox Styling

## Introduction

This pull request includes multiple improvements and new features. It enhances the security of the platform by adding Google reCAPTCHA to forms, ensuring that they are protected against spam and abuse. Additionally, it introduces custom styling for checkboxes to provide a modern and clean UI consistent with the platform's design language.

## Changes Overview

### Configuration and Environment

1. **File: `.env.example`**
    - **Status:** Modified
    - **Changes:** Updated the sample environment file with reCAPTCHA keys.
    - **Description:** This ensures new environments are set up with reCAPTCHA keys, enhancing security from the get-go.
    - **Impact:** Promotes a default secure setup for new installations.

    ```plaintext
    ...
    -RECAPTCHA_SITE_KEY=
    -RECAPTCHA_SECRET_KEY=
    +RECAPTCHA_SITE_KEY=6Le6n4spAAAAAN5pBRdzdS8slp5Sc2GwiViUd5KP
    +RECAPTCHA_SECRET_KEY=6Le6n4spAAAAAI0z692OdaLw-VytynygUVXnwjIt
    RECAPTCHA_SKIP_IP=
    ```

### CSS Enhancements

2. **File: `resources/css/app.css`**
    - **Status:** Modified
    - **Changes:** Added CSS rules for custom checkbox styling.
    - **Description:** Provides a visually appealing and consistent user interface for checkboxes across the platform.
    - **Impact:** Improves user experience by providing intuitive and visually consistent form elements.

    ```css
    ...
    input[type="checkbox"]:checked::after, input[type="checkbox"]:checked::before {
        content: '';
    }

    input[type="checkbox"]:checked:not(:hover) {
        background-color: transparent;
    }

    input[type="checkbox"]:focus {
        box-shadow: none;
        border: none;
        outline: none;
    }
    ...
    ```

### Custom Checkbox Blade Component

3. **File: `resources/views/components/checkbox.blade.php`**
    - **Status:** Modified
    - **Changes:** Enhanced the `<x-checkbox>` Blade component to include custom styling via a `<span>`.
    - **Description:** Provides modern-looking checkboxes that maintain a consistent design with other form elements.
    - **Impact:** Uniform checkbox design enhances the overall visual appeal and consistency of the platform.

    ```html
    <span class="relative block w-4">
        <input type="checkbox" {!! $attributes->merge([
            'class' =>
                'h-4 w-4 rounded border-none text-creatify-2 focus:ring-transparent checked:ring-none bg-transparent ring-0 checked:after:content-none checked:after:bg-transparent checked:outline-none checked:border-none checked:bg-transparent peer absolute z-10 cursor-pointer checked:opacity-0 checked:hover:bg-transparent',
        ]) !!}>
        <span class="rounded block w-4 h-4 border-2 border-stone-200 dark:border-neutral-700 focus:border-creatify-2 cursor-pointer transition-all peer-checked:rotate-45 peer-checked:translate-x-[15px] peer-checked:-translate-y-2 peer-checked:w-2 peer-checked:border-creatify-2 peer-checked:border-t-transparent peer-checked:border-l-transparent peer-checked:rounded-sm origin-[-4px_-1px]"></span>
    </span>
    ```

### reCAPTCHA Integration

4. **File: `resources/views/auth/forgot-password.blade.php`**
    - **Status:** Modified
    - **Changes:** Integrated reCAPTCHA in the forgot password form.
    - **Description:** Protects the password reset process from automated abuse.
    - **Impact:** Enhances security by preventing bots from abusing the password reset feature.

    ```html
    ...
    <form class="space-y-6" method="POST" action="{{ route('password.email') }}" id="{{ getFormId() }}">
        @csrf
        ...
        {!! htmlFormButton(__('auth.forgot.button1'), [
            'class' =>
                'inline-flex items-center px-3 py-2 text-sm font-semibold text-white border border-transparent rounded-lg bg-creatify-2 gap-x-2 hover:bg-creatify-2 focus:outline-none focus:ring-2 focus:ring-creatify-2 shadow-md shadow-gray-900/10 hover:shadow-lg hover:shadow-gray-900/20 dark:hover:shadow-gray-300/20 focus:opacity-[0.85] focus:shadow-none active:opacity-[0.85] active:shadow-none justify-center',
        ]) !!}
    </form>
    {!! htmlScriptTagJsApi() !!}
    ```

5. **File: `resources/views/auth/login.blade.php`**
    - **Status:** Modified
    - **Changes:** Integrated reCAPTCHA in the login form.
    - **Description:** Adds a layer of security to the login process, mitigating unauthorized access attempts by bots.
    - **Impact:** Strengthens the login mechanism against spam and automated attacks.

    ```html
    ...
    <form class="space-y-6" method="POST" action="{{ route('login') }}" id="{{ getFormId() }}">
        @csrf
        ...
        {!! htmlFormButton(__('auth.login.button1'), [
            'class' =>
                'inline-flex items-center px-3 py-2 text-sm font-semibold text-white border border-transparent rounded-lg bg-creatify-2 gap-x-2 hover:bg-creatify-2 focus:outline-none focus:ring-2 focus:ring-creatify-2 shadow-md shadow-gray-900/10 hover:shadow-lg hover:shadow-gray-900/20 dark:hover:shadow-gray-300/20 focus:opacity-[0.85] focus:shadow-none active:opacity-[0.85] active:shadow-none justify-center',
        ]) !!}
    </form>
    {!! htmlScriptTagJsApi() !!}
    ```

6. **File: `resources/views/auth/register.blade.php`**
    - **Status:** Modified
    - **Changes:** Integrated reCAPTCHA in the registration form.
    - **Description:** Protects the user registration process from spam and automated account creation.
    - **Impact:** Ensures that new user registrations are legitimate, reducing the risk of spam accounts.

    ```html
    ...
    <form class="space-y-6" method="POST" action="{{ route('register.post') }}" id="{{ getFormId() }}">
        @csrf
        @if(isset($role))
            <input type="hidden" name="role" value="{{ $role }}">
        @endif
        ...
        {!! htmlFormButton(__('auth.register.button1'), [
            'class' =>
                'inline-flex items-center px-3 py-2 text-sm font-semibold text-white border border-transparent rounded-lg bg-creatify-2 gap-x-2 hover:bg-creatify-2 focus:outline-none focus:ring-2 focus:ring-creatify-2 shadow-md shadow-gray-900/10 hover:shadow-lg hover:shadow-gray-900/20 dark:hover:shadow-gray-300/20 focus:opacity-[0.85] focus:shadow-none active:opacity-[0.85] active:shadow-none justify-center',
        ]) !!}
    ...
    </form>
    {!! htmlScriptTagJsApi() !!}
    ```

### Profile Update Enhancements - Custom Checkbox

7. **File: `resources/views/profile/update-creator-contact-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Integrated custom checkbox in the user profile update form.
    - **Description:** Provides a consistent user interface for checkboxes in the profile update form.
    - **Impact:** Improves the user experience with a clean and visually appealing profile update form.

    ```html
    ...
    @if($role == 'creator')
     <div class="col-span-6 sm:col-span-6">
         <div class="flex items-center">
             <span class="relative block w-4">
                 <input id="link-checkbox" wire:click="shippingAddress" {{ $isChecked ? 'checked' : ''  }} type="checkbox" value="" class="absolute z-10 w-4 h-4 bg-transparent border-none rounded cursor-pointer text-creatify-2 focus:ring-transparent checked:ring-none ring-0 checked:after:content-none checked:after:bg-transparent checked:outline-none checked:border-none checked:bg-transparent peer checked:opacity-0 checked:hover:bg-transparent">
                 <span class="rounded block w-4 h-4 border-2 border-stone-200 dark:border-neutral-700 focus:border-creatify-2 cursor-pointer transition-all peer-checked:rotate-45 peer-checked:translate-x-[15px] peer-checked:-translate-y-2 peer-checked:w-2 peer-checked:border-creatify-2 peer-checked:border-t-transparent peer-checked:border-l-transparent peer-checked:rounded-sm origin-[-4px_-1px]"></span>
             </span>
             <label for="link-checkbox" class="block ml-3 text-sm leading-6 text-gray-700 dark:text-gray-400">{{ __('profile.contact.differentshipping') }}</label>
         </div>
     </div>
    @endif
    ...
    ```

These changes collectively enhance the security and user interface of the platform, providing a more secure and pleasant experience for users. The integration of reCAPTCHA is crucial for preventing automated abuse, while the visually consistent checkboxes improve the overall design language of the platform.

---

# #69 Implementation of Middleware for Asaas and ContaAzul Integrations

## Introduction

This pull request introduces middleware for integrating Asaas and ContaAzul services. The implemented middleware checks and updates user information in Asaas and ContaAzul systems before proceeding with the request. This integration ensures that user data is synchronized across platforms, enhancing system consistency and user management.

## Changes Overview

### Middleware Files

1. **File: `app/Http/Middleware/CheckUserAsaas.php`**
    - **Status:** Added
    - **Changes:** Introduced a new middleware class to handle user data synchronization with the Asaas platform. 
    - **Description:** This middleware checks if the user's data exists in Asaas. If the user exists, it updates the data; otherwise, it creates a new entry. It uses the Guzzle HTTP client to send requests to the Asaas API.
    - **Impact:** Ensures user data is consistently updated on the Asaas platform.

    ```php
    <?php

    namespace App\Http\Middleware;

    use Closure;
    use Illuminate\Http\Request;
    use Illuminate\Support\Facades\Auth;
    use App\Models\UserAsaas;
    use App\Models\UserAddress;
    use Illuminate\Support\Facades\Log;
    use GuzzleHttp\Client;
    use GuzzleHttp\Exception\RequestException;

    class CheckUserAsaas
    {
        public function handle($request, Closure $next)
        {
            $user = Auth::user();
            $userAsaas = UserAsaas::where('user_id', Auth::id())->first();
            $userAddress = UserAddress::where('user_id', Auth::id())->first();

            $client = new Client();

            try {
                $url = $userAsaas ? config('app.asaas_url') . '/api/v3/customers/' . $userAsaas->asaas_id : config('app.asaas_url') . '/api/v3/customers';
                $method = $userAsaas ? 'PUT' : 'POST';

                $response = $client->request($method, $url, [
                    'json' => [
                        'name' => $user->firstname . ' ' . $user->lastname,
                        'cpfCnpj' => $user->data->cpf_cnpj_value,
                        'email' => $user->email,
                        'notificationDisabled' => false,
                        'company' => $userAddress->company ?? null,
                        'address' => $userAddress->street ?? null,
                        'complement' => $userAddress->apto ?? null,
                        'postalCode' => $userAddress->zip ?? null,
                    ],
                    'headers' => [
                        'accept' => 'application/json',
                        'access_token' => config('app.asaas_token'),
                        'content-type' => 'application/json',
                    ],
                ]);

                $responseArray = json_decode($response->getBody(), true);
                if (isset($responseArray['id'])) {
                    UserAsaas::updateOrCreate(
                        ['user_id' => $user->id],
                        ['asaas_id' => $responseArray['id']]
                    );
                }
            } catch (RequestException $e) {
                Log::error("RequestException: " . $e->getMessage());
            }

            return $next($request);
        }
    }
    ```

2. **File: `app/Http/Middleware/CheckUserContaAzul.php`**
    - **Status:** Added
    - **Changes:** Introduced a new middleware class to handle user data synchronization with the ContaAzul platform.
    - **Description:** This middleware checks if the user's data exists in ContaAzul. It updates or creates new entries and handles specific cases, such as when CPF/CNPJ is already linked to another user. It uses the Guzzle HTTP client to send requests to the ContaAzul API.
    - **Impact:** Ensures user data is consistently updated on the ContaAzul platform.

    ```php
    <?php

    namespace App\Http\Middleware;

    use Closure;
    use Illuminate\Http\Request;
    use Illuminate\Support\Facades\Auth;
    use App\Models\UserContaAzul;
    use App\Models\UserAddress;
    use Illuminate\Support\Facades\Log;
    use GuzzleHttp\Client;
    use GuzzleHttp\Exception\RequestException;

    class CheckUserContaAzul
    {
        public function handle($request, Closure $next)
        {
            $user = Auth::user();
            $userContaAzul = UserContaAzul::where('user_id', Auth::id())->first();
            $userAddress = UserAddress::where('user_id', Auth::id())->first();

            $client = new Client();

            try {
                $url = $userContaAzul ? 'https://api.contaazul.com/v1/customers/' . $userContaAzul->contaazul_id : 'https://api.contaazul.com/v1/customers';
                $method = $userContaAzul ? 'PUT' : 'POST';

                $cpfcnpjclean = preg_replace('/[^A-Za-z0-9]/', '', $user->data->cpf_cnpj_value);
                $person_type = $user->data->cpf_cnpj == 'CPF' ? 'NATURAL' : 'LEGAL';

                $response = $client->request($method, $url, [
                    'json' => [
                        'name' => $user->firstname . ' ' . $user->lastname,
                        'company_name' => $userAddress->company ?? null,
                        'email' => $user->email,
                        'person_type' => $person_type,
                        'document' => $cpfcnpjclean,
                        'identity_document' => $cpfcnpjclean,
                        'address' => [
                            'zip_code' => $userAddress->zip ?? null,
                            'street' => $userAddress->street ?? null,
                            'complement' => $userAddress->apto ?? null,
                        ],
                    ],
                    'headers' => [
                        'accept' => 'application/json',
                        'Authorization' => 'Bearer ' . config('app.contaazul_access_token'),
                        'content-type' => 'application/json',
                    ],
                ]);

                $responseArray = json_decode($response->getBody(), true);

                if (isset($responseArray[0]['id'])) {
                    UserContaAzul::updateOrCreate(
                        ['user_id' => $user->id],
                        ['contaazul_id' => $responseArray[0]['id']]
                    );
                }
            } catch (RequestException $e) {
                $responseBody = $e->getResponse()->getBody()->getContents();
                $responseArray = json_decode($responseBody, true);

                if (isset($responseArray['code']) && $responseArray['code'] == 'INVALID_PARAMETER' && $responseArray['message'] == 'CPF/CPNJ já utilizado por outro cliente.') {
                    $cpfcnpjclean = preg_replace('/\D/', '', $user->data->cpf_cnpj_value);
                    $response1 = $client->request('GET', 'https://api.contaazul.com/v1/customers?search=' . $cpfcnpjclean, [
                        'headers' => [
                            'accept' => 'application/json',
                            'Authorization' => 'Bearer ' . config('app.contaazul_access_token'),
                            'content-type' => 'application/json',
                        ],
                    ]);

                    $responseBody1 = $response1->getBody()->getContents();
                    $responseArray1 = json_decode($responseBody1, true);

                    if (isset($responseArray1[0]['id'])) {
                        UserContaAzul::updateOrCreate(
                            ['user_id' => $user->id],
                            ['contaazul_id' => $responseArray1[0]['id']]
                        );
                    }
                } else {
                    Log::error("RequestException: " . $e->getMessage());
                }
            }

            return $next($request);
        }
    }
    ```

### Command File

3. **File: `app/Console/Commands/ContaAzulGetAccessToken.php`**
    - **Status:** Modified
    - **Changes:** Updated the configurations for ContaAzul credentials to fetch them from the configuration file instead of environment variables.
    - **Description:** This update centralizes the credential management and improves security and maintainability by storing sensitive information in the configuration file.
    - **Impact:** Ensures secure and manageable access to ContaAzul credentials.

    ```php
    public function handle()
    {        
        $clientId = config('app.contaazul.client_id');
        $clientSecret = config('app.contaazul.client_secret');
        $refreshToken = config('app.contaazul.refresh_token');
        $authorization = base64_encode("$clientId:$clientSecret");
        // Further code...
    }
    ```

### Kernel Registration

4. **File: `app/Http/Kernel.php`**
    - **Status:** Modified
    - **Changes:** Registered the new middleware classes `CheckUserAsaas` and `CheckUserContaAzul`.
    - **Description:** This modification ensures that the middleware can be invoked in routes and controllers.
    - **Impact:** Facilitates middleware integration into the Laravel application's request lifecycle.

    ```php
    protected $routeMiddleware = [
        // ...
        'CheckUserAsaas' => \App\Http\Middleware\CheckUserAsaas::class,
        'CheckUserContaAzul' => \App\Http\Middleware\CheckUserContaAzul::class,
    ];
    ```

### Route Middleware

5. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Applied the new middleware to the checkout route.
    - **Description:** Ensures user data is synchronized with Asaas and ContaAzul before proceeding to the checkout process.
    - **Impact:** Enhances data consistency across different services involved in the checkout process.

    ```php
    Route::middleware(['CheckUserAsaas', 'CheckUserContaAzul'])->group(function () {
        Route::get('/pedido/{uuid}/finalizar', [OrderProcessController::class, 'checkout'])->name('order.checkout');
    });
    ```

### Configuration File

6. **File: `config/app.php`**
    - **Status:** Modified
    - **Changes:** Updated the configuration file to include Asaas and ContaAzul settings.
    - **Description:** Centralizes the configuration for external services, making it easier to manage and update credentials.
    - **Impact:** Improves configuration management and enhances security by minimizing exposed sensitive information.

    ```php
    return [
        // ...
        'asaas_token' => env('ASAAS_TOKEN', '$aact_YTU5YTE0M2M2N2I4MTbiNzk0YTI5N2U5MzdjNWZmNDQ6OjAwMDAwMDAwMDAwMDAwNzE3MTg6OiRhYWNoXzk3ZDA3ZjUzLTUyYTItNDI1Mi1hNTlmLTNhYzE0OWI0ZDY3MQ=='),
        'asaas_url' => config('app.env') === 'production' ? 'https://api.asaas.com' : 'https://sandbox.asaas.com',


---

# #68 Implementing Google reCAPTCHA in User Authentication Forms

## Introduction

This pull request introduces Google reCAPTCHA functionality to enhance the security of user authentication forms, such as login, registration, and password reset. The changes ensure that only human users can access these features, protecting the platform from automated attacks.

## Changes Overview

### Configuration Files

1. **File: `config/recaptcha.php`**
    - **Status:** Added
    - **Changes:** Introduced a new configuration file for reCAPTCHA settings, allowing customization of reCAPTCHA behavior and integration.
    - **Description:** This file provides a range of configurable options, such as site key, secret key, version, curl timeout, IP skipping, validation route, language, and tag attributes.
    - **Impact:** Centralizes reCAPTCHA configuration, making it easier to manage and update settings.

### Environment File

2. **File: `.env.example`**
    - **Status:** Modified
    - **Changes:** Added placeholders for reCAPTCHA site key and secret key environment variables.
    - **Description:** These variables are used within the reCAPTCHA configuration file to authenticate requests with Google's reCAPTCHA service.
    - **Impact:** Facilitates secure storage of sensitive reCAPTCHA credentials.

    ```env
    RECAPTCHA_SITE_KEY=
    RECAPTCHA_SECRET_KEY=
    RECAPTCHA_SKIP_IP=
    ```

### Composer Dependencies

3. **File: `composer.json`**
    - **Status:** Modified
    - **Changes:** Added the `biscolab/laravel-recaptcha` package.
    - **Description:** Integrates Google reCAPTCHA functionality into the Laravel application.
    - **Impact:** Provides out-of-the-box support for reCAPTCHA in Laravel forms.

### Validation Messages

4. **File: `resources/lang/pt_br/validation.php`**
    - **Status:** Modified
    - **Changes:** Added a validation message for reCAPTCHA.
    - **Description:** Localizes the error message that appears when reCAPTCHA validation fails.
    - **Impact:** Improves user experience by providing feedback in the user's language.

    ```php
    'recaptcha' => 'O campo :attribute é inválido.',
    ```

### Blade Templates

5. **File: `resources/views/auth/forgot-password.blade.php`**
    - **Status:** Modified
    - **Changes:** Integrated reCAPTCHA into the password reset form.
    - **Description:** Ensures that only human users can submit password reset requests.
    - **Impact:** Enhances security of the password reset process.

    ```html
    <form class="space-y-6" method="POST" action="{{ route('password.email') }}" id="{{ getFormId() }}">
        @csrf
        {!! htmlFormButton(__('auth.forgot.button1'), ['class' => 'inline-flex items-center px-3 py-2 text-sm font-semibold text-white...']) !!}
    </form>
    {!! htmlScriptTagJsApi() !!}
    ```

6. **File: `resources/views/auth/login.blade.php`**
    - **Status:** Modified
    - **Changes:** Integrated reCAPTCHA into the login form.
    - **Description:** Protects the login form from automated access attempts.
    - **Impact:** Improves security of the login feature.

    ```html
    <form class="space-y-6" method="POST" action="{{ route('login') }}" id="{{ getFormId() }}">
        @csrf
        {!! htmlFormButton(__('auth.login.button1'), ['class' => 'inline-flex items-center px-3 py-2 text-sm font-semibold text-white...']) !!}
    </form>
    {!! htmlScriptTagJsApi() !!}
    ```

7. **File: `resources/views/auth/register.blade.php`**
    - **Status:** Modified
    - **Changes:** Integrated reCAPTCHA into the registration form.
    - **Description:** Ensures that only real users can create new accounts.
    - **Impact:** Helps prevent spam account creation.

    ```html
    <form class="space-y-6" method="POST" action="{{ route('register.post') }}" id="{{ getFormId() }}">
        @csrf
        {!! htmlFormButton(__('auth.register.button1'), ['class' => 'inline-flex items-center px-3 py-2 text-sm font-semibold text-white...']) !!}
    </form>
    {!! htmlScriptTagJsApi() !!}
    ```

## Conclusion

By integrating Google reCAPTCHA into the user authentication forms, this update significantly enhances the security of the platform against automated threats. The centralized configuration and localized validation messages also contribute to a better user experience and easier management.

---

# #67 Improved Checkout Form with Enhanced Address Management

## Introduction

This pull request focuses on refining the checkout process by enhancing the address management functionality. Address fields now update the database in real-time, and the new `zipCall` method facilitates automatic address retrieval using ZIP code. The changes improve the user experience by ensuring address information is accurately and dynamically updated.

## Changes Overview

### Livewire Components

1. **File: `app/Livewire/Business/CheckoutForm.php`**
    - **Status:** Modified
    - **Changes:** 
        - Added multiple methods to handle individual address field updates.
        - Implemented the `zipCall` method to fetch and populate address fields using the ZIP code.
    - **Description:** This change ensures that each address field update is saved to the database as it is entered, providing a more dynamic and responsive user experience.
    - **Impact:** Improves address data accuracy and user convenience.

    ```php
    public function changeName()
    {
        $userAddress = UserAddress::firstOrNew(['user_id' => Auth::id()]);
        $userAddress->name = $this->name;
        $userAddress->save();
    }

    public function changeCompany()
    {
        $userAddress = UserAddress::firstOrNew(['user_id' => Auth::id()]);
        $userAddress->company = $this->company;
        $userAddress->save();
    }

    public function zipCall()
    {
        $apiUrl = "https://brasilapi.com.br/api/cep/v2/{$this->zip}";
        
        $ch = curl_init($apiUrl);
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
        
        $response = curl_exec($ch);
        
        if (curl_errno($ch)) {
            echo 'Error: ' . curl_error($ch);
        }
        
        curl_close($ch);
        
        $data = json_decode($response, true);
        
        if ($data) {
            $userAddress = UserAddress::firstOrNew(['user_id' => Auth::id()]);
            $userAddress->zip = $this->zip;
            $this->city = $data['city'] ?? $this->city;
            $userAddress->city = $this->city;
            $this->street = $data['street'] ?? $this->street;
            $userAddress->street = $this->street;
            $this->state = $data['state'] ?? $this->state;
            $userAddress->state = $this->state;
            $userAddress->save();
        }
    }

    public function changeStreet()
    {
        $userAddress = UserAddress::firstOrNew(['user_id' => Auth::id()]);
        $userAddress->street = $this->street;
        $userAddress->save();
    }

    public function changeState()
    {
        $userAddress = UserAddress::firstOrNew(['user_id' => Auth::id()]);
        $userAddress->state = $this->state;
        $userAddress->save();
    }

    public function changeCity()
    {
        $userAddress = UserAddress::firstOrNew(['user_id' => Auth::id()]);
        $userAddress->city = $this->city;
        $userAddress->save();
    }

    public function changeApto()
    {
        $userAddress = UserAddress::firstOrNew(['user_id' => Auth::id()]);
        $userAddress->apto = $this->apto;
        $userAddress->save();
    }
    ```

### Blade Files

2. **File: `resources/views/dashboard/business/checkout-form.blade.php`**
    - **Status:** Modified
    - **Changes:** 
        - Updated input elements to trigger their respective methods on keydown.
    - **Description:** These changes ensure that user inputs trigger immediate database updates, improving the responsiveness and accuracy of the checkout form.
    - **Impact:** Enhances real-time data consistency and user interaction.
    
    ```html
    <x-input id="name" type="text" class="block w-full mt-1" wire:model="name" wire:keydown="changeName" placeholder="{{ __('profile.contact.name_placeholder') }}" />
    <x-input id="company" type="text" class="block w-full mt-1" wire:model="company" wire:keydown="changeCompany" placeholder="{{ __('profile.contact.company_placeholder') }}" />
    <x-input id="city" type="text" class="block w-full mt-1" wire:model="city" wire:keydown="changeCity" placeholder="{{ __('profile.contact.city_placeholder') }}" />
    <x-input id="street" type="text" class="block w-full mt-1" wire:model="street" wire:keydown="changeStreet" placeholder="{{ __('profile.contact.street_placeholder') }}" />
    <x-input id="apto" type="text" class="block w-full mt-1" wire:model="apto" wire:keydown="changeApto" placeholder="{{ __('profile.contact.additional_placeholder') }}" />
    <x-input id="state" type="text" class="block w-full mt-1" wire:model="state" wire:keydown="changeState" placeholder="{{ __('profile.contact.state_placeholder') }}" />
    ```

## Conclusion

These enhancements ensure that address information in the checkout form is dynamically updated and stored in real-time, improving the overall user experience. The implementation of the `zipCall` method and individual change methods for each address field provides robust and responsive functionality, ensuring data accuracy and user convenience during the checkout process.

---

# #66 Introduction of Address Management and Checkout Enhancements

## Introduction

This pull request introduces new database tables for managing address data, implements significant enhancements to the checkout process, and improves the UI experience. The changes ensure better address handling, provide a streamlined user experience during checkout, and update form labels for consistency across the application.

## Changes Overview

### Migrations

1. **File: `database/migrations/2024_03_04_125245_create_ceps_states_table.php`**
    - **Status:** Added
    - **Changes:** Created a new table `ceps_states` for storing state information.
    - **Description:** This table will store state names and their abbreviations.
    - **Impact:** Enhances the structure of addresses by having a dedicated state table.

    ```php
    Schema::create('ceps_states', function (Blueprint $table) {
        $table->id();
        $table->string('name');
        $table->string('short');
        $table->timestamps();
    });
    ```

2. **File: `database/migrations/2024_03_04_125246_create_ceps_cities_table.php`**
    - **Status:** Added
    - **Changes:** Created a new table `ceps_cities` for storing city information.
    - **Description:** This table will store city names linked to states.
    - **Impact:** Offers better management of city data associated with states.

    ```php
    Schema::create('ceps_cities', function (Blueprint $table) {
        $table->id();
        $table->string('name');
        $table->foreignId('state_id')->constrained('ceps_states');
        $table->timestamps();
    });
    ```

3. **File: `database/migrations/2024_03_04_125246_create_ceps_table.php`**
    - **Status:** Added
    - **Changes:** Created a new table `ceps` for comprehensive address information.
    - **Description:** This table will store detailed address data including street, number, neighborhood, city, and state.
    - **Impact:** Enhances address data normalization and management.

    ```php
    Schema::create('ceps', function (Blueprint $table) {
        $table->id();
        $table->string('cep');
        $table->string('street');
        $table->string('numero');
        $table->string('neighborhood');
        $table->foreignId('city_id')->constrained('ceps_cities');
        $table->foreignId('state_id')->constrained('ceps_states');
        $table->timestamps();
    });
    ```

### Livewire Components

4. **File: `app/Livewire/Business/CheckoutForm.php`**
    - **Status:** Modified
    - **Changes:** Added functionality to fetch address details based on the ZIP code, and refactored some methods for better address management.
    - **Description:** Enhances the checkout form to allow users to retrieve and fill address information using the ZIP code.
    - **Impact:** Streamlines the checkout process by automating address retrieval, improving user convenience.

    ```php
    public function zipCall()
    {
        $apiUrl = "https://brasilapi.com.br/api/cep/v2/{$this->zip}";
        
        $ch = curl_init($apiUrl);
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
        
        $response = curl_exec($ch);
        
        if (curl_errno($ch)) {
            echo 'Error: ' . curl_error($ch);
        }
        
        curl_close($ch);
        
        $data = json_decode($response, true);
        
        if ($data) {
            $this->city = $data['city'] ?? '';
            $this->street = $data['street'] ?? '';
            $this->state = $data['state'] ?? '';
        }
    }
    ```

5. **File: `app/Livewire/UpdateCreatorContactForm.php`**
    - **Status:** Modified
    - **Changes:** Added the `company` field and incorporated ZIP code-based address retrieval.
    - **Description:** Extends address information management by including company details and automating address filling using ZIP code.
    - **Impact:** Enhances address handling capabilities for business users.

    ```php
    public function zipCall()
    {
        $apiUrl = "https://brasilapi.com.br/api/cep/v2/{$this->zip}";
        
        $ch = curl_init($apiUrl);
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
        
        $response = curl_exec($ch);
        
        if (curl_errno($ch)) {
            echo 'Error: ' . curl_error($ch);
        }
        
        curl_close($ch);
        
        $data = json_decode($response, true);
        if ($data) {
            $this->city = $data['city'] ?? '';
            $this->street = $data['street'] ?? '';
            $this->state = $data['state'] ?? '';
        }
    }
    ```

### Blade and Language Files

6. **Files: Various Blade templates under `resources/views/auth` and `resources/views/dashboard`**
    - **Status:** Modified
    - **Changes:** Updated input fields to ensure label backgrounds match their contexts, providing a consistent UI experience.
    - **Description:** Adds background colors to input labels to ensure they are readable in both light and dark modes.
    - **Impact:** Improves the readability and visual consistency of forms.

    ```html
    <x-label for="password" class="bg-white authpage-input-label dark:bg-neutral-800" value="{{ __('auth.login.password') }}" />
    ```

7. **File: `resources/views/dashboard/business/checkout-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Enhanced the logic to check for the presence of address fields.
    - **Description:** Ensures that users are prompted to fill out address information if any critical field is missing.
    - **Impact:** Guarantees that essential address information is collected during checkout.

    ```html
    @if(empty($user->address) || empty($user->address->name) || empty($user->address->street) || empty($user->address->city) || empty($user->address->zip) || empty($user->address->state))
    ```

## Conclusion

These changes introduce robust structures for managing address data, improve the user experience during the checkout process, and enhance the readability of form labels across the application. The updates streamline address management and ensure consistent and user-friendly interactions during critical processes like user registration and order checkout.

---

# #65 Introduction of Pricing Configuration, Address Adjustments, and Checkout Enhancements

## Introduction

This pull request implements new pricing configurations, updates to user address handling, and significant enhancements to the checkout process. These changes aim to improve the maintainability of the pricing structure, enhance user experience across different parts of the application, and streamline the checkout process.

## Changes Overview

### Configurations

1. **File: `config/app_pricing.php`**
    - **Status:** Added
    - **Changes:** Introduced a new configuration file to manage the pricing details for videos, hooks, photos, and services comprehensively.
    - **Description:** This helps centralize the pricing information and makes the application easily configurable.
    - **Impact:** Simplifies updates to pricing and ensures consistent use across the application.

    ```php
    return [
        // Video Pricing
        '15_seconds_duration' => 15,
        '15_seconds_price' => 119,
        '15_seconds_price_per_second' => 7.93,
        '15_seconds_icon' => 'img/svgs/chart-quarter.svg',
        // Other configurations...
    ];
    ```

## Migrations

2. **File: `database/migrations/2024_03_03_204104_add_company_to_users_address_table.php`**
    - **Status:** Added
    - **Changes:** Added a migration to introduce a `company` field to the `users_address` table.
    - **Description:** Allows users to add a company name to their address details.
    - **Impact:** Enhances the address information stored for business/enterprise users.

    ```php
    Schema::table('users_address', function (Blueprint $table) {
        $table->string('company')->after('name')->nullable();
    });
    ```

3. **File: `database/migrations/2024_03_03_214323_update_users_address_table.php`**
    - **Status:** Added
    - **Changes:** Modified multiple fields in the `users_address` table to be nullable.
    - **Description:** Provides flexibility in managing partial address data.
    - **Impact:** Improves the robustness of address data handling.

    ```php
    Schema::table('users_address', function (Blueprint $table) {
        $table->string('name')->nullable()->change();
        // Other changes...
    });
    ```

## Controllers and Components

4. **File: `app/Http/Controllers/OrderProcessController.php`**
    - **Status:** Modified
    - **Changes:** Changed hard-coded pricing details to read from the configuration file.
    - **Description:** Ensures pricing details are consistent and maintainable across the application.
    - **Impact:** Centralized pricing management improves the maintainability and scalability of pricing updates.

5. **File: `app/Livewire/Business/CheckoutForm.php`**
    - **Status:** Modified
    - **Changes:** Added new fields and methods to handle user address and company details during the checkout process.
    - **Description:** Enhances the checkout form to allow users to add or update their address and company information on the fly.
    - **Impact:** Streamlines the user experience during checkout, ensuring critical information is captured.

6. **File: `app/Livewire/Business/OrderProcessView.php`**
    - **Status:** Modified
    - **Changes:** Adjusted pricing fields to pull values from the configuration file and added functionality to update order details in the database.
    - **Description:** Ensures accurate pricing and order management.
    - **Impact:** Improved accuracy in order processing and better maintenance of pricing structures.

7. **File: `app/Livewire/FooterHomepage.php`**
    - **Status:** Modified
    - **Changes:** Added functionality for newsletter subscription management.
    - **Description:** Allows users to subscribe to a newsletter directly from the homepage footer.
    - **Impact:** Enhanced user engagement and communication.

## Blade and Language Files

8. **Files: `resources/views/dashboard/business/create_product.blade.php`, `resources/views/dashboard/business/edit_product.blade.php`**
    - **Status:** Modified
    - **Changes:** Adjusted labels and input fields for consistent UI/UX.
    - **Description:** Ensures alignment and aesthetic consistency across various forms.
    - **Impact:** Enhances the user interface and experience.

9. **Files: Various views under `resources/views/dashboard/business/` and `profile/`**
    - **Status:** Modified
    - **Changes:** Updated various blade files to use new pricing configurations and address fields.
    - **Description:** Reflects the new configuration-based pricing and extended address information capture.
    - **Impact:** Maintains consistency and improves the handling of pricing and address data.

10. **Language Files: `resources/lang/pt_br/dashboard.php`, `resources/lang/pt_br/general.php`, `resources/lang/pt_br/profile.php`**
    - **Status:** Modified
    - **Changes:** Added new language entries to support the UI/UX changes.
    - **Description:** Keeps the application multilingual and ensures new features are adequately supported in different languages.
    - **Impact:** Enhances user experience for non-English speaking users.

## Conclusion

These changes result in more maintainable and scalable pricing management, improved user address handling, and streamlined the checkout process. The consistency provided by these updates enhances overall user experience and maintainability for the developers.

---

# #62 UI Adjustments for Product Image Upload and Order Process Thumbnails

## Introduction

This pull request includes minor UI adjustments to improve the user experience when uploading product images and visualizing thumbnails during the order process. These enhancements ensure the styling and positioning of elements are consistent and aesthetically pleasing.

## Changes Overview

### Product Image Upload Enhancement

1. **File: `resources/views/dashboard/business/create_product.blade.php`**
    - **Status:** Modified
    - **Changes:**
        - Changed the height of the image upload container from a fixed pixel value to a responsive height using the `h-[19rem]` utility class.
    - **Description:** This change improves the responsiveness of the image upload container, ensuring it adapts better to different screen sizes.
    - **Impact:** Provides a more consistent and flexible UI for the product creation process.

    ```html
    <div class="flex items-center justify-center w-full">
        <label for="images" class="flex flex-col items-center justify-center w-full bg-white border border-dashed cursor-pointer h-[19rem] border-stone-300 rounded-xl dark:hover:bg-bray-800 dark:bg-neutral-800 dark:border-neutral-600 hover:bg-gray-50 dark:hover:border-gray-500 dark:hover:bg-gray-600">
            ...
        </label>
    </div>
    ```

2. **File: `resources/views/dashboard/business/edit_product.blade.php`**
    - **Status:** Modified
    - **Changes:**
        - Similarly adjusted the height of the image upload container to use `h-[19rem]`.
    - **Description:** Ensuring a consistent look and feel for image upload sections across both product creation and editing views.
    - **Impact:** Uniformity in UI elements related to image uploads enhances user experience.

    ```html
    <div class="flex items-center justify-center w-full">
        <label for="images" class="flex flex-col items-center justify-center w-full h-[19rem] bg-white border border-dashed cursor-pointer border-stone-300 rounded-xl dark:hover:bg-bray-800 dark:bg-neutral-800 dark:border-neutral-600 hover:bg-gray-50 dark:hover:border-gray-500 dark:hover:bg-gray-600">
            ...
        </label>
    </div>
    ```

### Order Process Thumbnails Enhancement

3. **File: `resources/views/dashboard/business/order-process-view.blade.php`**
    - **Status:** Modified
    - **Changes:**
        - Adjusted the absolute positioning and z-index of the image thumbnails within the order process view to improve their visual stacking.
    - **Description:** The changes involve minor adjustments to the thumbnail's z-index and top/left margins to ensure better stacking and alignment.
    - **Impact:** Improves the visual clarity and organization of image thumbnails, making the UI more intuitive and visually appealing.

    ```html
    <div class="relative grid grid-cols-3 gap-2 left-4 sm:left-12">
        <div class="relative">
            <div class="absolute z-0 -top-4">
                <div class="rounded-lg bg-white shadow-md h-[150px] flex justify-center items-center overflow-hidden w-[100px]">
                    <img src="{{ asset('img/hero/hero1.avif') }}" class="object-cover w-full h-full" alt="">
                </div>
            </div>
            <div class="relative z-10 left-6">
                <div class="rounded-lg bg-white shadow-md h-[150px] flex justify-center items-center overflow-hidden w-[100px]">
                    <img src="{{ asset('img/hero/hero2.avif') }}" class="object-cover w-full h-full" alt="">
                </div>
            </div>
            <div class="absolute z-20 -bottom-4 left-12">
                <div class="rounded-lg bg-white shadow-md h-[150px] flex justify-center items-center overflow-hidden w-[100px]">
                    <img src="{{ asset('img/hero/hero3.avif') }}" class="object-cover w-full h-full" alt="">
                </div>
            </div>
        </div>
    </div>
    ```

## Conclusion

These minor but impactful UI adjustments ensure a consistent and responsive design across various sections of the web application. They improve the visual appeal and usability, providing users with a seamless and intuitive experience.

---

# #61 Checkout Process Integration and UI Enhancements

## Introduction

This pull request introduces a comprehensive suite of changes aimed at enhancing the user experience, improving the checkout process, and upgrading the overall aesthetics and functionality of the application. These changes include the addition of new Livewire components for the checkout process, a new loader component, updates to the authentication pages, and various UI enhancements for better accessibility and user engagement.

## Changes Overview

### Checkout Process
1. **File: `app/Livewire/Business/CheckoutForm.php`**
    - **Status:** Added
    - **Changes:** Introduced a new Livewire component for handling the checkout form.
    - **Description:** This component manages the state and behavior of the checkout form, including payment method selection and card details entry.
    - **Impact:** Simplifies the checkout process with a dynamic user interface.

2. **File: `resources/views/dashboard/business/checkout-form.blade.php`**
    - **Status:** Added
    - **Changes:** Added the view for the checkout form component.
    - **Description:** This view provides the HTML structure for the checkout form, including payment method selection and card details input.
    - **Impact:** Provides users with an intuitive and seamless checkout experience.

3. **File: `resources/views/dashboard/business/checkout.blade.php`**
    - **Status:** Added
    - **Changes:** Added the checkout page view.
    - **Description:** This view combines the order overview and payment details sections, leveraging the `CheckoutForm` Livewire component.
    - **Impact:** Offers a comprehensive view of the checkout process, including order summary and payment completion.

### UI Components
4. **File: `resources/views/components/loader.blade.php`**
    - **Status:** Added
    - **Changes:** Introduced a new loader component.
    - **Description:** This component displays a loader animation, improving user feedback during asynchronous operations.
    - **Impact:** Enhances user experience by providing visual feedback during loading states.

### Order Process Enhancements
5. **File: `app/Http/Controllers/OrderProcessController.php`**
    - **Status:** Modified
    - **Changes:** Added a new method for the checkout view.
    - **Description:** The `checkout` method renders the checkout page.
    - **Impact:** Integrates the checkout process into the order flow.

6. **File: `app/Livewire/Business/OrderProcessView.php`**
    - **Status:** Modified
    - **Changes:** Added a method to redirect to the checkout page.
    - **Description:** The `submitCheckout` method redirects users to the new checkout page.
    - **Impact:** Streamlines the transition from order processing to checkout.

### Authentication Pages UI Enhancements
7. **Files:**
    - `resources/views/auth/confirm-password.blade.php`
    - `resources/views/auth/forgot-password.blade.php`
    - `resources/views/auth/login.blade.php`
    - `resources/views/auth/reset-password.blade.php`
    - `resources/views/auth/two-factor-challenge.blade.php`
    - `resources/views/auth/verify-email.blade.php`
    - `resources/views/auth/register.blade.php`
    - `resources/views/auth/register.blade.php`
    - `resources/views/auth/register.blade.php`
    - **Status:** Modified
    - **Changes:** Updated input fields, labels, and overall layout to improve usability and aesthetics, incorporating dark mode support.
    - **Description:** These updates ensure a consistent and modern look across all authentication pages.
    - **Impact:** Enhances the visual appeal and usability of authentication forms, providing a better user experience.

### UI General Enhancements
8. **Files:**
    - `resources/views/components/*.blade.php` (multiple components)
    - **Status:** Modified
    - **Changes:** Updated styles and classes to improve accessibility and aesthetics.
    - **Description:** Improvements include better color contrast, responsive design adjustments, and dark mode compatibility.
    - **Impact:** Provides a more consistent and user-friendly interface throughout the application.

### Styles and Scripts
9. **File: `resources/css/app.css`**
    - **Status:** Modified
    - **Changes:** Added styles to support the new UI components and enhancements.
    - **Description:** Includes styles for hiding number input arrows and enhancing authentication page fields.
    - **Impact:** Ensures visual consistency and usability across different components.

10. **File: `resources/js/app.js`**
    - **Status:** Modified
    - **Changes:** Added a script for handling the loader timeout.
    - **Description:** This script fades out the loader after a specified timeout.
    - **Impact:** Improves loading feedback and user experience during page transitions.

## Detailed Changes

### CheckoutForm.php

```php
namespace App\Livewire\Business;

use Livewire\Component;

class CheckoutForm extends Component
{
    public $paymentMethod = 'credit'; // credit || debit || pix || boleto
    public $isAddNewCard = false; // if user has saved credit card, set this value to FALSE

    public function updatePaymentMethod($type) {
        $this->paymentMethod = $type;
    }

    public function updateIsAddNewCard() {
        $this->isAddNewCard = !$this->isAddNewCard;
    }

    public function render()
    {
        return view('dashboard.business.checkout-form');
    }
}
```

### checkout-form.blade.php

```html
<form action="" method="" class="flex flex-col gap-5">
    <!-- Payment Method Selection -->
    <div class="flex flex-col gap-2">
        <x-label for="email" value="{{ __('Select Payment Method') }}" />
        <div class="grid grid-cols-2 gap-3 sm:gap-4">
            <!-- Payment Options -->
            <div class="relative">
                <input type="radio" name="payment_method" value="credit"
                    class="absolute inset-0 z-10 w-full h-full opacity-0 cursor-pointer peer"
                    {{ $paymentMethod == 'credit' ? 'checked' : null }} wire:click="updatePaymentMethod('credit')">
                <div
                    class="flex flex-col gap-3 items-start w-full p-5 peer-checked:bg-teal-50 peer-checked:ring peer-checked:ring-teal-200 peer-hover:bg-teal-50 peer-hover:ring-teal-200 peer-hover:ring dark:peer-checked:bg-[#242B34] dark:peer-hover:bg-[#242B34] border border-gray-200 dark:border-neutral-700 rounded-xl">
                    <svg class="w-6 h-6 stroke-gray-800 dark:stroke-neutral-200" fill="none"
                        stroke-width="2" stroke="currentColor" viewBox="0 0 24 24">
                        <path stroke-linecap="round" stroke-linejoin="round" d="M2.25 8.25h19.5M2.25 9h19.5m-16.5 5.25h6m-6 2.25h3m-3.75 3h15a2.25 2.25 0 0 0 2.25-2.25V6.75A2.25 2.25 0 0 0 19.5 4.5h-15a2.25 2.25 0 0 0-2.25 2.25v10.5A2.25 2.25 0 0 0 4.5 19.5Z">
                        </path>
                    </svg>
                    <p class="text-sm text-gray-800 dark:text-neutral-200">
                        {{ __('Credit Card') }}
                    </p>
                </div>
            </div>
            <div class="relative">
                <input type="radio" name="payment_method" value="debit"
                    class="absolute inset-0 z-10 w-full h-full opacity-0 cursor-pointer peer"
                    {{ $paymentMethod == 'debit' ? 'checked' : null }} wire:click="updatePaymentMethod('debit')">
                <div
                    class="flex flex-col gap-3 items-start w-full p-5 peer-checked:bg-teal-50 peer-checked:ring peer-checked:ring-teal-200 peer-hover:bg-teal-50 peer-hover:ring-teal-200 peer-hover:ring dark:peer-checked:bg-[#242B34] dark:peer-hover:bg-[#242B34] border border-gray-200 dark:border-neutral-700 rounded-xl">
                    <svg class="w-6 h-6 stroke-gray-800 dark:stroke-neutral-200" fill="none"
                        stroke-width="2" stroke="currentColor" viewBox="0 0 24 24">
                        <path stroke-linecap="round" stroke-linejoin="round" d="M2.25 8.25h19.5M2.25 9h19.5m-16.5 5.25h6m-6 2.25h3m-3.75 3h15a2.25 2.25 0 0 0 2.25-2.25V6.75A2.25 2.25 0 0 0 19.5 4.5h-15a2.25 2.25 0 0 0-2.25 2.25v10.5A2.25 2.25 0 0 0 4.5 19.5Z">
                        </path>
                    </svg>
                    <p class="text-sm text-gray-800 dark:text-neutral-200">
                        {{ __('Debit Card') }}
                    </p>
                </div>
            </div>
            <!-- Add other payment methods like PIX and Boleto -->

        </div>
    </div>

    <!-- Card Details -->
    @if ($paymentMethod == 'credit' || $paymentMethod == 'debit')
        <div class="flex flex-col">
            <x-label for="card_details" value="{{ __('Card Details') }}" />
            <div class="grid grid-cols-2 gap-3 my-2 sm:gap-4">
                <div class="relative">
                    <input type="radio" name="card_details" value="addNewCard"
                        class="absolute inset-0 z-10 w-full h-full opacity-0 cursor-pointer peer"
                        wire:click="updateIsAddNewCard" {{ $isAddNewCard ? 'checked' : null }}>
                    <div
                        class="flex flex-col gap-3 items-start w-full p-5 peer-checked:bg-teal-50 peer-checked:ring peer-checked:ring-teal-200 peer-hover:bg-teal-50 peer-hover:ring-teal-200 peer-hover:ring dark:peer-checked:bg-[#242B34] dark:peer-hover:bg-[#242B34] border border-gray-200 dark:border-neutral-700 rounded-xl">
                        <svg class="w-6 h-6 stroke-gray-800 dark:stroke-neutral-200" fill="none"
                            stroke-width="1.5" stroke="currentColor" viewBox="0 0 24 24">
                            <path stroke-linecap="round" stroke-linejoin="round"
                                d="M12 9v6m3-3H9m12 0a9 9 0 1 1-18 0 9 9 0 0 1 18 0Z">
                            </path>
                        </svg>
                        <p class="block text-sm text-gray-800 dark:text-neutral-200">
                            {{ __('Add New Card') }}
                        </p>
                    </div>
                </div>
                <div class="relative">
                    <input type="radio" name="card_details" value="savedCard"
                        class="absolute inset-0 z-10 w-full h-full opacity-0 cursor-pointer peer"
                        wire:click="updateIsAddNewCard" {{ !$isAddNewCard ? 'checked' : null }}>
                    <div
                        class="flex flex-col gap-3 items-start w-full p-5 peer-checked:bg-teal-50 peer-checked:ring peer-checked:ring-teal-200 peer-hover:bg-teal-50 peer-hover:ring-teal-200 peer-hover:ring dark:peer-checked:bg-[#242B34] dark:peer-hover:bg-[#242B34] border border-gray-200 dark:border-neutral-700 rounded-xl">
                        <div class="flex items-center gap-3">
                            <svg class="w-6 h-6 stroke-gray-800 dark:stroke-neutral-200" fill="none"
                                stroke-width="2" stroke="currentColor" viewBox="0 0 24 24">
                                <path stroke-linecap="round" stroke-linejoin="round"
                                    d="M2.25 8.25h19.5M2.25 9h19.5m-16.5 5.25h6m-6 2.25h3m-3.75 3h15a2.25 2.25 0 0 0 2.25-2.25V6.75A2.25 2.25 0 0 0 19.5 4.5h-15a2.25 2.25 0 0 0-2.25 2.25v10.5A2.25 2.25 0 0 0 4.5 19.5Z">
                                </path>
                            </svg>
                            <p class="text-base font-medium text-gray-800 dark:text-neutral-200">
                                Bank Name
                            </p>
                        </div>
                        <p class="block text-sm text-gray-800 dark:text-neutral-200">
                            {{ '**** **** **** 2209' }}
                        </p>
                    </div>
                </div>
            </div>
            @if ($isAddNewCard)
                <x-input id="cardholder_name" type="text" class="block w-full"
                    placeholder="{{ __('Cardholder Name') }}" required />
                <div>
                    <div class="relative">
                        <x-input id="cardholder_number" type="number" class="block w-full rounded-b-none"
                            placeholder="{{ __('Cardholder Number') }}" required />
                        <img src="{{ asset('img/svgs/visa.svg') }}"
                            class="absolute w-auto h-2 translate-y-1/2 right-3 bottom-1/2" alt="">
                    </div>
                    <div class="grid grid-cols-2">
                        <x-input id="card_exp_date" type="number"
                            class="block w-full !-mt-2 rounded-t-none !border-t-0 rounded-br-none"
                            placeholder="{{ __('Expiry date') }}" required />
                        <x-input id="card_cvv" type="number"
                            class="block w-full !-mt-2 rounded-t-none !border-t-0 rounded-bl-none" placeholder="•••"
                            required />
                    </div>
                </div>
                <p class="mt-1 mb-6 text-sm text-gray-400">
                    {{ __('Payment is secure and encrypted') }}
                </p>
            @endif
        </div>
    @endif

    <x-button>
        {{ __('Pay') }}
        R$ 255
    </x-button>
</form>

```

### checkout.blade.php

```html
<x-app-layout>
    <x-slot name="title">
        {{ __('Checkout Page') }} - {{ config('app.name', 'Creatify') }}
    </x-slot>

    <div class="p-2 space-y-5 sm:p-5 md:pt-5">
        <div
            class="flex flex-col p-5 space-y-4 bg-white border border-gray-200 shadow-sm rounded-xl dark:bg-neutral-800 dark:border-neutral-700">
            <div class="grid gap-5 lg:gap-12 sm:grid-cols-2">
                <!-- Order Overview -->
                <div>
                    <button type="button" onclick="window.history.back()"
                        class="inline-flex items-center gap-1 p-3 mb-10 font-semibold text-gray-800 transition-all dark:text-neutral-200 hover:bg-gray-200 dark:hover:bg-opacity-10 rounded-xl">
                        <svg class="w-4 h-4 stroke-gray-700 dark:stroke-neutral-200" fill="none" stroke-width="2"
                            stroke="currentColor" viewBox="0 0 24 24">
                            <path stroke-linecap="round" stroke-linejoin="round" d="M15.75 19.5 8.25 12l7.5-7.5"></path>
                        </svg>
                        Back to Order Page
                    </button>
                    <div class="overflow-hidden bg-white border border-gray-200 shadow rounded-xl lg:rounded-lg dark:bg-neutral-700 dark:border-neutral-700 dark:shadow-lg">
                        <div class="px-3 py-5 lg:px-5">
                            <p class="text-2xl font-bold text-gray-700 dark:text-neutral-200 mb-7">
                                {{ __('dashboard.orders.yourorder') }}
                            </p>
                            <div class="flex flex-col gap-3">
                                @foreach ($orderItems as $item)
                                    <x-pricing.pricing-parent :icon="asset($item->icon)"
                                        :title="$item->name . ': ' . $item->quantity"
                                        :price="$item->price * $item->quantity" />
                                @endforeach
                                <x-pricing.pricing-child title="{{ __('dashboard.orders.subtotal') }}"
                                    :price="$subtotal" />
                            </div>
                        </div>
                        <div class="px-3 py-5 lg:px-5 bg-neutral-800">
                            <div class="flex items-center justify-between gap-5 text-2xl font-bold text-white">
                                <p>
                                    Total
                                </p>
                                <p>
                                    R$ {{ $total }}
                                </p>
                            </div>
                        </div>
                    </div>
                </div>

                <!-- Payment Details -->
                <div>
                    <p class="text-base font-bold text-gray-800 sm:text-lg dark:text-neutral-200">
                        Payment Details
                    </p>
                    <p class="mt-1 mb-6 text-sm text-gray-400 sm:text-base">
                        Complete your order by providing your payment details
                    </p>

                    @livewire('business.checkout-form')
                </div>
            </div>
        </div>
    </div>
</x-app-layout>

```

## Impact on the Application

- **User Experience:** The checkout process has been significantly improved, providing a seamless and user-friendly experience for completing orders. The introduction of Livewire components ensures that the checkout form is dynamic and responsive, enhancing the overall user interaction.
- **Aesthetics:** Updated authentication pages and other UI components to ensure a consistent look and feel across the application, including dark mode support.
- **Functionality:** Added new features such as loaders and dynamic form handling, which improve the application's responsiveness and user feedback during critical operations like checkout and authentication.

This collection of updates positions the application as more user-centric, with enhanced visual appeal, streamlined processes, and robust functionality suitable for modern web applications.

---

# #60 Notification Enhancements, Address Autofill, and UI Updates

## Introduction

This pull request introduces several key enhancements, including the addition of custom email notifications, improvements to the address autofill functionality using the Brasil API, UI updates, and restructuring of some routes for better clarity. These changes collectively improve the user experience, enhance notifications, and ensure data consistency and integrity.

## Changes Overview

### Notifications
1. **File: `app/Notifications/CustomResetPassword.php`**
    - **Status:** Added
    - **Changes:** A new notification class for customizing the password reset email.
    - **Description:** This class allows for customized email notifications for password resets.
    - **Impact:** Users receive more tailored and brand-consistent notifications.

2. **File: `app/Notifications/CustomVerifyEmail.php`**
    - **Status:** Added
    - **Changes:** A new notification class for customizing the email verification email.
    - **Description:** This class customizes the email verification message.
    - **Impact:** Improved branding and user experience for email verification.

### Language Files
3. **File: `resources/lang/pt_br/email.php`**
    - **Status:** Added
    - **Changes:** Added email notification texts in Portuguese.
    - **Description:** Provides localized messages for email notifications.
    - **Impact:** Enhances localization support for email communications.

### Address Autofill
4. **File: `app/Livewire/UpdateCreatorContactForm.php`**
    - **Status:** Modified
    - **Changes:** Implemented address autofill using Brasil API for both billing and shipping addresses.
    - **Description:** Autofills address fields based on ZIP code input using Brasil API.
    - **Impact:** Improves user experience by simplifying form completion.

### UI Updates
5. **File: `resources/views/profile/update-creator-contact-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Enhanced input fields and added address autofill functionality.
    - **Description:** Improves form usability and aesthetics.
    - **Impact:** Provides a more user-friendly interface for profile updates.

6. **File: `resources/views/profile/update-creator-messenger-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated the form to make the email readonly and styled disabled inputs.
    - **Description:** Ensures email field reflects account email and is not editable from the social media form.
    - **Impact:** Prevents accidental changes to the email address while updating social media information.

7. **File: `resources/views/auth/register.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated form action to `register.post` and adjusted favicon paths.
    - **Description:** Aligns with routing changes and corrects image paths.
    - **Impact:** Fixes broken images and ensures proper form submission.

8. **File: `composer.json`**
    - **Status:** Modified
    - **Changes:** Added `predis/predis` package.
    - **Description:** Adds Redis support for caching.
    - **Impact:** Enhances performance and caching capability.

## Detailed Changes

### CustomResetPassword.php

```php
namespace App\Notifications;

use Illuminate\Notifications\Messages\MailMessage;
use Illuminate\Notifications\Notification;
use Illuminate\Support\Facades\Lang;

class CustomResetPassword extends Notification
{
    public $token;
    public static $createUrlCallback;
    public static $toMailCallback;

    public function __construct($token)
    {
        $this->token = $token;
    }

    public function via($notifiable)
    {
        return ['mail'];
    }

    public function toMail($notifiable)
    {
        if (static::$toMailCallback) {
            return call_user_func(static::$toMailCallback, $notifiable, $this->token);
        }

        return $this->buildMailMessage($this->resetUrl($notifiable));
    }

    protected function buildMailMessage($url)
    {
        return (new MailMessage)
            ->greeting(__('email.ResetPassword.greeting'))
            ->subject(__('email.ResetPassword.subject'))
            ->line(__('email.ResetPassword.line1'))
            ->action(__('email.ResetPassword.action'), $url)
            ->line(__('email.ResetPassword.line2', ['count' => config('auth.passwords.' . config('auth.defaults.passwords') . '.expire')]))
            ->line(__('email.ResetPassword.line3'))
            ->salutation(__('email.ResetPassword.salutation'));
    }

    protected function resetUrl($notifiable)
    {
        if (static::$createUrlCallback) {
            return call_user_func(static::$createUrlCallback, $notifiable, $this->token);
        }

        return url(route('password.reset', [
            'token' => $this->token,
            'email' => $notifiable->getEmailForPasswordReset(),
        ], false));
    }

    public static function createUrlUsing($callback)
    {
        static::$createUrlCallback = $callback;
    }

    public static function toMailUsing($callback)
    {
        static::$toMailCallback = $callback;
    }
}
```

### CustomVerifyEmail.php

```php
namespace App\Notifications;

use Illuminate\Notifications\Messages\MailMessage;
use Illuminate\Notifications\Notification;
use Illuminate\Support\Carbon;
use Illuminate\Support\Facades\Config;
use Illuminate\Support\Facades\Lang;
use Illuminate\Support\Facades\URL;

class CustomVerifyEmail extends Notification
{
    public static $createUrlCallback;
    public static $toMailCallback;

    public function via($notifiable)
    {
        return ['mail'];
    }

    public function toMail($notifiable)
    {
        $verificationUrl = $this->verificationUrl($notifiable);

        if (static::$toMailCallback) {
            return call_user_func(static::$toMailCallback, $notifiable, $verificationUrl);
        }

        return $this->buildMailMessage($verificationUrl);
    }

    protected function buildMailMessage($url)
    {
        return (new MailMessage)
            ->greeting(__('email.VerifyEmail.greeting'))
            ->subject(__('email.VerifyEmail.subject'))
            ->line(__('email.VerifyEmail.line1'))
            ->action(__('email.VerifyEmail.action'), $url)
            ->line(__('email.VerifyEmail.line2'))
            ->salutation(__('email.VerifyEmail.salutation'));
    }

    protected function verificationUrl($notifiable)
    {
        if (static::$createUrlCallback) {
            return call_user_func(static::$createUrlCallback, $notifiable);
        }

        return URL::temporarySignedRoute(
            'verification.verify',
            Carbon::now()->addMinutes(Config::get('auth.verification.expire', 60)),
            [
                'id' => $notifiable->getKey(),
                'hash' => sha1($notifiable->getEmailForVerification()),
            ]
        );
    }

    public static function createUrlUsing($callback)
    {
        static::$createUrlCallback = $callback;
    }

    public static function toMailUsing($callback)
    {
        static::$toMailCallback = $callback;
    }
}
```

### UpdateCreatorContactForm.php

```php
public function zipCall()
{
    $apiUrl = "https://brasilapi.com.br/api/cep/v1/{$this->zip}";
    
    $ch = curl_init($apiUrl);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    
    $response = curl_exec($ch);
    
    if (curl_errno($ch)) {
        echo 'Error: ' . curl_error($ch);
    }
    
    curl_close($ch);
    
    $data = json_decode($response, true);
    
    if ($data) {
        $this->city = $data['city'] ?? '';
        $this->street = $data['street'] ?? '';
        $this->state = $data['state'] ?? '';
    }
}

public function shippingCall()
{
    $apiUrl = "https://brasilapi.com.br/api/cep/v1/{$this->shipping_zip}";
    
    $ch = curl_init($apiUrl);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    
    $response = curl_exec($ch);
    
    if (curl_errno($ch)) {
        echo 'Error: ' . curl_error($ch);
    }
    
    curl_close($ch);
    
    $data = json_decode($response, true);
    if ($data) {
        $this->shipping_city = $data['city'] ?? '';
        $this->shipping_street = $data['street'] ?? '';
        $this->shipping_state = $data['state'] ?? '';
    }
}
```

### ContactReceived.php Updates for Localization

```php
public function toMail(object $notifiable): MailMessage
{
    return (new MailMessage)
        ->greeting(__('email.ContactReceived.greeting'))
        ->line(__('email.ContactReceived.line1', ['first_name' => $this->data['first_name']]))
        ->line(__('email.ContactReceived.line2', ['last_name' => $this->data['last_name']]))
        ->line(__('email.ContactReceived.line3', ['company' => $this->data['company']]))
        ->line(__('email.ContactReceived.line4', ['email' => $this->data['email']]))
        ->line(__('email.ContactReceived.line5', ['phone_number' => $this->data['phone_number']]))
        ->line(__('email.ContactReceived.line6', ['message' => $this->data['message']]))
        ->line('');
}
```

The adoption of these changes leads to a more robust, user-friendly, and customizable application. The notification improvements ensure consistent and branded communication, the UI updates enhance user interaction and experience, while the back-end adjustments maintain data integrity and simplify administrative processes.

---

# #58 Enhancements to CPF/CNPJ Validation in User Registration

## Introduction
This pull request improves the CPF/CNPJ validation process during user registration, providing more robust checks and better integration with external validation APIs. The updates ensure that only valid and active CPF/CNPJ entries are accepted, enhancing data integrity and user experience.

## Changes Overview

1. **File: `app/Actions/Fortify/CreateNewUser.php`**
- **Status:** Modified
- **Changes:**
  - Added detailed validations for CPF and CNPJ.
  - Integrated CPF/CNPJ validation through external API to confirm validity and activity status.
  - Enhanced error messaging for clearer feedback.
- **Description:** Improved CPF/CNPJ validation mechanism to ensure only valid and active entries are accepted during registration.
- **Impact:** Enhances data integrity by validating user identification details against official records.

## Detailed Changes

### CreateNewUser.php

```php
public function create(array $input): User
{
    Validator::make($input, [
        ...
    ],[
        ...
    ])->validate();

    // Get CPF/CNPJ value
    $cpf_cnpj_value = ($input['cpf']) ? $input['cpf'] : $input['cnpj'];

    // Validate CPF/CNPJ
    if ($input['cpf_cnpj_choice'] == "CPF") {
        Validator::make($input, [
            'cpf' => ['required', 'unique:users_cpf'],
            'birthday' => ['required']
        ])->validate();
    } else { // CNPJ
        Validator::make($input, ['cnpj' => [
            'required',
            'unique:users_cnpj',
        ]])->validate();
    }

    // Clean CPF/CNPJ value
    $cpfcnpjclean = preg_replace('/[^A-Za-z0-9]/', '', $cpf_cnpj_value);
    $token = config('app.cpfcnpj_token');
    $pacote = ($input['cpf_cnpj_choice'] == 'CPF') ? '2' : '10';

    // Get CPF/CNPJ data from API
    $url = "https://api.cpfcnpj.com.br/{$token}/{$pacote}/{$cpfcnpjclean}";
    $result = Http::get($url);

    // Set output based on CPF/CNPJ choice
    $output = ($input['cpf_cnpj_choice'] == 'CPF') ? 'cpf' : 'cnpj';

    $response = [];
    if ($result->successful()) {
        $response = $result->json();
        if ($input['cpf_cnpj_choice'] === 'CPF') {
            if (!empty($input['birthday'])) {
                $cpfBirthday = Carbon::createFromFormat('d/m/Y', $response['nascimento'])->format('Y-m-d');
                if ($cpfBirthday !== $input['birthday']) {
                    $data['erro'] = __('validation.custom.invalid_birthday');
                    Validator::make($input, [$output => [
                        new CPFCNPJRule($data)
                    ]])->validate();
                }
            }
        } else { // CNPJ
            if ($response['situacao']['nome'] !== "Ativa") {
                $data['erro'] = __('validation.custom.cnpj_not_active');
                Validator::make($input, [$output => [
                    new CPFCNPJRule($data)
                ]])->validate();
            }
        }
    } else {
        $response = $result->body();
        $data = json_decode($response, true);

        Validator::make($input, [$output => [
            new CPFCNPJRule($data)
        ]])->validate();
    }

    // checking
    return DB::transaction(function () use ($response, $input, $cpf_cnpj_value) {
        return tap(User::create([ ...
        ]), function (User $user) use ($input, $cpf_cnpj_value) {
            ...
        });
    });
}
```

## Explanation

1. **Detailed Validation**:
   - Added checks to ensure CPF is unique and birthday is required when `cpf_cnpj_choice` is "CPF".
   - For CNPJ, apart from checking uniqueness, it also validates against the external API to ensure the status is "Ativa".

2. **External API Integration**:
   - Cleaned the CPF/CNPJ value for API request.
   - Used the response from the API to validate the birthday for CPF and status for CNPJ.

3. **Enhanced Feedback**:
   - Clear error messages are provided if the birthday does not match or the CNPJ status is not active.
   - These feedback mechanisms help users correct their entries and ensure data integrity.

These updates significantly improve the robustness of the registration process, ensuring only valid and active CPF/CNPJ entries are accepted, thereby enhancing the reliability of user data within the system.

---

# #57 Enhancements to Address Form with Automatic ZIP Lookup

## Introduction
This pull request introduces improvements to the address form component by integrating automatic ZIP code lookup functionality. The updates enhance user experience by populating the address fields automatically based on the provided ZIP code, reducing manual input and potential errors.

### Key Features:
1. **Automatic ZIP Lookup**: Integrated BrasilAPI for real-time address lookup based on ZIP code.
2. **Dual ZIP Handling**: Supports both primary and shipping address ZIP code lookups.
3. **UI Improvements**: Simplified user interface, ensuring smoother interactions.

## Changes Overview

1. **File: `app/Livewire/UpdateCreatorContactForm.php`**
- **Status:** Modified
- **Changes:** 
  - Added `zipCall` and `shippingCall` methods to handle API calls for ZIP code lookup.
  - Integrated CURL requests to fetch address data from BrasilAPI.
- **Description:** These methods automatically populate city, street, and state fields based on the provided ZIP code.
- **Impact:** Reduces user effort and potential errors by automatically filling in address details.

2. **File: `resources/views/profile/update-creator-contact-form.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Changed input types for ZIP fields to `number` and added `wire:change` events for real-time processing.
  - Removed old JavaScript for fetching address data and replaced it with Livewire directives.
- **Description:** Ensures real-time updates and a cleaner approach to handling address data fetching.
- **Impact:** Enhances user experience by simplifying address lookup and input process.

These updates significantly improve the address form component, providing a more efficient and user-friendly interface. The automatic ZIP code lookup functionality ensures that users can quickly and accurately enter address information, enhancing the overall usability of the form. 

## Detailed Changes

### UpdateCreatorContactForm.php
```php
public function zipCall()
{
    $apiUrl = "https://brasilapi.com.br/api/cep/v2/{$this->zip}";
    
    $ch = curl_init($apiUrl);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    
    $response = curl_exec($ch);
    
    if (curl_errno($ch)) {
        echo 'Error: ' . curl_error($ch);
    }
    
    curl_close($ch);
    
    $data = json_decode($response, true);
    
    if ($data) {
        $this->city = $data['city'] ?? '';
        $this->street = $data['street'] ?? '';
        $this->state = $data['state'] ?? '';
    }
}

public function shippingCall()
{
    $apiUrl = "https://brasilapi.com.br/api/cep/v2/{$this->shipping_zip}";
    
    $ch = curl_init($apiUrl);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    
    $response = curl_exec($ch);
    
    if (curl_errno($ch)) {
        echo 'Error: ' . curl_error($ch);
    }
    
    curl_close($ch);
    
    $data = json_decode($response, true);
    if ($data) {
        $this->shipping_city = $data['city'] ?? '';
        $this->shipping_street = $data['street'] ?? '';
        $this->shipping_state = $data['state'] ?? '';
    }
}
```

### update-creator-contact-form.blade.php
```blade
<div class="sm:col-span-2 xl:col-span-1">
    <x-input id="zip" type="number" class="block w-full mt-1" wire:model="zip" wire:change="zipCall" placeholder="{{ __('profile.contact.zip_placeholder') }}" />
    <x-input-error for="zip" class="mt-2" />
</div>
...
<div class="sm:col-span-2 xl:col-span-1">
    <x-input id="shipping_zip" type="text" class="block w-full mt-1" wire:model="shipping_zip" wire:change="shippingCall" placeholder="{{ __('profile.contact.zip_placeholder') }}" />
    <x-input-error for="shipping_zip" class="mt-2" />
</div>
```

These changes ensure a more intuitive and efficient address entry process, leveraging real-time data fetching to enhance the overall user experience.

---

# #56 Enhancements to User Profile and Video Management

## Introduction
This pull request brings several improvements to the user profile and video management features within the application. Key updates include enhanced image resizing capabilities for avatar uploads, improved video management with dynamic updates, and UI adjustments for a better user experience.

### Key Features:
1. **Avatar Image Resizing**: Implemented image resizing for avatar uploads to ensure consistent and optimized profile photos.
2. **Video Management**: Improved handling and dynamic display of profile videos, including controls to change and upload new videos seamlessly.
3. **UI Adjustments**: Enhancements to the user interface for better user interaction and feedback.

## Changes Overview

1. **File: `app/Http/Controllers/UserProfileController.php`**
- **Status:** Modified
- **Changes:** 
  - Added dependencies for `File` and `Image`.
  - Implemented image resizing before storing the avatar.
- **Description:** Resized avatar images to 300px width while maintaining the aspect ratio, and stored them in the `public` disk.
- **Impact:** Ensures optimized and uniform profile photos, reducing storage space and improving load times.

2. **File: `resources/views/profile/avatar-upload.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Updated button classes and text for consistency.
- **Description:** Applied minor UI changes to enhance user interaction with avatar upload functionality.
- **Impact:** Improved user experience for profile photo uploads.

3. **File: `resources/views/profile/profile-video-upload.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Added dynamic video handling and controls.
- **Description:** Enhanced video upload section with better visibility controls and dynamic updates for video changes.
- **Impact:** Improved video management experience for users, allowing seamless video uploads and previews.

4. **File: `resources/views/profile/setcard.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Added JavaScript for video URL handling and dynamic DOM updates.
- **Description:** Incorporated functionality to handle video URLs dynamically and update the DOM elements accordingly.
- **Impact:** Ensures users can see video previews immediately after uploading, enhancing the overall user experience.

5. **File: `resources/views/profile/update-creator-contact-form.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Adjusted data bindings for better reactivity.
- **Description:** Enhanced Livewire data bindings for real-time updates in the contact form.
- **Impact:** Provides a more responsive form experience for users.

These updates collectively enhance the user profile and video management functionalities, providing a seamless and optimized experience for users. The improvements in image processing and video handling ensure that the application remains efficient and user-friendly.

---

# #55 User Profile Update and Address Autofill

## Introduction
This pull request introduces several improvements to the user profile management system, including better alert handling, address autofill based on zip code using the BrasilAPI, and minor adjustments to the component interactions and data bindings.

### Key Features:
1. **Alert Handling**: Standardized alert handling across the profile update features.
2. **Address Autofill**: Automatically fills out address details based on zip code using BrasilAPI.
3. **Data Binding**: Enhanced Livewire data bindings for form inputs to ensure consistency and reactivity.

## Changes Overview

1. **File: `app/Livewire/AvatarUpload.php`**
- **Status:** Modified
- **Changes:** 
  - Updated alert method to use the correct parameters.
- **Description:** Standardized the alert method call to ensure consistent success messages.
- **Impact:** Improved user feedback when deleting a profile photo.

2. **File: `app/Livewire/ProfileVideoUpload.php`**
- **Status:** Modified
- **Changes:** 
  - Updated alert method to use the correct parameters.
- **Description:** Standardized the alert method call to ensure consistent success messages.
- **Impact:** Improved user feedback when uploading profile videos.

3. **File: `app/Livewire/UpdateCreatorContactForm.php`**
- **Status:** Modified
- **Changes:**
    - Added the `fillAddressFromZip()` function to fetch address details from BrasilAPI.
    - Updated alert method to use the correct parameters.
- **Description:** Added functionality to automatically fill address fields based on zip code using an external API.
- **Impact:** Enhances the user experience by reducing the need for manual entry of address details.

4. **File: `app/Livewire/UpdateCreatorMessengerForm.php`**
- **Status:** Modified
- **Changes:** 
  - Updated alert method to use the correct parameters.
- **Description:** Standardized the alert method call to ensure consistent success messages.
- **Impact:** Improved user feedback when updating contact information.

5. **File: `app/Livewire/UpdateCreatorPayoutForm.php`**
- **Status:** Modified
- **Changes:** 
  - Updated alert method to use the correct parameters.
- **Description:** Standardized the alert method call to ensure consistent success messages.
- **Impact:** Improved user feedback when updating payout information.

6. **File: `app/Livewire/UpdateEmailAddressForm.php`**
- **Status:** Modified
- **Changes:** 
  - Updated alert method to use the correct parameters.
- **Description:** Standardized the alert method call to ensure consistent success messages.
- **Impact:** Improved user feedback when updating email address.

7. **File: `resources/views/profile/update-creator-contact-form.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Changed `wire:model.defer` to `wire:model` for more responsive input updates.
- **Description:** Enhanced Livewire data bindings to ensure form inputs are updated promptly.
- **Impact:** Ensures a better user experience with real-time data binding and display.

These updates collectively refine the user profile management functionalities, improve user feedback mechanisms, and add the convenience of automatic address filling based on zip code inputs.

---

# #52 User Profile Enhancements

## Introduction
This pull request focuses on enhancing the user profile functionalities, including avatar uploads, handling file sizes more effectively, and optimizing background processes. The changes ensure a more streamlined and user-friendly experience while managing profile attributes.

### Key Features:
1. **Avatar Upload**: Enhanced avatar upload process with better error handling and user feedback.
2. **File Size Validation**: Improved file size validation rules.
3. **Optimized Profile Layout**: Streamlined layout for user profile management.

## Changes Overview

1. **File: `app/Http/Controllers/UserProfileController.php`**
- **Status:** Modified
- **Changes:** 
  - Removed commented return statement in `profilePhotoDisk` method.
- **Description:** Cleaned up code by removing unnecessary commented-out lines.
- **Impact:** Reduces code clutter, making it easier to read and maintain.

2. **File: `app/Livewire/AvatarUpload.php`**
- **Status:** Modified
- **Changes:** 
  - Added `public $counter = 1;` property.
- **Description:** Initialized a counter property, potentially for tracking uploads or retries.
- **Impact:** Lays the groundwork for further enhancements related to avatar upload management.

3. **File: `app/Rules/FileSize.php`**
- **Status:** Modified
- **Changes:** 
  - Removed `Log::warning` statements for size replacements.
- **Description:** Cleaned up debugging logs that are no longer necessary.
- **Impact:** Simplifies code and improves performance by removing unnecessary logging.

4. **File: `resources/lang/pt_br/profile.php`**
- **Status:** Modified
- **Changes:** 
  - Fixed a minor translation formatting issue in `avatarfilesize`.
- **Description:** Corrected a translation string for better clarity.
- **Impact:** Improved user messaging for Portuguese-speaking users.

5. **File: `resources/views/profile/avatar-upload.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Simplified and refactored the avatar upload component layout.
- **Description:** Streamlined the layout structure for better readability and maintenance.
- **Impact:** Provides a cleaner UI/UX for avatar uploads with improved handling of file inputs.

6. **File: `resources/views/profile/setcard.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Major cleanup and refactoring of the setcard profile layout.
- **Description:** Enhanced the profile management section with better HTML structure and scripting.
- **Impact:** Offers a more intuitive and accessible interface for users managing their profile details.

7. **File: `resources/views/profile/update-profile-information-form.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Removed `wire:ignore` directive and included a wrapper div around `avatar-upload` component.
- **Description:** Ensured that the Livewire component for avatar uploads is properly managed within the form.
- **Impact:** Fixes potential issues with reactivity and dynamic updates in the profile form.

These updates collectively enhance the user profile functionalities, ensure better handling of file uploads, and provide a cleaner and more user-friendly interface for managing user information.

---

# #50 User Registration UI Enhancements and Background Optimizations

## Introduction
This pull request focuses on enhancing the user registration interface and optimizing the background layouts across various components. These changes aim to improve the user experience by incorporating cleaner designs, adding new visual elements, and ensuring better compatibility with dark mode.

### Key Features:
1. **User Registration UI**: Improved the overall user interface for registration forms by restructuring input fields, integrating better icons, and refining validation and submission processes.
2. **Background Layouts**: Moved SVG backgrounds to a dedicated component for better reusability and maintenance.

## Changes Overview

1. **File: `resources/views/components/background-guest-layout.blade.php`**
- **Status:** Added
- **Changes:** 
  - Added an SVG-based background layout component for the guest interface.
- **Description:** Encapsulates complex SVG-based background designs into a reusable component.
- **Impact:** Simplifies the inclusion of SVG backgrounds across multiple pages without duplicating code.

2. **File: `app/Actions/Fortify/CreateNewUser.php`**
- **Status:** Modified
- **Changes:** 
  - Simplified the ASAAS API call URL and token retrieval logic.
- **Description:** Consolidated environment-based URL and token logic for ASAAS API calls.
- **Impact:** Cleaner code with reduced redundancy, improving maintainability.

3. **File: `config/app.php`**
- **Status:** Modified
- **Changes:** 
  - Updated application-specific configurations such as `app.name`, `asaas_token`, and `asaas_url`.
- **Description:** Refined configuration values for consistency.
- **Impact:** Ensures configurations are easily manageable and centralized.

4. **File: `resources/views/auth/register.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Redesigned the registration form for a more user-friendly experience.
  - Included new SVG icons for input fields.
  - Improved form validation processes and readability.
- **Description:** Enhances the registration form layout and incorporates accessibility improvements.
- **Impact:** Provides a cleaner interface with better usability, especially in handling user inputs.

5. **File: `resources/views/layouts/guest.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Replaced the inline SVG background with the `background-guest-layout` component.
- **Description:** Streamlined the guest layout by encapsulating background SVGs in a reusable component.
- **Impact:** Reduces code duplication and ensures a consistent background across pages.

6. **File: `resources/views/register.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Updated layout to integrate the `background-guest-layout` component.
  - Enhanced the presentation and interaction of registration options for businesses and creators.
- **Description:** Provides a visually cohesive and interactive registration page.
- **Impact:** Improves the visual hierarchy and user flow during the registration process.

These updates collectively enhance the user experience, improve maintainability, and ensure a cohesive design language across the application by leveraging reusable components and optimizing the registration interface.

---

# #47 Product Management and User Profile Enhancements

## Introduction
This pull request introduces significant enhancements to product management and user profile functionalities in the application. Key changes include making product columns nullable, improving product image handling, refining user profile management, and updating database schemas.

### Key Features:
1. **Product Management**: Improved handling of product creation, editing, and deletion, including image management.
2. **User Profile Enhancements**: Better organization of social media and payout details with new methods and routes.
3. **Database Updates**: Making certain product columns nullable to allow flexibility in product data.

## Changes Overview

1. **File: `database/migrations/2024_02_18_173121_make_products_columns_nullable.php`**
- **Status:** Added
- **Changes:** 
  - Migration to make `pronounciation` and `price` columns nullable in the `products` table.
- **Description:** Improves flexibility for products that may not have these attributes.
- **Impact:** Allows for products to be saved without requiring all details upfront.

2. **File: `app/Console/Commands/ContaAzulGetAccessToken.php`**
- **Status:** Modified
- **Changes:** 
  - Moved and updated the heartbeat URL call to occur after a successful token refresh.
- **Description:** Ensures that the heartbeat is only sent after confirming the access token retrieval.
- **Impact:** Provides more reliable logging and monitoring of token refresh events.

3. **File: `app/Http/Controllers/ProductController.php`**
- **Status:** Modified
- **Changes:** 
  - Removed mandatory validation for `pronounciation` and `price`.
  - Added methods for editing, deleting products, and managing product images.
- **Description:** Enhances product management capabilities, including handling of optional fields and image deletion.
- **Impact:** Improves user experience by allowing more flexible product updates.

4. **File: `app/Models/ProductImage.php`**
- **Status:** Modified
- **Changes:** 
  - Added an accessor to retrieve the full S3 URL of product images.
- **Description:** Simplifies image URL retrieval.
- **Impact:** Enhances clarity and ease of access to product images.

5. **File: `public/js/isPrice.js`**
- **Status:** Modified
- **Changes:** 
  - Adjusted image preview handling to manage file inputs correctly upon removal.
- **Description:** Ensures that the file input value is updated when images are removed from the preview.
- **Impact:** Improves the usability of the image upload interface.

6. **File: `resources/lang/pt_br/auth.php`, `resources/lang/pt_br/dashboard.php`**
- **Status:** Modified
- **Changes:** 
  - Added new localization strings for product management actions.
- **Description:** Supports new actions and notifications.
- **Impact:** Enhances user feedback in the application interface.

7. **File: `resources/views/dashboard/business/edit_product.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Updated form for editing products, including image management.
- **Description:** Provides a complete interface for product editing, including the ability to remove existing images.
- **Impact:** Enhances the product editing workflow and user experience.

8. **File: `resources/views/dashboard/business/products.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Added buttons and modals for editing and deleting products.
- **Description:** Enhances the product list with action buttons for easier management.
- **Impact:** Improves the usability and manageability of products in the dashboard.

9. **File: `resources/views/dashboard/components/header.blade.php`, `sidebar.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Adjusted the z-index for consistent layering.
- **Description:** Ensures proper stacking of elements.
- **Impact:** Keeps the header and sidebar properly layered relative to other elements.

10. **File: `resources/views/layouts/app.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Corrected SVG icon color in success alert.
- **Description:** Enhanced consistency of alert styling.
- **Impact:** Improves visual feedback to users.

11. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** 
  - Refined and added routes for managing products and user profile sections.
- **Description:** Organizes routes for better clarity and functionality.
- **Impact:** Ensures users have access to the necessary endpoints for product and profile management.

These changes collectively improve the capabilities and user experience of product management and user profile functionalities, ensuring better flexibility, usability, and organization within the application.

---

# #45 New Models, Database Migrations, and Livewire Components Added

## Introduction
This pull request introduces several new models, database migrations, controllers, and livewire components to the application. These changes add functionality for managing products, categories, and related user information.

### Key Changes:
1. **New Models**: Added models for `Product`, `ProductCategory`, `ProductImage`, `UserPayoutDetails`, and `UserSetcardVideo`.
2. **Database Migrations**: Introduced migrations for the new tables related to products and user details.
3. **Controllers**: Created controllers for handling product and price-related interactions.
4. **Livewire Components**: Added new livewire components for dashboard interactions.

## Changes Overview

1. **File: `app/Http/Controllers/PriceController.php`**
- **Status:** Added
- **Changes:** 
  - New controller with a method `show` returning the `prices` view.
- **Description:** Handles displaying of the prices page.
- **Impact:** Allows users to view price-related information.

2. **File: `app/Http/Controllers/ProductController.php`**
- **Status:** Added
- **Changes:** 
  - Implements product listing, creation, saving, and editing functionalities.
- **Description:** Manages CRUD operations for products, including image handling using S3 storage.
- **Impact:** Empowers users to manage their products effectively within the application.

3. **File: `app/Livewire/DashboardFooter.php`**
- **Status:** Added
- **Changes:** 
  - New Livewire component rendering the footer view for the dashboard.
- **Description:** Separates the footer logic into a reusable component.
- **Impact:** Enhances code modularity and reusability.

4. **File: `app/Livewire/DashboardHeader.php`**
- **Status:** Added
- **Changes:** 
  - New Livewire component rendering the header view for the dashboard.
- **Description:** Separates the header logic into a reusable component.
- **Impact:** Improves modularity and header management.

5. **File: `app/Livewire/ProfileNavigation.php`**
- **Status:** Added
- **Changes:** 
  - New Livewire component rendering the profile navigation view.
- **Description:** Manages the profile navigation elements.
- **Impact:** Enhances modularity for the user profile section.

6. **File: `app/Models/Product.php`**
- **Status:** Added
- **Changes:** 
  - New Eloquent model defining `Product`, its relationships, and UUID generation on creation.
- **Description:** Represents products in the system with attributes such as title, description, price, etc.
- **Impact:** Enables product data management in the database.

7. **File: `app/Models/ProductCategory.php`**
- **Status:** Added
- **Changes:** 
  - New Eloquent model defining `ProductCategory`.
- **Description:** Represents product categories in the system.
- **Impact:** Organizes products into categories.

8. **File: `app/Models/ProductImage.php`**
- **Status:** Added
- **Changes:** 
  - New Eloquent model defining `ProductImage`.
- **Description:** Handles image data associated with products.
- **Impact:** Supports product image management.

9. **File: `app/Models/UserPayoutDetails.php`**
- **Status:** Added
- **Changes:** 
  - New Eloquent model defining `UserPayoutDetails`.
- **Description:** Manages payout details for users.
- **Impact:** Supports storing and retrieving user payout information.

10. **File: `app/Models/UserSetcardVideo.php`**
- **Status:** Added
- **Changes:** 
  - New Eloquent model defining `UserSetcardVideo`.
- **Description:** Manages setcard videos for users.
- **Impact:** Supports storing and retrieving user setcard videos.

11. **File: `database/migrations/2024_02_18_050317_create_products_categories_table.php`**
- **Status:** Added
- **Changes:** 
  - Migration for creating `product_categories` table.
- **Description:** Defines the schema for the product categories table.
- **Impact:** Adds the necessary database structure for product categories.

12. **File: `app/Http/Controllers/BlogPostPublicController.php`**
- **Status:** Modified
- **Changes:** 
  - Removed redundant queries for random posts.
- **Description:** Cleans up the `show` method.
- **Impact:** Ensures more efficient database querying.

13. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** 
  - Removed redundant `create_product` and `edit_product` methods.
- **Description:** Cleans up the `OrderProcessController`.
- **Impact:** Reduces unnecessary code and maintains controller focus.

14. **File: `app/Http/Controllers/UserProfileController.php`**
- **Status:** Modified
- **Changes:** 
  - Added `socialmedia` method to handle new social media view.
- **Description:** Better organization and handling of user profile data.
- **Impact:** Supports new features in user profile management.

15. **File: `app/Livewire/Business/OrderProcess.php`**
- **Status:** Modified
- **Changes:** 
  - Updated view path in the render method.
- **Description:** Corrects the path to the appropriate view.
- **Impact:** Ensures proper rendering of components.

16. **File: `app/Livewire/UpdateCreatorContactForm.php`, `UpdateCreatorMessengerForm.php`, `UpdateCreatorPayoutForm.php`**
- **Status:** Modified
- **Changes:** 
  - Updated import paths and model references.
- **Description:** Adjusts model usage to align with renamed models and fields.
- **Impact:** Ensures correct data handling and consistency.

17. **File: `app/Models/Order.php`**
- **Status:** Modified
- **Changes:** 
  - Adds UUID generation in the model boot method.
- **Description:** Ensures that each order has a unique identifier.
- **Impact:** Improves order management and tracking.

18. **File: `app/Models/User.php`**
- **Status:** Modified
- **Changes:** 
  - Added new relationships and UUID generation.
- **Description:** Expands user capabilities with more detailed relationships.
- **Impact:** Supports more detailed user-related data.

19. **File: `app/Providers/JetstreamServiceProvider.php`**
- **Status:** Modified
- **Changes:** 
  - Changed Livewire component alias.
- **Description:** Ensures dashboard components are correctly named.
- **Impact:** Influences component binding and usage clarity.

20. **File: `app/Rules/VideoFileSize.php`**
- **Status:** Modified
- **Changes:** 
  - Updated validation message to use localization key.
- **Description:** Ensures consistent error messaging.
- **Impact:** Enhances user feedback during file uploads.

21. **File: `composer.json`**
- **Status:** Modified
- **Changes:** 
  - Changed `intervention/image` to `intervention/image-laravel`.
- **Description:** Reflects proper package usage.
- **Impact:** Corrects dependency management.

22. **File: `config/app.php`**
- **Status:** Modified
- **Changes:** 
  - Removed unneeded provider and alias for `Intervention\Image`.
- **Description:** Cleaned up the configuration.
- **Impact:** Streamlines the service provider and alias management.

These changes collectively expand the application's functionality, enhance code maintenance, and improve data management within the system.

---

# #43 Social Authentication and Email Template Updates

## Introduction
This pull request introduces Microsoft social authentication, optimizes the inclusion of providers in the social stream configuration, updates authentication-related Blade templates, and refines email layouts for consistency and readability.

### Key Changes:
1. **Microsoft Authentication**: Added configuration for Microsoft OAuth.
2. **Social Stream Providers**: Ensured proper merging of social stream providers.
3. **Blade Template Updates**: Minor fixes and refinements in authentication and social stream templates.
4. **Email Layout Enhancement**: Extensive updates to the email layout template to ensure better readability and structure.

## Changes Overview

1. **File: `config/services.php`**
- **Status:** Modified
- **Changes:** 
  - Added Microsoft OAuth configuration.
- **Description:**
  - Added `microsoft` provider with client ID, client secret, and redirect URL.
  - Example:
    ```php
    'microsoft' => [
        'client_id' => env('MICROSOFT_CLIENT_ID'),
        'client_secret' => env('MICROSOFT_CLIENT_SECRET'),
        'redirect' => 'your-microsoft-redirect-url',
    ],
    ```
- **Impact:** Enables integration with Microsoft for OAuth authentication.

2. **File: `config/socialstream.php`**
- **Status:** Modified
- **Changes:** 
  - Resolved merge conflict for Twitter OAuth2 provider.
- **Description:**
  - Ensured that `Providers::twitterOAuth2()` is included correctly in the providers array.
  - Example:
    ```php
    Providers::twitterOAuth2(),
    ```
- **Impact:** Ensures the Twitter OAuth2 provider is included in the social stream configuration.

3. **File: `resources/views/components/authentication-card-logo.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Minor fix to ensure proper closing of tag.
- **Description:**
  - Removed trailing whitespace.
  - Example:
    ```diff
    - </a> 
    + </a>
    ```
- **Impact:** Ensures HTML validation and cleaner code.

4. **File: `resources/views/components/socialstream.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Removed trailing space in Google OAuth link.
- **Description:**
  - Adjusted whitespace for consistency.
  - Example:
    ```diff
    - <a href="{{ route('oauth.redirect', ['provider' => JoelButcher\Socialstream\Providers::google()]) }}" >
    + <a href="{{ route('oauth.redirect', ['provider' => JoelButcher\Socialstream\Providers::google()]) }}">
    ```
- **Impact:** Ensures consistent code formatting.

5. **File: `resources/views/vendor/mail/html/layout.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Extensive updates to improve readability and structure of the email template.
- **Description:**
  - Applied consistent indentation and spacing.
  - Ensured proper HTML formatting and readability.
  - Improved inline CSS and organized mobile responsive styles.
- **Impact:** Enhances the maintainability and readability of the email layout template.

These changes collectively enhance the application's authentication capabilities and ensure consistency and readability across various components and templates, thereby improving overall code quality and user experience.

---

# #42 Localization Enhancements and Profile Management Refinements

## Introduction
This pull request enhances the localization capabilities of the application by adding and reorganizing translation keys for the profile management and authentication sections. It also includes refactoring and cleaning up various components and views to ensure consistency and better user experience.

### Key Changes:
1. **Localization Updates**: Added translation keys, particularly for profile management and authentication-related texts.
2. **Refactoring**: Cleaned up and refactored views to utilize the newly added localization keys.
3. **Route Optimization**: Moved profile-related routes to be properly protected under authenticated routes.

## Changes Overview

1. **File: `resources/lang/pt_br/profile.php`**
- **Status:** Newly Added
- **Changes:** 
  - Added translation keys for various profile-related texts.
  - Includes keys for profile setcard, contact information, payment details, connected accounts, etc.
- **Description:**
  - Provides comprehensive Portuguese translations for all profile management sections.
- **Impact:** Enhances the application's internationalization by providing localized content for Portuguese-speaking users.

2. **File: `app/Actions/Fortify/CreateNewUser.php`**
- **Status:** Modified
- **Changes:** 
  - Cleaned up unnecessary comments and redundant lines.
- **Description:**
  - **Refactoring**: Removed commented-out code and streamlined method implementations.
- **Impact:** Improves readability and maintainability of the user creation logic.

3. **File: `app/Http/Controllers/UserProfileController.php`**
- **Status:** Modified
- **Changes:** 
  - Replaced hardcoded success messages with localization keys.
- **Description:**
  - Used `__('profile.setcard.videosuccess')` and similar keys for success messages upon video and avatar uploads.
- **Impact:** Ensures that return messages are properly localized, improving user experience for non-English speakers.

4. **File: `app/Livewire/AvatarUpload.php`**
- **Status:** Modified
- **Changes:** 
  - Replaced hardcoded success messages with localization keys.
- **Description:**
  - **Localization**: Used `__('profile.setcard.avatarremoved')` for the avatar deletion success message.
- **Impact:** Maintains message consistency across the application and supports localization.

5. **File: `resources/lang/pt_br.json`**
- **Status:** Modified
- **Changes:** 
  - Removed redundant translations and added a new key.
- **Description:**
  - Streamlined JSON file by removing unnecessary keys now covered in `profile.php`.
- **Impact:** Reduces redundancy and centralizes translations for better management.

6. **File: `resources/lang/pt_br/auth.php`**
- **Status:** Modified
- **Changes:** 
  - Added new translation keys specific to the pre-registration and registration sections.
- **Description:**
  - Includes translations for new user registration process flows.
- **Impact:** Enhances the registration flow for Portuguese-speaking users.

7. **File: `resources/lang/pt_br/general.php`**
- **Status:** Modified
- **Changes:** 
  - Added and updated translation keys for general text and menu items.
- **Description:**
  - Included menu labels, footer texts, and common phrases used across the application.
- **Impact:** Ensures all common text elements are localized effectively.

8. **File: `resources/views/...` (multiple files)**
- **Status:** Modified
- **Changes:** 
  - Refactored various Blade templates to use localization keys.
- **Description:**
  - Replaced hardcoded text strings with calls to the localization system using `__('key')`.
  - Examples include profile titles, button texts, and form labels.
- **Impact:** Enhances the multilingual support of the application, making it user-friendly for Portuguese-speaking users.

These updates collectively improve the internationalization and consistency of the application while also refining the profile management features for clarity and usability. The changes ensure that all user-facing texts are readily translatable and maintainable through the localization files.

---

# #41 Localization and Route Optimization Updates

## Introduction
This pull request involves the integration of localization for certain static text elements and optimizing routes by removing redundant or unnecessary route definitions. These changes aim to improve code maintainability and readability while ensuring that text elements are properly localized for internationalization.

### Key Changes:
1. **Text Localization**: Replaced hardcoded text with localization references for easier translation and adaptation.
2. **Route Optimization**: Cleaned up route definitions by removing redundancy and ensuring proper middleware application.

## Changes Overview

1. **File: `resources/views/layouts/errors.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Replaced hardcoded footer text with a localization reference.
- **Description:**
  - **Localization**: Replaced `All Rights Reserved.` with `{{ __('general.footer.rights') }}` to make it translatable.
  - **Example Change:**
    ```diff
    - {{ __('All Rights Reserved.') }} | CNPJ: 52.646.941/0001-09
    + {{ __('general.footer.rights') }} | CNPJ: 52.646.941/0001-09
    ```
- **Impact:** Ensures error page footer text can be translated based on user language settings, improving internationalization support.

2. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** 
  - Removed unnecessary routes and reorganized existing routes for better clarity.
- **Description:**
  - **Route Cleanup**: Removed Laravel Fortify-specific route imports which were not being utilized.
  - **Route Consolidation**: Moved profile-related routes under the authenticated and appropriately middleware-protected group.
  - **Example Change:**
    ```diff
    -Route::get('/perfil/contato', [UserProfileController::class, 'contact'])->name('profile.contact');
    -Route::get('/perfil', [UserProfileController::class, 'setcard'])->name('profile.setcard');
    -Route::post('/perfil/avatar-upload', [UserProfileController::class, 'avatar_upload'])->name('profile.setcard.avatar_upload');
    +Route::middleware([
    +    'auth',
    +    config('jetstream.auth_session'),
    +    'checkUserRole:creator,business,agency,admin',
    +    'checkUserStatus',
    +])->group(function () {
    +    Route::get('/perfil/contato', [UserProfileController::class, 'contact'])->name('profile.contact');
    +    Route::get('/perfil', [UserProfileController::class, 'setcard'])->name('profile.setcard');
    +    Route::post('/perfil/avatar-upload', [UserProfileController::class, 'avatar_upload'])->name('profile.setcard.avatar_upload');
    +    Route::redirect('/user/profile', '/perfil/configuracoes');
    +    Route::get('/perfil/configuracoes', [UserProfileController::class, 'settings'])->name('profile.settings');
    +});
    ```
- **Impact:** Simplifies the route file by removing unnecessary lines and grouping routes logically, improving readability and maintainability.

These changes streamline the codebase by enhancing localization capabilities and optimizing route definitions, thus contributing to a more maintainable and internationalized application.

---

# #39 Refactoring and Consistency Updates for Profile Management

## Introduction
This pull request includes significant refactoring and consistency updates for user profile management, focusing on code quality and user experience improvements. Key changes involve adjustments to the `UserProfileController.php`, avatar upload mechanism, profile information update form, and associated views.

### Key Changes:
1. **Controller Method Refactoring**: Improved code formatting and readability in user profile-related controller methods.
2. **Avatar Upload Enhancements**: Improved functionality and UI/UX for avatar uploads including better error handling and display.
3. **Form and View Adjustments**: Tweaks to the profile form for better responsiveness and structure.

## Changes Overview

1. **File: `app/Http/Controllers/UserProfileController.php`**
- **Status:** Modified
- **Changes:** 
  - Improved code formatting and consistency.
  - Minor refactoring in methods handling profile video and avatar uploads.
- **Description:**
  - **Formatting**: Standardized spacing and indentation for better readability.
  - **Consistency**: Ensured formatting and method signatures follow best practices.
  - **Removed Comments**: Cleaned up commented-out code and unnecessary whitespace.
- **Impact:** Enhances code maintainability and readability without altering functional behavior.

2. **File: `app/Livewire/AvatarUpload.php`**
- **Status:** Modified
- **Changes:** 
  - Improved code formatting and consistency.
  - Refactored methods to handle photo preview reset on avatar deletion.
- **Description:**
  - **Formatting**: Standardized spacing and indentation.
  - **Reset Functionality**: `photoPreview` now properly resets upon deleting the profile photo.
  - **Modified Dispatch Events**: Updated event names to be consistent with existing conventions (`refresh-nav`).
- **Impact:** Streamlines avatar upload functionality, making the component more robust and easier to manage.

3. **File: `app/Models/User.php`**
- **Status:** Modified
- **Changes:** 
  - Simplified profile photo disk retrieval to always use 's3'.
- **Description:**
  - **Hardcoded Return Value**: Simplified the `profilePhotoDisk` method to return 's3' directly.
  - **Removed Conditional Logic**: Removed commented-out logic that checks environment variables.
- **Impact:** Simplifies configuration management by directly specifying the storage disk.

4. **File: `resources/views/profile/avatar-upload.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Enhanced the UI/UX for the avatar upload component.
- **Description:**
  - **Added Data Binding**: Improved JavaScript interactions for photo preview and current photo display.
  - **Responsive Design**: Adjusted classes and tags for better responsiveness and visual consistency.
  - **Error Handling**: Added error display for avatar input.
- **Impact:** Provides a smoother user experience during avatar upload, improving visual feedback and interactivity.

5. **File: `resources/views/profile/update-profile-information-form.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Applied `wire:ignore` to enhance form reactivity.
  - Improved formatting and consistency in form elements.
- **Description:**
  - **wire:ignore**: Prevents reactivity issues by not applying Livewire logic to specific form sections unnecessarily.
  - **Formatting**: Ensured consistent spacing and indentation.
  - **Form Inputs**: Improved the layout and readability of form input fields and labels.
- **Impact:** Enhances form performance and user experience, ensuring form elements behave as expected without unnecessary reactivity.

These updates collectively aim to improve code readability, maintainability, and the overall user experience for profile management functionalities. The refactoring efforts ensure a cleaner, more robust implementation, while the UI/UX enhancements provide a more intuitive and visually appealing interface for users.

---

# #38 Adjustments to AOS Animation Delays and Initialization Settings

## Introduction
This pull request enhances the user experience by optimizing the delays and initialization settings for AOS (Animate On Scroll) animations on the homepage. The adjustments aim to create a more cohesive and synchronized animation flow throughout different sections of the page.

### Key Changes:
1. **AOS Delay Optimization**: Adjusted the delay settings for AOS animations across various sections to ensure a smoother and more harmonious animation sequence.
2. **AOS Initialization Settings**: Updated the AOS initialization script to include an offset adjustment, ensuring elements animate as desired based on their viewport position.

## Changes Overview

1. **File: `resources/views/index.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Adjusted the AOS delay attributes for multiple elements to create a better flow of animations.
- **Description:**
  - **Delay Optimization:** Fine-tuned various AOS animation delays for headings, paragraphs, images, and sections to maintain consistent and visually appealing transitions.
  - **Example Adjustments:**
    - Hero section paragraph delay changed from 400ms to 250ms.
    - Button animation delay in hero section changed from 600ms to 300ms.
    - Image animations delay changed from a stretched delay pattern to a more consistent and quicker display (e.g., from 1000ms to 400ms, etc.).
    - Testimonials, pricing, and blog sections' delays adjusted to a uniform 250ms for consistency.
    - Reduced excessive delays for elements to ensure smoother sequential animations.
- **Impact:**
  - **Visual Consistency:** Creates a more harmonious and engaging animation flow, reducing abrupt or disjointed transitions.
  - **User Experience:** Enhances user engagement by making interactions more visually appealing and fluid.

2. **File: `resources/views/layouts/homepage.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Added `offset: 0` to the AOS initialization script.
- **Description:**
  - **Initialization Update:** Adjusts the AOS initialization to include an offset of 0, ensuring elements animate in sync with the intended scroll position.
  - **Script Update:**
    ```javascript
    <script>
      AOS.init({
          once: true,
          duration: 600,
          offset: 0
        });
    </script>
    ```
- **Impact:**
  - **Animation Precision:** Ensures animations trigger exactly when elements are in the viewport, enhancing the overall timing and visual narrative of the animations.
  - **User Experience:** Provides a more predictable and engaging animation experience for users scrolling through the homepage.

These adjustments collectively optimize the visual storytelling of the website by ensuring animations are well-timed and consistent, enhancing the overall user experience with a polished, professional interface.

---

# #37 User Interface Enhancements and Error Page Refactoring

## Introduction
This pull request focuses on enhancing the user interface, particularly through the addition of animation and refined styles, and refactoring error pages to improve design consistency. Key areas of changes include new layouts for error pages, improved homepage sections with animations, and adding new routes for testing error pages.

### Key Changes:
1. **Error Page Refactoring**: Introduction of a new layout for error pages to ensure consistency and reusability.
2. **Homepage Enhancements**: Improved visual appearance and responsiveness with animations and refined designs.
3. **Testing Routes**: Added new routes to facilitate testing of error pages during development.

## Changes Overview

1. **File: `resources/views/layouts/errors.blade.php`**
- **Status:** Newly Added
- **Changes:** 
  - Created a centralized layout for error pages.
- **Description:**
  - Provides a consistent structure and styling for different error types.
  - Includes favicon links, CSS, and JS references for a unified look across error pages.
- **Impact:** Ensures consistency and reduces redundancy in error page designs.

2. **File: `resources/views/components/footer-homepage.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Added fade-up animation to the footer component.
- **Description:**
  - **Enhancement**: Adds visual appeal and engagement with AOS (Animate on Scroll) library.
- **Impact:** Improves user experience with subtle animations.

3. **File: `resources/views/components/menu-homepage.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Added AOS animations.
  - Simplified and cleaned up the markup.
- **Description:**
  - **Enhancement**: Adds fade-down and delay animations for a visually engaging menu.
- **Impact:** Provides a more dynamic and modern user interface.

4. **File: `resources/views/errors/404.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Refactored to extend from the new error layout.
  - Organized styles and scripts to align with the new layout.
- **Description:**
  - **Consolidation**: Utilizes common layout to maintain consistency.
- **Impact:** Simplifies maintenance and ensures a coherent look across error pages.

5. **File: `resources/views/errors/419.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Refactored to extend from the new error layout.
  - Organized styles and scripts to align with the new layout.
- **Description:**
  - **Consolidation**: Utilizes common layout to maintain consistency.
- **Impact:** Simplifies maintenance and ensures a coherent look across error pages.

6. **File: `resources/views/errors/500.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Refactored to extend from the new error layout.
  - Organized styles and scripts to align with the new layout.
- **Description:**
  - **Consolidation**: Utilizes common layout to maintain consistency.
- **Impact:** Simplifies maintenance and ensures a coherent look across error pages.

7. **File: `resources/views/errors/503.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Refactored to extend from the new error layout.
  - Organized styles and scripts to align with the new layout.
- **Description:**
  - **Consolidation**: Utilizes common layout to maintain consistency.
- **Impact:** Simplifies maintenance and ensures a coherent look across error pages.

8. **File: `resources/views/index.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Applied animations and refined layout elements.
  - Improved section styling and responsiveness.
  - Incorporated dynamic AOS library for animations.
- **Description:**
  - **Enhancements**: Adds various animations for different sections (e.g., hero, process, pricing).
  - **Responsive Design**: Improvements ensure better display on multiple devices.
- **Impact:** Enhances user engagement with smoother transitions and a visually appealing layout.

9. **File: `resources/views/layouts/homepage.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Added AOS animations for different sections.
  - Cleaned up and organized the markup.
- **Description:**
  - **Enhancement**: Adds smooth scrolling and animation features.
  - **Organization**: Improved code readability and maintainability.
- **Impact:** Provides users with a more interactive and engaging homepage experience.

10. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** 
  - Added new routes for testing different error pages (404, 419, 500, 503).
- **Description:**
  - **Testing**: Facilitates easy testing and previewing of error pages during development.
- **Impact:** Ensures that error pages are working as intended and allows developers to test changes efficiently.

These changes collectively enhance user experience through visual improvements and consistency, while also streamlining error handling with a unified layout. The introduction of animations across various sections adds a modern touch, making the platform more engaging and user-friendly.

---

# #36 Age Verification Middleware and Registration Form Enhancements

## Introduction
This pull request introduces an age verification middleware to ensure users meet the minimum age requirement and enhances the registration form to improve user experience and validation accuracy. It includes the addition of new middleware for checking user age, updates to validation logic during user registration, and modifications to improve the registration form's responsiveness and functionality.

### Key Changes:
1. **Middleware Addition**: New middleware for age verification (`CheckUserAge`) to ensure users are at least 18 years old.
2. **Enhancements in User Registration**: Strengthened validation rules and improved registration form layout and functionality.
3. **Configuration and Localization Updates**: Updated configuration and language files to support age verification messaging.

## Changes Overview

1. **File: `app/Http/Middleware/CheckUserAge.php`**
- **Status:** Newly Added
- **Changes:** 
  - Implemented middleware to check if the authenticated user's age is above 18.
- **Description:**
  - **Functionality:** Middleware checks the user's birthdate and calculates the age. If under 18, the user is logged out and redirected to the login page with an error message.
- **Impact:** Ensures that only users above the specified age can access certain routes, enhancing compliance and user safety.

2. **File: `app/Actions/Fortify/CreateNewUser.php`**
- **Status:** Modified
- **Changes:** 
  - Added validation for the 'birthday' field for creators.
  - Removed redundant comment lines.
- **Description:**
  - **Validation:** Ensures 'birthday' is required for users registering as creators.
  - **Streamlined Logic:** Simplified conditional checks for CPF and CNPJ validations.
- **Impact:** Enhances user data validation during registration, preventing incomplete or erroneous data submissions.

3. **File: `app/Http/Kernel.php`**
- **Status:** Modified
- **Changes:** 
  - Registered the new `CheckUserAge` middleware.
- **Description:**
  - Middleware is added to the route middleware array to be used in protected routes.
- **Impact:** Age verification is enforced across routes where this middleware is applied.

4. **File: `config/socialstream.php`**
- **Status:** Modified
- **Changes:** 
  - Enabled `linkedin` and `twitterOAuth2` providers.
- **Description:**
  - **Providers:** Enabled LinkedIn and Twitter OAuth2 for social login capabilities.
- **Impact:** Expands social login options for users, potentially increasing registration and login convenience.

5. **File: `resources/lang/en/auth.php`**
- **Status:** Modified
- **Changes:** 
  - Added an age-related error message.
- **Description:**
  - **Message Content:** Provides feedback to users who fail the age verification process.
- **Impact:** Clearer communication with users regarding age-related access restrictions.

6. **File: `resources/lang/pt_br/auth.php`**
- **Status:** Modified
- **Changes:** 
  - Added an age-related error message in Brazilian Portuguese.
- **Description:**
  - **Message Content:** Provides feedback to Portuguese-speaking users who fail the age verification process.
- **Impact:** Ensures consistent error messaging for Brazilian Portuguese users.

7. **File: `resources/views/auth/register.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Enhanced form layout and added necessary fields for registration.
- **Description:**
  - **Form Layout:** Improved input field placements, added birthdate for creators, and refined conditional display logic.
  - **Scripts:** Provided JavaScript functions for dynamic form adjustments and input masking based on user selections.
- **Impact:** Improved user experience during registration with a more intuitive and responsive form layout.

8. **File: `routes/web.php`**
- **Status:** Modified
- **Changes:** 
  - Integrated `CheckUserAge` middleware into relevant route groups.
- **Description:**
  - **Route Protection:** Applied age verification to appropriate protected routes.
- **Impact:** Enforces age restrictions uniformly across protected user areas.

These changes collectively ensure enhanced security, improved user experience, and compliance with age-related access restrictions. The modifications to the registration form and middleware integrations aim to provide a seamless, user-friendly interface while maintaining stringent validation and security measures.

---

# #32 New Validation Rules and User Creation Enhancements

## Introduction
This pull request introduces new validation rules and enhances the user creation process. The primary aim is to integrate ASAAS and ContaAzul API validations while ensuring robust error handling during user registration. Key changes involve newly added files, modifications to existing validation rules, and updates to the user creation logic.

### Key Changes:
1. **New Validation Rules**: Introduction of `ASAASRule`, `CONTAAZUlRule`, and the renaming of `CPFRule` to `CPFCNPJRule`.
2. **Enhanced User Creation**: Adjusted API logic to handle responses from ASAAS and ContaAzul services and modified user creation flows accordingly.
3. **Configuration Updates**: Addition of new API tokens and endpoints in the configuration file.

## Changes Overview

1. **File: `app/Rules/ASAASRule.php`**
- **Status:** Newly Added
- **Changes:** Introduced `ASAASRule` class implementing `ValidationRule`.
- **Description:**
  - Added data handling and validation logic. 
  - The `validate` method processes API response errors and communicates them.
- **Impact:** Ensures proper validation of user data against the ASAAS API, improving data integrity.

2. **File: `app/Rules/CONTAAZUlRule.php`**
- **Status:** Newly Added
- **Changes:** Introduced `CONTAAZUlRule` class implementing `ValidationRule`.
- **Description:**
  - Added validation logic for handling errors from the ContaAzul API.
- **Impact:** Validates user information against ContaAzul's requirements, fostering seamless integration.

3. **File: `app/Actions/Fortify/CreateNewUser.php`**
- **Status:** Modified
- **Changes:** 
  - Integrated new validation rules.
  - Refined API call logic for ASAAS and ContaAzul during user creation.
  - Comprehensive error handling for API responses.
  - Added methods `ASAAS_apiCall` and `contaazul_apiCall` to encapsulate API interaction logic.
- **Description:**
  - **Validation**: Incorporated `ASAASRule` and `CONTAAZUlRule` for stricter validation.
  - **API Calls**: Established helper methods for communicating with ASAAS and ContaAzul.
  - **Error Handling**: Added robust error capturing and validation replay mechanisms.
- **Impact:** Enhances the robustness of user creation by integrating external API validations, ensuring smoother user onboarding.

4. **File: `composer.json`**
- **Status:** Modified
- **Changes:** 
  - Relaxed the version constraint for `spatie/laravel-backup`.
- **Description:**
  - Changed version constraint from `"^8.3"` to `"*"` to support a broader range of package versions.
- **Impact:** Increases compatibility with other package versions, potentially avoiding dependency conflicts.

5. **File: `config/app.php`**
- **Status:** Modified
- **Changes:** 
  - Added new environment variables for ASAAS and ContaAzul API tokens and endpoints.
- **Description:**
  - **New Configurations**: Introduced environment variables for ASAAS and ContaAzul APIs.
  - **Consolidated Tokens**: Added tokens to facilitate secure API communications.
- **Impact:** Ensures configurations are centralized and manageable through environment variables, promoting secure and scalable API integration.

6. **File: `app/Rules/CPFCNPJRule.php`**
- **Status:** Renamed (previously `CPFRule.php`)
- **Changes:** 
  - Renamed the rule from `CPFRule` to `CPFCNPJRule`.
  - Adjusted validation logic to accommodate both CPF and CNPJ validations.
- **Description:**
  - **Renaming**: Reflects the broader scope of CPF and CNPJ validations.
  - **Logic Update**: Improved validation handling for both identification types.
- **Impact:** Enhances clarity and functionality, making the rule more versatile and self-explanatory.

7. **File: `app/Rules/CNPJRule.php`**
- **Status:** Deleted
- **Changes:** 
  - Removed the `CNPJRule` class.
- **Description:**
  - **Deletion**: The functionality is now consolidated under the `CPFCNPJRule`.
- **Impact:** Simplifies the codebase by reducing rule redundancy and centralizing validation logic.

These updates collectively aim to improve the robustness of user registration, ensure accurate data validation through external APIs, and maintain a clean and manageable codebase.

---

# #31 User Interface Enhancements for the Registration Page

## Introduction
This pull request enhances the `register.blade.php` file, focusing on improving the visual layout and responsiveness of the registration page. The changes aim to provide a more user-friendly experience across various screen sizes and ensure aesthetic consistency.

### Key Changes:
1. **Layout Adjustments**: Updated the height and positioning properties to improve the layout on different devices.
2. **Styling Improvements**: Fine-tuned CSS classes to enhance the visual appearance and interaction effects.
3. **Responsive Design**: Enhanced responsiveness for better display on multiple screen sizes.

## Changes Overview

1. **File: `resources/views/register.blade.php`**
- **Status:** Modified
- **Changes:** 
  - Modified the height and padding properties for the main container.
  - Adjusted flexbox properties to ensure better alignment and spacing across different devices.
  - Added max-width properties to key elements to ensure they fit well within different screen sizes.
  - Modified SVG container from absolute to fixed positioning and adjusted its height.

- **Description:**
  - **Container Height Adjustments:** Changed the height from a formula-based approach (`calc(100vh-140px)`) to fixed height values (`500px` and `700px`) ensuring predictable layout across devices.
  - **Flexbox Adjustments:** Updated `flex` properties such as `items-center`, `gap`, and `flex-wrap` to improve alignment and spacing.
  - **Max-Width Properties:** Added `max-w-[85%]`, `sm:max-w-[45%]` to elements, so they behave more responsively and maintain visual balance.
  - **Image and Text Styling:** Ensured consistent sizing and alignment for images (`w-10 h-10 md:w-[60px]`) and text blocks (`max-w-[300px]`) to enhance readability.
  - **SVG Styling:** Changed the positioning of the SVG container from `absolute` to `fixed` and adjusted its height for better visual consistency.

- **Impact:**
  - **Enhanced User Experience:** Users on different devices (mobile, tablet, desktop) will have a more consistent and visually pleasing experience.
  - **Improved Readability:** Text and images are better aligned, making the content more digestible and user-friendly.
  - **Responsiveness:** The page layout adjusts more gracefully to various screen sizes, ensuring usability across a wide range of devices.
  - **Aesthetic Improvements:** Hover effects and visual interactions are maintained, providing a dynamic and engaging interface.

These adjustments focus on refining the user interface, ensuring a smoother and more consistent experience for users registering on the platform.

---

# #30 Adjustment to the ContaAzul Access Token Refresh Command

## Introduction
This pull request modifies the `ContaAzulGetAccessToken.php` file, particularly focusing on how the results of the access token refresh process are handled. The main objective is to comment out email notifications and prioritize logging for better tracking and debugging.

### Key Changes:
1. **Command Process Modification**: Email notifications related to access token refreshes are commented out.
2. **Logging Priority**: Enhanced logging to ensure that the process results are properly logged and monitored without unnecessary email notifications.

## Changes Overview

1. **File: `app/Console/Commands/ContaAzulGetAccessToken.php`**
- **Status:** Modified
- **Changes:** 
  - Commented out code lines related to email notifications on access token refresh.
  - Maintained existing logging functionality to capture the results of the access token refresh process.
- **Description:**
  - **Commented Out:** The email content setup and `Mail::raw` function calls which send email notifications to `sascha@creatify.com.br`.
  - **Retained:** The logging functionality using `\Log::info` to document the result of the token refresh operation.
  - Adjusted code comments to document the changes for future reference.
- **Impact:**
  - **Reduced Email Notifications:** By commenting out the email functionality, the system will not send emails after each access token refresh, which can reduce unnecessary email traffic.
  - **Enhanced Debugging:** Logs will still capture the essential results of the process, aiding in system monitoring and debugging.
  - **Code Maintenance:** The changes make future adaptations easier if email functionality needs to be reinstated or further modified.

These modifications streamline the token refresh process by focusing on essential logging and reducing dependency on email notifications, thereby potentially lowering operational overhead and clutter.

---

# #29 Modification to the Kernel Scheduler Configuration for Improved Maintenance

## Introduction
This pull request modifies the scheduling configuration in the `Kernel.php` file, specifically adjusting how a certain command is scheduled. The impact of these changes affects how the system operates in maintenance mode, improving overall system reliability and availability.

### Key Changes:
1. **Functional Adjustments**: Changes focus on the handling of the `contaazul:getaccesstoken` command, ensuring it runs in specific environments and even during maintenance periods.
2. **Utility Enhancement**: By enabling the command to execute during maintenance, the reliability of access token management is enhanced, crucial for operations that depend on these tokens.

## Changes Overview

1. **File: `app/Console/Kernel.php`**
- **Status:** Modified
- **Changes:** 
  - Adjusted the scheduling configuration for the `contaazul:getaccesstoken` command.
  - Removed execution in the `staging` environment.
  - Added the ability to run the command even in maintenance mode.
  - Rearranged method calls for clarity.
- **Description:**
  - **Removed:** The `everyThirtyMinutes()` call from the scheduling sequence to the end of the method chain.
  - **Added:** `evenInMaintenanceMode()` to ensure the command runs even if the application is in maintenance mode.
  - **Changed:** The command now exclusively runs in the `production` environment, removing it from the `staging` environment.
- **Impact:**
  - **Reliability:** The `contaazul:getaccesstoken` command will now execute even when the system is under maintenance, thus ensuring uninterrupted access token management.
  - **Environment Specificity:** By excluding the `staging` environment, the environment-specific behavior is refined, potentially reducing unnecessary load in non-production settings.
  - **Code Clarity:** The rearranged method calls improve readability and maintainability of the scheduling configuration.

This update targets better service continuity and refined environment-specific actions, enhancing the overall robustness and scalability of the scheduling system.

---

# #28 UI Enhancements, Scheduling Improvements, and Locale Updates for Conta Azul Integration

## Introduction
This pull request encompasses a broad range of updates focusing on user interface enhancements, scheduling improvements, and locale adjustments. The changes include the addition of new SVG assets, styling updates, modifications in scheduling configuration for token refresh, and localization improvements for the application. These updates aim to improve the user experience, ensure a more consistent and flexible schedule for automated tasks, and enhance language support in the user interface.

## Changes Overview

1. **File: `public/img/svgs/line-chart.svg`**
   - **Status:** Added
   - **Changes:** New SVG asset for a line chart icon.
   - **Description:**
     - Adds a new SVG file to be used in UI components.
   - **Impact:**
     - Provides a visually appealing and consistent icon for UI elements, enhancing the user experience.

2. **File: `public/img/svgs/rocket.svg`**
   - **Status:** Added
   - **Changes:** New SVG asset for a rocket icon.
   - **Description:**
     - Adds a new SVG file to be used in UI components.
   - **Impact:**
     - Enhances visual elements in the user interface, contributing to a more engaging user experience.

3. **File: `app/Console/Kernel.php`**
   - **Status:** Modified
   - **Changes:** Update to the scheduling configuration of the `contaazul:getaccesstoken` command.
   - **Description:**
     - Schedule the command to run `everyThirtyMinutes` and expand its environment scope to include both `staging` and `production`.
   - **Impact:**
     - Ensures more frequent token refreshes, reducing the risk of token expiration and improving the reliability of API integrations in both `staging` and `production` environments.

4. **File: `resources/css/app.css`**
   - **Status:** Modified
   - **Changes:** Add new CSS classes for button components.
   - **Description:**
     - Creates reusable button classes with TailwindCSS directives.
   - **Impact:**
     - Enhances the consistency and maintainability of button styles across the application.
     - Provides a uniform look and feel for buttons, improving the user experience.

5. **File: `resources/lang/pt_br.json`**
   - **Status:** Modified
   - **Changes:** Various updates to the Portuguese (Brazil) locale file.
   - **Description:**
     - Adjust translations for clarity and precision.
     - Replace instances like `"Registrar como criador"` with `"Juntar como criador"`.
   - **Impact:**
     - Improves the localization quality, providing a better user experience for Portuguese-speaking users.
     - Ensures accurate and user-friendly translations across the application.

6. **File: `resources/views/register.blade.php`**
   - **Status:** Modified
   - **Changes:** Major updates to the registration page layout and contents.
   - **Description:**
     - Refactor the registration page to include new SVG icons and update the layout for better responsiveness and visual appeal.
   - **Impact:**
     - Enhances the aesthetic and functional aspects of the registration page.
     - Provides a more engaging and user-friendly registration process, likely improving conversion rates.

These updates collectively enhance the system's visual appeal, usability, and operational reliability, ensuring a more streamlined and engaging user experience while maintaining robust backend functionality.

---

# #26 Database and Route Enhancements for User Profile Management and Token Refresh System

## Introduction
This pull request introduces several significant updates aimed at enhancing the database schema related to user profiles, refining various route settings and middleware configurations, and improving the scheduling of automatic token refreshes. The changes involve migrating user-related database fields, modifying URL paths for profile settings, ensuring these modifications improve security and user experience, and updating the frequency of the token refresh process. These changes collectively contribute to a more robust, user-friendly, and maintainable system.

## Changes Overview

1. **File: `database/migrations/2024_01_02_202400_add_contaazul_asaas_to_users_table.php`**
   - **Status:** Added
   - **Changes:** This migration file updates the `users` table.
   - **Description:**
     - Drops the existing `asaas_id` and `contaazul_id` columns.
     - Adds new nullable columns: `contaazul_cusId`, `contaazul_supId`, and `asaas_cusId`.
   - **Impact:**
     - Updates the database schema to better reflect the current requirements for storing user-related IDs for Conta Azul and Asaas integrations.
     - Ensures more consistency and clarity in the database structure, facilitating future developments and maintenance.

2. **File: `app/Http/Controllers/UserProfileController.php`**
   - **Status:** Modified
   - **Changes:** Update to the redirect URL in the `redirect` method.
   - **Description:**
     - The redirect URL is changed from `/usuario/configuracoes` to `/perfil/configuracoes`.
   - **Impact:**
     - Ensures the routing follows a more intuitive and user-friendly path structure.
     - Improves localization and consistency with other parts of the application.

3. **File: `app/Http/Middleware/VerifyCsrfToken.php`**
   - **Status:** Modified
   - **Changes:** Update to the CSRF token exception URL.
   - **Description:**
     - The exception for CSRF verification is updated from `/usuario/setcard/video-upload` to `/perfil/setcard/video-upload`.
   - **Impact:**
     - Ensures consistent and accurate route definitions for CSRF exceptions, thereby improving application security and reliability.

4. **File: `app/Models/User.php`**
   - **Status:** Modified
   - **Changes:** Addition of new attributes to the User model.
   - **Description:**
     - New fillable attributes added: `contaazul_cusId`, `contaazul_supId`, and `asaas_cusId`.
   - **Impact:**
     - Aligns the User model with the updated database schema, facilitating seamless data management.
     - Supports the new integration requirements for Conta Azul and Asaas.

5. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Update to the route definition for user profile settings.
   - **Description:**
     - The route path is changed from `/usuario/configuracoes` to `/perfil/configuracoes`.
   - **Impact:**
     - Simplifies the URL structure for user profile settings, providing a clearer and more intuitive navigation experience.
     - Ensures consistency across all related routes and improves maintainability of route definitions.

6. **File: `app/Console/Commands/ContaAzulGetAccessToken.php`**
   - **Status:** Modified
   - **Changes:** Enhanced error logging in the `handle` method.
   - **Description:** 
     - The error log now includes more context: `ClientID`, `ClientSecret`, and `RefreshToken`.
   - **Impact:**
     - Facilitates better troubleshooting and debugging by providing richer context in error logs.
     - Enhances maintainability and operational efficiency by making it easier to identify and resolve issues related to token retrieval.

7. **File: `app/Console/Kernel.php`**
   - **Status:** Modified
   - **Changes:** Update to the scheduling frequency of the `contaazul:getaccesstoken` command.
   - **Description:**
     - The command is now scheduled to run `everyThirtyMinutes` instead of every 45 minutes.
     - Removed the `onOneServer` directive to simplify scheduling.
   - **Impact:**
     - Ensures more frequent token refreshes, reducing the risk of token expiration and improving the reliability of API integrations.
     - Simplifies the scheduling configuration, maintaining the focus on execution frequency.

These updates collectively ensure a more resilient, user-friendly, and maintainable system, with improved database and route structures and a robust mechanism for automated token management.

---

# #25 Database and Route Enhancements for User Profile Management and Token Refresh System

## Introduction
This pull request introduces several significant updates aimed at enhancing the database schema related to user profiles, as well as refining various route settings and middleware configurations. The changes involve migrating user-related database fields, modifying URL paths for profile settings, and ensuring these modifications improve security, maintainability, and user experience. Additionally, the previous enhancement for automatic token refreshing has also been updated.

## Changes Overview

1. **File: `database/migrations/2024_01_02_202400_add_contaazul_asaas_to_users_table.php`**
   - **Status:** Added
   - **Changes:** This migration file updates the `users` table.
   - **Description:**
     - Drops the existing `asaas_id` and `contaazul_id` columns.
     - Adds new nullable columns: `contaazul_cusId`, `contaazul_supId`, and `asaas_cusId`.
   - **Impact:**
     - Updates the database schema to better reflect the current requirements for storing user-related IDs for Conta Azul and Asaas integrations.
     - Ensures more consistency and clarity in the database structure, facilitating future developments and maintenance.

2. **File: `app/Http/Controllers/UserProfileController.php`**
   - **Status:** Modified
   - **Changes:** Update to the redirect URL in the `redirect` method.
   - **Description:**
     - The redirect URL is changed from `/usuario/configuracoes` to `/perfil/configuracoes`.
   - **Impact:**
     - Ensures the routing follows a more intuitive and user-friendly path structure.
     - Improves localization and consistency with other parts of the application.

3. **File: `app/Http/Middleware/VerifyCsrfToken.php`**
   - **Status:** Modified
   - **Changes:** Update to the CSRF token exception URL.
   - **Description:**
     - The exception for CSRF verification is updated from `/usuario/setcard/video-upload` to `/perfil/setcard/video-upload`.
   - **Impact:**
     - Ensures consistent and accurate route definitions for CSRF exceptions, thereby improving application security and reliability.

4. **File: `app/Models/User.php`**
   - **Status:** Modified
   - **Changes:** Addition of new attributes to the User model.
   - **Description:**
     - New fillable attributes added: `contaazul_cusId`, `contaazul_supId`, and `asaas_cusId`.
   - **Impact:**
     - Aligns the User model with the updated database schema, facilitating seamless data management.
     - Supports the new integration requirements for Conta Azul and Asaas.

5. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Update to the route definition for user profile settings.
   - **Description:**
     - The route path is changed from `/usuario/configuracoes` to `/perfil/configuracoes`.
   - **Impact:**
     - Simplifies the URL structure for user profile settings, providing a clearer and more intuitive navigation experience.
     - Ensures consistency across all related routes and improves maintainability of route definitions.

6. **File: `app/Console/Commands/ContaAzulGetAccessToken.php`**
   - **Status:** Modified
   - **Changes:** Enhanced error logging in the `handle` method.
   - **Description:** 
     - The error log now includes more context: `ClientID`, `ClientSecret`, and `RefreshToken`.
   - **Impact:**
     - Facilitates better troubleshooting and debugging by providing richer context in error logs.
     - Enhances maintainability and operational efficiency by making it easier to identify and resolve issues related to token retrieval.

Overall, these updates collectively aim to refine the database schema, enhance the routing system, and improve the user management functionalities, while ensuring a more reliable and automated token refresh mechanism for integration with third-party services.

---

# #24 Automatic Token Refresh System Enhancement for Conta Azul Integration

## Introduction
This pull request enhances the existing automated system for refreshing access tokens for the Conta Azul API. The key changes include improved error logging that provides more detailed information for troubleshooting purposes. These improvements further enhance the reliability and maintainability of the system by offering clearer insights into issues related to token retrieval.

## Changes Overview

1. **File: `app/Console/Commands/ContaAzulGetAccessToken.php`**
   - **Status:** Modified
   - **Changes:**
     - Enhanced the error logging to include additional context such as `ClientID`, `ClientSecret`, and `RefreshToken` when logging a token retrieval error.
   - **Description:** 
     - The modification is within the `handle` method where it logs an error if the token retrieval process fails.
     - This additional information in the error logs helps in diagnosing issues related to the token retrieval process more effectively.
   - **Impact:**
     - Provides more granular and actionable information in the logs, aiding faster resolution of issues.
     - Enhances the system's maintainability by giving developers and operators more insights into the state of the environment during an error, thus improving the debugging process.

By incorporating these changes, the system's robustness and maintainability are further strengthened, ensuring smoother and more reliable integration with the Conta Azul API.

---

# #23 Automatic Token Refresh System for Conta Azul Integration

## Introduction
This pull request introduces a new automated system to refresh access tokens for the Conta Azul API. The main component of this update is a new console command designed to seamlessly acquire new access tokens and update the system environment variables accordingly. Additionally, the scheduling of this command ensures consistent and periodic execution. These changes significantly improve the robustness and reliability of the integration with Conta Azul by automating token management, minimizing the risk of disruptions caused by token expiration, and enhancing the overall user experience by reducing the need for manual intervention.

## Changes Overview
1. **File: `app/Console/Commands/ContaAzulGetAccessToken.php`**
   - **Status:** Added
   - **Changes:** A new console command class `ContaAzulGetAccessToken` has been introduced.
   - **Description:** 
     - Provides functionality to refresh Conta Azul API tokens.
     - The `handle` method retrieves client credentials and the current refresh token, makes a cURL request to the Conta Azul token endpoint, and updates environment variables with the new tokens.
     - Logs errors and successful token refresh operations.
     - Sends an email notification with the new tokens to a specified recipient.
   - **Impact:** 
     - Automates the process of refreshing Conta Azul tokens, reducing manual overhead and minimizing the risk of service disruptions due to expired tokens.
     - Enhances security by ensuring tokens are always up-to-date.
     - Improves maintainability and operational efficiency by clear logging and notification mechanisms.

2. **File: `app/Console/Kernel.php`**
   - **Status:** Modified
   - **Changes:** 
     - Added a new scheduled task to execute the `ContaAzulGetAccessToken` command.
     - The task runs every 45 minutes and is restricted to the production environment, ensuring it does not interfere with development or testing instances.
   - **Description:** 
     - Ensures periodic execution of the token refresh command to maintain valid API access tokens.
     - Specifies the task should only run on one server in a multi-server setup to avoid redundant operations.
   - **Impact:**
     - Guarantees the Conta Azul tokens are refreshed frequently, maintaining uninterrupted access to the API.
     - Reduces the potential for token-related errors in the production environment.
     - Ensures the task is efficiently managed in production, preventing duplicate executions.

These updates collectively ensure a more resilient and self-sustaining integration with the Conta Azul API, enhancing both the backend system's reliability and the overall user experience.

---

# #22 Enhancements in User Registration, CPF/CNPJ Validation, and Localization

## Introduction
This pull request introduces a series of improvements and updates across different parts of the application. The main areas of change include the enhancement of the user registration process, modifications to CPF/CNPJ validation rules, UI adjustments in validation error displays, localization improvements, and refinement of registration views.

The purpose of these changes is to enhance the application's functionality, improve API response handling, provide better error messages, and update language files for a more cohesive user experience. These enhancements contribute to improved reliability, security, and user interaction within the application.

## Changes Overview
1. **File: `app/Actions/Fortify/CreateNewUser.php`**
   - **Status:** Modified
   - **Changes:** Extensive modification including reworking the validation rules, adding detailed error messages, fixing API call logic for CPF/CNPJ validation, and handling API responses.
   - **Description:** 
     - Improved validation by separating input data validation and adding custom error messages for email-related checks.
     - Removed direct instantiation of `CPFRule` and `CNPJRule` and modified it to dynamically fetch CPF/CNPJ validation errors from API responses.
     - Cleaned and restructured API call to external CPF/CNPJ validation service, ensuring proper handling of different response cases, and included detailed logging of response data.
     - Reorganized the transaction block to include API response data into the user creation process dynamically.
   - **Impact:** 
     - Enhanced robustness and granularity in user data validation.
     - Improved maintainability and readability of the code.
     - More detailed error feedback to users helps in better troubleshooting.
     - Integration with external API for CPF/CNPJ validation improves data accuracy and reliability.

2. **File: `app/Rules/CPFRule.php`**
   - **Status:** Modified
   - **Changes:** Modified the constructor and validation logic to depend on external API error data instead of direct validation inside the rule.
   - **Description:** 
     - The `CPFRule` rule now accepts validation data through its constructor, enabling dynamic handling of validation errors received from the external API.
     - Disabled commented-out code related to previous direct calls within the rule.
   - **Impact:** 
     - Makes the rule more flexible and responsive to external validation.
     - Streamlines the approach to API integration, ensuring separation of concerns.
   
3. **File: `resources/lang/pt_br.json`**
   - **Status:** Modified
   - **Changes:** Minor additions and cleanup of the JSON structure, including correcting whitespace and adding new localized strings.
   - **Description:** 
     - Added a few missing localized strings.
     - Cleaned up redundant and misplaced whitespace for better readability.
   - **Impact:** 
     - Provides a more complete and accurate localization setup.
     - Improves structure for maintenance and future updates.

4. **File: `resources/views/components/validation-errors.blade.php`**
   - **Status:** Modified
   - **Changes:** Minor changes to the SVG rendering within the validation error display component.
   - **Description:** 
     - Improved rendering of SVG icons for better readability and aesthetic coherence.
   - **Impact:** 
     - Enhances the visual display of validation errors, contributing to a better user experience.

5. **File: `resources/views/register.blade.php`**
   - **Status:** Modified
   - **Changes:** Extensive refactoring of the HTML structure, including reformatting meta tags, reworking the layout, and improving readability.
   - **Description:** 
     - Reformatted meta tags and link elements to follow a consistent style.
     - Updated layout structure to be more responsive and user-friendly.
     - Enhanced overall readability of the registration view template.
   - **Impact:** 
     - Improves the loading and rendering of the registration page.
     - Enhances user experience with a better-structured and visually appealing registration form.
   
These changes collectively enhance the overall functionality, security, and user experience of the application, while also improving the maintainability and readability of the codebase.

---

# #15 Addition of New Business Components and SVG Assets

## Introduction
This pull request introduces significant additions and updates to enhance the functionality of our business module. Two key Livewire components, `CreateProduct` and `OrderProcess`, are added to manage product creation and order processing, respectively. Additionally, new SVG assets are integrated to support visual elements across the app. These changes improve the application's user experience and overall functionality by enabling image uploads, product previews, and dynamic order processing capabilities.

## Changes Overview
1. **File: `app/Livewire/Business/CreateProduct.php`**
- **Status:** Added
- **Changes:** 59 lines of code were added.
- **Description:** This file introduces the `CreateProduct` component, which facilitates the upload and preview of product images.
   - The component includes methods for image validation (`updatedImages()`), image removal (`removeImage()`), and image uploads (`uploadTest()`).
   - Image validation rules restrict file types to images and file size to a maximum of 1MB.
   - The component supports temporary URL previews for uploaded images.
- **Impact:** This enhancement allows users to manage product images more effectively, adding visual feedback and ensuring file constraints are maintained for optimal performance.

2. **File: `app/Livewire/Business/OrderProcess.php`**
- **Status:** Added
- **Changes:** 161 lines of code were added.
- **Description:** This file implements the `OrderProcess` component, which handles various order-related functionalities.
   - Manages prices, selected durations, hooks, services, photos, and add-on creators.
   - Provides methods for updating selections, calculating subtotals and totals, applying coupons, and toggling the coupon field.
   - Compiles all necessary data for the order process dynamically, adjusting based on user input.
- **Impact:** Enhances the order processing workflow by providing an interactive and dynamic interface, leading to better engagement and flexibility for users when managing orders.

3. **File: `public/img/spinner.gif`**
- **Status:** Added
- **Changes:** No changes within the file; new asset added.
- **Description:** Adds a loading spinner GIF to the assets directory.
- **Impact:** This improves user experience by providing visual feedback during actions that require loading.

4. **File: `public/img/svgs/american-express.svg`**
- **Status:** Added
- **Changes:** 13 lines of code were added.
- **Description:** New SVG for American Express added to support visual representation in payment processing.
- **Impact:** Enhances the UI by providing a recognizable and professional visual element for American Express payments.

5. **File: `public/img/svgs/apple-pay.svg`**
- **Status:** Added
- **Changes:** 10 lines of code were added.
- **Description:** Adds an SVG for Apple Pay to support the visual presence in payment sections.
- **Impact:** Facilitates a better user experience by showing recognizable payment icons, increasing trust and usability.

6. **File: `public/img/svgs/arrow-right-left.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Implements a direction arrow SVG for the UI.
- **Impact:** Enhances navigational cues within the application, improving user flow and interaction.

7. **File: `public/img/svgs/chart-full.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** SVG that represents a full chart, used likely for analytics or price breakdowns.
- **Impact:** Enables better visual data representation, aiding users in grasping analytical data quickly.

8. **File: `public/img/svgs/chart-halfquarter.svg`**
- **Status:** Added
- **Changes:** 11 lines of code were added.
- **Description:** Adds a half-quarter chart SVG, likely for intermediate analytics.
- **Impact:** Provides intermediate visual data representation for users, enhancing analytic capabilities.

9. **File: `public/img/svgs/chart-quarter.svg`**
- **Status:** Added
- **Changes:** 4 lines of code were added.
- **Description:** Incorporates a quarter-chart SVG for data representation.
- **Impact:** Augments user understanding of smaller data segments, making analytics more granular.

10. **File: `public/img/svgs/check.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Check SVG added for indicating completed tasks or activities.
- **Impact:** Visual feedback elements like this improve user interface intuitive design and user satisfaction.

11. **File: `public/img/svgs/close.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Close button SVG added to signal closable actions.
- **Impact:** Enhances user control over UI elements, facilitating better navigation and user experience.

12. **File: `public/img/svgs/euro.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** SVG representing the Euro currency symbol added.
- **Impact:** Provides clear, recognizable symbols for financial elements, increasing clarity and professionalism.

13. **File: `public/img/svgs/film.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Adds a film-reel SVG, likely for media-related features or components.
- **Impact:** Improves the aesthetic and organization of media-related sections or functionalities, making the app visually engaging.

14. **File: `public/img/svgs/google-pay.svg`**
- **Status:** Added
- **Changes:** 9 lines of code were added.
- **Description:** SVG for Google Pay added to support its visual integration.
- **Impact:** Boosts UI quality by providing visual identifications for supported payment methods, thus building user trust.

15. **File: `public/img/svgs/hand-wavy.svg`**
- **Status:** Added
- **Changes:** 19 lines of code were added.
- **Description:** Adds a wavy hand icon, likely for illustrative or welcoming sections.
- **Impact:** This SVG adds a friendly and engaging element to the user interface, improving user interaction and experience.

16. **File: `public/img/svgs/image-placeholder-filled.svg`**
- **Status:** Added
- **Changes:** 12 lines of code were added.
- **Description:** Placeholder SVG for images, likely used when images are not yet uploaded.
- **Impact:** Helps maintain design consistency and improves user comprehension of functionalities not yet engaged.

17. **File: `public/img/svgs/image-placeholder.svg`**
- **Status:** Added
- **Changes:** 12 lines of code were added.
- **Description:** Similar to the above but possibly used in a different context or with a different style.
- **Impact:** Provides design alternatives for image placeholders, ensuring various UI needs are met.

18. **File: `public/img/svgs/mastercard.svg`**
- **Status:** Added
- **Changes:** 12 lines of code were added.
- **Description:** Mastercard SVG added to display during payment processes.
- **Impact:** Builds reliability and trust by showing compatible payment options to users.

19. **File: `public/img/svgs/minus.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Minus symbol SVG added, likely for decrement actions.
- **Impact:** Improves input and modification capabilities within UI elements that require numeric adjustments.

20. **File: `public/img/svgs/pencil.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Pencil icon SVG, likely for edit actions.
- **Impact:** Enhances user interaction by providing clear editable areas or tools for modification, increasing usability.

21. **File: `public/img/svgs/plus.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Plus symbol SVG for increment actions.
- **Impact:** Complements the minus symbol, enhances the ease of adding items or values.

22. **File: `public/img/svgs/scissors.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Adds a scissors icon, potentially for cut or trim actions.
- **Impact:** Improves the user’s understanding of actionable icons, making specific functionalities more intuitive.

23. **File: `public/img/svgs/sofort-uberweisung.svg`**
- **Status:** Added
- **Changes:** 11 lines of code were added.
- **Description:** SVG for Sofort Überweisung added, supporting visual identity in payment interfaces.
- **Impact:** Enhances UI with relevant visual elements for supported payment methods, increasing user confidence.

24. **File: `public/img/svgs/stripe.svg`**
- **Status:** Added
- **Changes:** 16 lines of code were added.
- **Description:** SVG representing the Stripe payment method.
- **Impact:** Supports payment process visual elements, fostering a professional look and increasing trust in the application’s payment handling.

25. **File: `public/img/svgs/truck.svg`**
- **Status:** Added
- **Changes:** 5 lines of code were added.
- **Description:** Truck icon SVG added, likely for logistics or delivery-related functionalities.
- **Impact:** Assists in user understanding of delivery or logistics sections, making UI components more meaningful.

26. **File: `public/img/svgs/turn-left.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Turn left arrow SVG added for navigational purposes.
- **Impact:** Enhances navigation cues within the application, improving directional interactions.

27. **File: `public/img/svgs/users.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Adds a users icon, likely for user management or group functionalities.
- **Impact:** Enhances user interface visuals for multi-user or team-based sections, improving navigation and usability in this context.

28. **File: `public/img/svgs/video-camera.svg`**
- **Status:** Added
- **Changes:** 3 lines of code were added.
- **Description:** Video camera icon SVG for media or recording purposes.
- **Impact:** Improves visual representation of video-related functionalities, making the app more user-friendly.

29. **File: `public/img/svgs/visa.svg`**
- **Status:** Added
- **Changes:** 7 lines of code were added.
- **Description:** Visa card SVG added for the payment section.
- **Impact:** Enhances security and reliability indicators for users by showcasing accepted payment methods.

30. **File: `app/Http/Controllers/OrderProcessController.php`**
- **Status:** Modified
- **Changes:** 92 lines of addition, 3 lines of deletion.
- **Description:** Updates include dummy product data for the select product view, and additional variables for process view.
  - Dummy products are passed to `select_product` view.
  - `process` method now includes structured data for video prices, hooks, and services.
- **Impact:** Enhances order process workflow by providing necessary data dynamically and improving the listing and selection of products. This boosts the overall functionality and user experience within these workflows.

---

# #14 Enhancements in HTML Minification, Database Schema Migration, Middleware Configuration, and UI Improvements

## Introduction
This pull request introduces several important changes that aim to improve the application in multiple aspects, including functionality, user experience, and performance. The main updates involve adding a new configuration for HTML minification, extending the database schema for users, and integrating a new middleware component. Additionally, there are numerous minor updates to the user interface which enhance the visual and functional user experience. These changes collectively improve the overall efficiency, maintainability, and responsiveness of the application.

## Changes Overview
1. **File: `config/htmlminify.php`**
   - **Status:** Added
   - **Changes:** A new configuration file for HTML minification was introduced. 
   - **Description:** This file allows setting the environment variable `HTML_MINIFY` to enable or disable HTML minification. It also allows specifying routes to be excluded from minification. 
   - **Impact:** This change provides a configurable option to improve HTML response size and loading times, enhancing the application's performance.

2. **File: `database/migrations/2023_12_31_171600_create_column_users.php`**
   - **Status:** Added
   - **Changes:** New migration file to add columns `asaas_id` and `contaazul_id` to the `users` table.
   - **Description:** The migration updates the database schema to include IDs related to external services (Asaas and ContaAzul) for users, supporting additional features and integrations.
   - **Impact:** Enhances the database schema, enabling future integrations with external financial services which could enrich user profiles.

3. **File: `app/Http/Kernel.php`**
   - **Status:** Modified
   - **Changes:** Inclusion of `LaravelMinifyHtml` middleware in the web middleware stack.
   - **Description:** This change integrates an HTML minification middleware to minify HTML output automatically.
   - **Impact:** Improves loading speed by reducing HTML response sizes, potentially enhancing page performance and reducing bandwidth usage.

4. **File: `composer.json`**
   - **Status:** Modified
   - **Changes:** Added a dependency for `laravel-html-minify` and removed numerous blade icon dependencies.
   - **Description:** Dependency management changes that optimize the package requirements by including HTML minification support and removing redundant blade icon packages.
   - **Impact:** Streamlines the application's dependencies, reducing potential bloat and conflicts, thereby enhancing overall maintainability.

5. **File: `resources/views/admin/blog/list.blade.php`**
   - **Status:** Modified
   - **Changes:** Adjustment to an SVG element’s class attributes.
   - **Description:** Minor UI improvement for icon alignment within the "New Blog Post" button.
   - **Impact:** Enhances visual consistency and aesthetics in the admin blog list view.

6. **File: `resources/views/components/menu-dashboard.blade.php`**
   - **Status:** Modified
   - **Changes:** Adjusted dropdown links and improved the conditional logic for menu items.
   - **Description:** Corrected the layout and conditional display of dropdown items in the dashboard menu.
   - **Impact:** Enhances user interface and user experience by fixing menu behaviors and ensuring proper link display based on user roles.

7. **File: `resources/views/components/menu-homepage.blade.php`**
   - **Status:** Modified
   - **Changes:** Updated inline JavaScript for the header component.
   - **Description:** Simplified the scroll event handler for dynamic header background transition.
   - **Impact:** Improves the maintainability and readability of the client-side code for header behavior.

8. **File: `resources/views/contact.blade.php`**
   - **Status:** Modified
   - **Changes:** Minor adjustments to the SVG icon element within Success alert.
   - **Description:** Improved the display of success messages by refining the icon usage in the contact view.
   - **Impact:** Slightly improves the visual presentation of success messages, enhancing user experience.

9. **File: `resources/views/faqs.blade.php`**
   - **Status:** Modified
   - **Changes:** Updated SVG icons in both business and creator FAQ sections.
   - **Description:** Modified SVG elements to use stroke-based icons for a consistent look.
   - **Impact:** Improves visual consistency and readability of FAQ sections, providing a better user experience.

---

# #12 Introducing Sitemap Generation, Role-Based Profiles, and Enhancements

## Introduction
This pull request brings several key updates to the `creatify-app` project, including the addition of a new Sitemap generation command, handling of environment configurations, role-based profile management, and other enhancements to the existing functionalities. These updates improve the application's SEO, user experience, and overall system functionality.

## Changes Overview
1. **File: `app/Console/Commands/GenerateSitemap.php`**
   - **Status:** Newly added
   - **Changes:** Added a new console command `GenerateSitemap` to create `sitemap.xml` using Spatie packages.
   - **Description:** This command generates a sitemap by crawling the site and excludes routes beginning with `/oauth`.
   - **Impact:** Enhances SEO by facilitating the discovery of website content by search engines.

2. **File: `config/sitemap.php`**
   - **Status:** Newly added
   - **Changes:** Added configuration for the Sitemap generator including Guzzle options and crawl profiles.
   - **Description:** Provides settings for the Sitemap generation process, including timeouts, redirects, and Javascript execution.
   - **Impact:** Customizes and optimizes the process of Sitemap generation.

3. **File: `.env.example`**
   - **Status:** Modified
   - **Changes:** Updated environment variables to include application-specific settings like `APP_NAME`, `APP_KEY`, and tokens for APIs.
   - **Description:** Specifies environment configurations, facilitating easy setup of development environments.
   - **Impact:** Improves manageability and configuration of application environment settings.

4. **File: `app/Actions/Fortify/CreateNewUser.php`**
   - **Status:** Modified
   - **Changes:** Cleaned up redundant code by removing unnecessary comments and return statements.
   - **Description:** Simplifies the new user creation process.
   - **Impact:** Enhances code readability and maintainability.

5. **File: `composer.json`**
   - **Status:** Modified
   - **Changes:** Added new Blade icon packages to enhance the icon library available for UI components.
   - **Description:** Introduces multiple icon libraries such as Github Octicons, Feather Icons, and others.
   - **Impact:** Offers a richer set of icons for improving the user interface design flexibility.

6. **File: `resources/lang/pt_br.json`**
   - **Status:** Modified
   - **Changes:** Removed redundant strings from the Portuguese locale file.
   - **Description:** Cleans up locale file by removing unnecessary messages.
   - **Impact:** Improves localization file maintainability.

7. **File: `resources/views/components/menu-dashboard.blade.php`**
   - **Status:** Modified
   - **Changes:** Adjusted the dashboard menu to conditionally display options based on user roles.
   - **Description:** Differentiates between links for creators and other roles, showing relevant options only.
   - **Impact:** Improves user navigation by providing role-specific menu options, enhancing the user experience.

8. **File: `resources/views/index.blade.php`**
   - **Status:** Modified
   - **Changes:** Fixed blog post URLs to include trailing slashes.
   - **Description:** Ensures URL correctness for blog post links.
   - **Impact:** Prevents broken links and improves content accessibility.

9. **File: `resources/views/legal/terms.blade.php`**
   - **Status:** Modified
   - **Changes:** Reformatted and updated terms of service content for better readability and consistency.
   - **Description:** Adjusts the formatting to make terms and conditions more user-friendly.
   - **Impact:** Enhances the clarity and readability of legal content, improving compliance communication.

10. **File: `resources/views/profile/contact.blade.php`**
    - **Status:** Modified
    - **Changes:** Added role-based conditions to customize the profile sections displayed.
    - **Description:** Shows different sections in the profile based on whether the user is a creator.
    - **Impact:** Provides a more relevant and personalized profile page for different user roles.

11. **File: `resources/views/profile/setcard.blade.php`**
    - **Status:** Modified
    - **Changes:** Role-specific adjustments to the navigation and displayed sections within the setcard profile.
    - **Description:** Tailors the profile details and options based on the user role.
    - **Impact:** Enhances user experience by providing role-specific interface elements.

12. **File: `resources/views/profile/settings.blade.php`**
    - **Status:** Modified
    - **Changes:** Conditioned the display of certain settings and options based on user roles.
    - **Description:** Adjusts the profile settings page to show relevant options depending on user type.
    - **Impact:** Improves the relevancy and usability of the settings page for different users.

13. **File: `resources/views/profile/update-profile-information-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Corrected misplaced conditional statements for displaying the birthday field.
    - **Description:** Ensures that the birthday field is conditionally displayed correctly.
    - **Impact:** Fixes UI issues and ensures accurate form rendering.

14. **File: `resources/views/vendor/mail/html/layout.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated the email layout to use the correct SVG logo link.
    - **Description:** Ensures email templates have the correct branding elements.
    - **Impact:** Improves the professional appearance and consistency of outgoing emails.

15. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added routes for user profile setcard and avatar uploads.
    - **Description:** Expands the routing to support profile management functionalities.
    - **Impact:** Enhances the system's capability to handle user profile updates.

These updates collectively enhance the application's functionality by enabling better SEO through sitemap generation, improving user navigation and experience with role-based modifications, and refining existing features for stability and usability. Users and administrators benefit from optimized processes and a more robust system configuration.

---

# #11 Adding Dashboard, Orders, and Blog Enhancements

## Introduction
This pull request introduces several new features and improvements to the `creatify-app` project. These changes include adding a new dashboard controller to serve different user roles, integrating a model for handling orders, modifying blog post requirements, and enhancing migrations. These updates improve how users interact with dashboards, manage orders, and handle blog posts, ultimately enhancing the overall user experience and functionality of the application.

## Changes Overview
1. **File: `app/Http/Controllers/DashboardController.php`**
   - **Status:** Newly added
   - **Changes:** Added a new `DashboardController` that handles different views based on user roles (creator, business, agency). 
   - **Description:** This controller determines which dashboard to display based on the user's role, fetching orders for business users.
   - **Impact:** Provides role-specific dashboard experiences, improving the user navigation and user-specific content availability.

2. **File: `app/Models/Order.php`**
   - **Status:** Newly added
   - **Changes:** Introduced a new model class `Order` with relationships to `User` and `Product`.
   - **Description:** Defines the structure and relationships of an Order, capable of linking to users and products, and supports fetching related images.
   - **Impact:** Enables order management functionalities, enhancing how orders are handled within the app.

3. **File: `database/migrations/2023_12_08_183605_change_columns_in_blog_posts_table.php`**
   - **Status:** Newly added
   - **Changes:** Migration to alter the `blog_posts` table, changing the data types for fields like `seo_description`, `title`, `seo_title`, and `description`.
   - **Description:** Updates the `blog_posts` table to support new text and long text fields.
   - **Impact:** Improves how blog content is stored and handled, allowing for more extensive descriptions and titles.

4. **File: `database/migrations/2023_12_09_015956_create_products_table.php`**
   - **Status:** Newly added
   - **Changes:** Migration to create the `products` table with fields like `user_id`, `title`, `description`, `pronounciation`, and `price`.
   - **Description:** Sets up a new table to manage products with appropriate fields and relationships.
   - **Impact:** Enables product management capabilities within the application.

5. **File: `database/migrations/2023_12_09_015957_create_products_images_table.php`**
   - **Status:** Newly added
   - **Changes:** Migration to create the `products_images` table linked to users and products.
   - **Description:** Establishes a table to store product images, maintaining relationships with respective users and products.
   - **Impact:** Enhances product image management and storage.

6. **File: `database/migrations/2023_12_09_021624_create_orders_table.php`**
   - **Status:** Newly added
   - **Changes:** Migration to create the `orders` table with fields like `user_id`, `product_id`, `seconds`, `hooks`, `cta`, `subtitle`, `music`, `pictures`, and `creators`.
   - **Description:** Defines the orders table structure, which includes essential details about each order and its relationships.
   - **Impact:** Supports storing and managing order information within the database efficiently.

7. **File: `public/img/background/authpages.png`**
   - **Status:** Newly added
   - **Changes:** Added a new PNG image for authentication backgrounds.
   - **Description:** Provides a graphical enhancement for authentication pages.
   - **Impact:** Enhances visual appeal and branding.

8. **File: `public/img/background/authpages.svg`**
   - **Status:** Newly added
   - **Changes:** Added a new SVG image for authentication backgrounds.
   - **Description:** Utilizes SVG for sharper graphics on authentication pages.
   - **Impact:** Improves the visual quality of authentication pages with scalable vector graphics.

9. **File: `app/Http/Controllers/BlogPostController.php`**
   - **Status:** Modified
   - **Changes:** Updated validation rules for `create_store` method to ensure unique `title` and `url` fields and increased the allowed image size to 2MB.
   - **Description:** Enhances validation and increases the maximum permissible image upload size.
   - **Impact:** Improves blog post creation robustness and flexibility.

10. **File: `app/Http/Controllers/BlogPostPublicController.php`**
    - **Status:** Modified
    - **Changes:** Adjusted logic for fetching random and latest blog posts, increasing the count of latest posts to 5, and ensuring random posts exclude the current post.
    - **Description:** Enhances the display logic for blog posts on the public-facing side.
    - **Impact:** Improves user engagement by displaying relevant and varied blog content.

These changes collectively improve the application by making dashboards user-role specific, refining order and product management, and enhancing blog post handling. Users benefit from a more tailored and efficient interface, while administrators and developers gain better tools for content and order management.

---

# #10 Adding Custom Validation Rules for CPF and CNPJ in User Registration

## Introduction
This pull request introduces significant functionality to the `creatify-app` project by adding custom validation rules for Brazilian CPF (Individual Taxpayer Registry) and CNPJ (National Registry of Legal Entities) numbers during the user registration process. Additionally, it enhances the user interface to support these new validation checks seamlessly. The changes ensure that users' tax identification numbers are verified against an external service, providing a robust mechanism to validate data integrity. These changes impact the application's validation logic, registration security, and overall user experience.

## Changes Overview
1. **File: `app/Rules/CNPJRule.php`**
   - **Status:** Newly added
   - **Changes:** Introduced a validation rule for CNPJ numbers using an external API to verify the authenticity of the given CNPJ.
   - **Description:** The `CNPJRule` class implements the `ValidationRule` interface, removing non-alphanumeric characters from the input and making an API request to validate the CNPJ. If the API response is unsuccessful, it provides the corresponding error message.
   - **Impact:** Adds a layer of verification during registration ensuring that the CNPJ numbers provided are accurate and legitimate.

2. **File: `app/Rules/CPFRule.php`**
   - **Status:** Newly added
   - **Changes:** Introduced a validation rule for CPF numbers using an external API to validate the provided CPF.
   - **Description:** The `CPFRule` class implements the `ValidationRule` interface, formatting and sending an API request to validate the CPF. If validation fails, it captures and displays the error.
   - **Impact:** Ensures the user-provided CPF numbers are verified against a reliable source, enhancing data accuracy.

3. **File: `app/Actions/Fortify/CreateNewUser.php`**
   - **Status:** Modified
   - **Changes:** Added validation logic to check the CPF and CNPJ using their respective new rules. Integrated API calls to pull detailed data about the CPF/CNPJ and store it in respective tables.
   - **Description:** Implements detailed validation for CPF and CNPJ, ensuring uniqueness, proper formatting, and compliance by querying the external API and persisting the verified data.
   - **Impact:** Improves the registration process by performing thorough checks on tax ID numbers, reducing fraudulent entries and enhancing authenticity.

4. **File: `app/Http/Controllers/ContactController.php`**
   - **Status:** Modified
   - **Changes:** Removed redundant code and commented lines related to fetching IP information.
   - **Description:** Cleaned up the code for a more streamlined controller execution path.
   - **Impact:** Improves code maintainability and readability.

5. **File: `config/app.php`**
   - **Status:** Modified
   - **Changes:** Added a configuration entry for the CPF/CNPJ API token.
   - **Description:** Facilitates the configuration of the API token used for CPF and CNPJ validation.
   - **Impact:** Provides a centralized and secure location for managing the API token used across the application.

6. **File: `resources/views/auth/register.blade.php`**
   - **Status:** Modified
   - **Changes:** Updated the registration form to include radio button selection for CPF and CNPJ and integrated JavaScript to show relevant input fields based on user selection.
   - **Description:** Enhances the registration UI, allowing users to enter either a CPF or CNPJ with appropriate validation feedback.
   - **Impact:** Improves user experience by presenting a cleaner and more intuitive registration form.

7. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Added `Http` and `Client` classes at the top of the file for potential usage.
   - **Description:** Minor adjustment to improve code readiness for potential HTTP requests.
   - **Impact:** Ensures necessary classes are available for use in routing and middleware where HTTP functionalities are required.

By integrating these changes, the application now provides a more robust and verified registration process, reducing errors and enhancing trustworthiness in user-submitted data. These updates also contribute to a cleaner codebase and improved user experience, particularly for users in Brazil who need to validate their CPF and CNPJ information.

---

# #9 Introducing New CRUD Functionalities and UI Enhancements

## Introduction
This pull request introduces several updates to the `creatify-app` project. The changes focus on adding new CRUD functionalities for handling blog posts and FAQ items, as well as implementing UI enhancements to improve the user experience. These changes have a significant impact on the application's functionality by enabling better content management and editing capabilities. The updates also enhance the architectural organization, especially by creating new routes and controllers. Below are the categorized changes and their implications.

## Changes Overview
1. **File: `app/Http/Controllers/OrderProcessController.php`**
   - **Status:** New file added
   - **Changes:** Added new controller `OrderProcessController` with methods (`select_product`, `create_product`, `process`, `edit_product`) to handle various order-related activities.
   - **Description:** This controller handles the views related to selecting, creating, editing, and processing products by returning the respective views.
   - **Impact:** This change enables better separation of concerns by specifically handling order-related business logic in one controller.

2. **File: `resources/views/admin/blog/edit.blade.php`**
   - **Status:** New file added
   - **Changes:** Created a new view for editing blog posts with form fields including title, image, author, URL, SEO title, SEO description, headline, and description.
   - **Description:** Provides a user interface for administrators to edit blog posts.
   - **Impact:** Improves the backend functionality allowing blog post content to be updated directly through the UI.

3. **File: `resources/views/admin/faq/edit.blade.php`**
   - **Status:** New file added
   - **Changes:** Created a new view for editing FAQ posts with form inputs for the question, answer, author, and target audience.
   - **Description:** Provides an interface for administrators to update FAQ content.
   - **Impact:** Enhances the ease of managing FAQ entries and keeps the FAQ section up-to-date.

4. **File: `resources/views/dashboard/business/create_product.blade.php`**
   - **Status:** New file added
   - **Changes:** Added a blade view for the "Create Product" page in the business dashboard.
   - **Description:** Sets up the structure for the product creation view.
   - **Impact:** Supports product management functionalities for business users.

5. **File: `resources/views/dashboard/business/edit_product.blade.php`**
   - **Status:** New file added
   - **Changes:** Adds a view for editing existing products within the business dashboard.
   - **Description:** Facilitates product-related modifications for business users.
   - **Impact:** Improves the capability to manage product info effectively.

6. **File: `resources/views/dashboard/business/process.blade.php`**
   - **Status:** New file added
   - **Changes:** Adds a blade view for processing orders.
   - **Description:** Utilized in streamlining the order processing workflow.
   - **Impact:** Enhances the skillset for business users to manage orders.

7. **File: `resources/views/dashboard/business/select_product.blade.php`**
   - **Status:** New file added
   - **Changes:** Added view for selecting products in the business dashboard.
   - **Description:** Aids users in product selection for orders.
   - **Impact:** Facilitates user interaction with product management features.

8. **File: `app/Http/Controllers/BlogPostController.php`**
   - **Status:** Modified
   - **Changes:** Added new methods `edit` and `edit_store` for editing blog posts; updated validation rules and file storage operations.
   - **Description:** Enables CRUD functionality for blog posts, particularly editing existing entries.
   - **Impact:** Increases flexibility and control over blog content management.

9. **File: `app/Http/Controllers/FAQController.php`**
   - **Status:** Modified
   - **Changes:** Added new methods `edit` and `edit_store` for updating FAQ entries.
   - **Description:** Supports CRUD operations for FAQs similar to the blog post functionality.
   - **Impact:** Enables better management of FAQ content.

10. **File: `package.json`**
    - **Status:** Modified
    - **Changes:** Added dependencies for `tinymce` and `tocbot` packages.
    - **Description:** Introduces new JavaScript libraries for enhanced text editing and table of contents generation.
    - **Impact:** Expands the application's capability in providing rich text editing and documentation features.

11. **File: `resources/css/app.css`**
    - **Status:** Modified
    - **Changes:** Imported `tocbot.css` for TOC styling.
    - **Description:** Sets up the necessary CSS for using the table of contents plugin.
    - **Impact:** Improves the user interface by enabling styled tables of contents.

12. **File: `resources/js/app.js`**
    - **Status:** Modified
    - **Changes:** Integrated `tocbot` initialization and customized headers for table of contents generation.
    - **Description:** Adds JavaScript functionality for better documentation and navigation through content sections.
    - **Impact:** Creates a more user-friendly interface by enabling TOC features.

13. **File: `resources/lang/pt_br.json`**
    - **Status:** Modified
    - **Changes:** Added translations for "Update FAQ post" and "Update Blog post".
    - **Description:** Improves localization support for new features.
    - **Impact:** Enhances user experience for Portuguese-speaking users.

14. **File: `resources/views/admin/blog/create.blade.php`**
    - **Status:** Modified
    - **Changes:** Added script inclusion for `tinymce` HTML editor.
    - **Description:** Enhances the blog post creation interface with rich text editing capabilities.
    - **Impact:** Improves the content creation experience for administrators.

15. **File: `resources/views/admin/blog/list.blade.php`**
    - **Status:** Modified
    - **Changes:** Enabled "Edit" functionality in the blog post list view.
    - **Description:** Simplifies navigation to the blog post editing interface.
    - **Impact:** Increases admin productivity in managing blog posts.

16. **File: `resources/views/admin/components/sidebar.blade.php`**
    - **Status:** Modified
    - **Changes:** Added the active state class for the FAQ sidebar link.
    - **Description:** Improves sidebar navigation by highlighting the active link.
    - **Impact:** Enhances UI feedback for better user orientation.

17. **File: `resources/views/admin/faq/create.blade.php`**
    - **Status:** Modified
    - **Changes:** Included `tinymce` script for text fields.
    - **Description:** Adds rich text editing while creating a FAQ post.
    - **Impact:** Improves content creation for FAQ entries.

18. **File: `resources/views/admin/faq/list.blade.php`**
    - **Status:** Modified
    - **Changes:** Enabled "Edit" functionality in the FAQ list view.
    - **Description:** Simplifies navigation to the FAQ post editing interface.
    - **Impact:** Makes FAQ management more efficient.

19. **File: `resources/views/blog-single.blade.php`**
    - **Status:** Modified
    - **Changes:** Updated formatting and TOC-related URL fixes.
    - **Description:** Optimized the format and enhanced content readability.
    - **Impact:** Provides a better reading experience on single blog pages.

20. **File: `resources/views/faqs.blade.php`**
    - **Status:** Modified
    - **Changes:** Enabled HTML rendering for FAQ answers.
    - **Description:** Supports rich text format in FAQ answers.
    - **Impact:** Enhances how FAQ information is displayed.

21. **File: `resources/views/layouts/admin.blade.php`**
    - **Status:** Modified
    - **Changes:** Added script to initialize `tinymce` in text areas.
    - **Description:** Supports rich text editing capabilities for admin layouts.
    - **Impact:** Extends text editing features across admin views.

22. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added routes for the new order process views and designated specific dashboard views for creator, business, and agency.
    - **Description:** Organizes the routing scheme to include clearly defined paths for new functionalities.
    - **Impact:** Improves navigational structure and accessibility in the application.

23. **File: `resources/views/dashboard/agency/dashboard.blade.php`**
    - **Status:** Renamed
    - **Changes:** Dashboard file renamed for agency users.
    - **Description:** Refactors the view structure for better organization.
    - **Impact:** Improves the modularity of the codebase.

24. **File: `resources/views/dashboard/business/dashboard.blade.php`**
    - **Status:** Renamed
    - **Changes:** Dashboard file renamed for business users.
    - **Description:** Refactors the view structure for better organization.
    - **Impact:** Enhances the maintainability of the codebase.

25. **File: `resources/views/dashboard/creator/dashboard.blade.php`**
    - **Status:** Renamed
    - **Changes:** Dashboard file renamed for creator users.
    - **Description:** Refactors the view structure for better organization.
    - **Impact:** Increases the clarity and modularity of the application.

These changes collectively enhance the application's content management capabilities, improve the user experience, especially in admin functionalities, and ensure a clearer code structure for future development.

---

# #8 Added and Modified Log Files and User Creation Logic Update

## Introduction

This pull request introduces several changes primarily focused on logging and user creation enhancements. It includes the addition and modification of different log files within the `npm-cache/_logs` directory, capturing various activities and internal state during NPM operations. Additionally, there is a significant update in the user creation logic within the application, aimed at improving the handling of user data, particularly around personal and business identification data (`cpf` and `cnpj`). These changes enhance the debugging capability and user data handling, ensuring better maintainability and data integrity within the application.

## Changes Overview

1. **File: `app/Actions/Fortify/CreateNewUser.php`**
   - **Status:** Modified
   - **Changes:** 5 additions and 3 deletions, changing the logic for creating new users, particularly dealing with `cpf` and `cnpj`.
   - **Description:** Added logic to handle `cpf` and `cnpj` more robustly, storing user identification data effectively.
   - **Impact:** Enhances user data integrity and expands functionality to manage personal and business identification effectively.

---

# #7 Add Redirect After Video Upload and Comment Out Unused Import in app.js

## Introduction
This pull request introduces two critical changes to the codebase. Firstly, it adds a redirectional flow to the video upload process, ensuring better user navigation by directing users to the 'profile.setcard' route upon a successful video upload. Secondly, it modifies the JavaScript application by commenting out an unused import statement, which can lead to cleaner and potentially quicker loading of the application's resources. These changes collectively aim to improve user experience and maintain code efficiency.

## Changes Overview

1. **File: `app/Livewire/ProfileVideoUpload.php`**
    - **Status:** Modified
    - **Changes:** Added a redirection after a successful video upload.
    - **Description:** The `updateVideoInformation` function now includes a redirection call using `return redirect()->route('profile.setcard');` after the success alert.
    - **Impact:**
      - **User Flow:** Users will now be automatically navigated to the 'profile.setcard' route upon successfully uploading their profile video. 
      - **User Experience:** This change improves the flow and usability of the video upload process by seamlessly moving users to the next logical part of the profile setup, hence reducing confusion and additional clicks.

2. **File: `resources/js/app.js`**
    - **Status:** Modified
    - **Changes:** Commented out an import statement.
    - **Description:** The line `import "./alpinejs";` has been commented out.
    - **Impact:**
      - **Code Efficiency:** By commenting out the unused import, the JavaScript bundle size might be slightly reduced, potentially improving load times.
      - **Maintains Clean Code:** This change helps in maintaining cleaner code by eliminating unused code imports, thereby making future maintenance easier.

---

# #6 Enhancement of "Contacts" Feature with Country and Timezone Information

## Introduction
This pull request focuses on enhancing the "Contacts" feature of the application by adding functionalities to track and store the country and timezone of contacts. This improvement aims to enrich the data captured from users, providing more geographical context which can be useful for analytics, personalized communication, and improving overall user experience. The changes involve additions to the database schema, modifications to the controller for data handling, updates to the front-end to fetch and display this new data, as well as relevant route and view updates.

## Changes Overview

1. **File: `database/migrations/2023_11_14_081910_add_country_timezone_to_contacts_table.php`**
   - **Status:** Added
   - **Changes:** Introduces a new migration script to add `country` and `timezone` columns to the `contacts` table.
   - **Description:** This migration script adds two new columns (`country` and `timezone`) to the `contacts` table to store additional information about the user's geographical location.
   - **Impact:** Enables more detailed records of contact information, which will be beneficial for future analytics and personalized user interactions.

2. **File: `resources/js/contact.js`**
   - **Status:** Added
   - **Changes:** JavaScript functionality to fetch country and timezone data from the server when the contact form page loads.
   - **Description:** This script fetches data about the user's IP, country, and timezone from an endpoint and populates hidden input fields in the contact form.
   - **Impact:** Automates the capture of supplementary user data without requiring user input, enhancing data completeness for backend processing.

3. **File: `app/Http/Controllers/ContactController.php`**
   - **Status:** Modified
   - **Changes:** Refactored to include IP information fetching and storage of the country and timezone data. Adds a new method `getIPinformation` to retrieve IP-related information.
   - **Description:** These changes allow the controller to handle and save extra fields (`country` and `timezone`). The new method `getIPinformation` uses an external API to fetch and process this data.
   - **Impact:** Improved handling of contact submissions by including additional contextual data, providing richer insights into user demographics.

4. **File: `app/Models/Contact.php`**
   - **Status:** Modified
   - **Changes:** Added `country` and `timezone` fields to the fillable attributes of the `Contact` model.
   - **Description:** This modification ensures that the model correctly processes the new data fields included in contact submissions.
   - **Impact:** Enables the application to save and manage new data attributes without issues, ensuring data integrity within the model.

5. **File: `composer.json`**
   - **Status:** Modified
   - **Changes:** Updated `guzzlehttp/guzzle` dependency version from `^7.2` to `^7.8`.
   - **Description:** This update ensures compatibility and includes potential bug fixes and improvements from the newer version of the Guzzle HTTP client.
   - **Impact:** Potentially improved performance and security in HTTP requests due to the updated library version.

6. **File: `resources/views/contact.blade.php`**
   - **Status:** Modified
   - **Changes:** Added hidden input fields for `ip`, `timezone`, and `country`.
   - **Description:** These new fields allow for automatic inclusion of additional user information in the contact form submission.
   - **Impact:** Enhances the backend's ability to store more detailed contact information with minimal user interaction.

7. **File: `resources/views/layouts/homepage.blade.php`**
   - **Status:** Modified
   - **Changes:** Included the newly added `contact.js` in the list of JavaScript files to be loaded on the homepage.
   - **Description:** Ensures that the script responsible for fetching and populating country and timezone data is correctly loaded and executed.
   - **Impact:** This is crucial for the proper functionality of the enhanced contact form on the homepage.

8. **File: `routes/web.php`**
   - **Status:** Modified
   - **Changes:** Added a new route to retrieve IP information.
   - **Description:** The new route `'/contato/information'` points to the `getIPinformation` method in the `ContactController`.
   - **Impact:** Facilitates the functionality of fetching additional user data, enabling the front-end to display contextual information about the user.

By incorporating these changes, the application will now be able to collect and utilize additional details about users accessing the contact form, which could lead to better user insights, improved personalization, and enhanced overall user experience.

---

# #5 New Avatar and Video Upload Functionalities with Extended User Profile Attributes

## Introduction
This pull request introduces several new features and improvements aimed at enhancing user experience and profile management within the application. The main areas of change include the addition of new avatar and video uploading functionalities, the introduction of custom validation rules, and the extension of user profile attributes to include gender. Additionally, various UI updates and backend logic adjustments have been made to support these new functionalities. These changes affect multiple parts of the system, including user controllers, Livewire components, validation rules, routes, and language resource files.

## Changes Overview
1. **File: `app/Livewire/AvatarUpload.php`**
   - **Status:** Added
   - **Changes:** Implementation of a Livewire component for handling avatar uploads, including functionalities for uploading and deleting profile photos.
   - **Description:** This new file includes methods to upload and delete profile photos, manage alerts, and update the navigation menu upon changes.
   - **Impact:** Enhances user profile customization by allowing users to easily manage their avatar photos, impacting user profile appearance and accessibility.

2. **File: `app/Livewire/ProfileVideoUpload.php`**
   - **Status:** Added
   - **Changes:** Implementation of a Livewire component for handling profile video uploads.
   - **Description:** This addition provides functionalities to upload profile videos and includes success alert mechanisms.
   - **Impact:** Allows users to upload profile videos, enriching user profiles with multimedia content and enhancing profile interactivity.

3. **File: `app/Rules/FileSize.php`**
   - **Status:** Added
   - **Changes:** Custom validation rule to check file size for avatars.
   - **Description:** This rule validates the file size against an environment variable `MAX_AVATAR_SIZE`, ensuring uploaded avatar files meet specified size constraints.
   - **Impact:** Improves user experience by ensuring that uploaded files do not exceed size limits, preventing potential upload issues.

4. **File: `app/Rules/VideoFileSize.php`**
   - **Status:** Added
   - **Changes:** Custom validation rule to check file size for videos.
   - **Description:** This rule validates video file sizes against an environment variable `MAX_VIDEO_SIZE`, applicable for uploaded video files.
   - **Impact:** Ensures uploaded videos meet size requirements, thus maintaining application performance and storage management.

5. **File: `resources/lang/en/auth.php`**
   - **Status:** Added
   - **Changes:** Language strings for authentication messages.
   - **Description:** Provides predefined messages related to authentication actions.
   - **Impact:** Enhances localization and user feedback during authentication processes.

6. **File: `resources/lang/en/pagination.php`**
   - **Status:** Added
   - **Changes:** Language strings for pagination controls.
   - **Description:** Adds pagination control texts for better navigation.
   - **Impact:** Supports user interface by providing necessary localization for pagination.

7. **File: `resources/lang/en/passwords.php`**
   - **Status:** Added
   - **Changes:** Language strings for password reset processes.
   - **Description:** Includes standard messages for password reset actions.
   - **Impact:** Improves user experience with clear feedback during password recovery.

8. **File: `resources/lang/en/validation.php`**
   - **Status:** Added
   - **Changes:** Comprehensive set of validation messages.
   - **Description:** Adds validation messages covering various form inputs and actions.
   - **Impact:** Ensures users receive appropriate feedback during form validation processes.

9. **File: `resources/lang/pt_br/auth.php`**
   - **Status:** Added
   - **Changes:** Portuguese translations for authentication messages.
   - **Description:** Provides localized authentication messages for Portuguese-speaking users.
   - **Impact:** Enhances accessibility and usability for Portuguese-speaking users.

10. **File: `resources/lang/pt_br/pagination.php`**
    - **Status:** Added
    - **Changes:** Portuguese translations for pagination controls.
    - **Description:** Adds localized text for pagination controls.
    - **Impact:** Aids navigation for Portuguese-speaking users.

11. **File: `resources/lang/pt_br/passwords.php`**
    - **Status:** Added
    - **Changes:** Portuguese translations for password reset messages.
    - **Description:** Includes localized texts for password reset processes.
    - **Impact:** Supports Portuguese-speaking users during password recovery actions.

12. **File: `resources/lang/pt_br/validation.php`**
    - **Status:** Added
    - **Changes:** Portuguese translations for validation messages.
    - **Description:** Comprehensive translations for validation messages.
    - **Impact:** Ensures Portuguese-speaking users receive relevant feedback during form validations.

13. **File: `resources/views/livewire/profile-video-upload.blade.php`**
    - **Status:** Added
    - **Changes:** Blade template for the profile video upload component.
    - **Description:** Provides a user interface for uploading profile videos, including progress bars and success messages.
    - **Impact:** Enhances user interaction by providing a clear video upload interface.

14. **File: `resources/views/profile/avatar-upload.blade.php`**
    - **Status:** Added
    - **Changes:** Blade template for avatar upload.
    - **Description:** Allows users to upload or change their profile avatar, including previews and removal options.
    - **Impact:** Improves user profile management by providing an intuitive interface for avatar changes.

15. **File: `app/Actions/Fortify/UpdateUserProfileInformation.php`**
    - **Status:** Modified
    - **Changes:** Added 'gender' attribute for profile information update.
    - **Description:** Extends user profile update functionality to include gender information.
    - **Impact:** Allows for more comprehensive user profiles by including gender as an updatable attribute.

16. **File: `app/Http/Controllers/UserProfileController.php`**
    - **Status:** Modified
    - **Changes:** Added methods to handle avatar and video uploads, validations for file types and sizes.
    - **Description:** Implements backend logic for managing avatar and video uploads, including storage management and validation.
    - **Impact:** Enhances backend functionality to support new media features, improving overall application capabilities.

17. **File: `app/Http/Middleware/VerifyCsrfToken.php`**
    - **Status:** Modified
    - **Changes:** Exempted video upload route from CSRF verification.
    - **Description:** Ensures smooth operation of video upload functionality by exempting specific route from CSRF checks.
    - **Impact:** Prevents upload failures due to CSRF verification issues, maintaining user experience.

18. **File: `app/Models/User.php`**
    - **Status:** Modified
    - **Changes:** Added 'gender' and 'profile_photo_path' attributes to the fillable array.
    - **Description:** Extends the user model to include gender and profile photo path for mass assignment.
    - **Impact:** Supports the inclusion of additional user profile attributes, allowing for more detailed user information.

19. **File: `resources/css/app.css`**
    - **Status:** Modified
    - **Changes:** Added styles for progress bars and upload sections.
    - **Description:** Enhances the user interface by adding CSS for new upload components.
    - **Impact:** Improves visual appeal and user experience during file uploads.

20. **File: `resources/js/app.js`**
    - **Status:** Modified
    - **Changes:** Minor import statement adjustments.
    - **Description:** Ensures correct loading of JavaScript dependencies.
    - **Impact:** Maintains functionality integrity by ensuring proper JS asset inclusion.

21. **File: `resources/lang/pt_br.json`**
    - **Status:** Modified
    - **Changes:** Added and updated translation strings for Portuguese.
    - **Description:** Enhances localization for Portuguese-speaking users, especially focusing on new features and success messages.
    - **Impact:** Improves accessibility and usability for Portuguese-speaking users.

22. **File: `resources/views/layouts/app.blade.php`**
    - **Status:** Modified
    - **Changes:** Added links to Font Awesome and jQuery.
    - **Description:** Ensures necessary resources for improved UI components are loaded.
    - **Impact:** Enhances UI components functionality and aesthetics.

23. **File: `resources/views/profile/setcard.blade.php`**
    - **Status:** Modified
    - **Changes:** Additional sections and scripts for the setcard page including media upload scripts.
    - **Description:** Integrates new upload functionalities and enhances user interaction with profile sections.
    - **Impact:** Provides a more thorough and interactive user profile management page.

24. **File: `resources/views/profile/update-profile-information-form.blade.php`**
    - **Status:** Modified
    - **Changes:** Replaced inline profile photo logic with the new avatar-upload component.
    - **Description:** Streamlines and enhances the profile update form by leveraging the new component-based structure.
    - **Impact:** Improves maintainability and user experience with a cleaner interface.

25. **File: `routes/web.php`**
    - **Status:** Modified
    - **Changes:** Added routes for avatar and video upload.
    - **Description:** Ensures routing is set up for the new functionalities, linking front end actions to backend logic.
    - **Impact:** Enables new features by providing necessary route definitions, ensuring seamless integration.

---

# #4 Overview of Pull Request: Caching and Contact Form Improvements

## Introduction
This pull request primarily introduces the addition of npm cache files and minor enhancements to the contact form functionality within the application. These changes have several impacts, including potential performance optimizations through caching mechanisms and improved data handling within the contact form. The modifications span across new cache file additions and slight adjustments in the `ContactController`.

## Changes Overview
1. **File: `app/Http/Controllers/ContactController.php`**
   - **Status:** Modified
   - **Changes:** 
     - Added validation check for phone number concatenation.
     - Added a hook to append country code to the phone number.
     - Added extra space for error capture.
   - **Description:** 
     - The modification aims to improve data validation and handling within the contact form. By concatenating the country code with the phone number, consistency in phone number formatting is ensured.
     - Additionally, the try-catch block has been updated for enhanced error handling with added spacing for code readability.
   - **Impact:** 
     - Enhanced user experience by ensuring proper phone number formatting.
     - Improved code maintainability and readability.
     - More robust form validation and error handling capabilities.

In summary, the primary focus of these changes is to enhance the npm caching mechanism, which will result in better dependency management and quicker build times. Additionally, by enhancing the `ContactController`, the data handling, and overall user experience for the contact form is improved. These changes collectively contribute to both the backend efficiency and frontend reliability of the application.

---

# #3 Feature Enhancements and User Information Update: Improved Contact, Messaging, and Email Management

## Introduction
This pull request introduces several new features and enhancements, focusing on user contact and messaging information management within the application. It incorporates new Livewire components for updating user address, contact details, and email addresses, and integrates new database tables to store these details. The enhancements improve the user experience by providing easy and secure ways to handle their personal information. Additionally, the system's architecture is enhanced by adding new Eloquent models and database migration scripts, ensuring robust data handling and consistency.

## Changes Overview
1. **File: `app/Livewire/UpdateCreatorContactForm.php`**
   - **Status:** Added
   - **Changes:** 114 lines of code added.
   - **Description:** Introduces a new Livewire component to handle the creation and update of user address information.
   - **Impact:** Enables users to update their address information, including shipping details, improving the user profile management capabilities.

2. **File: `app/Livewire/UpdateCreatorMessengerForm.php`**
   - **Status:** Added
   - **Changes:** 70 lines of code added.
   - **Description:** Adds a new Livewire component for updating user messenger contact details like WhatsApp, email, Instagram, and TikTok.
   - **Impact:** Enhances user experience by allowing updates to messenger details, facilitating better communication channels.

3. **File: `app/Livewire/UpdateEmailAddressForm.php`**
   - **Status:** Added
   - **Changes:** 76 lines of code added.
   - **Description:** Introduces a new Livewire component enabling users to update their email addresses and re-send verification emails if needed.
   - **Impact:** Improves user account management and security by providing functionality to update email addresses and handle email verifications.

4. **File: `app/Models/UserAddress.php`**
   - **Status:** Added
   - **Changes:** 36 lines of code added.
   - **Description:** Adds a new Eloquent model for user address data, including fields for regular and shipping addresses.
   - **Impact:** Structures and handles user address data efficiently, enhancing database integrity and operations related to user addresses.

5. **File: `app/Models/UserCreatorDetails.php`**
   - **Status:** Added
   - **Changes:** 28 lines of code added.
   - **Description:** Adds a new Eloquent model for storing user creator details such as contact information and social media handles.
   - **Impact:** Facilitates the management and retrieval of user creator details within the application, improving the overall data model consistency.

6. **File: `config/livewire-alert.php`**
   - **Status:** Added
   - **Changes:** 27 lines of code added.
   - **Description:** Configuration file for LivewireAlert, providing settings for alert positions, timers, and styles.
   - **Impact:** Enhances user interaction by integrating customizable alert messages, improving feedback mechanisms.

7. **File: `database/migrations/2023_11_04_212531_create_users_address_table.php`**
   - **Status:** Added
   - **Changes:** 46 lines of code added.
   - **Description:** New migration script for creating `users_address` table which stores user address information.
   - **Impact:** Establishes a new database table to support user address management, ensuring proper data storage.

8. **File: `resources/views/profile/update-creator-contact-form.blade.php`**
   - **Status:** Added
   - **Changes:** 125 lines of code added.
   - **Description:** Blade view for the update creator contact form, allowing users to input and update their address details.
   - **Impact:** Provides a front-end form for users to interact with address information, enhancing user profile management.

9. **File: `resources/views/profile/update-creator-messenger-form.blade.php`**
   - **Status:** Added
   - **Changes:** 45 lines of code added.
   - **Description:** Blade view for the update creator messenger form, allowing users to update their contact and social media details.
   - **Impact:** Improves user interface for managing messenger contact information, enhancing user experience.

10. **File: `resources/views/profile/update-email-address-form.blade.php`**
    - **Status:** Added
    - **Changes:** 48 lines of code added.
    - **Description:** Blade view for the update email address form, enabling email updates and verification link resending.
    - **Impact:** Facilitates email management and verification for users, improving account security.

11. **File: `composer.json`**
    - **Status:** Modified
    - **Changes:** 2 lines of code added.
    - **Description:** Adds new package dependencies for `jantinnerezo/livewire-alert` and `propaganistas/laravel-phone`.
    - **Impact:** Ensures the application has required packages for enhanced alert and phone number validation functionalities.

12. **File: `database/migrations/2023_10_25_233413_create_users_creatordetails_table.php`**
    - **Status:** Modified
    - **Changes:** 4 lines of code added.
    - **Description:** Updates the existing migration to include new fields for contact information like WhatsApp, email, Instagram, and TikTok.
    - **Impact:** Extends the data schema to support additional user creator details, improving data richness.

13. **File: `resources/lang/pt_br.json`**
    - **Status:** Modified
    - **Changes:** 25 lines added, 6 lines deleted.
    - **Description:** Adds translations for various user contact and address-related phrases in Brazilian Portuguese.
    - **Impact:** Enhances localization support, improving user experience for Portuguese-speaking users.

14. **File: `resources/views/components/input-error.blade.php`**
    - **Status:** Modified
    - **Changes:** 1 line added, 1 line deleted.
    - **Description:** Adjusts the input error component to display localized error messages.
    - **Impact:** Ensures error messages are user-friendly and localized, improving accessibility and user comprehension.

15. **File: `resources/views/layouts/app.blade.php`**
    - **Status:** Modified
    - **Changes:** 3 lines added, 1 line deleted.
    - **Description:** Adds script tags to include SweetAlert2 library and Livewire Alert scripts.
    - **Impact:** Ensures alert integrations function correctly, enhancing the user interface with better feedback mechanisms.

16. **File: `resources/views/profile/contact.blade.php`**
    - **Status:** Modified
    - **Changes:** 9 lines added, 6 lines deleted.
    - **Description:** Updates the profile contact page to include the newly created forms for updating contact and messenger details.
    - **Impact:** Enhances the profile page with additional forms, improving user interaction for profile updates.

17. **File: `resources/views/profile/settings.blade.php`**
    - **Status:** Modified
    - **Changes:** 1 line added, 1 line deleted.
    - **Description:** Updates the settings view to use the new email address update form.
    - **Impact:** Improves email management functionality within user settings, enhancing user control over their account information.

This pull request brings significant improvements to user information management by introducing new features and enhancements that streamline user interactions, ensuring data accuracy and improving the overall user experience.

---

# #2 New Blog Post Features and Infrastructure Enhancements

## Introduction
This pull request introduces significant updates to the blog post management features of the application. It brings about the addition of several new controllers for blog post handling, both from an administrative and public perspective, a new model representing blog posts, database migrations, configuration updates, and language file adjustments. These changes aim to enhance the blog's functionality, improve the user experience for both administrators and visitors, and streamline content management processes. The updates also contain significant deletions of unused or redundant language files, which simplifies the system and reduces clutter.

## Changes Overview
1. **File: `app/Http/Controllers/BlogPostController.php`**
   - **Status:** Added
   - **Changes:** Addition of a new controller to manage blog post operations such as listing, creating, and storing blog posts.
   - **Description:** 
     - Methods added:
       - `list()`: Fetches and lists all blog posts.
       - `create()`: Displays the form for creating a new blog post.
       - `create_store(Request $request)`: Validates and stores the submitted blog post, including image uploads to S3.
     - Use of models `BlogPost` and `User`, validation, and image handling were implemented to facilitate the creation and management of blog content.
   - **Impact:**
     - Enhances the ability for admins to manage blog posts directly through the application.
     - Provides a structured process for blog post creation and storage, ensuring data integrity and proper resource management.

2. **File: `app/Http/Controllers/BlogPostPublicController.php`**
   - **Status:** Added
   - **Changes:** Addition of a public-facing controller for displaying individual and lists of blog posts.
   - **Description:** 
     - Methods added:
       - `show(BlogPost $blogPost)`: Displays a single blog post along with suggested posts.
       - `list()`: Displays all blog posts to the public.
     - Integrates the presentation logic for blog posts, showing random and latest posts.
   - **Impact:**
     - Enhances user experience by providing readers with a structured and engaging way to browse and read blog posts.

3. **File: `app/Http/Controllers/IndexController.php`**
   - **Status:** Added
   - **Changes:** Addition of an index controller to display the latest blog posts.
   - **Description:** 
     - Methods added:
       - `show(BlogPost $blogPost)`: Fetches and displays the latest three blog posts.
     - Provides a convenient entry point for the blog, linking the homepage to the latest content.
   - **Impact:**
     - Improves the visibility of the latest blog content on the homepage, potentially increasing reader engagement and site activity.

4. **File: `app/Models/BlogPost.php`**
   - **Status:** Added
   - **Changes:** Addition of the BlogPost model to represent blog posts in the database.
   - **Description:** 
     - Defines the relationship with the `User` model via `authorRelation()`.
   - **Impact:**
     - Structurally underpins the blog post functionality by providing a clear model for handling blog data.

5. **File: `config/image.php`**
   - **Status:** Added
   - **Changes:** Addition of a new configuration file for handling image processing.
   - **Description:** 
     - Sets up the image processing driver to "gd" by default.
   - **Impact:**
     - Ensures that all image operations are standardized across the application, improving consistency and reliability in image manipulations.

6. **File: `database/migrations/2023_10_27_133526_create_blog_posts_table.php`**
   - **Status:** Added
   - **Changes:** Addition of a migration file for creating the blog posts table.
   - **Description:** 
     - Defines the schema for the `blog_posts` table, including fields for title, url, image, author, description, headline, SEO title, and SEO description.
   - **Impact:**
     - Establishes the necessary database structure to store and manage blog posts, facilitating the new blog features.

7. **File: `app/Http/Controllers/ContactController.php`**
   - **Status:** Modified
   - **Changes:** Removal of debug dumps and unnecessary S3 image upload methods.
   - **Description:** Cleans up the controller by removing unnecessary debugging and redundant methods.
   - **Impact:**
     - Streamlines the contact functionality, ensuring a cleaner codebase and more focus on core functionalities.

8. **File: `composer.json`**
   - **Status:** Modified
   - **Changes:** Addition of the "intervention/image" library dependency.
   - **Description:** 
     - Adds the Intervention Image library to handle image processing tasks.
   - **Impact:**
     - Provides robust image manipulation capabilities necessary for the enhanced blog post features.

9. **File: `config/app.php`**
   - **Status:** Modified
   - **Changes:** Addition of `Intervention\Image\ImageServiceProvider` and the alias `Image`.
   - **Description:** 
     - Registers the service provider and facade for the Intervention Image library.
   - **Impact:**
     - Integrates the Intervention Image library into the Laravel service container, enabling easy and efficient image processing.

10. **File: `config/filesystems.php`**
    - **Status:** Modified
    - **Changes:** Change of S3 scheme from `http` to `https`.
    - **Description:** 
      - Enhances security by defaulting to the secure HTTP scheme for S3 file operations.
    - **Impact:**
      - Improves data security during image upload and retrieval operations.

11. **File: `resources/lang/pt_br.json`**
    - **Status:** Modified
    - **Changes:** Addition of new translations for blog-related fields.
    - **Description:** 
      - Adds translation strings related to the blog functionality.
    - **Impact:**
      - Enhances multilingual support for blog features, improving accessibility for Portuguese-speaking users.

12. **File: `resources/lang/vendor/backpack/**/*.php`**
    - **Status:** Removed
    - **Changes:** Removal of various unused translation files.
    - **Description:** 
      - Deletes redundant and unused language files related to backup notifications.
    - **Impact:**
      - Cleans up the repository, reducing unnecessary clutter and simplifying maintenance.

The summary above captures not only the technical details of what was changed but also provides insight into why the changes were made and what impact they will have on the system. This ensures that all stakeholders, irrespective of technical proficiency, have a clear understanding of the updates.

(h
pk

	��̷��(i
�0evector"�0��0
�0}��;�v<��~<���<��;Ӭ�oeü��M<���;IO<��<��a���:�<4���Ɋ<<hZ=�;e<oX=;���W�<��=���^��<��<�_��28�DV���u<�ڼ:r_��S;=�X��d}�>*�<��ڼc|ػ�<u?<h�=�_ڼ�߃;�Q��Q;�y=<c���o\=
y��a<�F<R�Z<:��|RȻ��üj~�-��#�����xJ�E,����:�A<����ܒ<���J}��UA<i6b���弛�=�<I�.B=�<��w;�<���'��1���m=�a=�S�υ��u���.�?<��߼c����_���]hO�^�������"���P��q�;	J0��T�;�w�<��2�jU��ވ��N��
9=�=k�}�� ]�{ᅼ�C)=�l�w��<;�<����
�!���飼;aY���l<3�;S���*�<��������0�$[����U�H�<����u�<�v�?���d6�;�}���y!�Ƕ==�y2=�T=^ft�$�o�G�;�'����<Qa��"g��A�;���{�;	�<�1y�"���B<��F<��1��;:]���;&H��:?�^�)<ى���7M=�ϡ=�z\���鼻��&_;ƍ�P.��MW�K���)D���������W1��}M9���h
;�����ZA<»�<`��<�i<��=< �ٺ��=!��*��ۆ���ܨ��Ű���ܼ���<�	�b<pyJ=
��<@�<j8��5�:��5��<�PỮ=�;W��<���5�#<�o=�ջw)�eYD��-�z�^<k�ü��ɻ�n�<�S�����=�^���<��s<R/�<��뼬Z�<�5=ϭ==B�ż+�[=�,�<o�=�\�z��;A��;��<�I{���.��P=���;�%x���u<�y�;�`<4�<㮰;�x-=�V��"t�<��;�c<}9���i���6�;��,=B�Y=8�W:~��<�V;��s����	h��g�;.�g<�[0=w�<o�-�h�d�#j��w=�{<I�<4c<={{�;��H��6D=�Vz=��f<m�;�ݤ�D�����]r�=H_<2~.��(=�_����=��9<�ԛ�W��<Q>�f'<�U<����.�(���~"���B����<�j�<ݴ�<���T:�=�>�<�e�<����̉��~=O=�XB<4e���雼�G/�Z�W;K����[�$P��#nU��C��xG;�=�<Uj���0F<��������(��j�v�*<����O�:�g�<4�/<������=�cŻ�k=X=˼���<*�%<Ș;�=�<��G�.��<.׳��W=�s�Ѽ�9��f<C$O����<�=
<Z<�m�<�s�%ң;�s<��8=�笽���<�sQ:|����c
����1�<vb���
�QF�<\�h<+/���"�M���ћ�ۢ�ְϻ�	�<
P<斦����Ҵۼ<閺�i$<��2=��<��<|�<M�;�k	=䈮�-��:��w����b�<Rü�
.<"�<j�$�k;�<�=��D=��=>(�=]�;���<�0���b��<��_*�,aW�'��;�e<R����]�<���<�6�;|<#<�p�;"N�<�$�2=
:=vA�;PD�<b��;u��A��f$4��`�G��;s�<��q��	�;P�c�2��q<~=����y�<캼��y���-=��z<Q���]<aS���3=���<C<��<l%ּ��R��W��ٍ=�����@�=�L<2Ȧ�h�2�i����a=�5���T	=+Σ�cX�;P9=q9;�ӓ=�m0=5ݼ��뼿�H<�/�;V���^=X�7=�����<�.����H*�,]L<w��<�m��]V<w�=�ٷ��{�;���<� �<INT�[c�<���H<��j��8]<��w=�r�>�»�=��㖻�>6O���[<ˁ�V(<��ϻ�<�ϙ<l=ÿ9�PZ;�,=#������1�S�;G��<�)��6�K��<<�����<�ː�s<����f"��q�7<J2���C�<��T�w`ƽ�V����;d��<��7��'�;�
=��2�9;���J���<��:���ʪ0<!~5<��K9{(<`x�<�JS<	*�<��ƺ%�N��d���=CCP���<��<jT�n�;A�G<
�ɼ߹;�K��>`�<\�B�<С�;��x��<�!<=��`��t�3����Ξ�<[�p���3D==�<�Zy:�p<�l�<���:��(���R���;��=��K�<�;9;�J�.H�<�j�;m=λI��<�7�<��
=���<��ƻ�N�;�%<�o��f�;�L�C��q!��ĳ;��2����<Z�3=dO��V��:L���,�1<�>��f��ź��pֹA8�<���:���5
=�)��n��g�N�|t����;�:�<���<����h; ��O�;���)���`5"��u�<�������	Mc�G=E�<�"�<=y��wn<��<1��<�=ֺ��?�FN��Np?���<�O�;�������#\��=q�<�	�<�ۖ:��<ط�;h�����!=b}���Oa;�HѼ���;�ȁ�e�<����>)0;$<�4?�N
�����<n>=ފm<��[����<�pU<>����ό<�j=Ƽl;R�<�Ƽ��ڼ�aP��D�;����q�<����:�<�eҼ��;L,��u;����<QK<�'�<s"�٭��>���J��><�F˼�𼴀�<Đ�=�x<w5�<��ռ�E��2�,<����
�<�H
=	�����P;I?
<7r������rYټ�iۼ%5��eH<-��<�mռMׅ=Pqv��P<�Ǽ(<lM�<�Y>�B*%�1a(<���A�<>c��o�x=�eG�C���<ͼ3����[��_�A����=�!�]<�<�4<e�9<0�;G�{���Ӽ	b��xxg<���<8�e�I�=D�K���Z=$�7<��;,���LۼLb�<2���Տ<p=O
L��!�_^���C�<��8<�F��z�<���H��<����_8�:4��<�����b3�*^<q~��Q<�<μ4����ʼ�'H�《��d�<��=ý6<�L�;DO<�$��MU�4�<lF�� ��<������=<�B=xI�<�x&���=�8	����9J6-���R�u�:���Q�*=��<%@��>^��&�%�.�|���근t�M<?�)��B=O�	�-=��<�.��m��V�;�ȉ;�i�<��g�>Br���<����`��<_̌< �=�k��V��bA�;����;�,=#��<v,�:��;x��v�J��
ż�<,�,�9���Ļ)�;bv�<z��l��	ļ1<�.m�:�	����<��ἐ�⻞�ּV�Z=��0;�h�DA��V^�A��<E�b�<�.��v�=ָ�<ȡ.<>��<�C�����<{�3�gE¼�0�<X*a���=T��<��<lة�Hͨ<�8��;Q<��<��<wx$��p�<�銼]�:�]<:N�O��7<�|l;�9"�P�N�x=:�i�*�<�.<1L=d?�����<�C�<�y�<��;���`M�<t����N=���&a<�5�;�*C<��=Z����<�h=V�(�Z��<٩��!�<Q<{l+�}Yϼ�}�6'%���+<*�X�5��<�,=[��<V���J<�(��У:���;az�<���1�= ~���6<�v��O[��姼���;�(�<S�<��;r
:7�m�0���T�>����9
�;N�;��슻�w;+ė<��S=+�<�uz==]<<}�<�Ϳ<�im�"�+��U�<V%�q���p�=�~�<px�9H�;��:^LR��I<�=x�ɲ�<�cP�疅����<��<�
�C����<�>=P��:�P�<�з<�u�<#������<�6�/�F��:4a=�=��I��<��ἻbF<��.�����sel��
�3[)�=q�<�/�<��<6K�<v��)�3���:��:i�׼��E<�ټ�V�y��<�n��f{u;��[�c,;���;|�;���<�ƴ��1ּ��;ŋ2��Ԕ<0.s<g<��.;�ݸ��]j<Լ;d��9�Z<�ډ�]�4=��<���`=c;&6K:�c�<��<6�ȼ��k��~����G�;��=���<:�:φ�<a׻cu�<��V:�������^U=�;&�1��ѡ�|��Q6n<��v;n��<t�*��$<O���ZPm;�����<Y��<�2<8�+��;^y�;T_���Cº���<�����<���<Jp�<�G=�o��G <��</A{��j�<J�	<2:����VX-<�S����ۻ��d<?���%L,<X^�;,����<t��<+�=m5z<�3�������~���<��k�<ɢ@=�@ü]�:��k_;k�x���=������;����D���D仐»��'�����;PD=�Va:}W����<}⺼L��:K��=^p��E�=��~=v�	=fܼ���	==�ͼPмı�%��<�n�<e&=��N<$?��a��P�=�\�<ю<��~< .T���;I���:�D<�;�;�h�;�V��"3=��<�O�<T9s�T=N�I<*���*q<�C�<K��;}�9=Wn⼻T�b{7����<_�;�湼_e<5{���'�����<�����S���;��:Ƥ��'^�;�3���ւ��A=H�.SG��L;��m5=F?	��/�<�י<����Is�'�<�W���7<�z���<7�x;2=դ�<%
d<�Ҽ;���tO<!
ȼV8ʻ�
��T���<0�)c0;[fK=X�:��u�ٻ=�k�<9r:�;�<W!7=�>�<e�<\�ϼի	��t����}���=�{�<v�;&7<���C<�*8<�ϼFތ�t�{:��۸	<��q<�Z�<�H���;�R�<�V�<މ�U���'�<N��� D<i���3�뒤��7 ;-��4�,T�<�$���<.����#¼�e����lD;�M��m���w��K�M�"߼9���<�=�����a�<ӕ̼ݽ���� ;�q��2<�2��=����Ƥ���c����<����gg��쪻�좓�W ������'b|;9[9�������u;Z%�<Hл�1��������x�=��<È<�;ito�,𑼉�G�
:�f�}��;�n��(�<�������<H���HV��'�<�D�<�^��a!�<�p����=���<�r�<̦)<?9��&{E<cQټ��<*�8�4/%��Yܻ!�ƻ
P�<^��]�<#{/=�]��TC<c0n<�gp<���<�L�<sК;a��<�|k��@�����
%<���;^c���;<%�=|�?�(�;���y������<�!�2��=\�_<�۝;��+�����������:;��<����c�<�:���;��=���������;`��;:��<}�<�Y�j=��RP�Zw�<�������<���p���G�]��;�(�; ;B�=�f:������>�����������<O!�;8�G<6�=��<6�Ntp�4	>�����>�<Ҭü�����o=�<i+��Kͅ<�LK<��<$�=bB�< �5���ؼ��<���<�
"��}`;�s%�)�V�����v�<��%�:�\�<;	<���<	ͫ�eVu���;�Vo<lӎ��|5<�2λ�<C�%�Dd�;���<(�`<�k�<@x�:�oM:��L=���;X��U�<��h;�=����<�[��5=���b�<l?�;�K<ɞ=9�=�*��j��i��;��L<�"t;��;��5=����4��<��ƺ���`n�<�/�<��0:�<s��<��$<���<���]��<cj������<�/N;s:<܆"<i7Z<?P�<�}i:$b���<��s<gm-�w��<]��8�<E ��Jv���^^<���;���ֺ�<˶��\�<��<A������'����Y�;Mg<(j
RowID

	��̷��
	Timestamp

	ه��̷��(


