Visual Layer Documentation home page
Search...
⌘K
Ask AI
VL-Blog
Support
Try Now
Try Now
Search...
Navigation
Guides
API Reference
fastdup
Releases
Getting started
Introduction to Visual Layer
Quick start
Deploy Visual Layer
Definitions & entities
On-premises
System requirements
Set up the environment
Air-Gapped environment installation
Basic operations
run_profiler.sh
User management
Configuration
S3 Configuration
Troubleshooting
Integrations
Amazon S3
CVAT - soon
Labelbox - soon
Creating datasets
Upload data
Custom Metadata
Importing annotations
Managing datasets
Save views
User Tags
Share dataset
Export dataset
Using exported VL metadata
Update data - soon
Update metadata - soon
Exploring datasets
Exploration overview
Semantic search
Caption search
Visual search
Filter dataset
Mislabels
Unlabeled
Duplicates
Outliers
Class outlier
Select unique items
Quality issues
Dataset enrichment
Enrich dataset
Explore model catalog
Analyze enriched dataset
Use custom models – coming soon
On this page
Mintlify documentation
Working relationship
Project context
Content strategy
docs.json
Frontmatter requirements for pages
Writing standards
Git workflow
Do not
Claude
Copy page
Copy page
Mintlify documentation
Working relationship
You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
ALWAYS ask for clarification rather than making assumptions
NEVER lie, guess, or make up information
Project context
Format: MDX files with YAML frontmatter
Config: docs.json for navigation, theme, settings
Components: Mintlify components
Content strategy
Document just enough for user success - not too much, not too little
Prioritize accuracy and usability of information
Make content evergreen when possible
Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason
Check existing patterns for consistency
Start by making the smallest reasonable changes
docs.json
Refer to the
docs.json schema
when building the docs.json file and site navigation
Frontmatter requirements for pages
title: Clear, descriptive page title
description: Concise summary for SEO/navigation
Writing standards
Second-person voice (“you”)
Prerequisites at start of procedural content
Test all code examples before publishing
Match style and formatting of existing pages
Include both basic and advanced use cases
Language tags on all code blocks
Alt text on all images
Relative paths for internal links
Git workflow
NEVER use —no-verify when committing
Ask how to handle uncommitted changes before starting
Create a new branch when no clear branch exists for changes
Commit frequently throughout development
NEVER skip or disable pre-commit hooks
Do not
Skip frontmatter on any MDX file
Use absolute URLs for internal links
Include untested code examples
Make assumptions - always ask for clarification
Was this page helpful?
Yes
No
Suggest edits
Raise issue
Assistant
Responses are generated using AI and may contain mistakes.