Setup basic information-architecture

[nimworks]

Setup a basic directory structure adhering to the intended information-architecture as per Gatsby requirements.

Information segmentation

[asturur]

The information architecture seems bigger for a start.
I would collapse Docs and Tutorials together, the getting started guide needs a rewrite anyway.

Tutorials, Docs ( js docs ), demos, Changelog. And a link to the github repo in the top right corner that is basically the only support channel.

I would add the Download section as pictured,

Extra is fine

Marketing i m not sure if i want to keep it at all.
A blog section is nice, but i m not sure if we will have time to fill it up with content.

[nimworks]

The idea of having a tutorials section apart from docs section was to harbour all tutorial-like content (for eg. How to make a radar-chart with FabricJs) while the docs would house getting started related guides.
And thus had shifted the JS documentation under the API section which wud mostly act as reference while using FabricJS methods
So for now, maybe we can skip the tutorials section which we could maybe incorporate later

Sorry if the image portrays a architecture but it actually is just segmentation of data! 😇. Which means we won't have a marketing section per say on our site but only portray relevant data on our site which would help captivate the user's attention. For eg. The features would be portrayed on the home page right below the banner.

Blog we can skip for now and anyways we cud add it later anytime if need arises

@asturur kindly let me know what u think on this 😊

[asturur]

Everything is good @nimworks move in the direction you think is better.

[nimworks]

The 'Who's using Fabric' section can be a good start in implementing the showcase for FabricJS!
Although not among the priority features we need to work on 😇