History

Steve Larson 22fcd21fbb Fixed Portal honeypot field (#20825 ) ref INC-97 ref https://github.com/TryGhost/Ghost/issues/20767 - finishes wiring up the honeypot fied - updates state handing to properly set the value - maintains honeypot field across page changes within portal There isn't a single previous commit to point to here since they didn't get squashed. We added a honeypot field to help mitigate bot signup activity. It's hidden, and if filled out, we can anticipate it's a bot. Right now this just logs to Ghost while we collect data.		2024-08-26 22:51:57 +00:00
..
src	Fixed Portal honeypot field (#20825 )	2024-08-26 22:51:57 +00:00
.env	Moved Portal to `apps/`	2023-06-16 13:37:58 +02:00
.env.development.local.example	Moved Portal to `apps/`	2023-06-16 13:37:58 +02:00
.eslintignore	Moved Portal to `apps/`	2023-06-16 13:37:58 +02:00
.yarnrc	Prevented git tags from being created for apps	2023-07-10 13:09:28 +02:00
jsconfig.json	Moved Portal to `apps/`	2023-06-16 13:37:58 +02:00
package.json	Update dependency jsdom to v24.1.3	2024-08-26 09:44:19 +02:00
README.md	Updated Portal readme with updated develop and release instructions (#20576 )	2024-07-10 10:05:41 +00:00
vite.config.js	Hidden "info" Vite output unless in CI	2023-11-15 10:11:22 +01:00

README.md

Portal

Drop-in script to make the bulk of Ghost membership features work on any theme.

Usage

Ghost automatically injects Portal script on all sites running Ghost 4 or higher.

Alternatively, Portal can be enabled on non-ghost pages directly by inserting the below script on the page.

<script defer src="https://unpkg.com/@tryghost/portal@latest/umd/portal.min.js" data-ghost="https://mymemberssite.com"></script>

The data-ghost attribute expects the URL for your Ghost site, which is the only input Portal needs to work with your site's membership data via Ghost APIs.

Custom trigger button

By default, the script adds a default floating trigger button on the bottom right of your page which is used to trigger the popup on screen.

Its possible to add custom trigger button of your own by adding data attribute data-portal to any HTML tag on page, and also specify a specific page to open from it by using it as data-portal=signup.

The script also adds custom class names to this element for open and close state of popup - gh-portal-open and gh-portal-close, allowing devs to update its UI based on popup state.

Refer the docs to read about ways in which Portal can be customized for your site.

Develop

Run Portal within the Ghost monorepo with:

yarn dev --portal

Alternatively, use yarn dev --all to load Portal and other supported apps/services, see dev.js for more information.

To run Portal in a standalone fashion, use yarn start and open http://localhost:3000.

Build

To create a production minified bundle in umd/portal.min.js:

yarn build

Test

To run tests in watch mode:

yarn test

Release

A patch release can be rolled out instantly in production, whereas a minor/major release requires the Ghost monorepo to be updated and released. In either case, you need sufficient permissions to release @tryghost packages on NPM.

Patch release

Run yarn ship and select a patch version when prompted
(Optional) Clear JsDelivr cache to get the new version out instantly (docs). Typically, you'll need to open https://purge.jsdelivr.net/ghost/portal@~${PORTAL_VERSION}/umd/portal.min.js and https://purge.jsdelivr.net/ghost/portal@~${PORTAL_VERSION}/umd/main.css in your browser, where PORTAL_VERSION is the latest minor version in ghost/core/core/shared/config/defaults.json (code)

Minor / major release

Run yarn ship and select a minor or major version when prompted
Update the Portal version in ghost/core/core/shared/config/defaults.json to the new minor or major version (code)
Wait until a new version of Ghost is released