From d5bd2670a5bd1a1c1b38d25c8a6548708d1d6fc5 Mon Sep 17 00:00:00 2001 From: Brian (bex) Exelbierd Date: Oct 25 2016 19:28:01 +0000 Subject: Adding README with Conversion Project Plan --- diff --git a/README.md b/README.md new file mode 100644 index 0000000..912508c --- /dev/null +++ b/README.md @@ -0,0 +1,40 @@ +This repository holds the build scripts and skeleton site for docs.fedoraproject.org. + +This is under construction. The docs team is implementing a new publication workflow. + +Note: Today, pagure.io doesn't support AsciiDoc so this is temporarily in markdown + +# Docs Conversion Project Timeline and Plan + +Note: This still needs dates! + +Note: Steps are done in parallel wherever possible. Each major step +should be reproducible during this process to begin to set up a pipeline. + +1. Convert repositories to Asciidoc + 1. Convert DocBook using script by randomuser + 1. Eliminate Common Content + 1. Break into rough/large topics + +1. Build prototypes in both AsciiBinder and Pintail + + * **Pintail - insert plan here** + + * **AsciiBinder** + 1. Restructure Repositories to be individually buildable + 1. Extend builder.sh to properly build an English only site + 1. Engage design for CSS + 1. Design English Site + 1. With design/others implement javascript to switch languages and detect language + 1. Implement translation push + 1. Ensure po4a does Asciidoc correctly + 1. Tables + 1. Full Review + 1. Push sample POT files to Zanata and ask i18n to review + 1. Implement translation pull and merge + 1. Determine how to pull just translations that are "finished" or that meet minimum requirements + * This may involve a perentage finished by language setting that can be maintained by i18n + 1. Ensure po4a produces valid output + 1. Build each language with English documentation available where there is no translation + +1. Make a decision and publish F26