Standardize a color palette

[LunaticHacker]

Is your feature request related to a problem? Please describe.

• Since there is no guidelines on what colors to use in the project ,contributors are using colors according to their discretion
• The codebase is also cluttered with hexcodes since variables are underutilized

Describe the solution you'd like

• Design a color palette
• Translate the color palette to less variables
• Add instructions on how to use this palette in Contributing guidelines
• Clean up the codebase using said variables

[gautamkrishnar]

@Dexters-Hub @akhilmhdh thoughts?

[akhilmhdh]

Well i think @irenekurien mentioned some changes to will made in like couple of weeks, so i would say co-ordinate with her if needed.

Yah color palette is an awesome idea. But the effort vs the rightful need, still unsure. If someone is willing to take it, awesome. Would love to see that change.

[Dexters-Hub]

Thanks @LunaticHacker for opening this issue. Color Palette is a great Idea. It would be a reference and a standard to follow.

[LunaticHacker]

Just to be clear, this is a low priority issue (maybe we should add a label for that). we should focus on improving learning paths for now.

[gautamkrishnar]

@irenekurien can you please explain here what is the plan you guys have for the redesign?

[irenekurien]

We have not finalized the structure yet. What we have planned is to split the contents into different tiles (say Web, App, Cloud/DevOps, Future Technologies, Game Dev). Now, if a user chooses any one of these tiles, they will get a list of career paths available under this. On further choosing, they will receive the resources from where they can learn the stack.

This is the basic flow we are planning to implement. Also considering adding a roadmap they can flow listing the topic down.

For further clarity, you may refer to this.

[LunaticHacker]

Now, if a user chooses any one of these tiles, they will get a list of career paths available under this. On further choosing, they will receive the resources from where they can learn the stack.

• This is a huge breaking change, we will have to rethink all the taxonomies,content sections and CMS stuff if we want to implement hierarchy.
• We should probably make a new issue and discuss the merits of this before moving forward with ideas like this.

Also considering adding a roadmap they can flow listing the topic down.

This is all what we have for majority of the paths now. :laughing: