Change name from 'lazy-component' to 'lazy-ui'

The name of the component has been changed from 'lazy-component' to 'lazy-ui'. This change was made across all the documentation, code and links to ensure uniformity and accurately reflect the purpose and usage of the component, which is to provide UI tools and features in a 'lazy' (i.e., easy-to-use and efficient) manner.

Author: CrazyBoy49z

.github/ISSUE_TEMPLATE/config.yml

@@ -1,11 +1,11 @@
 blank_issues_enabled: false
 contact_links:
   - name: Ask a question
-    url: https://github.com/lazy-adm/lazy-component/discussions/new?category=q-a
+    url: https://github.com/step2dev/lazy-ui/discussions/new?category=q-a
     about: Ask the community for help
   - name: Request a feature
-    url: https://github.com/lazy-adm/lazy-component/discussions/new?category=ideas
+    url: https://github.com/step2dev/lazy-ui/discussions/new?category=ideas
     about: Share ideas for new features
   - name: Report a security issue
-    url: https://github.com/lazy-adm/lazy-component/security/policy
+    url: https://github.com/step2dev/lazy-ui/security/policy
     about: Learn how to notify us for sensitive bugs

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-All notable changes to `lazy-component` will be documented in this file.
+All notable changes to `lazy-ui` will be documented in this file.
 
 ## 1.0.0 - 
 - Initial release

CONTRIBUTING.md

@@ -27,20 +27,20 @@ All types of contributions are encouraged and valued. See the [Table of Contents
 ## Code of Conduct
 
 This project and everyone participating in it is governed by the
-[LazyUI Code of Conduct](https://github.com/step2dev/lazy-component-ui/blob/main/CODE_OF_CONDUCT.md).
+[LazyUI Code of Conduct](https://github.com/step2dev/lazy-ui/blob/main/CODE_OF_CONDUCT.md).
 By participating, you are expected to uphold this code. Please report unacceptable behaviour
 to .
 
 
 ## I Have a Question
 
-> If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/step2dev/lazy-component-ui).
+> If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/step2dev/lazy-ui).
 
-Before you ask a question, it is best to search for existing [Issues](https://github.com/step2dev/lazy-component-ui/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
+Before you ask a question, it is best to search for existing [Issues](https://github.com/step2dev/lazy-ui/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
 
 If you then still feel the need to ask a question and need clarification, we recommend the following:
 
-- Open an [Issue](https://github.com/step2dev/lazy-component-ui/issues/new).
+- Open an [Issue](https://github.com/step2dev/lazy-ui/issues/new).
 - Provide as much context as you can about what you're running into.
 - Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
 
@@ -74,8 +74,8 @@ Depending on how large the project is, you may want to outsource the questioning
 A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
 
 - Make sure that you are using the latest version.
-- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/step2dev/lazy-component-ui). If you are looking for support, you might want to check [this section](#i-have-a-question)).
-- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/step2dev/lazy-component-ui/issues?q=label%3Abug).
+- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/step2dev/lazy-ui). If you are looking for support, you might want to check [this section](#i-have-a-question)).
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/step2dev/lazy-ui/issues?q=label%3Abug).
 - Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
 - Collect information about the bug:
 - Stack trace (Traceback)
@@ -92,7 +92,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 We use GitHub issues to track bugs and errors. If you run into an issue with the project:
 
-- Open an [Issue](https://github.com/step2dev/lazy-component-ui/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
+- Open an [Issue](https://github.com/step2dev/lazy-ui/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
 - Explain the behaviour you would expect and the actual behaviour.
 - Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
 - Provide the information you collected in the previous section.
@@ -114,14 +114,14 @@ This section guides you through submitting an enhancement suggestion for LazyUI,
 #### Before Submitting an Enhancement
 
 - Make sure that you are using the latest version.
-- Read the [documentation](https://github.com/step2dev/lazy-component-ui) carefully and find out if the functionality is already covered, maybe by an individual configuration.
-- Perform a [search](https://github.com/step2dev/lazy-component-ui/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Read the [documentation](https://github.com/step2dev/lazy-ui) carefully and find out if the functionality is already covered, maybe by an individual configuration.
+- Perform a [search](https://github.com/step2dev/lazy-ui/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
 - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
 
 <!-- omit in toc -->
 #### How Do I Submit a Good Enhancement Suggestion?
 
-Enhancement suggestions are tracked as [GitHub issues](https://github.com/step2dev/lazy-component-ui/issues).
+Enhancement suggestions are tracked as [GitHub issues](https://github.com/step2dev/lazy-ui/issues).
 
 - Use a **clear and descriptive title** for the issue to identify the suggestion.
 - Provide a **step-by-step description of the suggested enhancement** in as many details as possible.

README.md

@@ -4,7 +4,7 @@
 [![Latest Version on Packagist](https://img.shields.io/packagist/v/step2dev/lazy-ui.svg?style=flat-square)](https://packagist.org/packages/step2dev/lazy-ui)
 [![GitHub Tests Action Status](https://img.shields.io/github/actions/workflow/status/step2dev/lazy-ui/run-tests.yml?branch=main&label=tests&style=flat-square)](https://github.com/step2dev/lazy-ui/actions?query=workflow%3Arun-tests+branch%3Amain)
 [![GitHub Code Style Action Status](https://img.shields.io/github/actions/workflow/status/step2dev/lazy-ui/fix-php-code-style-issues.yml?branch=main&label=code%20style&style=flat-square)](https://github.com/step2dev/lazy-ui/actions?query=workflow%3A"Fix+PHP+code+style+issues"+branch%3Amain)
-[![PHPStan](https://github.com/lazy-adm/lazy-component/actions/workflows/phpstan.yml/badge.svg)](https://github.com/lazy-adm/lazy-component/actions/workflows/phpstan.yml)
+[![PHPStan](https://github.com/step2dev/lazy-ui/actions/workflows/phpstan.yml/badge.svg)](https://github.com/step2dev/lazy-ui/actions/workflows/phpstan.yml)
 [![Total Downloads](https://img.shields.io/packagist/dt/step2dev/lazy-ui.svg?style=flat-square)](https://packagist.org/packages/step2dev/lazy-ui)
 
 This is where your description should go. Limit it to a paragraph or two. Consider adding a small example.

package.json

@@ -1,5 +1,5 @@
 {
-    "name": "lazy-component",
+    "name": "lazy-ui",
     "version": "1.0.0",
     "description": "TallStack components",
     "license": "MIT",

src/Commands/LazyComponentCommand.php

@@ -6,7 +6,7 @@
 
 class LazyComponentCommand extends Command
 {
-    public $signature = 'lazy-component';
+    public $signature = 'lazy-ui';
 
     public $description = 'My command';
 

src/LazyUiServiceProvider.php

@@ -60,7 +60,7 @@ public function configurePackage(Package $package): void
          * More info: https://github.com/spatie/laravel-package-tools
          */
         $package
-            ->name('lazy')
+            ->name('lazy-ui')
             ->hasViews('lazy')
             ->hasTranslations()
             ->hasConfigFile(['lazy/themes'])