I don't think that people use PDF versions much. As a first step we can delete them on the web site and see if there are any complains. We can also monitor 404 errors in httpd logs, at least count how many times people requested PDF content in a month.
I'm +1 to get rid from PDF on the POI web site. Yegor On Sat, Jun 30, 2012 at 10:18 PM, Nick Burch <[email protected]> wrote: > Hi All > > Currently, the POI website is build with Apache Forrest, which allows us to > automatically generate PDF versions of all of our pages, alongside the HTML > version. > > For example, as well as the HTML version of the component overview page: > http://poi.apache.org/overview.html > There's also a downloadable PDF version: > http://poi.apache.org/overview.pdf > > Does anyone out there use these? > > The reason for asking is that the way the project website gets published > needs to change by the end of December (the old box we deploy through is > being disabled), and changing the deployment route may also be a good point > to update how the site is built. A lot of Apache projects now use the Apache > CMS, and Markdown, which makes for quicker edits and allows for easy > contributrions of site fixes from non-committers. The current setup is a > little tricky to get setup, so it takes a while to do site changes (which > may well contribute to fewer of them happening...). > > If we did switch to using markdown + the cms for the site, we'd get quicker > and simpler site builds, but we'd loose the PDF versions we get from > Forrset. The question is - would anyone miss them? > > Nick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
