-
-
- )
-}
-
-export default Browser
diff --git a/landing/components/button.tsx b/landing/components/button.tsx
deleted file mode 100644
index d67a66ac..00000000
--- a/landing/components/button.tsx
+++ /dev/null
@@ -1,16 +0,0 @@
-import * as React from 'react'
-
-type props = {
- onClick?: (event: any) => void
- children?: any
-}
-
-const Button: React.FC
- {props.children}
-
- )
-}
-
-export default Card
diff --git a/landing/components/content.tsx b/landing/components/content.tsx
deleted file mode 100644
index 49a2cbd4..00000000
--- a/landing/components/content.tsx
+++ /dev/null
@@ -1,18 +0,0 @@
-import * as React from 'react'
-
-type props = {
- navigation?: boolean
- children ?: any
-}
-
-const Content: React.FC
- {props.children}
-
- )
-}
-
-export default Content
diff --git a/landing/components/decor.tsx b/landing/components/decor.tsx
deleted file mode 100644
index 5982a2b3..00000000
--- a/landing/components/decor.tsx
+++ /dev/null
@@ -1,22 +0,0 @@
-import * as React from 'react'
-
-const Decor: React.FC = () => {
- return (
-
-
-
-
-
- )
-}
-
-export default Decor
diff --git a/landing/components/footer.tsx b/landing/components/footer.tsx
deleted file mode 100644
index fae2c478..00000000
--- a/landing/components/footer.tsx
+++ /dev/null
@@ -1,41 +0,0 @@
-import Link from 'next/link'
-import * as React from 'react'
-
-type props = {
- bg?: string
- children?: any
-}
-
-const Footer: React.FC
-
-
- )
-}
-
-export default Logo
diff --git a/landing/components/open-payments-button.tsx b/landing/components/open-payments-button.tsx
deleted file mode 100644
index 976a5e60..00000000
--- a/landing/components/open-payments-button.tsx
+++ /dev/null
@@ -1,71 +0,0 @@
-import React, { useEffect, useState } from 'react'
-
-type LogoProps = {
- size?: number
-}
-
-export const OpenPaymentsLogo = ({size}: LogoProps) => {
- return (
-
- )
-}
-
-type Props = {
- className?: string
- verb: string
-}
-
-const OpenPaymentsButton: React.FC
-
-
- )
-}
-
-export default Phone
diff --git a/landing/next-env.d.ts b/landing/next-env.d.ts
deleted file mode 100644
index 4f11a03d..00000000
--- a/landing/next-env.d.ts
+++ /dev/null
@@ -1,5 +0,0 @@
-///
-
- )
-}
-
-const Divider: React.FC = () => {
- return (
-
- )
-}
-
-type cardProps = {
- children?: any
-}
-
-const Card: React.FC
- {props.header}
-
- {props.children}
-
- {props.children}
-
- )
-}
-
-type colourBoxProps = {
- colour: string
- name: string
- padding?: string
-}
-
-const ColourBox: React.FC
-
-
- )
-}
-
-const Home: NextPage = () => {
- const router = useRouter()
- return (
-
- {props.name}
-
-
-
- )
-}
-
-export default Home
diff --git a/landing/pages/index.tsx b/landing/pages/index.tsx
deleted file mode 100644
index 866d3280..00000000
--- a/landing/pages/index.tsx
+++ /dev/null
@@ -1,81 +0,0 @@
-import React from 'react'
-import { NextPage } from 'next'
-// import { UsersService } from '../services/users'
-import { Button, Logo, Decor, Phone, Browser, Footer } from '../components'
-import { useRouter } from 'next/router'
-
-const Home: NextPage = () => {
- const router = useRouter()
- return (
-
-
-
- Brand guidelines
-
-
- Representing the
Open Payments brand -
-
- Open Payments brand -
-
-
-
-
-
-
-
-
-
-
-
-
-
- Do not use the Open Payments mark or any variant of the Open Payments mark in conjunction with the overall name of your application, product, service, or website.
- Do not alter or use the Open Payments mark in a way that may be confusing or misleading, and never use Open Payments branding as the most prominent element on your page.
-
-
-
-
-
-
- 
-
-
-
- Standard lockup
-
- -
- The standard lockup can be used in slide decks and blog posts.
-
- Whenever possible, the logo should be represented as a horizontal lockup with a full color logomark and #1E3250 or solid white logotype.
-
-
-
- 
-
-
-
- Logomark
-
- -
- When there is limited vertical and horizontal space, the logomark can be used by itself without the logotype. -
-
-
-
-
-
-
-
- Logo
-
- -
- The Open Payments logo consists of 6 base colours, each with a light secondary variant. -
-
-
-
-
-
-
-
-
-
-
-
- Emphasis
-
- -
- There are two auxilary colours which are used for emphasis or text. -
-
- These guidelines are to be used as a reference point when implementing an Open Payments payment button within your app or website.
- The Open Payments payment button must always use the Open Payments specification when making payments.
-
-
- -
- All Open Payments payment buttons within your app or website must adhere to our brand guidelines, which include, but are not limited to, the following requirements:
-
-
-
-
-
-
- 
-
-
-
- Specification
-
- -
- Open Payments logo size 24 dp.
- Minimum width 90 dp, and minimum height 48 dp.
- Minimum 8 dp margin on all sides of the button.
- Minimum 8 dp padding between elements inside the button.
- Content must be vertically centered.
-
-
-
-
-
-
-
-
-
- Contrast
-
- -
- The button colour must contrast with the background colour of the surrounding area.
- Use white buttons on dark or colourful backgrounds.
- Use black buttons on white or light background.
-
-
-
-
-
-
- Rubik
- Regular
- 20 - -
- - Regular
- 20 - -
- Button
-
-
- Text
-
- -
- The text on the button must be a single, title case, verb. For example, Pay, Tip, Donate, Subscribe, Buy, etc.
- The text should always be to the right of the logo.
-
- Although Open Payments payment buttons must adhere to the above brand guidelines, specific implementations may vary to fit into the branding or style of your app or website, which can include:
-
-
-
-
-
-
-
-
- Shape
-
- -
- Variations in the button's corner radius and shape, to match other elements on the page. Note the larger width and corner radius. -
-
-
-
-
-
- Elevation
-
- -
- Variations in the elevation or shadow of the button. Note the higher elevation. -
-
-
-
-
-
- State
-
- -
- Variations specific states of the button, such as active, hover, or focus. Note the change in elevation with the various states. -
-
- The Open Payments pay mark should be used when displaying Open Payments as a payment option in a payment flow.
-
-
-
-
-
-
- 
-
-
-
- Mark
-
- -
- Do not change the color or weight of the mark's outline or alter the mark in any way. Use only the mark provided by Open Payments. -
-
-
-
-
-
-
-
-
-
-
-
-
- navigate_next
-
- Open Payments
-
-
-
-
-
-
- 
-
- navigate_next
-
- Generic Pay
-
-
-
-
-
- 
-
- navigate_next
-
- **** 4242
-
- Size
-
- -
- If needed, adjust the height of the mark to match other brand identities displayed in your payment flow. Always maintain the minimum clear space of 8 dp on all sides of the mark. -
-
-
- )
-}
-
-export default Home
diff --git a/landing/postcss.config.js b/landing/postcss.config.js
deleted file mode 100644
index 33ad091d..00000000
--- a/landing/postcss.config.js
+++ /dev/null
@@ -1,6 +0,0 @@
-module.exports = {
- plugins: {
- tailwindcss: {},
- autoprefixer: {},
- },
-}
diff --git a/landing/public/Browser.svg b/landing/public/Browser.svg
deleted file mode 100644
index ed9b7bfa..00000000
--- a/landing/public/Browser.svg
+++ /dev/null
@@ -1,19 +0,0 @@
-
diff --git a/landing/public/CARD Mark.svg b/landing/public/CARD Mark.svg
deleted file mode 100644
index b6802e99..00000000
--- a/landing/public/CARD Mark.svg
+++ /dev/null
@@ -1,5 +0,0 @@
-
diff --git a/landing/public/Open_Payments_Brand_Assets.zip b/landing/public/Open_Payments_Brand_Assets.zip
deleted file mode 100644
index 47577afe0c7bdd172c84665942cdfac23218bcff..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001
literal 11668
zcmb7~WpEu`lBRXVk|m4LVrFJ$u$Y;zn3
-
- {/* SCREEN 2 */}
-
-
-
- Open Payments
-
-
- An inter-wallet
payments protocol -
- payments protocol -
-
-
-
- or continue reading arrow_downward
-
-
-
- {/* SCREEN 3 */}
-
-
-
-
-
- For applications
-
-
- Open Payments allows easy integration into new or existing applications that require the use of a digital wallet.
-
-
- Facilitating the discovery, setup and authorization of payments between different wallet providers; so you don't have to. -
- -
- Facilitating the discovery, setup and authorization of payments between different wallet providers; so you don't have to. -
-
-
-
-
-
-
-
-
- For wallets
-
-
- Open Payments allows for seamless, secure, easy inter-wallet payments.
-
-
- Facilitating the discovery, setup and authorization of payments with other wallet providers; so you don't have to. -
- -
- Facilitating the discovery, setup and authorization of payments with other wallet providers; so you don't have to. -
-
-
-
-
-