https://github.com/amazeelabs/silverback_campaign_urls

https://github.com/amazeelabs/silverback_campaign_urls

Last synced: about 2 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/amazeelabs/silverback_campaign_urls
• Owner: AmazeeLabs
• Created: 2023-06-08T06:57:27.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-09-09T12:00:58.000Z (4 months ago)
• Last Synced: 2024-09-09T14:16:48.222Z (4 months ago)
• Language: PHP
• Size: 30.3 KB
• Stars: 0
• Watchers: 6
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md

Awesome Lists containing this project

README

        
# Silverback campaign urls

The _Silverback campaign urls_ module allows the Drupal admins to create

campaign urls. These are basically redirects that have no restriction for the

source and the destination fields, meaning that the admin can input any kind of

strings into them.

These campaign urls are stored as Drupal entities, and they can be retrieved

using graphql in a Gatsby app for example. An example can be found in the

silverback-gatsby app (check the gatsby-node.ts file).

The endpoint to administer these redirects is

_/admin/config/search/campaign_url_

### Gatsby integration

The modules contains a schema extension plugin that can be enabled on the

GraphQL server. This schema extension contains a new GraphQL type called

**CampaignUrl** which will be added to the schema when the extension is enabled

on the GraphQL server. When this is done, the **gatsby-source-silverback** npm

package will fetch these entities and create redirects for them.

Usually, in the Gatsby app, there should be an integaration with a sepcific

hosting provider, like **gatsby-plugin-netlify** for netlify which should create

the redirects in a specific file and format.