diff --git a/resources/views/components/layout/navigation/index.blade.php b/resources/views/components/layout/navigation/index.blade.php index 8004079b..e28c7746 100644 --- a/resources/views/components/layout/navigation/index.blade.php +++ b/resources/views/components/layout/navigation/index.blade.php @@ -33,6 +33,9 @@ class="hidden w-full lg:flex items-center text-sm leading-6 text-slate-400 round
  • +
  • + +
  • diff --git a/resources/views/documentation/faq.blade.php b/resources/views/documentation/faq.blade.php new file mode 100644 index 00000000..851c7bf6 --- /dev/null +++ b/resources/views/documentation/faq.blade.php @@ -0,0 +1,103 @@ + + + Frequently Asked Questions + + + Answers to the most frequently asked questions about TallStackUI. + + +

    + FilamentPHP is one of the best form builders, with little time and effort + you can have a complete administrative panel, however, there are some scenarios + in which using a tool like it is not favorable. TallStackUI, on the other hand, + is a component library for UI, that is: TallStackUI does not generate PHP code, + and it does not take care of business rules, so the code that makes the application + work is completely under your control, only the UI - visual, will be available through + the TallStackUI components. If you need something fast, tools like Filament are always + the best way to go. However, if you or your project are careful about dependencies, or + you want to have control over all PHP code but save time just on the UI, TallStackUI is the best way. +

    +
    + +

    + TallStackUI was created and is maintained by people who, in addition to being users of the library itself, + are people fully connected with the TallStack ecosystem, mainly Laravel and Livewire, capable developers + who know everything about this ecosystem. Therefore, when using TallStackUI the biggest guarantee you and + your project will have is frequent updates. After all, the TallStackUI developer team are also TallStackUI + users. No updates for TallStackUI = no updates for our projects, which doesn't make sense. +

    +
    + +

    + Yes, totally! TallStackUI components support a prefix key, + which consists of prefixing TallStackUI components avoiding conflicts in component names. +

    +
    + +

    + From concept to creation, TallStackUI was designed to offer forms of personalization, + so you can personalize TallStackUI components however you want, using two different + methods available, which we will explain below. +

    + +
    + +

    + Internally, yes. We like to prepare things with surprises, so the roadmap remains solely with the team, internally. + We currently have over 30 components and expect the release of over 15 more new components in 2024. +

    +
    + +

    + Although there is a sponsorship program, which raises funds to encourage the work of developers + of tools like TallStackUI, TallStackUI itself is free and does not require payment. However, + if you agree to support the library, you can do so by sponsoring the creator. +

    +
    + +

    + There are several ways to contribute to TallStackUI, from the sponsorship program, as mentioned above, + to share the library or offering help with code by sending pull requests. + Read the guide on how to prepare a development environment to submit a pull request to TallStackUI. +

    +
    + +

    + You can follow AJ, the creator of TallStackUI, on social media: LinkedIn and X, and also join our + Discord server, which already has more than 100 people, so you'll have access to early updates and news. +

    +
    + + + + + + + + +
    diff --git a/routes/web.php b/routes/web.php index 0bdd10f9..f929ccd9 100644 --- a/routes/web.php +++ b/routes/web.php @@ -14,8 +14,9 @@ ->group(function () { Route::view('/get-started', 'get-started')->name('get-started'); Route::view('/installation', 'documentation.installation', Example::Installation->variables())->name('installation'); - Route::view('/updates', 'documentation.updates', Example::Updates->variables())->name('updates'); Route::view('/troubleshooting', 'documentation.troubleshooting', Example::Troubleshooting->variables())->name('troubleshooting'); + Route::view('/updates', 'documentation.updates', Example::Updates->variables())->name('updates'); + Route::view('/faq', 'documentation.faq', Example::Updates->variables())->name('faq'); Route::prefix('/form') ->name('form.') diff --git a/tests/Feature/StructureTest.php b/tests/Feature/StructureTest.php index 312790a2..03148fdd 100644 --- a/tests/Feature/StructureTest.php +++ b/tests/Feature/StructureTest.php @@ -23,6 +23,7 @@ fn () => route('documentation.installation'), fn () => route('documentation.troubleshooting'), fn () => route('documentation.updates'), + fn () => route('documentation.faq'), // fn () => route('documentation.form.input'), fn () => route('documentation.form.password'),