docs: Change structure of document

[jungpaeng]

Description

Related Issue: Fixes #62

Changes

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [x] Documentation update

Checklist

• [ ] I have performed a self-review of my own code.
• [ ] My code is commented, particularly in hard-to-understand areas.
• [ ] I have made corresponding changes to the documentation.
• [ ] My changes generate no new warnings.
• [ ] I have added tests that prove my fix is effective or that my feature works.
• [ ] New and existing unit tests pass locally with my changes.
• [ ] Any dependent changes have been merged and published in downstream modules.

Further Comments

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
overlay-kit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 15, 2024 6:23pm

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: f57ed9867c6f240fde19f9c4cd778305093f40d6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[jungpaeng]

Our team is currently in the process of reviewing the document. Once the review is complete, significant changes to the structure are likely.

I will incorporate your comments after this task is finished. Thank you.

[jungpaeng]

Continue to #67