🔰 [Initiative] Near.org Website Redesign

[near-arthur]

Description

This effort is a revamp of the near.org website landing pages and main navigation.

Figma

### Tasks
- [ ] https://github.com/near/near-discovery/issues/424
- [ ] https://github.com/near/near-discovery/issues/416
- [ ] https://github.com/near/near-discovery-components/issues/360
- [ ] https://github.com/near/near-discovery-components/issues/361
- [ ] https://github.com/near/near-discovery-components/issues/362
- [ ] https://github.com/near/near-discovery/issues/626
- [ ] https://github.com/near/near-discovery-components/issues/364
- [ ] https://github.com/near/near-discovery/issues/663
- [ ] https://github.com/near/near-discovery/issues/708
- [ ] https://github.com/near/near-discovery/issues/697

[heycorwin]

@ravigautham I don't know if it's necessary that everything under an initiative like this one be an Epic. If we try too hard to adhere to that pattern, we end up forcing some redundancy.

Example can be seen above. I've removed the navigation redesign Epic because the navigation redesign is in fact just a singular task (ie does not need to contain subtasks). I've just included the navigation redesign issue you created here under the initiative.

[ravigautham]

@heycorwin Great point, I totally agree with this. If there is something that is standalone and a single task we'll just keep it as an issue. There can be a combination of epics/issues under a single initiative. Thanks!