This project aims for Road to web3 Hackathon powered by Polygon

Related tags

Learning resource BlogStream
Overview

BlogStream

A blog site where users directly pay the writers for only what they are reading

This is a project created for Road to Web3 hackathon by WebXDAO (Team1) - Sreekar Sarvepalli, David Kim, Abhinav MV

🚀 Quick Start

📄 Clone or fork BlogStream:

git clone https://github.com/WebXDAO/BlogStream.git

💿 Install all dependencies:

cd BlogStream
npm install

✏ Rename .env.example to .env in the main folder and provide your appId and serverUrl from Moralis (How to start Moralis Server) Example:

NEXT_PUBLIC_APP_ID = xxxxxxxxxxxx
NEXT_PUBLIC_SERVER_URL = https://xxxxxx.grandmoralis.com:2053/server

🚴‍♂️ Run your App:

npm run dev
Comments
  • Create nextjs and tailwindcss app, and working on creating layout

    Create nextjs and tailwindcss app, and working on creating layout

    Related Issue

    None.

    Closes: #

    Describe the changes you've made

    1. Setup Next.js and TailwindCSS
    2. Working on creating Layout(Footer and Header)

    Type of change

    What sort of change have you made:

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] Documentation update.
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [x] My code follows the guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [ ] I have commented on my code, particularly wherever it was hard to understand.
    • [ ] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

    Code of Conduct

    opened by hyomiTheTech 2
  • Dev contracts

    Dev contracts

    Related Issue

    • Information about the related issue

    Closes: #

    Describe the changes you've made

    Type of change

    What sort of change have you made:

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] Documentation update.
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [ ] My code follows the guidelines of this project.
    • [ ] I have performed a self-review of my own code.
    • [ ] I have commented on my code, particularly wherever it was hard to understand.
    • [ ] I have made corresponding changes to the documentation.
    • [ ] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

    Code of Conduct

    opened by AbhinavMV 1
  • Add 'How it work' section in landing page

    Add 'How it work' section in landing page

    Related Issue

    • Information about the related issue

    Closes: #

    Describe the changes you've made

    1. Create How it work section

    Type of change

    What sort of change have you made:

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] Documentation update.
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [x] My code follows the guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [ ] I have commented on my code, particularly wherever it was hard to understand.
    • [ ] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

    Code of Conduct

    opened by hyomiTheTech 1
  • Dev walletsection

    Dev walletsection

    Related Issue

    • Information about the related issue

    Closes: #

    Describe the changes you've made

    1. Create the wallet section of the landing page.

    Type of change

    What sort of change have you made:

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] Documentation update.
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [ ] My code follows the guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [ ] I have commented on my code, particularly wherever it was hard to understand.
    • [ ] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

    Code of Conduct

    opened by hyomiTheTech 1
  • David layout and hero

    David layout and hero

    Related Issue

    • Information about the related issue

    Closes: #

    Describe the changes you've made

    1. Move Layout component from _app.js page to index.js
    2. Create Hero section of Landing Page.

    Type of change

    What sort of change have you made:

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] Documentation update.
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [x] My code follows the guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [ ] I have commented on my code, particularly wherever it was hard to understand.
    • [ ] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

    Code of Conduct

    opened by hyomiTheTech 1
  • Dev dashboard

    Dev dashboard

    Related Issue

    Dashboard Setup

    • Information about the related issue

    Closes: #

    Describe the changes you've made

    Type of change

    What sort of change have you made:

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] Documentation update.
    • [x] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [x] My code follows the guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [x] I have commented on my code, particularly wherever it was hard to understand.
    • [x] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [x] I have added tests that prove my fix is effective or that my feature works.
    • [x] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

    Code of Conduct

    opened by AbhinavMV 1
  • fix: LinkedIn link to point to WebXDAO

    fix: LinkedIn link to point to WebXDAO

    Describe the changes you've made

    • Fix LinkedIn link to point to WebXDAO.
      • CC: @WebXDAO/core-maintainer

    Type of change

    What sort of change have you made:

    • [x] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] Documentation update.
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [x] My code follows the guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [ ] I have commented on my code, particularly wherever it was hard to understand.
    • [ ] I have made corresponding changes to the documentation.
    • [ ] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    I don't think this applies here.

    Code of Conduct

    opened by Panquesito7 0
  • [Fix]: Flowrate Calculations

    [Fix]: Flowrate Calculations

    Related Issue

    • Information about the related issue

    Closes: #

    Describe the changes you've made

    1. Fixed flow rate calculations.
    2. Add title on the tabs for all pages.
    3. Add hardhat deploy and test scripts.

    Type of change

    What sort of change have you made:

    • [x] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [x] Documentation update.
    • [x] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [x] My code follows the guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [x] I have commented on my code, particularly wherever it was hard to understand.
    • [x] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [x] I have added tests that prove my fix is effective or that my feature works.
    • [x] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

    Code of Conduct

    opened by AbhinavMV 0
  • Add export script for the deployment on fleek.co

    Add export script for the deployment on fleek.co

    Related Issue

    • Information about the related issue

    Closes: #

    Describe the changes you've made

    1. Add "export" script for deployment on fleek.co.

    Type of change

    What sort of change have you made:

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] Documentation update.
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [x] My code follows the guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [ ] I have commented on my code, particularly wherever it was hard to understand.
    • [ ] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

    Code of Conduct

    opened by hyomiTheTech 0
  • Dev mediaquery

    Dev mediaquery

    Related Issue

    • Information about the related issue

    Closes: #

    Describe the changes you've made

    1. Add URLs to the anchor tags.
    2. Add contents to the articles and testimonials.
    3. Add CSS animations to cards.

    Type of change

    What sort of change have you made:

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] Documentation update.
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [x ] My code follows the guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [x] I have commented on my code, particularly wherever it was hard to understand.
    • [ ] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

    Code of Conduct

    opened by hyomiTheTech 0
  • Dev latestarticles

    Dev latestarticles

    Related Issue

    • Information about the related issue

    Closes: #

    Describe the changes you've made

    1. Added 'Latest Articles' section.
    2. Added 'FAQ' section.
    3. Added 'Testimonial' section.

    Type of change

    What sort of change have you made:

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] Documentation update.
    • [ ] This change requires a documentation update

    How Has This Been Tested?

    Checklist

    • [x] My code follows the guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [x] I have commented on my code, particularly wherever it was hard to understand.
    • [ ] I have made corresponding changes to the documentation.
    • [ ] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] Any dependent changes have been merged and published in downstream modules.

    Screenshots (if applicable)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

    Code of Conduct

    opened by hyomiTheTech 0
