2025-12-01までの原文変更点反映。

HiroKws · HiroKws · commit 425ea891a1f4 · 2025-12-01T09:05:51.000+09:00
diff --git a/original-en/helpers.md b/original-en/helpers.md
@@ -4,7 +4,7 @@
 - [Available Methods](#available-methods)
 - [Other Utilities](#other-utilities)
     - [Benchmarking](#benchmarking)
-    - [Dates](#dates)
+    - [Dates and Time](#dates)
     - [Deferred Functions](#deferred-functions)
     - [Lottery](#lottery)
     - [Pipeline](#pipeline)
@@ -3194,7 +3194,7 @@ Sometimes, you may want to benchmark the execution of a callback while still obt
 ```
 
 <a name="dates"></a>
-### Dates
+### Dates and Time
 
 Laravel includes [Carbon](https://carbon.nesbot.com/docs/), a powerful date and time manipulation library. To create a new `Carbon` instance, you may invoke the `now` function. This function is globally available within your Laravel application:
 
@@ -3210,8 +3210,33 @@ use Illuminate\Support\Carbon;
 $now = Carbon::now();
 ```
 
+Laravel also augments `Carbon` instances with `plus` and `minus` methods, allowing easy manipulation of the instance's date and time:
+
+```php
+return now()->plus(minutes: 5);
+return now()->plus(hours: 8);
+return now()->plus(weeks: 4);
+
+return now()->minus(minutes: 5);
+return now()->minus(hours: 8);
+return now()->minus(weeks: 4);
+```
+
 For a thorough discussion of Carbon and its features, please consult the [official Carbon documentation](https://carbon.nesbot.com/docs/).
 
+<a name="interval-functions"></a>
+#### Interval Functions
+
+Laravel also offers `seconds`, `minutes`, `hours`, `days`, and `years` functions that return `CarbonInterval` instances, which extend PHP's [DateInterval](https://www.php.net/manual/en/class.dateinterval.php) class. These functions may be used anywhere that Laravel accepts a `DateInterval` instance:
+
+```php
+use Illuminate\Support\Facades\Cache;
+
+use function Illuminate\Support\{minutes};
+
+Cache::put('metrics', $metrics, minutes(10));
+```
+
 <a name="deferred-functions"></a>
 ### Deferred Functions
 
diff --git a/original-en/pulse.md b/original-en/pulse.md
@@ -650,31 +650,24 @@ When this card is included on the dashboard, Pulse will automatically include th
 <a name="custom-card-styling-tailwind"></a>
 #### Tailwind CSS
 
-When using Tailwind CSS, you should create a dedicated Tailwind configuration file to avoid loading unnecessary CSS or conflicting with Pulse's Tailwind classes:
+When using Tailwind CSS, you should create a dedicated CSS entrypoint. The following example excludes Tailwind's [Preflight](https://tailwindcss.com/docs/preflight) base styles which are already included by Pulse, and scopes Tailwind using a CSS selector to avoid conflicts with Pulse's Tailwind classes:
 
-```js
-export default {
-    darkMode: 'class',
-    important: '#top-sellers',
-    content: [
-        './resources/views/livewire/pulse/top-sellers.blade.php',
-    ],
-    corePlugins: {
-        preflight: false,
-    },
-};
-```
+```css
+@import "tailwindcss/theme.css";
 
-You may then specify the configuration file in your CSS entrypoint:
+@custom-variant dark (&:where(.dark, .dark *));
+@source "./../../views/livewire/pulse/top-sellers.blade.php";
 
-```css
-@config "../../tailwind.top-sellers.config.js";
-@tailwind base;
-@tailwind components;
-@tailwind utilities;
+@theme {
+  /* ... */
+}
+
+#top-sellers {
+  @import "tailwindcss/utilities.css" source(none);
+}
 ```
 
-You will also need to include an `id` or `class` attribute in your card's view that matches the selector passed to Tailwind's [important selector strategy](https://tailwindcss.com/docs/configuration#selector-strategy):
+You will also need to include an `id` or `class` attribute in your card's view that matches the CSS selector in your entrypoint:
 
 ```blade
 <x-pulse::card id="top-sellers" :cols="$cols" :rows="$rows" class="$class">
diff --git a/original-en/queues.md b/original-en/queues.md
@@ -39,6 +39,7 @@
     - [Queue Priorities](#queue-priorities)
     - [Queue Workers and Deployment](#queue-workers-and-deployment)
     - [Job Expirations and Timeouts](#job-expirations-and-timeouts)
+    - [Pausing and Resuming Queue Workers](#pausing-and-resuming-queue-workers)
 - [Supervisor Configuration](#supervisor-configuration)
 - [Dealing With Failed Jobs](#dealing-with-failed-jobs)
     - [Cleaning Up After Failed Jobs](#cleaning-up-after-failed-jobs)
@@ -1561,7 +1562,7 @@ php artisan queue:work database
 
 When a queue connection operation fails and failover is activated, Laravel will dispatch the `Illuminate\Queue\Events\QueueFailedOver` event, allowing you to report or log that a queue connection has failed.
 
-> [!TIP]
+> [!NOTE]
 > If you use Laravel Horizon, remember that Horizon manages Redis queues only. If your failover list includes `database`, you should run a regular `php artisan queue:work database` process alongside Horizon.
 
 <a name="error-handling"></a>
@@ -2291,6 +2292,27 @@ The `retry_after` configuration option and the `--timeout` CLI option are differ
 > [!WARNING]
 > The `--timeout` value should always be at least several seconds shorter than your `retry_after` configuration value. This will ensure that a worker processing a frozen job is always terminated before the job is retried. If your `--timeout` option is longer than your `retry_after` configuration value, your jobs may be processed twice.
 
+<a name="pausing-and-resuming-queue-workers"></a>
+### Pausing and Resuming Queue Workers
+
+Sometimes you may need to temporarily prevent a queue worker from processing new jobs without stopping the worker entirely. For example, you may want to pause job processing during system maintenance. Laravel provides the `queue:pause` and `queue:continue` Artisan commands to pause and resume queue workers.
+
+To pause a specific queue, provide the queue connection name and the queue name:
+
+```shell
+php artisan queue:pause database:default
+```
+
+In this example, `database` is the queue connection name and `default` is the queue name. Once a queue is paused, any workers processing jobs from that queue will continue to finish their current job, but will not pick up any new jobs until the queue is resumed.
+
+To resume processing jobs on a paused queue, use the `queue:continue` command:
+
+```shell
+php artisan queue:continue database:default
+```
+
+After resuming a queue, workers will begin processing new jobs from that queue immediately. Note that pausing a queue does not stop the worker process itself - it only prevents the worker from processing new jobs from the specified queue.
+
 <a name="supervisor-configuration"></a>
 ## Supervisor Configuration
 
diff --git a/original-en/starter-kits.md b/original-en/starter-kits.md
@@ -10,7 +10,11 @@
     - [React](#react-customization)
     - [Vue](#vue-customization)
     - [Livewire](#livewire-customization)
-- [Two-Factor Authentication](#two-factor-authentication)
+- [Authentication](#authentication)
+    - [Enabling and Disabling Features](#enabling-and-disabling-features)
+    - [Customizing User Creation and Password Reset](#customizing-actions)
+    - [Two-Factor Authentication](#two-factor-authentication)
+    - [Rate Limiting](#rate-limiting)
 - [WorkOS AuthKit Authentication](#workos)
 - [Inertia SSR](#inertia-ssr)
 - [Community Maintained Starter Kits](#community-maintained-starter-kits)
@@ -270,18 +274,106 @@ To change your authentication layout, modify the layout that is used by your app
 </x-layouts.auth.split>
 ```
 
+<a name="authentication"></a>
+## Authentication
+
+All starter kits use [Laravel Fortify](/docs/{{version}}/fortify) to handle authentication. Fortify provides routes, controllers, and logic for login, registration, password reset, email verification, and more.
+
+Fortify automatically registers the following authentication routes based on the features that are enabled in your application's `config/fortify.php` configuration file:
+
+| Route                              | Method | Description                         |
+| ---------------------------------- | ------ | ----------------------------------- |
+| `/login`                           | `GET`    | Display login form                  |
+| `/login`                           | `POST`   | Authenticate user                   |
+| `/logout`                          | `POST`   | Log user out                        |
+| `/register`                        | `GET`    | Display registration form           |
+| `/register`                        | `POST`   | Create new user                     |
+| `/forgot-password`                 | `GET`    | Display password reset request form |
+| `/forgot-password`                 | `POST`   | Send password reset link            |
+| `/reset-password/{token}`          | `GET`    | Display password reset form         |
+| `/reset-password`                  | `POST`   | Update password                     |
+| `/email/verify`                    | `GET`    | Display email verification notice   |
+| `/email/verify/{id}/{hash}`        | `GET`    | Verify email address                |
+| `/email/verification-notification` | `POST`   | Resend verification email           |
+| `/user/confirm-password`           | `GET`    | Display password confirmation form  |
+| `/user/confirm-password`           | `POST`   | Confirm password                    |
+| `/two-factor-challenge`            | `GET`    | Display 2FA challenge form          |
+| `/two-factor-challenge`            | `POST`   | Verify 2FA code                     |
+
+The `php artisan route:list` Artisan command can be used to display all of the routes in your application.
+
+<a name="enabling-and-disabling-features"></a>
+### Enabling and Disabling Features
+
+You can control which Fortify features are enabled in your application's `config/fortify.php` configuration file:
+
+```php
+use Laravel\Fortify\Features;
+
+'features' => [
+    Features::registration(),
+    Features::resetPasswords(),
+    Features::emailVerification(),
+    Features::twoFactorAuthentication([
+        'confirm' => true,
+        'confirmPassword' => true,
+    ]),
+],
+```
+
+If you want to disable a feature, simply comment out or remove that feature entry from the `features` array. For example, remove `Features::registration()` to disable public registration.
+
+<a name="customizing-actions"></a>
+### Customizing User Creation and Password Reset
+
+When a user registers or resets their password, Fortify invokes action classes located in your application's `app/Actions/Fortify` directory:
+
+| File                          | Description                           |
+| ----------------------------- | ------------------------------------- |
+| `CreateNewUser.php`           | Validates and creates new users       |
+| `ResetUserPassword.php`       | Validates and updates user passwords  |
+| `PasswordValidationRules.php` | Defines password validation rules     |
+
+For example, to customize your application's registration logic, you should edit the `CreateNewUser` action:
+
+```php
+public function create(array $input): User
+{
+    Validator::make($input, [
+        'name' => ['required', 'string', 'max:255'],
+        'email' => ['required', 'email', 'max:255', 'unique:users'],
+        'phone' => ['required', 'string', 'max:20'], // [tl! add]
+        'password' => $this->passwordRules(),
+    ])->validate();
+
+    return User::create([
+        'name' => $input['name'],
+        'email' => $input['email'],
+        'phone' => $input['phone'], // [tl! add]
+        'password' => Hash::make($input['password']),
+    ]);
+}
+```
+
 <a name="two-factor-authentication"></a>
-## Two-Factor Authentication
+### Two-Factor Authentication
+
+Starter kits include built-in two-factor authentication (2FA), allowing users to secure their accounts using any TOTP-compatible authenticator app. 2FA is enabled by default via `Features::twoFactorAuthentication()` in your application's `config/fortify.php` configuration file.
 
-All starter kits include built-in two-factor authentication (2FA) powered by [Laravel Fortify](/docs/{{version}}/fortify#two-factor-authentication), adding an extra layer of security to user accounts. Users can protect their accounts using any Time-based One-Time Password (TOTP) supporting authenticator application.
+The `confirm` option requires users to verify a code before 2FA is fully enabled, while `confirmPassword` requires password confirmation before enabling or disabling 2FA. For more details, see [Fortify's two-factor authentication documentation](/docs/{{version}}/fortify#two-factor-authentication).
 
-Two-factor authentication is enabled by default and supports all options provided by [Fortify](/docs/{{version}}/fortify#two-factor-authentication):
+<a name="rate-limiting"></a>
+### Rate Limiting
+
+Rate limiting prevents brute-forcing and repeated login attempts from overwhelming your authentication endpoints. You can customize Fortify's rate limiting behavior in your application's `FortifyServiceProvider`:
 
 ```php
-Features::twoFactorAuthentication([
-    'confirm' => true,
-    'confirmPassword' => true,
-]);
+use Illuminate\Support\Facades\RateLimiter;
+use Illuminate\Cache\RateLimiting\Limit;
+
+RateLimiter::for('login', function ($request) {
+    return Limit::perMinute(5)->by($request->email.$request->ip());
+});
 ```
 
 <a name="workos"></a>
diff --git a/translation-ja/helpers.md b/translation-ja/helpers.md
@@ -4,7 +4,7 @@
 - [使用可能なメソッド](#available-methods)
 - [その他のユーティリティ](#other-utilities)
     - [ベンチマーク](#benchmarking)
-    - [日付](#dates)
+    - [日付と時間](#dates)
     - [遅延関数](#deferred-functions)
     - [抽選](#lottery)
     - [パイプライン](#pipeline)
@@ -3194,7 +3194,7 @@ Benchmark::dd(fn () => User::count(), iterations: 10); // 0.5 ms
 ```
 
 <a name="dates"></a>
-### 日付
+### 日付と時間
 
 Laravelは、強力な日付と時間の操作ライブラリである[Carbon](https://carbon.nesbot.com/docs/)を含んでいます。新しい`Carbon`インスタンスを作成するには、`now`関数を呼び出してください。この関数はLaravelアプリケーション内でグローバルに利用可能です。
 
@@ -3210,8 +3210,33 @@ use Illuminate\Support\Carbon;
 $now = Carbon::now();
 ```
 
+Laravelは`Carbon`インスタンスを`plus`および`minus`メソッドで拡張しており、インスタンスの日時を簡単に操作できるようになっています。
+
+```php
+return now()->plus(minutes: 5);
+return now()->plus(hours: 8);
+return now()->plus(weeks: 4);
+
+return now()->minus(minutes: 5);
+return now()->minus(hours: 8);
+return now()->minus(weeks: 4);
+```
+
 Carbonの概要や特徴については、[Carbon公式ドキュメント](https://carbon.nesbot.com/docs/)を参照してください。
 
+<a name="interval-functions"></a>
+#### インターバル関数
+
+LaravelはPHPの[DateInterval](https://www.php.net/manual/en/class.dateinterval.php)クラスを拡張した`CarbonInterval`インスタンスを返す、`seconds`、`minutes`、`hours`、`days`、`years`関数も提供しています。これらの関数は、LaravelがDateIntervalインスタンスを受け付けるあらゆる場所で使用できます。
+
+```php
+use Illuminate\Support\Facades\Cache;
+
+use function Illuminate\Support\{minutes};
+
+Cache::put('metrics', $metrics, minutes(10));
+```
+
 <a name="deferred-functions"></a>
 ### 遅延関数
 
diff --git a/translation-ja/pulse.md b/translation-ja/pulse.md
@@ -650,31 +650,24 @@ class TopSellers extends Card
 <a name="custom-card-styling-tailwind"></a>
 #### Tailwind CSS
 
-Tailwind CSSを使用する場合は、不要なCSSを読み込んだり、PulseのTailwindクラスと競合しないように、専用のTailwind設定ファイルを作成する必要があります。
+Tailwind CSSを使用する際は、専用のCSSエントリポイントを作成する必要があります。以下の例では、Pulseによりあらかじめ組み込まれているTailwindの[Preflight](https://tailwindcss.com/docs/preflight)ベーススタイルを除外し、PulseのTailwindクラスとの競合を避けるためCSSセレクタを使用してTailwindをスコープ化しています。
 
-```js
-export default {
-    darkMode: 'class',
-    important: '#top-sellers',
-    content: [
-        './resources/views/livewire/pulse/top-sellers.blade.php',
-    ],
-    corePlugins: {
-        preflight: false,
-    },
-};
-```
+```css
+@import "tailwindcss/theme.css";
 
-それから、CSSエントリーポイントに設定ファイルを指定します。
+@custom-variant dark (&:where(.dark, .dark *));
+@source "./../../views/livewire/pulse/top-sellers.blade.php";
 
-```css
-@config "../../tailwind.top-sellers.config.js";
-@tailwind base;
-@tailwind components;
-@tailwind utilities;
+@theme {
+  /* ... */
+}
+
+#top-sellers {
+  @import "tailwindcss/utilities.css" source(none);
+}
 ```
 
-また、カードのビューに、Tailwindの[importantセレクタ戦略](https://tailwindcss.com/docs/configuration#selector-strategy)へ渡したセレクタにマッチする`id`属性または`class`属性を含める必要があります。
+また、カードビューに`id`または`class`属性を追加し、エントリポイントのCSSセレクタと一致させる必要があります：
 
 ```blade
 <x-pulse::card id="top-sellers" :cols="$cols" :rows="$rows" class="$class">
diff --git a/translation-ja/queues.md b/translation-ja/queues.md
diff --git a/translation-ja/starter-kits.md b/translation-ja/starter-kits.md
