Goal
Help guide users through the document conversion process so that they are able to move forward with RAG or Model Customization

Problem statement
Assumption: Default docling conversion is good when used with the proper pipeline, when default conversion does not work users are not sure what to do next.

We want to make this process feel intuitive and supportive by:

• Breaking the task down into clear, manageable steps
• Providing helpful examples and tips along the way
• Reminding them of the real-world use case their work is supporting
• Making it easy to re-run
• Helping them feel confident that what they’re doing is correct and impactful

Acceptance Criteria

• Docling serve - get this up and running and do an assessment of the functionality
  • Eg. Where in the docling serve UI can I see conversion errors?
  • Evaluate how this connects to Vaclav’s work
  • Evaluate how your chunking work can extend this experience
• Meet with Ali/Fabiano to understand the related notebook/sdk experiences
  • Rewatch their demos from Thursday May 1
  • Fabiano's demo covers the ability to do many conversions at once, and provides output guidance on what configuration may work best

Resources

• Vaclav's Figma Mocks 
• May 8th, Discovery demo
• Miro, mark up of current mocks and brainstorming
• User Stories demo

Deliverables
[Fill in]