The team is now working on the WordPress Interactivity API. This unblocks the same UX Frontity framework enabled but directly in WordPress Core, fully compatible with the new Site Editor.
Infinite Scroll hooks stable version. With just a few lines of code, you can add now Infinite Scroll to your Frontity project. Thanks @orballo and @David for the implementation . Here you have a demo of how it works and how to implement it.
Support for Google Analytics 4. We have released a new version of the @frontity/google-analytics package with support for Google Analytics 4, while keeping the support for Universal Analytics.
It includes breaking changes, so if you are sending your own pageviews or events, make sure you migrate them following this guide before updating this package. If you are just sending the default pageviews, you shouldn’t worry.
AMP package (Work In Progress). We have released an initial version with some functionalities but it’s not ready to use yet. Once this issue is released, we can start testing it. You can follow the whole progress on its board. Issues already merged and released:
3673a228#687 Thanks @cristianbote! - Expose the render, template and App methods to override the built-in default with user-defined ones.
Patch Changes
49c0429c#729 Thanks @cristianbote! - Downgrade webpack-dev-middleware@3.7.2 which is the last known version that was not slow.
d6421f08#721 Thanks @DAreRodz! - Handle the case where the query param frontity_name is an array of strings.
63effecb#725 Thanks @cristianbote! - Expose head and scripts API on frontity namespace for ease of defining custom tags for the html document.
2f7169cb#720 Thanks @cristianbote! - Export CacheProvider from @frontity/core and use it to extract critical css into a custom style tag, needed for the @frontity/amp package.
@frontity/hooks@2.2.0
Minor Changes
31102365#429 Thanks @orballo and @DAreRodz for the amazing work! - Implements the brand new and long-awaited infinite scroll hooks collection, featuring useArchiveInfiniteScroll, usePostTypeInfiniteScroll and useInfiniteScroll. Feature Discussion
32c03d58#533 Thanks @orballo! - Adds isError boolean to infinite scroll hooks will be true when either the last post or the last page has failed to fetch.
Patch Changes
9bdf948b#476 Thanks @orballo! - Fixes a bug on the usePostTypeInfiniteScroll where the archive is not requested if we are loading the post type from SSR.
c702ab9f#575 Thanks @orballo! - Use state.source.subdirectory and state.source.postsPage to get the link of the post archive in usePostTypeInfiniteScroll.
464aa87f#575 Thanks @orballo! - Fix isLast value when last post returned isError.
31102365#429 Thanks @orballo! - Implements actions.router.updateState() which takes a browser state object as an argument and executes a window.history.replaceState() with that object and the current url.
31102365#429 Thanks @orballo! - Implements actions.router.updateState() which takes a browser state object as an argument and executes a window.history.replaceState() with that object and the current url.
Patch Changes
7d8d1af4#652 Thanks @DAreRodz! - Fix the order search and hash are used internally to generate links.
f7152d38#722 Thanks @cristianbote! - Add a dedicated AMP template for the @frontity/amp package, that strips away the scripts and keeps the critical css into a custom style tag
2f7169cb#720 Thanks @cristianbote! - Export CacheProvider from @frontity/core and use it to extract critical css into a custom style tag, needed for the @frontity/amp package.
31102365#429 Thanks @orballo! - Fixes types for connect() with the new options parameter.
f7152d38#722 Thanks @cristianbote! - Add a dedicated AMP template for the @frontity/amp package, that strips away the scripts and keeps the critical css into a custom style tag
63effecb#725 Thanks @cristianbote! - Expose head and scripts API on frontity namespace for ease of defining custom tags for the html document.
7e701d57#717 Thanks @michalczaplinski! - Update the value of link in actions.fetch if there’s an internal redirection.
32c03d58#533 Thanks @orballo! - Fix an array check by using Array.isArray instead of instanceof Array.
804f19fe#686 Thanks @michalczaplinski! - Change how libraries.source.normalize|parse|stringify used inside of actions.source.fetch(). From now on, they are not imported from their module but received from the libraries parameter of actions.source.fetch.