Yeah I think better to ignore my original request, I understand why it isn't in the git repository now so all sweet. Should be able to have docs transferred from confluence + new design and new design for website done by first week of September. If there is any features on new website that you two would personal want in the new revision before i submit a patch just let me know. I'll let the mailing group look at it and then they can submit requests through the issue tracker.
On 23 August 2015 at 09:40, Evan Hughes <ehu...@gmail.com> wrote: > Ill get back to you about it, I think current system is fine just forgot > where it was located. > > Trying to get a patch ready for wave anyway atm so wont be able to touch > website design just yet. Hopefully before the review. > On 23/08/2015 5:23 AM, "Ali Lown" <a...@lown.me.uk> wrote: > >> Hi Evan, >> >> Not entirely sure what this would constitute. Are you proposing >> redesigning the website from scratch to not make use of the Apache >> CMS? >> >> Currently the reference version lives in the Wave subversion space (as >> required for all the CMS scripts to work properly). This is already as >> close to a separate repository as possible for the project. >> (The staging and 'published' editions live in infra's space at >> https://svn.apache.org/repos/infra/websites/) >> >> If we made a github repository for the website, then the flow would >> need to involve copying this in to the subversion space, then forcing >> a rebuild, then publishing it from there if we wanted to use the CMS. >> >> The alternative for a non-CMS site would look almost identical: as the >> only alternate mechanism is via Infra's svnpubsub system, so the repo >> gets copied to a designated space in svn, and then published by that >> instead. (We just need to pre-build it first). >> >> More information on the options can be found at: >> https://www.apache.org/dev/project-site >> >> Which of these options are you suggesting? >> >> Ali >> >> On 11 August 2015 at 11:39, Evan Hughes <ehu...@gmail.com> wrote: >> > Making styling for the docs already, might as well chuck the website's >> css >> > ontop. >> > >> > On 11 August 2015 at 20:37, Yuri Z <vega...@gmail.com> wrote: >> > >> >> Fine with me, but I think that would require sufficient effort. >> >> >> >> On Tue, Aug 11, 2015 at 12:58 PM, Evan Hughes <ehu...@gmail.com> >> wrote: >> >> >> >> > Does the mailing list think it would be beneficial for the Apache >> Wave >> >> > website's design and content to be a separate repository if this is >> even >> >> > possible? >> >> > >> >> > By making the change the layout of the design can be improved on >> (made to >> >> > be more modern) and content more up to date taking away the >> >> responsibility >> >> > from the commiters to only allow pull requests/patches. >> >> > >> >> > Also allows the docs in html form to be added to the website in a >> >> > structured way as well with the pdf copies. >> >> > >> >> > ~ Evan >> >> > >> >> >> >
