megabyte0x / certified_cliche Goto Github PK

Describe the bug
For now the tab in the Brower looks like this and looks bad.
To Reproduce

Expected behaviour
It should name Certified Cliché.

Screenshots

Additional context
Can fix this using Head tag of the next.js. Can you assign me this?

Is your feature request related to a problem? Please describe.
In the figma design. Figma Page: home: select a certificate

Describe the solution you'd like
Add the Modal of transfer certificate using Material UI or Chakra UI

Additional context
I would love to work on this Feature.

Page - home page and transferred certificate

tracking in #15

description:

Create home page for the organisation flow. Which will contain unique certificate and events/ groups.
Please refer to the Figma file

Figma page name:

• 3.home page
• 7.transferred certificate

(both are the same page with different functionality)

The folder should be like follows:

js: components/components-name/components-name.js
css: components/components-name/components-name.module.css

Figma Link: click here

Description
=>

• We will be accepting the Excel sheet which can be in any format XLS or XLSX format from the user.
• The Sheet will contain the following attributes initially :-
  (Name, Description, ImageUrl, Receiver Address)
• We have to get this data in the JSON format so that we can upload it to the IPFS.

Task
=>
Make a function in the client directory in a separate directory utils in a file named excelToJSON.js, which will accept the Excel Sheet and convert it into the JSON Format.

You may refer here for some guidance.

Description
=> Smart Contracts are immutable hence they needed to be test thoroughly to avoid any type of security breaches after deployment.

Task
=> Write all the test cases possible to test both NFT.sol and NFTTransfer.sol smart contract in CONTRACT/test/sample-test.js

Adding dark mode to the website

Enhance the tech doc of the certified_cliche
Can you assign this task to me.

Page - Select Role

tracking in #15

description:

The user need to select the role when the web app appear. After that the user will be redirect to particular flow.

Figma page name:

• 1. select role

(both are the same page with different functionality)

The folder should be like follows:

js: components/components-name/components-name.js
css: components/components-name/components-name.module.css

Figma Link: click here

An alert pop-up which appears only if metamask is not installed
Why it's essential ?
Metamask extension installed in the web browser is very important in order to run this project.

I would like to work on this.

New design implementation

Description:

The design we're currently using is not going with our flow. (for flow read the readme file).
So we need to implement the new design.
We'll add multiple sub task, for better maintaining

Figma Link: click here

Sub-task

Pages (refer to Figma file)

• #22
• #18
• #20
• #21
• #23
• #26

Components

• #16
• #17
• #47
• #55

Please start with the components first, because every page uses it.
Don't redundant the common elements.

If you want I can make more sub-task or update the task.

Components - Footer

tracking in #15

description:
Create the bottom most purple area (Footer).

• The folder should be like follows:
  js: components/components-name/components-name.js
  css: components/components-name/components-name.module.css

Figma Link: click here

In the project README it's written that

Uncomment the LocalHost provider in client/pages/index.js

 const provider = new ethers.providers.JsonRpcProvider();

But this line of code is not in client/pages/index.js

It is actually in client/pages/home.js on line 34

Describe the bug
Change all the Current Card Code to the New Component. Here is a image of that. And pass props to display data.

Additional context
I would love to work on this!

Describe the bug
In the code some of the CSS is written in CSS sheets. Some of them are in inline using style tag and some of them are in Tailwind CSS. This causes problem for the developers where to find which CSS.

Expected behaviour
Should only use one style.

Can I change all the CSS to Tailwind and also add some utility classes to improve development experience?

Describe the bug
Committing contract details again and again.

Additional context
As per our conversation in Footer pull request I will make the necessary changes to it.

Dialog - select certificate

tracking in #15

description:

When you click on any certificate NFT from organisation role, this dialog should appear. From here the organisation can transfer the certificate to a participant.

Figma page name:

• 4.home page: select a certificate

(both are the same page with different functionality)

The folder should be like follows:

js: components/components-name/components-name.js
css: components/components-name/components-name.module.css

Figma Link: click here

Describe the bug
There is events/group component in the figma file, which is there in the many pages and should be a component.

Expected behaviour
The event/group card should be a component.

Additional context
I would love to work on this.

Description
=> As mentioned in the README, you have to paste the addresses, nftAddress and nftTransferAddress from the terminal after deploying the contract on LOCAL HOST or on TESTNET.

TASK
=> Automate the editing of the config.js file in CONTRACT directory.

Image for reference from the README

Page - events and transferred certificate

tracking in #15

description:

When the user clicks on the events/groups card from the home page, this page should be shown.
Please refer to the Figma file

Figma page name:

• 5.events
• 8.transferred certificate - events

(both are the same page with different functionality)

The folder should be like follows:

js: components/components-name/components-name.js
css: components/components-name/components-name.module.css

Figma Link: click here

Description
=>
The 2nd Screen of Figma which will login the user to the platform and will redirect him to the page (if it's organisation then Organisation dashboard [3rd Screen], if it's an applicant then Applicant Dashboard [9th Screen] ).

MORALIS SDK need to be use in this

Task
=> Make a function in client directory which will Login the user using Wallet Connect

You may refer here

Describe the solution you'd like

I want to add website name as the title of the page and also create a navbar in which the name of the website will be on left part and other navbar item would be on right side to make it more presentable

Describe the bug
The card is not a component although it will be used the multiple times in the website.

Expected behaviour
The card should be component.

I would love to work on this.

Adding Alert Pop-Ups before submitting the information of the certificate.

Benefits of adding alert prompt :-

• reduce chance of mistakes by user
• more accurate data will be collected

Components - Navbar + tabs

tracking in #15

description:
Create the top most purple area (nav bar).

• The folder should be like follows:
  js: components/components-name/components-name.js
  css: components/components-name/components-name.module.css

Figma Link: click here

Page - Received Certificate

tracking in #15

description:

This page is to show all the certificate of participates

Figma page name:

• 9.received certificate

(both are the same page with different functionality)

The folder should be like follows:

js: components/components-name/components-name.js
css: components/components-name/components-name.module.css

Figma Link: click here

Page - Create certificate

tracking in #15

description:

In this page the organisation can create certificate

Figma page name:

• 6.create certificate

(both are the same page with different functionality)

The folder should be like follows:

js: components/components-name/components-name.js
css: components/components-name/components-name.module.css

Figma Link: click here

Issue: On loading(running on localhost), the page shows:

Error: XMLHttpRequest failed: Unable to Connect to the Parse API.

This error persists, even after logging in using a test wallet. The pages do render, despite this error.

To Recreate:
Follow all the installation steps mentioned in the dev branch readme file.

Run on Localhost using any of the sample accounts provided by hardhat.

Node version: 16.14.2 -LTS
NPM - 8.5.0
Chrome Version: 100.0.4896.127

VSCode proxy settings in settings.json:

"http.proxy": "",
"http.proxyAuthorization": null,
"http.proxyStrictSSL": false,
"rest-client.excludeHostsForProxy": []

Screen Shot:

It seems to be a proxy issue. But even after disabling all the proxy settings(windows, VSCode), the error persists.

If anyone is able to recreate the issue, or even has no issues setting up in a similar environment, please reply in the thread.