a2z-hq / a2z-frontend Goto Github PK

I have used npm build to create a /build folder to deploy the React Application on github.io. But it doesn't seems to be working.

If anyone knows how to do this, kindly redo it and mention the steps here.
Thank you.

• Restructure the folder, make it cleaner for better URLs and access.
• Add a package.json file, if needed.
• Add linter.
• Add npm scripts, if required.

The Login container will have a state with username and password as variables.

It should contain 2 input elements (pass and text), submit button and a heading.

The state should be updated as the user types in the input boxes.

Please move it from To-do to in progress if you want to work on it

As in our previous master branch, the website had a header saying "Explore the ultimate collection" and sub head saying "What do you want to do today? Learn something new? Attend a meetup"

Goal: Add the header and sub header in a responsive manner to the Home-page component.

Now that we have everything setup. It's time to dive in and get developing! But before that we need to lay out the tasks in front of ourselves so that everyone in the team can choose what to do, without conflicts.

I will add some tasks now. You guys do the same. If there is any doubt, mention it and we shall resolve it via discussion.

From now, keep an eye on the project To-do for tasks.

The front-end site works fine in the homepage and navigating to other pages.
But while refreshing a page or entering into a sub-domain directly, it shows a 404 error.
I am not sure if this is a problem with React or React Navigation or Github pages.

First version shall be as plain as possible, but as Front-end Architects we are never satisfied with one design. Look for inspirations on dribbble, codepen etc and suggest some add ons that I can make to the website.

We need to make the stack we are going to use crystal clear to everyone. I am going to suggest a stack and you guys can give back your reviews and suggestions.

• React
• Pure CSS + Flexbox or Grid (no pre-processor)

I want to bring everyone to a common understanding of the stack that we will be using. So we must settle on the stack which everybody agrees with.
Feedbacks please.
@miteshree @HishamMubarak @nileshlaxmi

Since we need login features, auth and more , isn't it better if we used react than VanillaJs? Let me know what you think.

In Case of using only Oauth, we will not need any SignUp container.

The hamburger menu button, when clicked must change the state variable openNav to true.

The functions and state has already been implemented, all we need to do is pass down the function to Hamburger component using our context component so that it could execute it when clicked.

This is a topic related to Context API of react.

The SignUp container will have a state with name, user-name, email and password as variables.

It should contain 5 input elements (name, desired user-name, email, pass and re-pass), submit button and a heading.

The state should be updated as the user types in the input boxes.

Please move it from To-do to in progress if you want to work on it

As the majority out there, I fear CSS and I am rubbish at it. If you feel like you need to contribute and you do not catch with the overly complex React, feel free to check the CSS, which is pure as ever. Propose some changes. Play around with it.

If you all remember from the webpage we created earlier, it consisted of cards of different colors as a link to different sections.

Goal: The task is to build a reusable card component with the same CSS features as previously. It should accept a Link, a Title and a Color as props.

@miteshree @HishamMubarak @dipakkr @nileshlaxmi

The new branch for react is up and live. I have done my best to make the project understandable (except I haven't included comments but react is pretty self-explainatory).

• First, confirm that you understand and accept the project structure and design.
• Second, take a note of the global variables declared in index.css, we'll be using those everywhere (Feel free to add).
• Third, I am fairly new to using Router, so verify the way that I have used it and guide for the same in future.

After you guys have done this much, we can start assigning tasks to ourselves and instead of someone pointing out others what to do, we'll assign ourselves to one of the available tasks and alert everyone by creating an issue about it + adding it to To-do.

I'll try to lay out as many tasks as possible for you guys to pick from, but even if I don't, feel free to choose any task.

The design for different pages is under development, the designer is working on it. It may take some time for the designs to come out. Till then we can create routes, add any necessary component or any feature.

Generally mentioning the steps to view the running model:

• clone the repo
• run npm install in the cloned dir
• after that's done, run npm start

The designer and I have given our best to keep the UI clean. But still a new perspective never hurts, does it? Give out suggestions, like change the margin here, change the border-radius here, change the color here. Honestly, I am just bad with colors so I could use a third eye.. or many eyes.

The first section is of Coding Resources and hence we must create a component for it with following musts:

• Must look similar to the Home container, except it should be a component instead of a container.
• Must be routed at the /pages/coding-resources URL.