Owner
WebX DAO
We're rebranding to WebX DAO. @Web3Community will continue simple project
WebX DAO
GitHub https://blog-stream.vercel.app/
Hemsida för personer i Sverige som kan och vill erbjuda boende till människor på flykt

Getting Started with Create React App This project was bootstrapped with Create React App. Available Scripts In the project directory, you can run: np

null 4 May 3, 2022
Kurs-repo för kursen Webbserver och Databaser

Webbserver och databaser This repository is meant for CME students to access exercises and codealongs that happen throughout the course. I hope you wi

null 14 Jan 3, 2023
A web3 starter project using Typescript, Hardhat, ethers.js and @web3-react

Starter React Typescript Ethers.js Hardhat Project This repo contains a Hardhat and React Dapp starter project. The React Dapp in the frontend dir of

ChainShot 39 Dec 31, 2022
This terminal application aims to help new developers to quickly create ready to play applications, powered by Supabase.

Welcome to Create Supabase App ?? ⚡️ ?? Supabase is an open-source Firebase alternative. This terminal application aims to help new developers quickly

Raphaël Moreau 17 Nov 8, 2022
A simple project to learn more about developing smart contracts on polygon.

polygon-books-hardhat A simple project to learn more about developing smart contracts using Solidity. Local Development Environment Setup Install all

Lionel Bersee 1 Jan 25, 2022
Web3-citizens-app - React application based on smart contract using web3 and MetaMask extention.

