diff --git a/docs/_layouts/default.html b/docs/_layouts/default.html index c743c6e0a..52ee693f8 100644 --- a/docs/_layouts/default.html +++ b/docs/_layouts/default.html @@ -96,6 +96,7 @@

{{ site.title | default: site.github.repository_name }}

Basic Concepts

How To

 +

Migrate WillPaginate/Kaminari

API

Pagy

Pagy::Backend

 @@ -122,7 +123,6 @@

{{ site.title | default: site.github.repository_name }}

Support

Trim

UIkit

 -

Migrate WillPaginate/Kaminari

➡ Chat Support on Gitter ➡

 diff --git a/docs/api/frontend.md b/docs/api/frontend.md index 4b68608c3..f7eb26836 100644 --- a/docs/api/frontend.md +++ b/docs/api/frontend.md @@ -170,7 +170,7 @@ The pagy internal i18n is implemented around the `Pagy::I18n` constant. You may #### Pagy::I18n.load configuration -By default pagy will render its output using the built-in `en` locale. If your app uses only `en` and you are fine with the built-in strings, you are done without configuring anything at all. +By default pagy will render its output using the built-in `en` locale. If your app uses only `en` and you are fine with the built-in strings, you are done without configuring anything at all and you can just skip this whole section. If you need to load different built-in locales, and/or custom dictionary files or even non built-in languages and pluralizations, you can do it all by passing a few arguments to the `Pagy::I18n.load` method. diff --git a/docs/api/javascript.md b/docs/api/javascript.md index cd64c6ee9..85ce6bc84 100644 --- a/docs/api/javascript.md +++ b/docs/api/javascript.md @@ -217,7 +217,7 @@ The following `pagy*_combo_nav_js` offer an alternative pagination UI that combi - `pagy_materialize_combo_nav_js` - `pagy_semantic_combo_nav_js` -They are the fastest and lighter `nav` on modern environments, recommended when you care about efficiency and server load _(see [Maximizing Performance](../how-to.md#maximizing-performance))_. +They are the fastest and lightest `nav` on modern environments, recommended when you care about efficiency and server load _(see [Maximizing Performance](../how-to.md#maximizing-performance))_. Here is a screenshot (from the `bootstrap` extra): diff --git a/docs/api/pagy.md b/docs/api/pagy.md index 26995579d..8ad311dab 100644 --- a/docs/api/pagy.md +++ b/docs/api/pagy.md @@ -147,7 +147,7 @@ Which means: - there is always a `page` #`1` in the pagination, even if it's empty - `pages` and `last` are always at least both `1` -- the `series` array contains always at least the page #`1`, which for a single page is also the current page, thus a string. With `size: []` series returns `[]` +- the `series` array contains always at least the page #`1`, which for a single page is also the current page, thus a string. With `size: []` the `series` method returns `[]` - `from` and `to` of an empty page are both `0` - `prev` and `next` of a single page (not necessary an empty one) are both `nil` (i.e. there is no other page) diff --git a/docs/how-to.md b/docs/how-to.md index 29cb326ad..61ad8f144 100644 --- a/docs/how-to.md +++ b/docs/how-to.md @@ -136,7 +136,7 @@ Pagy can also work in any other scenario assuming that: You can control the items per page with the `items` variable. (Default `20`) -You can set its default in the `pagy.rb` initializer _(see [Configuration](#global-configuration)_. For example: +You can set its default in the `pagy.rb` initializer _(see [Configuration](#global-configuration))_. For example: ```ruby Pagy::VARS[:items] = 25 @@ -432,7 +432,7 @@ By default Pagy generates all the page links including the `page` param. If you The `pagy_nav*` helpers are optimized for speed, and they are really fast. On the other hand editing a template might be easier when you have to customize the rendering, however every template system adds some inevitable overhead and it will be about 30-70% slower than using the related helper. That will still be dozens of times faster than the other gems, but... you should choose wisely. -Pagy provides the replacement templates for the `pagy_nav`, `pagy_bootstrap_nav`, `pagy_bulma_nav` and the `pagy_foundation_nav` helpers (available with the relative extras) in 3 flavors: `erb`, `haml` and `slim`. +Pagy provides the replacement templates for the `pagy_nav`, `pagy_bootstrap_nav`, `pagy_bulma_nav`, `pagy_foundation_nav`, and the `pagy_uikit_nav` helpers (available with the relative extras) in 3 flavors: `erb`, `haml` and `slim`. They produce exactly the same output of the helpers, but since they are slower, using them wouldn't make any sense unless you need to change something. In that case customize a copy in your app, then use it as any other template: just remember to pass the `:pagy` local set to the `@pagy` object. Here are the links to the sources to copy: