I’ve made some updates to the current site code in its current location. Given that CMS/infra is expecting the site source to be in https://svn.apache.org/repos/asf/incubator/slider/site/, it would appear that this directory would require someone to create a local commit that:
1) adds a pom.xml file to the root (slider/site) 2) Adds a content sub-directory (slider/site/content) 3) moves current markdown files to either “content” or a “content/markdown” sub-directory (slider/site/content/markdown) 4) mv site.xml to “content” 5) move current resource dir to “content/resources” this all assumes that we can use the maven approach to building the site (setting maven as the external build approach). Is that something we file a JIRA for? Related question: is the only reason we don’t have a current site, even though there is a file in “slider/site” (index.html) in that root directory? For the time being I even tried mimicking the published content directory (i.e. I moved index.html to site/content/index.html) but still get a 404 from the website (incubator.apache.org/slider/), so I have very little confidence in undertaking the more extensive move outlined above. — Jon On May 5, 2014, at 12:21 PM, Jon Maron <jma...@hortonworks.com> wrote: > > On May 5, 2014, at 11:47 AM, Josh Elser <josh.el...@gmail.com> wrote: > >> On 5/5/14, 11:30 AM, Jon Maron wrote: >>> On May 5, 2014, at 11:09 AM, Josh Elser<josh.el...@gmail.com> wrote: >>> >>>> >Ah, ok. How doeshttp://people.apache.org/~elserj/slider/site/ look for >>>> >starters? >>> I’ve been iterating through this as well and made some changes: >>> >>> - announcement.html - doesn’t actually exist. for the time being I >>> replaced it with a modified version of the getting_started doc we provided >>> with the release last week >>> - client_cofifguration.html - doesn’t exist. remove it? >>> - cluster_descriptions - doesn’t exist. remove for now? >>> - logging - same >>> >>> In addition, there was a bunch of stuff missing from pom to complete some >>> of the standard menu items - <scm> update to svn settings, top level <url>, >>> <mailingLists>, <distributionManagement>.. >>> >>> Did you make similar changes or should I commit them so you can review? >>> >> >> I made one content change (a newline) to make doxia work on trunk as-is, and >> updated a maven plugin to silence some errors coming out of Aether. >> >> Apparently I don't have commit rights though (or something is still hosed >> for me post-HB resets). I IM'ed Billie and she said she thinks she has the >> karma to verify that for me. >> >> In short, I was going to commit, but it's of no consequence for you to wait >> around for me to get there :). Fire away. > > Cool. Some of the changes will have to be modified when we move to git: > > <scm> > <url>https://svn.apache.org/repos/asf/incubator/slider/</url> > <connection>scm:svn:https://svn.apache.org/repos/asf/incubator/slider/ > </connection> > <developerConnection> > scm:svn:https://svn.apache.org/repos/asf/incubator/slider/ > </developerConnection> > </scm> > > — Jon > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
