[DOC] Write local documentation developer guide.

[aadya940]

Write steps to build documentation locally.

[aeon-actions-bot[bot]]

Thank you for contributing to aeon

I have added the following labels to this PR based on the title: [ $\color{#F3B9F8}{\textsf{documentation}}$ ].

The Checks tab will show the status of our automated tests. You can click on individual test runs in the tab or "Details" in the panel below to see more information if there is a failure.

If our pre-commit code quality check fails, any trivial fixes will automatically be pushed to your PR unless it is a draft.

Don't hesitate to ask questions on the aeon Slack channel if you have any.

PR CI actions

These checkboxes will add labels to enable/disable CI functionality for this PR. This may not take effect immediately, and a new commit may be required to run the new configuration.

• [ ] Run pre-commit checks for all files
• [ ] Run all pytest tests and configurations
• [ ] Run all notebook example tests
• [ ] Run numba-disabled codecov tests
• [ ] Stop automatic pre-commit fixes (always disabled for drafts)
• [ ] Push an empty commit to re-run CI checks

[MatthewMiddlehurst]

Mind if i make changes to this? Quite a bit that can be improved on this page IMO.

[aadya940]

@MatthewMiddlehurst Yes sure, were you able to build the docs?

[aadya940]

@MatthewMiddlehurst Oh, Okay! I build my docs in the way I wrote and have written this as per my experience. However, if this works, it would be much simpler. :))

[aadya940]

Could you please edit accordingly?

[MatthewMiddlehurst]

absorbed into #2297. Includes your commit so you should still get credit

[MatthewMiddlehurst]

@all-contributors add @aadya940 for docs

[allcontributors[bot]]

@MatthewMiddlehurst

@aadya940 already contributed before to doc