Citizens App (web3-react-redux) React application based on smart contract using web3 and MetaMask extention. Start the applicarion Recomend to install

Denys Voloshyn 3 Aug 25, 2022
(🔗, 🌲) Web3 Link Tree is a free & open-source alternative to Linktree built with React.js, Next.js, Tailwind and Web3-React

Getting Started Read the detailed guide here Customize Add your name, wallet address, social media links and more in config.ts Images Save images to t

Naut 35 Sep 20, 2022
🛠 Solana Web3 Tools - A set of tools to improve the user experience on Web3 Solana Frontends.

?? Solana Web3 Tools - A set of tools to improve the user experience on Web3 Solana Frontends.

Holaplex 30 May 21, 2022
Decentralized Twitter prototype built with Polygon, GraphQL, Next.js, Ceramic, Arweave, and Bundlr

Titter - Web3 Social chat beta as fuck ?? Built with Next.js, Arweave, Bundlr, Ceramic, GraphQL, & Polygon How it works This is a working prototype of

Nader Dabit 154 Dec 14, 2022
Small, typed, dependency free tool to round corners of 2d-polygon provided by an array of { x, y } points.

round-polygon Small, typed, dependency-free tool to round corners of 2d-polygon provided by an array of { x, y } points. The algorithm prevents roundi

Sergey Borovikov 10 Nov 26, 2022
SW DAOs open-source Polygon dApp frontend.

SW DAOs open-source Polygon dApp frontend. At SW DAO, we're committed to being the industry-leading provider of automated investing solutions and cryp

SW DAO 5 Jul 27, 2022
✨ An IRL tokenization platform to turn your hopes, dreams, and desires into fundable NFTs on the Polygon blockchain using Chainlink, IPFS, Moralis, and NFT.Storage.

GoFundYourself Getting funding for your passion project, needs or dream doesn't have to be a nightmare! check out our live demo on Netlify Let's Fundi

Brian H. Hough | brianhuff.eth 7 Dec 6, 2022
This Next.js app is designed to be used with the Figment Learn Pathways, to help developers learn about various blockchain protocols such as Solana, NEAR, Secret, Polygon and Polkadot!

???? What is learn-web3-dapp? We made this decentralized application (dApp) to help developers learn about Web 3 protocols. It's a Next.js app that us

t0nto 8 Oct 1, 2022
Svaasthy project - a part of the Electrothon-4.0 Hackathon

Svaasthy View the presentaton The problems we address... The covid-19 crisis is drawing attention to the already overburdened public health systems in

PAVITRA BEHARA 5 Jun 16, 2022
Our project for The Microsoft Azure Trial Hackathon on Dev.to

Moodflix your mood, our suggestions. ?? About Overview of our project We have started this project with the purpose of participating to the Microsoft

Emanuele Bartolesi 37 Dec 22, 2022
Monorepo project that shows the current weather data and weather forecast for next 7 days. Created from scratch to participate in a 14-days hackathon.

Climatic Monorepo project that shows the current weather data and weather forecast for next 7 days. Created from scratch to participate in a 14-days h

Luis Marsiglia 6 Jun 23, 2022
This simple project aims to connect to an API to fetch score data and display it on a LeaderBoard box, as well as provide the tool to submit a new score.

Leader Board: Hit the API! This simple project aims to connect to an API to fetch score data and display it on a LeaderBoard box, as well as provide t

Andrés Felipe Arroyave Naranjo 12 Apr 6, 2022
Project that aims to connect people interested in helping NGOs with open campaigns.

<b>BE HERO!</b> Technologies | Project | Layout | Getting started | How to contribute | License ?? Technologies This project was developed with the f

null 3 Sep 22, 2022
🚀 Blazing Fast S3 Powered CDN ✨ Powered By Fastify, S3 Buckets & Docker!

?? WasiCDN Blazing Fast S3 Powered CDN, Powered By Fastify, S3 Compatible Buckets & Docker! Core DockerHub: https://hub.docker.com/r/maximking19/wasic

Maxim 5 Aug 31, 2022