Split DOCX into Structured HTML
Budget: €250 – €400 EUR
I have a lengthy .docx file that follows a strict hierarchy—Chapters, Articles, Sub-articles, Annexes, Sub-annexes & Subsections. I need it broken down into lean, standards-compliant HTML while keeping the document easy to navigate and reuse.
Scope of work
• Convert the entire .docx into clean, minimal HTML (no inline styling beyond what’s essential).
• Apply proper semantic tags: <h1> for Chapters, <h2> for Articles, progressively down to <h6> when the depth requires it.
• Maintain all Images, Tables, and Lists exactly as they appear; everything else can be simplified.
• Split the source into multiple files:
– One file per Scheme Article.
– One file for each Annex sub-subsection.
• Name each output file in the pattern 01_chapter_article01-definitions, 01_chapter_article02-scope, 02_chapter_article04-auth2fish, and so on.
• Generate a separate table-of-contents HTML that links to every Chapter, Article, and Annex file.
Acceptance criteria
1. All headings nest correctly without skipping levels.
2. No extraneous inline styles—CSS should live in a single external sheet if needed.
3. All internal links resolve, including those in the table of contents.
4. Images render, tables keep their structure, and ordered/unordered lists are preserved.
5. File names strictly match the provided pattern.
Let me know which toolchain you prefer—Pandoc, Python-docx, custom scripts, or something else—so long as the final output meets the above points.
Scope of work
• Convert the entire .docx into clean, minimal HTML (no inline styling beyond what’s essential).
• Apply proper semantic tags: <h1> for Chapters, <h2> for Articles, progressively down to <h6> when the depth requires it.
• Maintain all Images, Tables, and Lists exactly as they appear; everything else can be simplified.
• Split the source into multiple files:
– One file per Scheme Article.
– One file for each Annex sub-subsection.
• Name each output file in the pattern 01_chapter_article01-definitions, 01_chapter_article02-scope, 02_chapter_article04-auth2fish, and so on.
• Generate a separate table-of-contents HTML that links to every Chapter, Article, and Annex file.
Acceptance criteria
1. All headings nest correctly without skipping levels.
2. No extraneous inline styles—CSS should live in a single external sheet if needed.
3. All internal links resolve, including those in the table of contents.
4. Images render, tables keep their structure, and ordered/unordered lists are preserved.
5. File names strictly match the provided pattern.
Let me know which toolchain you prefer—Pandoc, Python-docx, custom scripts, or something else—so long as the final output meets the above points.