I think this content is superfluous to the DOMPDF library. Certainly we can
highlight the power of DOMPDF through samples, but I think this could be done
through it's own subproject. We can provide a separate download for the sample
site for anyone interested, but I think we should aim for a clean and
unburdened directory structure. Plus, the more content we add to the sample
site the larger the download becomes.
As with the CPDF library, this is something that has to be developed in
conjunction with DOMPDF since it contains documentation relevant to the current
release. But it also gives us the change to make changes to the web site trunk
that don't get pushed out until we decide they're ready.
I'm not quite as set on this idea as on extracting CPDF, but I think it's still
worthwhile. So what does everyone think?
Original issue reported on code.google.com by eclecticgeek on 3 Sep 2010 at 12:56
Original issue reported on code.google.com by
eclecticgeek
on 3 Sep 2010 at 12:56