Releases: sharetribe/ftw-hourly
v12.1.0
Changes v12.1.0
- [fix] AuthenticationPage.duck.js: had wrong asset name for terms-of-service.json
#228
Updates from upstream (FTW-daily v10.1.0)
- [change] remove the
background-colorfrom images (to allow opacity) and don't stretch small markdown images.
#1590 - [change] improve error handling possibilities on PageBuilder.
#1589 - [fix] AuthenticationPage.duck.js: had wrong asset name for terms-of-service.json
#1588 - [change] P.js: remove the requirement for mandatory children.
#1587
v12.0.0
Changes v12.0.0
Updates from upstream (FTW-daily v10.0.0)
-
[add] This adds support for page asset files that can be created in Console. These asset files are
taken into use for- LandingPage
- TermsOfServicePage
- PrivacyPolicyPage
- AboutPage
- and other static pages can also be created through Console (they'll be visible in route:
/p/:asset-name/)
This adds rendering for page assets.
Rendering flow
The rendering happens in these steps (for LandingPage):
- LandingPage.duck.js defines that it needs page asset called
content/pages/landing-page.json - src/ducks/hostedAssets.duck.js fetches that asset and saves it to Redux store
- It also calls src/util/data.js, which has code to denormalize the asset data
(assetImage entities are by default in included part of the returned asset).
- LandingPage.js gets pageAssetsData as props and passes the rendering to a new component: PageBuilder
- PageBuilder reads the content of the page asset: sections and meta
- "sections" (data that goes inside
<body>) - "meta" (which is data that goes inside
<head>)
- "meta" information is passed to
<StaticPage>component, which is moved under PageBuilder directory. - SectionsBuilder takes "sections" as props and continues rendering the UI components.
- Different types of section components
- Block components (block could also contain fields)
- Field components
In addition to the landing page, there are similar renderings made for TermsOfServicePage and PrivacyPolicyPage
For generic page assets, the routing now contains CMSPage component (with route: /p/<page-asset-id>/)
Markdown
Block component can contain a key text, which has markdown content.
This solution uses Unified and it's plugin ecosystem to render that markdown as React components.
Unified/rehype is also used by references like Gatsby.
We use these versions at this point:
"rehype-react": "^6.2.1",
"rehype-sanitize": "^4.0.0",
"remark-parse": "^9.0.0",
"remark-rehype": "^8.1.0",
"unified": "^9.2.2",
More Docs
Learn more about Pages:
- Introducing Pages
- How to try Pages in your Demo marketplace
- Content management in Flex
- Headless content management
- How to take Pages into use in an existing Flex marketplace
- How the templates render content pages using the PageBuilder
- Tutorial: modify the look & feel of your Pages-powered landing page
- How to create a blog-style library of articles using Pages
- How to customise a Section, Block or Field using options
Taking an update from upstream
This is causing a major version change - and you need to check the code in this PR if you experience merge conflicts. You also need to make choices about whether or not you keep your current pages (e.g. LandingPage) or start using Pages for that too.
Most of the new code changes of this PR are inside:
src/containers/PageBuilder/- The content of
src/containers/LandingPage/is swapped to use the Pages feature- You need to decide if you want to keep your existing LandingPage design or start using PageBuilder (and Page Editor in Console)
- The same applies to
src/containers/TermsOfSerivcePage/src/containers/PrivacyPolicyPage/src/containers/AboutPage/
- There are a couple of other components that also were modified a bit. E.g. Page, Footer
- AspectRatioWrapper component was added to FTW-daily too
- Util files updated or added:
- data.js
- sanitize.js
- seo.js
- string.js
- types.js
- AuthenticationPage was refactored and it had to read Terms of Service data from the new page asset.
- Server: fetching of page asset data was taken into account there.
v11.1.0
Changes v11.1.0
Updates from upstream (FTW-daily v9.1.0)
-
[change] Norway's stripe config should use NOK, not EUR.
#1579 -
[delete] Update README.md after changes in [#1555].
#1569 -
[change] Added some dependabot updates earlier: passport-0.6.0, loader-utils-2.0.4,
decode-uri-component-0.2.2
Note: Passport-0.6.0 changed login and logout parameter list. -
[change] Update Browserlist db / caniuse-lite.
#1567 -
[change] Update minimum Node version to >=16.18.0. (v14.15 had problems with some libs and v14
support ends soon.) #1566 -
[delete] Remove unnecessary polyfills (dependencies might still use these)
- array-includes
- array.prototype.find
- object.entries
- object.values
- Number.parseFloat, Number.parseInt, Number.isNaN
-
[add] Add the cross-env package to better support Windows command prompts
#1555
v11.0.2
v11.0.1
Changes v11.0.1
Updates from upstream (FTW-daily v9.0.1)
-
[fix] Use sharetribe-scripts v6.0.1. Fixes for
- GENERATE_SOURCEMAP = false
- async Redux Thunks
-
[fix] Add cookie_flags and relax google analytics domain
#1538 -
[fix] the import of customMediaQueries.css was somehow missed with these components:
FieldReviewRating, SearchFiltersSecondary and TopbarMobileMenu.
#1537
v11.0.0
Changes v11.0.0
This is a major release since it includes a major update to sharetribe-scripts aka our fork of
Create React App.It includes major update to Webpack (v4 > v5) and PostCSS (v7 > v8). These caused
some advanced CSS syntax to be invalid - and therefore some changes must be done to CSS files.
- CSS Property Sets are deprecated and the related file is removed from the codebase
- Custom media queries file need to be imported into all the files, that use them.
Read more from PR: sharetribe/ftw-daily#1531
Updates from upstream (FTW-daily v9.0.0)
-
[change] sharetribe-scripts is updated to v6.0.0. This causes a new major release for FTW
templates. Because most of the CSS files need to be updated!
#1531 -
[change] ImageCarousel uses react-image-gallery. It renders all the images early on and supports
touch swipes. #1529 -
[fix] Fixing a small typo. #1518
v10.6.1
v10.6.0
Changes v10.6.0
NOTE: There were some invalid characters in the CSP file. Use v10.6.1 instead.
Updates from upstream (FTW-daily v8.6.0)
v10.5.0
Changes v10.5.0
-
[add] Add support for hosted translations.
https://www.sharetribe.com/docs/ftw/hosted-translations/- This PR fetches "content/translation.json" from a new Asset Delivery API. The file is editable through the Flex Console.
- It also adds all the missing translation keys to existing non-English translation files. This
means that those files might now include messages in English.
Read more from the pull request in FTW-daily's repo: #1510
-
[delete] Remove old unused translation keys.
v10.4.1
Changes v10.4.1
- [fix] FieldDateInput: input font-size must be min 16px for mobile.
EditListingPage.duck: fix image upload (dublicate images shown).
#186
Updates from upstream (FTW-daily v8.4.1)
- [fix] Portal version of Modals couldn't use 100vh on mobile Safari. Safari changes the window's
height based on if the location bar is squeezed or not (and that depends on scroll-effect).
#1501 - [fix] Setting multiple environment variables in Windows requires using the set command before each
individual variable. Updated the 'for windows users' section in documentation.
#1491 - [add] Code comment about "REACT_APP" prefix in environment variables.
#1492