Add DataHUB documentation and API reference

- Introduced new documentation for the DataHUB service, including purpose, roles, and business case.
- Added detailed API reference for Quotes and Visits, including search endpoints and response structures.
- Created sections for service records, time reports, and visits in the CustomerHUB documentation.
- Implemented a change log and test plan for the DataHUB project.
- Updated the introduction to include links to the new DataHUB documentation.
- Modified navbar configuration to reflect changes in documentation structure.
This commit is contained in:
jaime.meza committed 2026-11-17 10:42:21 -05:00
1 parent d1251a5f05
commit 928a4451f7
38 files changed
+1725 -3

No files matched your search

+19
View File
@@ -11,6 +11,16 @@ Use the sections below to find what you need.
---
## [CustomerHUB](/docs/customerhub/explanation/what-is-customerhub)
User documentation for the CustomerHUB application — the operational portal built on HOIST HUB.
- **Explanation** — What CustomerHUB is and how it connects to IFS
- **Reference** — Field-by-field documentation for Dashboard and Customers
- **How-to Guides** — Find a customer, import from IFS, and more
---
## [HOIST HUB](/docs/hoist-hub/ifs-integration)
Technical documentation for the HOIST HUB platform itself.
@@ -19,6 +29,15 @@ Technical documentation for the HOIST HUB platform itself.
---
## [DataHUB](/docs/datahub/explanation/purpose-and-roles)
REST API for extracting HUB data — built for Martin Engineering as a self-service alternative to ad hoc data requests.
- **Explanation** — Purpose, roles, and the business case for the DataHUB service
- **Reference** — Solution design, dataset structures, API endpoints (Quotes/Search, Visits/Search), test plan, and delivery estimates
---
## [HOIST HUB Documentation Standard](/docs/hub-documentation/explanation/purpose)
The standard that defines how HUB specs are written, structured, and approved. If you are authoring or reviewing a HUB spec, start here.