0% found this document useful (0 votes)
38 views3 pages

SOW For Timeline

The document outlines tasks for improving various aspects of a website and builder platform, including payment integration, API testing, UI changes, analytics functionality, profile customization, user management features, and security testing.

Uploaded by

Job Guru
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
38 views3 pages

SOW For Timeline

The document outlines tasks for improving various aspects of a website and builder platform, including payment integration, API testing, UI changes, analytics functionality, profile customization, user management features, and security testing.

Uploaded by

Job Guru
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

1.

Website -

● The Stripe payment gateway is working fine but its functionality needs to be
embedded.
● Have to implement and test the Shiprocket API via email.
● A 11 pointer list of changes with minor text and formatting changes mentioned
in the excel sheet shared with you.

2. Builder -

● A fb like full screen page with our logo needs to come before everything loads
in the background for the builder (after login). As soon as everything loads this
full page disappears and the users can see our builder.
● After login into the builder, it doesn't load the builder due to the repetition of
the url. So we need to check and make sure there’s no broken link or any other
problems with the URLs.
● The animation of graphs is not happening on the builder, so we need to sort
that. The builder is a theme that we’ve purchased and the animation does
happen on that.
● Toastify triggers (notifications) needs to be created and implemented across
the builder. This functionality needs to work whenever there’s a new
section/information added or deleted or modified in the builder.
● Date range section of the analytics section. The data doesn’t change as per the
range.
● 2-3 graph element changes in the analytics section.
● Video functionality needs to have mute/unmute and replay function like
Instagram.
● Few edit link cards categories need to be added and edited.
● A detailed list of changes for each page of the builder mentioned in the excel
sheet shared with you.
● Web responsiveness + Cross browser testing + Cross device testing

3. Know Profile -

● This profile has been already created within the builder. We need to call it on a
separate page with a custom URL with that DIV in the page.
● We need to add finesse in the final profile of the user. Especially the footer.
● The functionality of save cards needs to work. It should create a .vcf file and save
it in the contact app. I can share a reference for y'all to check.
● There a page that comes after the save contact function to share their details
back as an email. We need to format that page as well as in the email we need
a functionality to let users save the data as a .vcf file again.

4. Manage.know.cards panel-

● The Pagination issue of the panel needs to be sorted. As of now it doesn’t go to


page-2 and all the fields load in one page.
● Server setup for SSL.
● Certain functionality additions/removal of the creating user function in regards
with mandatory details or the user type. There will be 2 users i can add - Single
user or a group user.
● Functionality of coupon codes/ free trial for users.

5. Corporate panel -
● This panel will also share the same URL as manage.know.cards.
● This panel is essentially for the corporate clients to add their group users. These
are some of the functionalities (though let’s have a detailed discussion on this) -
○ Corporate users can upload an excel file that creates users on our
platform just with that excel file.
○ They can create internal groups of people within this panel in different
categories.
○ Then the corporate user can define which fields they want to lock and
provide a data value for each of those fields. Essentially making different
rules for each group so the users within the group can only enter the
fields in their personal profiles that aren't locked.
○ The master user can also download all of the individual profile analytical
data as one excel file.
● This needs to be built for the backend. We will use the frontend design and
code from the theme we’ve purchased.
● Imagine this to be broadly a corporate user login that lets the user add people
and create groups along with restricting or non-restriction of the profile data
fields.

6. Signup, password reset and some other email triggers need to be


implemented for the verification, and account related details.
7. When you compile the files, there are some Medium and Low project
vulnerabilities that need to be sorted out.

9. Chip cards testing and fixing if any. The individual profile of a user can be
shared in multiple ways - QR Code, URL and a chip enabled card that loads the
profile.

10. Uploading on AWS + Testing + bug fixing + making it finally live.

Also, there might be some very small UI related points that I might have missed or will
realize once we close all the above points. Just requesting you to keep that also in
mind.

You might also like