Product documentation that behaves like a help system, not a blog or PDF shelf.
Search guides, categories, interactive tutorials, FAQs, video placeholders, and future API-ready documentation across the YUKU ecosystem. Content is structured so it can move into a CMS later.
Search results
6 documentation entries
Getting Started
YUKU Platform Overview
Understand how Field, Time, Community, Marketplace, Account, AI, and Estimating fit into one ecosystem.
Field Operations
Create a Field Project
Interactive tutorial for setting up a project, assigning tasks, adding notes, uploading photos, and generating reports.
Time Tracking
Clock In with YUKU Time
Step-by-step guide for site selection, GPS status, clock in/out, and shift timeline review.
Marketplace
Marketplace Downloads and Products
Documentation architecture for physical products, digital downloads, templates, calculators, plugins, and subscriptions.
Account
Unified Account Access
Guide to the future shared YUKU account model for product access, licenses, downloads, orders, and subscriptions.
Integrations
Future API Documentation
Placeholder structure for future API references, webhooks, authentication scopes, and code examples.
FAQ
Answers are content-driven and filtered by the same search, product, and category controls.
Is this a blog?
No. The documentation center is structured around product help, tutorials, references, FAQs, and future API material.
Are documents delivered as PDFs?
No. Documentation is code-native and content-driven. Future downloads may exist in Marketplace, but docs are not PDF-based.
Is the AI documentation assistant live?
No. The AI assistant area is a placeholder for future search, summarization, and guided help.
Are API docs live?
No. API docs, code examples, auth scopes, and webhooks are architecture placeholders only.
Can documentation content be edited later?
Yes. Documentation content is stored as structured data and can be moved into a CMS without changing page architecture.
Future documentation capabilities
Placeholders only. No AI, API, video hosting, screenshot service, or code generation is connected.
Future AI assistant
Placeholder for conversational help, contextual answers, and guided product support.
futureFuture code examples
Placeholder for SDK snippets, API request examples, and integration samples.
futureFuture API docs
Placeholder for endpoint references, webhooks, auth scopes, and changelog entries.
futureFuture screenshots
Placeholder for visual walkthrough screenshots and product state captures.
placeholderFuture product selector
Placeholder for switching documentation context between Field, Time, Marketplace, Account, and AI.
placeholder