7b3a0c6863
no issue - During the one click subscribe flow, the outboundLinkTagging should affect whether we send a history or not to the signup endpoint. But for internal history this is the members_track_sources setting. This happens in the backend normally. - Do not send a (constructed) history to external sites (= one click subscribe flow in recommendations) if outboundLinkTagging is false - Do always send a history internally for local signups (backend handles whether to store it based on the members_track_sources setting that is currently not exposed in the frontend). The history is not built if this setting is disabled, but we could have an old history entry if this setting was enabled in the past. |
||
|---|---|---|
| .. | ||
| src | ||
| .env | ||
| .env.development.local.example | ||
| .eslintignore | ||
| .yarnrc | ||
| jsconfig.json | ||
| package.json | ||
| README.md | ||
| vite.config.js | ||
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.
Basic Setup
This section is mostly relevant for core team only for active Portal development. Always use the unpkg link for testing/using latest released portal script.
- Run
yarn start:devto start Portal in development mode - Open http://localhost:3000 to view it in the browser.
- To use the local Portal script in a local Ghost site
- Update
config.local.jsonin Ghost repo to add "portal" config pointing to local dev server url as instructed on terminal. - By default, this uses port
5368for loading local Portal script on Ghost site. It's also possible to specify a custom port when running the script using ---port=xxxx.
- Update
Available Scripts
In the project directory, you can also run:
yarn start
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Start the portal server when developing Ghost by running Ghost (in root folder) via yarn dev --all or yarn dev --portal. This will host the portal JavaScript files, and makes sure that Ghost uses these locally hosted assets instead of the ones from the CDN.
yarn build
Creates the production single minified bundle for external use in umd/portal.min.js.
yarn test
Launches the test runner in the interactive watch mode.
Publish
Run yarn ship to publish new version of script.
yarn ship is an alias for npm publish
- Builds the script with latest code using
yarn build(prePublish) - Publishes package on npm as
@tryghost/portaland creates an unpkg link for script at https://unpkg.com/@tryghost/portal@VERSION
(Core team only)