Overview
Custom development refers to cosmetic edits to the guest website that require custom code changes by a Web Developer. This can include adding extra content rows on the homepage to include an app download callout, a description of membership perks, a different layout for pages, or a complete rebrand of the page.
What changes can be made to the guest website?
The guest website tool has 3 different themes to choose from as a base. All requested modifications build on one of these themes. Below is a list of possible modifications and associated considerations.
All Themes
The guest website does support Google and Adobe Fonts.
Fonts that were bought from a Font foundry or where custom designed the client might need to provide font files (.tff, .woff, .woff2, etc.) in order for the fonts to render properly on the guest website.
Navigation Bar
Add logo (CSS can change logo size and alignment). In the HTML the logo can be linked to the client’s main website.
Add and remove links by using jQuery. We cannot remove the the navigation bar because once a guest logs in then there is no way for the guest to log out.
Add language translations to the guest website or remove the language selection dropdown
Jumbotron
Remove heading text via CSS or change it through jQuery or the Guest Website UI
Can add a banner image that repeats on every page of the guest website. The mobile view will automatically focus on the center of the image.
To optimize banners for mobile please provide a 900 x 900 image.
Alternatively, it is better to design a banner with layers that automatically become mobile responsive.
Can use a custom font for the heading.
Homepage Body
You can additional content rows like reminders to download the app, graphic overview of the loyalty program, loyalty benefits etc. These rows can either be only on the homepage or repeated on each of the internal pages.
The homepage body cannot include form fields. This requires integrations work.
Internal Page Body
The body will change content based on the page.
Internal pages generally have a panel. The panel design and form style can be changed via CSS.
jQuery can be used to add content before or after the panel.
We can also edit error messages.
Footer
Footer code is repeated on all pages.
The footer cannot include elements like a sign up fields. This required integrations work.
Browser
Favicon can be changed.
eGift Guest Website
The eGift card selector or carousel cannot be edited to change how the eGift cards are displayed.
The navigation bar is turned off by default but it can link back to the loyalty homepage.
We cannot add additional form fields like checkboxes.
NOTE: It is not possible to add new pages or new functionalities to the guest website. This type of request would be considered a feature request that would need to be prioritized and require development work from the Paytronix engineering team.
If you need the guest website to look or function a certain way that is different from the above listed modifications, then the recommended approach is to work with a 3rd party or in-house development team to develop a custom website and integrate it to Paytronix.
How can I request Paytronix Custom Development services for my guest website?
Please contact [email protected] for information on custom development services for your guest website. The process for requests is below.
1. Provide Mock Up
Please provide a mockup of how the guest website should look like. The mockup should include the mobile layout as well as body copy text. We will do our best to match the mockup.
You can send assets to us in 2 ways:
Design files preferably
.psdor photoshop files.All individual image assets and custom font files in a zipped folder.
2. Scoping/Proposal
When the team has received all of the required information, there will be a scheduled call to review the requirements. The technical feasibility of the requested changes will be determined and confirmed on this call. There will then be a 5 business day period during which the scope of the project will be determined.
The development team will then provide an estimate for the level of effort required to make this change. If the estimate of the work requires the project to be billed, you will receive a statement of work outlining the requirements, changes to be made, the timeline, and the number of revisions that are accounted for in the process.
The statement of work needs to be signed before any work can begin.
3. Development
If the client has a test environment like Train, then the Configuration team will work on all edits in Train. Please note that egift set up, registration forms, etc. are different on each server. Please focus on cosmetic and layout edits.
Once the changes are complete, the client is should provide a list of feedback in an email or during the feedback meeting. Clients will be limited to 2 major revision rounds.
If the guest website is ready then the Configuration team needs written approval to move the guest website package over to prod. During this process all links pointing to Train will be switched over to Production.
4. Launch
Once the last revision has been signed off and approved, the development team will transfer the page from the lower train environment to production. It is responsibility of the client to do a final round of review on the production version of the page to ensure the website is visually and functionally working as approved in the lower environment.
For any additional edits that improve customer communications or alleviates customer confusion please email s[email protected] for these edits.