(From Stain's 8/14/15 email with the example: ) > The biggest change was cleaning up the Markdown > files that had invalid HTML in them, and to > repeat the menu in site.xml
Does this mean the menu is being duplicated in multiple files? Does the menu have to be duplicated in many files? > So there would be quite a downsizing in flexibility here > (unless you make your own skin) - but considerably easier > to contribute to - I found it so much easier to edit and test locally. Easier to contribute to sounds like a good thing. I don't understand what the loss in flexibility is, though. Gale -----Original Message----- From: Stian Soiland-Reyes [mailto:[email protected]] Sent: Friday, August 14, 2015 9:08 AM To: [email protected] Subject: Re: [jira] [Commented] (TAVERNA-870) Move Taverna website away from SVN and cms.apache.org? Have a look at this example: http://stain.github.io/incubator-taverna-site/ This was generated with the Maven site plugin: from https://github.com/stain/incubator-taverna-site To generate it locally, use mvn clean site and look in target/site or mvn site:run to run a mini-sever on localhost. Note that relative links might be broken here. The biggest change was cleaning up the Markdown files that had invalid HTML in them, and to repeat hte menu in site.xml So there would be quite a downsizing in flexibility her e(unless you make your own skin) - but considerably easier to contribute to - I found it so much easier to edit and test locally.
