-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a new page for #2PlaysAMonth initiative #109
Comments
Hey @atapas , so 2 plays a month home structure will be same as hackerplay section like about, judge, faq, winner |
You are right. |
Should I start with basic templating of the page with dummy data? |
Sure but use existing components as much as possible. |
yup! |
Ok I will setup and check the code too. |
Here are the changes:
with these text:
here is the content:
Change
Use these 3 points:
Use this:
|
The FAQ section @debjit and @Amyx000 Q: Why should I participate in the #2PlaysAMonth event? Q: Do I need to Register for #2PlaysAMonth? Q: Is it mandatory to create 2 plays? Q: What if my play review gets delayed? Q: Can we participate as a team? Q: Can I use anything other than React? Q: Can I submit my old React project as a play? Q: Can I submit code/project of someone else? Q: Is creating an issue for my PR a must? Q: Is sharing my journey on Twitter and LinkedIn of the #2PlaysAMonth a must? Q: When and How the #2PlaysAMonth result will be published? Q: Do I get prizes? Q: I have questions. Where can I ask them? |
hey @atapas to remove the winner from navbar, right now the navbar has the static data which from layout component, can I change it and make it dynamic by taking value from props so it can be used in any homepage by providing data for navbar? I can take home links from props so that I can remove the winner |
Yes, feel free to do any such improvements 👍 |
Ok👍 and to start working together someone has to push the 2023 folder with home.js first otherwise it will be conflict, should I just push the page first? |
Yes, let me merge that first |
Additionally,
|
Right. Let's take that as a separate issue @koustov . Can you please create one? We can work on that independently to this one. |
|
Yeap, the winners one can be taken separately but lets include the archive one here |
We don't have the archive page design.. so not keen on blocking this PR work. We can take archive also as separate issue so that we can ask someone to start with it in parallel. What say? |
I think we should create an dedicated index page later and create separate page template for hackathons. |
ok, Lets push it some other issue however I was suggesting to have archive section pretty much simple in nature, not archive page |
Merged. Now you both can distribute and do. Make sure to create all new branches from the 2-plays-a-month branch. |
@koustov can you plz create one with expectations? We can assign to a contributor. |
@debjit start editing the 2playsamonth/2023/home.js file ..and pull the latest commit |
OK sure! |
Design #1 |
Design #2 |
@atapas Here is the link that has the detailed design specs like colors, logo etc., Please start with the development work. |
It has been deployed. There is one issue with the OG image that we will fix as part of the next issue. |
Is your feature request related to a problem? Please describe.
We need to create a new initiative page for the event #2PlaysAMonth initiative.
The Motto:
Describe the solution you'd like
Right now the home page route sets to:
hackrplay/2022/home
. Create a new route called2playsamonth/2023/home
and the new home should have the followings:Additional context
Once this page is up and deployed, we need to link it from ReactPlay main page from a banner.
https://github.com/reactplay/activities/tree/2-plays-a-month
@atapas will add all updates here in this issue.
The text was updated successfully, but these errors were encountered: