AW: AW: AW: AW: AW: AW: [Website] Progress on the Website-Generation topic
Hi Alex, well we couldn't just copy stuff to GIT as the Apache CMS didn't seem to support Git at all and there are no plans on supporting this. The maven-site-plugin has several options for generating the site for a project. There are the usual templates that for example the maven project uses to generate its site, but that was too unsexy for a framework like Flex. So I gave the Reflow skin [1] a try and was pretty happy with this as it seems to have provided most of the things I thought I needed to port the page. It was while having my first success with the skin, that I noticed, that porting the pages to Markup was pretty easy. I bet the Apache guys internally sort of use Markup or something very similar to that. It was also about then, when I noticed that our site seems to be using bootstrap for layouting. Conveniently the reflow skin also uses bootstrap, but probably a newer version. After I customized and fine-tuned most of the page to look nice, I converted those pages, that were full of HTML markup. I had quite some spare time in my last project as they managed to supply me with work for about 10% of my time so I was able to invest that time into the website as this doesn't require you to zone-out. Here I could deal with little interruptions by my paying customer without going nuts. Generics support is on a completely different page now. I really need some exclusive flex-time for that. And I needed this functionality in general, if I wanted to auto publish the maven sites generated by sub projects (FlexJS: Compiler, Typedefs, Framework). Anyway ... the website migration from my point of view is in a state in which I won't put much effort in it as most is already done. If we decide to go down that path, it would be great if some people with more CSS experience could jump in and help finish the last styling tasks. Chris [1] http://andriusvelykis.github.io/reflow-maven-skin/ Von: Alex Harui Gesendet: Mittwoch, 19. Oktober 2016 19:21:52 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: AW: [Website] Progress on the Website-Generation topic On 10/19/16, 2:18 AM, "Christofer Dutz" wrote: >Ok picking up this thread again ... > > >Well I think that allowing non-comitters to contribute to the page is a >pretty slim benefit. I couldn't say that we have used that even for a >single time in the past. And I think it would be good not to allow this >in general. At least I couldn't find a way to release only parts of the >site, so it's an all or nothing. And I also couldn't see any "this has >changed" so you would actually have to verify the entire page just to >make sure no one pushed anything bad. So I think it's a good thing that >non-comitters can't contribute to the site. This way we also don't have >to worry about signed ICLAs and so. "this has changed" would be on commits@. But yeah, I do not like having to push the entire site, and going through the web interface to do it. > >One thing I couldn't find in the codebase however was the footer of each >page containing the Twitter feed, the latest releases, the about flex >text and how to subscribe to mailinglists. I couldn't find this content >anywhere :-( I think that is in trunk/templates. I've been wondering why this move to Maven didn't involve just copying the templates and other files to Git. Did you try to implement a port to Bootstrap at the same time because you had to, or was it an option? > > >And I would like to state that I didn't expect this to be a race in which >the first one wins. If there are other initiatives to generating the site >in git, why not simply setup a separate branch and put that stuff in >there? I could change the buildbot job to push to "asf-site-maven" and >different solutions could co-exist. All that I want, is the ability to >produce the sites of sub-modules such as FlexJS (and it's part) >automatically. I don't think it is a race. We are just experimenting with various options. I saw an old mail where Harbs tried to get GitHub pages up. I don't know of any other current alternatives. It really is a matter of whether it is worth your time since nobody else seems to have time to help. I'm definitely not a fan of ASF CMS, I just am wondering if it truly needs replacing right now. Would it be higher impact to the project to work on Generics support instead? -Alex
Re: AW: AW: AW: AW: AW: [Website] Progress on the Website-Generation topic
On 10/19/16, 2:18 AM, "Christofer Dutz" wrote: >Ok picking up this thread again ... > > >Well I think that allowing non-comitters to contribute to the page is a >pretty slim benefit. I couldn't say that we have used that even for a >single time in the past. And I think it would be good not to allow this >in general. At least I couldn't find a way to release only parts of the >site, so it's an all or nothing. And I also couldn't see any "this has >changed" so you would actually have to verify the entire page just to >make sure no one pushed anything bad. So I think it's a good thing that >non-comitters can't contribute to the site. This way we also don't have >to worry about signed ICLAs and so. "this has changed" would be on commits@. But yeah, I do not like having to push the entire site, and going through the web interface to do it. > >One thing I couldn't find in the codebase however was the footer of each >page containing the Twitter feed, the latest releases, the about flex >text and how to subscribe to mailinglists. I couldn't find this content >anywhere :-( I think that is in trunk/templates. I've been wondering why this move to Maven didn't involve just copying the templates and other files to Git. Did you try to implement a port to Bootstrap at the same time because you had to, or was it an option? > > >And I would like to state that I didn't expect this to be a race in which >the first one wins. If there are other initiatives to generating the site >in git, why not simply setup a separate branch and put that stuff in >there? I could change the buildbot job to push to "asf-site-maven" and >different solutions could co-exist. All that I want, is the ability to >produce the sites of sub-modules such as FlexJS (and it's part) >automatically. I don't think it is a race. We are just experimenting with various options. I saw an old mail where Harbs tried to get GitHub pages up. I don't know of any other current alternatives. It really is a matter of whether it is worth your time since nobody else seems to have time to help. I'm definitely not a fan of ASF CMS, I just am wondering if it truly needs replacing right now. Would it be higher impact to the project to work on Generics support instead? -Alex
AW: AW: AW: AW: AW: [Website] Progress on the Website-Generation topic
Ok picking up this thread again ... Well I think that allowing non-comitters to contribute to the page is a pretty slim benefit. I couldn't say that we have used that even for a single time in the past. And I think it would be good not to allow this in general. At least I couldn't find a way to release only parts of the site, so it's an all or nothing. And I also couldn't see any "this has changed" so you would actually have to verify the entire page just to make sure no one pushed anything bad. So I think it's a good thing that non-comitters can't contribute to the site. This way we also don't have to worry about signed ICLAs and so. Today I have continued on the new maven-style site and added stuff that was obviously missing: pmc_Flex.rdf, doap_Flex.rdf (don't quite know what they are good for ... looks as if this is some internal stuff for the ASF to gather information about it's own projects) ... at least that's in now. What's still missing is some installer-related stuff. I can see: - track-installer.cmsPage, - all the single-mirror pages - sdk-installer-config xmls I would assume the stuff in the sub-directory would actually come from sub-projects. One thing I couldn't find in the codebase however was the footer of each page containing the Twitter feed, the latest releases, the about flex text and how to subscribe to mailinglists. I couldn't find this content anywhere :-( And I would like to state that I didn't expect this to be a race in which the first one wins. If there are other initiatives to generating the site in git, why not simply setup a separate branch and put that stuff in there? I could change the buildbot job to push to "asf-site-maven" and different solutions could co-exist. All that I want, is the ability to produce the sites of sub-modules such as FlexJS (and it's part) automatically. Chris Von: Alex Harui Gesendet: Freitag, 14. Oktober 2016 17:20:05 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: [Website] Progress on the Website-Generation topic On 10/14/16, 12:42 AM, "Christofer Dutz" wrote: > >So if we are comparing the new three-step user workflow: > >1. Do changes > >2. Test them locally with a "mvn clean site" > >3. Commit changes > > >to the current user workflow, which is: > >1. Do changes > >2. Commit changes > >3. Wait for buildbot to stage the changes > >4. Check if the output is what we want in the staging area > >5. Go to the Web-Ui and release all changes at once (Could be a problem >that you release stuff someone else is currently working on, but I guess >that's a more theoretical problem) > I wouldn't mind getting rid of that step 5 in the current workflow, so if there are enough volunteers to re-create our site in Git that's fine with me. Interestingly, I just saw on another list that a supposed advantage of the current workflow is that non-committers can use ASF CMS and its web UI to make changes. Collecting doc changes from non-committers might be a good thing. Our wiki has a separate account system that allows us to do that as well. But would anyone in the community want to leverage that? Maybe using the Web UI is old-school and submitting pull requests is sufficient. So, in sum, no objections from me but I doubt I'll be much help on finishing the port. I am, however, curious as to how this will impact Nick. I think he was in-progress on a web-site revamp. Thanks, -Alex
Re: AW: AW: AW: AW: [Website] Progress on the Website-Generation topic
On 10/14/16, 12:42 AM, "Christofer Dutz" wrote: > >So if we are comparing the new three-step user workflow: > >1. Do changes > >2. Test them locally with a "mvn clean site" > >3. Commit changes > > >to the current user workflow, which is: > >1. Do changes > >2. Commit changes > >3. Wait for buildbot to stage the changes > >4. Check if the output is what we want in the staging area > >5. Go to the Web-Ui and release all changes at once (Could be a problem >that you release stuff someone else is currently working on, but I guess >that's a more theoretical problem) > I wouldn't mind getting rid of that step 5 in the current workflow, so if there are enough volunteers to re-create our site in Git that's fine with me. Interestingly, I just saw on another list that a supposed advantage of the current workflow is that non-committers can use ASF CMS and its web UI to make changes. Collecting doc changes from non-committers might be a good thing. Our wiki has a separate account system that allows us to do that as well. But would anyone in the community want to leverage that? Maybe using the Web UI is old-school and submitting pull requests is sufficient. So, in sum, no objections from me but I doubt I'll be much help on finishing the port. I am, however, curious as to how this will impact Nick. I think he was in-progress on a web-site revamp. Thanks, -Alex
AW: [Website] Progress on the Website-Generation topic
Hi Maxim, I initially setup the fluido skin, but that is more a skin for the normal maven-style pages. Generating our website with that would look sort of 90s or max early 2000s ;-) The cool thing with the reflow-skin is that it's a reactive version that adjusts to mobile devices nicely and allows us to auto-generate something looking very similar to our current Website. Chris Von: Maxim Solodovnik Gesendet: Freitag, 14. Oktober 2016 11:54:40 An: dev@flex.apache.org Betreff: Re: [Website] Progress on the Website-Generation topic On Fri, Oct 14, 2016 at 4:02 PM, Christofer Dutz wrote: > Hi Om, > > > I think that approach is probably the best ... I did encounter problems > when running the website from the working directory of Jenkins. Don't know > why. > > Jenkins is on https:// and scripts are being loaded from CDN via http:// Things like this need to be fixed in final version :( For our project we are generating site using https://maven.apache.org/skins/maven-fluido-skin/ Works for us :) > The template is configured in the site.xml document, as this configures > the the reflow themes built-in template. You can see all the options here: > > http://andriusvelykis.github.io/reflow-maven-skin/skin/components.html > > > The toc component seems to have this sort of option (offsetTopnav), but > not the topNav element responsible for the top navigation. I hope this is > customizable without having to adjust the reflow template itself. > > > But I just stumbled over the bottomNav column feature ... will add that > right away :-) > > > Another option would be to overwrite the css style by adding the > declarations to "site.css" but as I said ... I'm no web-developer and I > sort of feel like wasting days on stuff like that ... so if you know what > to do, just give it a try. > > > With a simple: > > > mvn clean site > > > you can re-generate the site and have a look at the result in the > "target/site" directory. > > > > Chris > > > Von: omup...@gmail.com im Auftrag von OmPrakash > Muppirala > Gesendet: Freitag, 14. Oktober 2016 10:33:28 > An: dev@flex.apache.org > Betreff: Re: [Website] Progress on the Website-Generation topic > > Never mind, I checked out the flex-site. > > The proper fix would be to > 1. Remove the class "navbar-fixed-top" on the navbar div in all pages. > 2. Set padding-top = 0 for body in bootswatch.css > > (2) is straightforward. But it looks like we need to make the change for > (1) in every page. Is there a html template that drives all the pages? > > Thanks, > Om > > On Fri, Oct 14, 2016 at 1:28 AM, Harbs wrote: > > > The link is lower down in this thread: > > https://builds.apache.org/view/E-G/view/Flex/job/Flex- > > Site%20(Maven)/ws/target/site/index.html > > > > On Oct 14, 2016, at 11:07 AM, OmPrakash Muppirala > > wrote: > > > > > Where can I find this site? > > > > > > It sounds like the nav bar has CSS setting position: sticky; > > > Either that, or the position of the nav bar is being translated in an > > > onScroll event handler in javascript. > > > > > > Thanks, > > > Om > > > > > > On Fri, Oct 14, 2016 at 12:59 AM, Christofer Dutz < > > christofer.d...@c-ware.de > > >> wrote: > > > > > >> If someone knows bootstrap good enough to eventually help me with the > > >> position of the navigation bar? Currently it's stuck to the top no > > matter > > >> where you scroll to. I would prefer it to have the Flex and Apache > logo > > >> above (like in the current version) but as soon as you scroll down and > > the > > >> header hit's the top of the browser window, it stays there and remains > > >> visible. I know I have seen this behavior but I simply don't know the > > CSS > > >> magic I would have to apply here ;-) > > >> > > >> > > >> So if anyone here knows this stuff, please come forward and help me > get > > >> this site a little more into shape :-) > > >> > > >> > > >> Chris > > >> > > >> > > >> Von: Justin Mclean > > >> Gesendet: Freitag, 14. Oktober 2016 09:44:27 > > >> An: dev@flex.apache.org > > >> Betreff: Re: [Website] Progress on the Website-Generation topic > > >> > > >> Hi, > > >> > > >>> So has anyone else had a look at the newly generated documentation in > > >> the flex-site.git "maven-site" branch? As I mentioned, if you checkout > > the > > >> "asf-site" branch you can see the generated output. > > >> > > >> Just taking look now. It been a couple of busy weeks with conferences > > and > > >> other work (yesterday I assembled, programmed and tested 40 prototype > > >> devices) and I’m just catching up on a few things. > > >> > > >> Thanks, > > >> Justin > > >> > > > > > -- WBR Maxim aka solomax
AW: [Website] Progress on the Website-Generation topic
Hi Om, I think that approach is probably the best ... I did encounter problems when running the website from the working directory of Jenkins. Don't know why. The template is configured in the site.xml document, as this configures the the reflow themes built-in template. You can see all the options here: http://andriusvelykis.github.io/reflow-maven-skin/skin/components.html The toc component seems to have this sort of option (offsetTopnav), but not the topNav element responsible for the top navigation. I hope this is customizable without having to adjust the reflow template itself. But I just stumbled over the bottomNav column feature ... will add that right away :-) Another option would be to overwrite the css style by adding the declarations to "site.css" but as I said ... I'm no web-developer and I sort of feel like wasting days on stuff like that ... so if you know what to do, just give it a try. With a simple: mvn clean site you can re-generate the site and have a look at the result in the "target/site" directory. Chris Von: omup...@gmail.com im Auftrag von OmPrakash Muppirala Gesendet: Freitag, 14. Oktober 2016 10:33:28 An: dev@flex.apache.org Betreff: Re: [Website] Progress on the Website-Generation topic Never mind, I checked out the flex-site. The proper fix would be to 1. Remove the class "navbar-fixed-top" on the navbar div in all pages. 2. Set padding-top = 0 for body in bootswatch.css (2) is straightforward. But it looks like we need to make the change for (1) in every page. Is there a html template that drives all the pages? Thanks, Om On Fri, Oct 14, 2016 at 1:28 AM, Harbs wrote: > The link is lower down in this thread: > https://builds.apache.org/view/E-G/view/Flex/job/Flex- > Site%20(Maven)/ws/target/site/index.html > > On Oct 14, 2016, at 11:07 AM, OmPrakash Muppirala > wrote: > > > Where can I find this site? > > > > It sounds like the nav bar has CSS setting position: sticky; > > Either that, or the position of the nav bar is being translated in an > > onScroll event handler in javascript. > > > > Thanks, > > Om > > > > On Fri, Oct 14, 2016 at 12:59 AM, Christofer Dutz < > christofer.d...@c-ware.de > >> wrote: > > > >> If someone knows bootstrap good enough to eventually help me with the > >> position of the navigation bar? Currently it's stuck to the top no > matter > >> where you scroll to. I would prefer it to have the Flex and Apache logo > >> above (like in the current version) but as soon as you scroll down and > the > >> header hit's the top of the browser window, it stays there and remains > >> visible. I know I have seen this behavior but I simply don't know the > CSS > >> magic I would have to apply here ;-) > >> > >> > >> So if anyone here knows this stuff, please come forward and help me get > >> this site a little more into shape :-) > >> > >> > >> Chris > >> > >> > >> Von: Justin Mclean > >> Gesendet: Freitag, 14. Oktober 2016 09:44:27 > >> An: dev@flex.apache.org > >> Betreff: Re: [Website] Progress on the Website-Generation topic > >> > >> Hi, > >> > >>> So has anyone else had a look at the newly generated documentation in > >> the flex-site.git "maven-site" branch? As I mentioned, if you checkout > the > >> "asf-site" branch you can see the generated output. > >> > >> Just taking look now. It been a couple of busy weeks with conferences > and > >> other work (yesterday I assembled, programmed and tested 40 prototype > >> devices) and I’m just catching up on a few things. > >> > >> Thanks, > >> Justin > >> > >
AW: [Website] Progress on the Website-Generation topic
If someone knows bootstrap good enough to eventually help me with the position of the navigation bar? Currently it's stuck to the top no matter where you scroll to. I would prefer it to have the Flex and Apache logo above (like in the current version) but as soon as you scroll down and the header hit's the top of the browser window, it stays there and remains visible. I know I have seen this behavior but I simply don't know the CSS magic I would have to apply here ;-) So if anyone here knows this stuff, please come forward and help me get this site a little more into shape :-) Chris Von: Justin Mclean Gesendet: Freitag, 14. Oktober 2016 09:44:27 An: dev@flex.apache.org Betreff: Re: [Website] Progress on the Website-Generation topic Hi, > So has anyone else had a look at the newly generated documentation in the > flex-site.git "maven-site" branch? As I mentioned, if you checkout the > "asf-site" branch you can see the generated output. Just taking look now. It been a couple of busy weeks with conferences and other work (yesterday I assembled, programmed and tested 40 prototype devices) and I’m just catching up on a few things. Thanks, Justin
AW: AW: AW: AW: [Website] Progress on the Website-Generation topic
Ok ... pinging this thread again ... So has anyone else had a look at the newly generated documentation in the flex-site.git "maven-site" branch? As I mentioned, if you checkout the "asf-site" branch you can see the generated output. Chris Von: Christofer Dutz Gesendet: Donnerstag, 13. Oktober 2016 07:49:01 An: dev@flex.apache.org Betreff: AW: AW: AW: AW: [Website] Progress on the Website-Generation topic Hi Alex, Well you do need buildbot ... nothing else is allowed to commit. But nothing else than buildbot. I was talking about the user workflow. These three steps are the steps you need, if you want to change something and I guess you can't get any simpler than that. Especially with the ability to test your changes locally before committing. Buildbot kicks in as soon as you commit and does the rest. But needing buildbot isn't a change as we currently need buildbot for the current version too (https://ci.apache.org/builders/flex-site-staging). So in this case we would simply replace on buildbot job with another. So if we are comparing the new three-step user workflow: 1. Do changes 2. Test them locally with a "mvn clean site" 3. Commit changes to the current user workflow, which is: 1. Do changes 2. Commit changes 3. Wait for buildbot to stage the changes 4. Check if the output is what we want in the staging area 5. Go to the Web-Ui and release all changes at once (Could be a problem that you release stuff someone else is currently working on, but I guess that's a more theoretical problem) I think the new workflow is a great improvement. And especially if it's just the fixing of typos, it boils down to a two step Workflow: 1. Do changes 2. Commit changes And another thing I noticed is that the new page performs a lot better on small resolutions like on tablets or mobile phones (If you decrease the width of the browser window the site adjusts like in the old version, but the mobile-menu-version of the new version looks a lot nicer than that of the current version) And I just wanted to put straight that this workflow is not more complicated than anything we have right now. I know 99% of people on this list just read and don't let their voice be heard and I just think if they read your email containing a completely incorrect "How I understood it" summary from you, it would manipulate them in thinking the whole thing is too complicated - which it is not. Chris Von: Alex Harui Gesendet: Donnerstag, 13. Oktober 2016 06:40:35 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: [Website] Progress on the Website-Generation topic Well, maybe I'm just being dense, but in the most recent two threads you started on this topic, you mention buildbot, and I saw a lot of buildbot traffic come into my mailbox. So apologies if I haven't followed your emails in detail, but I did not see any prior mention of not needing buildbot and could not find your 3-step workflow in previous emails. On 10/12/16, 12:54 PM, "Christofer Dutz" wrote: >Well I think I wrote down the entire workflow as well as the when's and >why's so many times that I'm not going to repeat them again. > >You don't need the build at builds.a.o at all. I just set that up in the >beginning because in the beginning I thought I would have to trigger >buildbot from there and didn't delete it after finishing, because I >simply forgot it's there. > >What you get is: >- A website in git and not svn. >- The code is generally a lot cleaner. >- You don't have to commit changes to test them in the staging area. >- You don't have to use that stupid web interface to release staged stuff >to production. > >I currently don't have asciidoctor in there at all, so please stop >describing this approach as complicated and simply read my emails. I've been trying to figure out the advantage of using builds.a.o vs buildbot. It sounds like the key point is that we can publish without having to go through the web interface. That sounds like a good deal to me. Let's see what others think. > >Workflow is: > >1. Do changes in the "maven-site" branch >2. Test them locally by running "mvn clean site" >3. Commit and push them > >That's it. Nothing more to it. So assuming others are in favor, what are the remaining steps? Do we want to exactly reproduce the existing site? Do we need to be concerned about the "insecure content" errors/warnings? Nick K was working on a revamp of our website. I wonder how that work will be impacted. Thanks, -Alex
AW: AW: AW: AW: [Website] Progress on the Website-Generation topic
Hi Alex, Well you do need buildbot ... nothing else is allowed to commit. But nothing else than buildbot. I was talking about the user workflow. These three steps are the steps you need, if you want to change something and I guess you can't get any simpler than that. Especially with the ability to test your changes locally before committing. Buildbot kicks in as soon as you commit and does the rest. But needing buildbot isn't a change as we currently need buildbot for the current version too (https://ci.apache.org/builders/flex-site-staging). So in this case we would simply replace on buildbot job with another. So if we are comparing the new three-step user workflow: 1. Do changes 2. Test them locally with a "mvn clean site" 3. Commit changes to the current user workflow, which is: 1. Do changes 2. Commit changes 3. Wait for buildbot to stage the changes 4. Check if the output is what we want in the staging area 5. Go to the Web-Ui and release all changes at once (Could be a problem that you release stuff someone else is currently working on, but I guess that's a more theoretical problem) I think the new workflow is a great improvement. And especially if it's just the fixing of typos, it boils down to a two step Workflow: 1. Do changes 2. Commit changes And another thing I noticed is that the new page performs a lot better on small resolutions like on tablets or mobile phones (If you decrease the width of the browser window the site adjusts like in the old version, but the mobile-menu-version of the new version looks a lot nicer than that of the current version) And I just wanted to put straight that this workflow is not more complicated than anything we have right now. I know 99% of people on this list just read and don't let their voice be heard and I just think if they read your email containing a completely incorrect "How I understood it" summary from you, it would manipulate them in thinking the whole thing is too complicated - which it is not. Chris Von: Alex Harui Gesendet: Donnerstag, 13. Oktober 2016 06:40:35 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: [Website] Progress on the Website-Generation topic Well, maybe I'm just being dense, but in the most recent two threads you started on this topic, you mention buildbot, and I saw a lot of buildbot traffic come into my mailbox. So apologies if I haven't followed your emails in detail, but I did not see any prior mention of not needing buildbot and could not find your 3-step workflow in previous emails. On 10/12/16, 12:54 PM, "Christofer Dutz" wrote: >Well I think I wrote down the entire workflow as well as the when's and >why's so many times that I'm not going to repeat them again. > >You don't need the build at builds.a.o at all. I just set that up in the >beginning because in the beginning I thought I would have to trigger >buildbot from there and didn't delete it after finishing, because I >simply forgot it's there. > >What you get is: >- A website in git and not svn. >- The code is generally a lot cleaner. >- You don't have to commit changes to test them in the staging area. >- You don't have to use that stupid web interface to release staged stuff >to production. > >I currently don't have asciidoctor in there at all, so please stop >describing this approach as complicated and simply read my emails. I've been trying to figure out the advantage of using builds.a.o vs buildbot. It sounds like the key point is that we can publish without having to go through the web interface. That sounds like a good deal to me. Let's see what others think. > >Workflow is: > >1. Do changes in the "maven-site" branch >2. Test them locally by running "mvn clean site" >3. Commit and push them > >That's it. Nothing more to it. So assuming others are in favor, what are the remaining steps? Do we want to exactly reproduce the existing site? Do we need to be concerned about the "insecure content" errors/warnings? Nick K was working on a revamp of our website. I wonder how that work will be impacted. Thanks, -Alex
Re: AW: AW: AW: [Website] Progress on the Website-Generation topic
Well, maybe I'm just being dense, but in the most recent two threads you started on this topic, you mention buildbot, and I saw a lot of buildbot traffic come into my mailbox. So apologies if I haven't followed your emails in detail, but I did not see any prior mention of not needing buildbot and could not find your 3-step workflow in previous emails. On 10/12/16, 12:54 PM, "Christofer Dutz" wrote: >Well I think I wrote down the entire workflow as well as the when's and >why's so many times that I'm not going to repeat them again. > >You don't need the build at builds.a.o at all. I just set that up in the >beginning because in the beginning I thought I would have to trigger >buildbot from there and didn't delete it after finishing, because I >simply forgot it's there. > >What you get is: >- A website in git and not svn. >- The code is generally a lot cleaner. >- You don't have to commit changes to test them in the staging area. >- You don't have to use that stupid web interface to release staged stuff >to production. > >I currently don't have asciidoctor in there at all, so please stop >describing this approach as complicated and simply read my emails. I've been trying to figure out the advantage of using builds.a.o vs buildbot. It sounds like the key point is that we can publish without having to go through the web interface. That sounds like a good deal to me. Let's see what others think. > >Workflow is: > >1. Do changes in the "maven-site" branch >2. Test them locally by running "mvn clean site" >3. Commit and push them > >That's it. Nothing more to it. So assuming others are in favor, what are the remaining steps? Do we want to exactly reproduce the existing site? Do we need to be concerned about the "insecure content" errors/warnings? Nick K was working on a revamp of our website. I wonder how that work will be impacted. Thanks, -Alex
AW: AW: AW: [Website] Progress on the Website-Generation topic
Well I think I wrote down the entire workflow as well as the when's and why's so many times that I'm not going to repeat them again. You don't need the build at builds.a.o at all. I just set that up in the beginning because in the beginning I thought I would have to trigger buildbot from there and didn't delete it after finishing, because I simply forgot it's there. What you get is: - A website in git and not svn. - The code is generally a lot cleaner. - You don't have to commit changes to test them in the staging area. - You don't have to use that stupid web interface to release staged stuff to production. I currently don't have asciidoctor in there at all, so please stop describing this approach as complicated and simply read my emails. Workflow is: 1. Do changes in the "maven-site" branch 2. Test them locally by running "mvn clean site" 3. Commit and push them That's it. Nothing more to it. Chris Von meinem Samsung Galaxy Smartphone gesendet. Ursprüngliche Nachricht Von: Alex Harui Datum: 12.10.16 20:20 (GMT+01:00) An: dev@flex.apache.org Betreff: Re: AW: AW: [Website] Progress on the Website-Generation topic Safari spit some warnings like that to the console but the menu and carousel seems to be working. I noticed in the emails from the buildbot that it seems to be copying html files into the flex-site repo. The version of index.html in the repo comes out differently. https://git1-us-west.apache.org/repos/asf/flex-site/repo?p=flex-site.git;a= blob_plain;f=index.html;hb=HEAD I added an "Archive artifacts" option to the Maven site build and hit "Build Now'. That might make a version of the files folks can access without having to log in. https://builds.apache.org/view/E-G/view/Flex/job/Flex-Site%20(Maven)/lastSu ccessfulBuild/artifact/target/site/index.html So, AIUI, using this workflow would make changing the website dependent on both builds.a.o and buildbot, whereas svnpubsub and gitpubsub only require buildbot? But what we get for this additional step is asciidoc support? Thanks, -Alex On 10/12/16, 10:56 AM, "Christofer Dutz" wrote: >Ok ... I just noticed that if you do it that way Chrome complained about >"unsecure scripts" (I don't get that message when accessing the files >otherwise. I had to enable those scripts to get the menus and carousel >working. > > >Chris > >________________ >Von: Alex Harui >Gesendet: Mittwoch, 12. Oktober 2016 19:45:54 >An: dev@flex.apache.org >Betreff: Re: AW: [Website] Progress on the Website-Generation topic > >I'm seeing emails titled "Automatic Site Publish by Buildbot". Are you >sure we can't see the buildbot output? I think you'd get more feedback if >folks don't have to bring down the repos and set it up. > >-Alex > >On 10/12/16, 10:39 AM, "Christofer Dutz" >wrote: > >>Hi Alex, >> >> >>Currently there is no such place, where you can just go with the browser, >>but just clone the flex-site repo and checkout the "asf-site" branch and >>you should have the working version locally. >> >> >>Just open index.html with your favorite browser :-) >> >> >>At least I just checked exactly that path and it worked as expected. >> >> >>Chris >> >> >>Von: Alex Harui >>Gesendet: Mittwoch, 12. Oktober 2016 18:31:05 >>An: dev@flex.apache.org >>Betreff: Re: [Website] Progress on the Website-Generation topic >> >>Is there a URL we can go to and see the results of this workflow? >> >>-Alex >> >>On 10/12/16, 5:48 AM, "Christofer Dutz" >>wrote: >> >>>Hi, >>> >>> >>>I just wanted to post, that I have finished setting up a new version of >>>the Website. The source is located in the "maven-site" branch of the >>>"flex-site.git" repository. >>> >>> >>>This is a Maven build which produces the Website using the >>>maven-site-plugin and the reflow-site plugin to render a responsive >>>version of the website using bootstrap (Seems that this is pretty >>>similar >>>to the original version). >>> >>> >>>I migrated all the ".cmsPage" files I needed to Markdown format and >>>removed unnecessary html code inside. I think the code is a lot cleaner >>>and easier to maintain. >>> >>> >>>Currently the site does look a little different than the original, but >>>I'm no CSS guru. I invested about 5 full days in migrating things to the >>>current point
Re: AW: AW: [Website] Progress on the Website-Generation topic
Safari spit some warnings like that to the console but the menu and carousel seems to be working. I noticed in the emails from the buildbot that it seems to be copying html files into the flex-site repo. The version of index.html in the repo comes out differently. https://git1-us-west.apache.org/repos/asf/flex-site/repo?p=flex-site.git;a= blob_plain;f=index.html;hb=HEAD I added an "Archive artifacts" option to the Maven site build and hit "Build Now'. That might make a version of the files folks can access without having to log in. https://builds.apache.org/view/E-G/view/Flex/job/Flex-Site%20(Maven)/lastSu ccessfulBuild/artifact/target/site/index.html So, AIUI, using this workflow would make changing the website dependent on both builds.a.o and buildbot, whereas svnpubsub and gitpubsub only require buildbot? But what we get for this additional step is asciidoc support? Thanks, -Alex On 10/12/16, 10:56 AM, "Christofer Dutz" wrote: >Ok ... I just noticed that if you do it that way Chrome complained about >"unsecure scripts" (I don't get that message when accessing the files >otherwise. I had to enable those scripts to get the menus and carousel >working. > > >Chris > > >Von: Alex Harui >Gesendet: Mittwoch, 12. Oktober 2016 19:45:54 >An: dev@flex.apache.org >Betreff: Re: AW: [Website] Progress on the Website-Generation topic > >I'm seeing emails titled "Automatic Site Publish by Buildbot". Are you >sure we can't see the buildbot output? I think you'd get more feedback if >folks don't have to bring down the repos and set it up. > >-Alex > >On 10/12/16, 10:39 AM, "Christofer Dutz" >wrote: > >>Hi Alex, >> >> >>Currently there is no such place, where you can just go with the browser, >>but just clone the flex-site repo and checkout the "asf-site" branch and >>you should have the working version locally. >> >> >>Just open index.html with your favorite browser :-) >> >> >>At least I just checked exactly that path and it worked as expected. >> >> >>Chris >> >> >>Von: Alex Harui >>Gesendet: Mittwoch, 12. Oktober 2016 18:31:05 >>An: dev@flex.apache.org >>Betreff: Re: [Website] Progress on the Website-Generation topic >> >>Is there a URL we can go to and see the results of this workflow? >> >>-Alex >> >>On 10/12/16, 5:48 AM, "Christofer Dutz" >>wrote: >> >>>Hi, >>> >>> >>>I just wanted to post, that I have finished setting up a new version of >>>the Website. The source is located in the "maven-site" branch of the >>>"flex-site.git" repository. >>> >>> >>>This is a Maven build which produces the Website using the >>>maven-site-plugin and the reflow-site plugin to render a responsive >>>version of the website using bootstrap (Seems that this is pretty >>>similar >>>to the original version). >>> >>> >>>I migrated all the ".cmsPage" files I needed to Markdown format and >>>removed unnecessary html code inside. I think the code is a lot cleaner >>>and easier to maintain. >>> >>> >>>Currently the site does look a little different than the original, but >>>I'm no CSS guru. I invested about 5 full days in migrating things to the >>>current point and think we should start discussing if fine-tuning makes >>>sense (I don't see any sense in investing more time and then we decide >>>not to use it) >>> >>> >>>The current workflow is that you checkout the "maven-site" branch >>>(eventually apply your changes) and do a "mvn clean site" build. This >>>will produce the website content in the "target/site" directory. Here >>>you >>>can have a look at the content which is produced. If you are satisfied >>>with your changes, you commit and push them and a buildbot build-job I >>>configured (what was quite a task) will run the same build and push the >>>generated content to the "asf-site" branch in the same git repo >>>(Currently you should be able to have a look at the generated content, >>>by >>>checking out that branch). >>> >>> >>>As soon as we are happy with the new version, all we have to do is to >>>tell Infra to sync the "asf-site" branch with their website repo and the >>>website is online. >>> >>> >>>I also documented the procedure of auto-building the website on the >>>website itself as an additional page under Documentation "Contributing >>>to >>>the Flex Website". >>> >>> >>>So I'm ready for some feedback ;-) >>> >>> >>>Chris >> >
AW: AW: [Website] Progress on the Website-Generation topic
Ok ... I just noticed that if you do it that way Chrome complained about "unsecure scripts" (I don't get that message when accessing the files otherwise. I had to enable those scripts to get the menus and carousel working. Chris Von: Alex Harui Gesendet: Mittwoch, 12. Oktober 2016 19:45:54 An: dev@flex.apache.org Betreff: Re: AW: [Website] Progress on the Website-Generation topic I'm seeing emails titled "Automatic Site Publish by Buildbot". Are you sure we can't see the buildbot output? I think you'd get more feedback if folks don't have to bring down the repos and set it up. -Alex On 10/12/16, 10:39 AM, "Christofer Dutz" wrote: >Hi Alex, > > >Currently there is no such place, where you can just go with the browser, >but just clone the flex-site repo and checkout the "asf-site" branch and >you should have the working version locally. > > >Just open index.html with your favorite browser :-) > > >At least I just checked exactly that path and it worked as expected. > > >Chris > > >Von: Alex Harui >Gesendet: Mittwoch, 12. Oktober 2016 18:31:05 >An: dev@flex.apache.org >Betreff: Re: [Website] Progress on the Website-Generation topic > >Is there a URL we can go to and see the results of this workflow? > >-Alex > >On 10/12/16, 5:48 AM, "Christofer Dutz" wrote: > >>Hi, >> >> >>I just wanted to post, that I have finished setting up a new version of >>the Website. The source is located in the "maven-site" branch of the >>"flex-site.git" repository. >> >> >>This is a Maven build which produces the Website using the >>maven-site-plugin and the reflow-site plugin to render a responsive >>version of the website using bootstrap (Seems that this is pretty similar >>to the original version). >> >> >>I migrated all the ".cmsPage" files I needed to Markdown format and >>removed unnecessary html code inside. I think the code is a lot cleaner >>and easier to maintain. >> >> >>Currently the site does look a little different than the original, but >>I'm no CSS guru. I invested about 5 full days in migrating things to the >>current point and think we should start discussing if fine-tuning makes >>sense (I don't see any sense in investing more time and then we decide >>not to use it) >> >> >>The current workflow is that you checkout the "maven-site" branch >>(eventually apply your changes) and do a "mvn clean site" build. This >>will produce the website content in the "target/site" directory. Here you >>can have a look at the content which is produced. If you are satisfied >>with your changes, you commit and push them and a buildbot build-job I >>configured (what was quite a task) will run the same build and push the >>generated content to the "asf-site" branch in the same git repo >>(Currently you should be able to have a look at the generated content, by >>checking out that branch). >> >> >>As soon as we are happy with the new version, all we have to do is to >>tell Infra to sync the "asf-site" branch with their website repo and the >>website is online. >> >> >>I also documented the procedure of auto-building the website on the >>website itself as an additional page under Documentation "Contributing to >>the Flex Website". >> >> >>So I'm ready for some feedback ;-) >> >> >>Chris >
AW: AW: [Website] Progress on the Website-Generation topic
Hi, I just noticed that I had setup a Jenkins job in parallel, that does the same generation thing, but doesn't commit to the "asf-site" branch. So you should be able to access it from the jobs workspace at: https://builds.apache.org/view/E-G/view/Flex/job/Flex-Site%20(Maven)/ws/target/site/index.html But you have to login to the Jenkins instance ... hope that's not too much to ask for ;-) Chris Von: Alex Harui Gesendet: Mittwoch, 12. Oktober 2016 19:45:54 An: dev@flex.apache.org Betreff: Re: AW: [Website] Progress on the Website-Generation topic I'm seeing emails titled "Automatic Site Publish by Buildbot". Are you sure we can't see the buildbot output? I think you'd get more feedback if folks don't have to bring down the repos and set it up. -Alex On 10/12/16, 10:39 AM, "Christofer Dutz" wrote: >Hi Alex, > > >Currently there is no such place, where you can just go with the browser, >but just clone the flex-site repo and checkout the "asf-site" branch and >you should have the working version locally. > > >Just open index.html with your favorite browser :-) > > >At least I just checked exactly that path and it worked as expected. > > >Chris > > >Von: Alex Harui >Gesendet: Mittwoch, 12. Oktober 2016 18:31:05 >An: dev@flex.apache.org >Betreff: Re: [Website] Progress on the Website-Generation topic > >Is there a URL we can go to and see the results of this workflow? > >-Alex > >On 10/12/16, 5:48 AM, "Christofer Dutz" wrote: > >>Hi, >> >> >>I just wanted to post, that I have finished setting up a new version of >>the Website. The source is located in the "maven-site" branch of the >>"flex-site.git" repository. >> >> >>This is a Maven build which produces the Website using the >>maven-site-plugin and the reflow-site plugin to render a responsive >>version of the website using bootstrap (Seems that this is pretty similar >>to the original version). >> >> >>I migrated all the ".cmsPage" files I needed to Markdown format and >>removed unnecessary html code inside. I think the code is a lot cleaner >>and easier to maintain. >> >> >>Currently the site does look a little different than the original, but >>I'm no CSS guru. I invested about 5 full days in migrating things to the >>current point and think we should start discussing if fine-tuning makes >>sense (I don't see any sense in investing more time and then we decide >>not to use it) >> >> >>The current workflow is that you checkout the "maven-site" branch >>(eventually apply your changes) and do a "mvn clean site" build. This >>will produce the website content in the "target/site" directory. Here you >>can have a look at the content which is produced. If you are satisfied >>with your changes, you commit and push them and a buildbot build-job I >>configured (what was quite a task) will run the same build and push the >>generated content to the "asf-site" branch in the same git repo >>(Currently you should be able to have a look at the generated content, by >>checking out that branch). >> >> >>As soon as we are happy with the new version, all we have to do is to >>tell Infra to sync the "asf-site" branch with their website repo and the >>website is online. >> >> >>I also documented the procedure of auto-building the website on the >>website itself as an additional page under Documentation "Contributing to >>the Flex Website". >> >> >>So I'm ready for some feedback ;-) >> >> >>Chris >
Re: AW: [Website] Progress on the Website-Generation topic
I'm seeing emails titled "Automatic Site Publish by Buildbot". Are you sure we can't see the buildbot output? I think you'd get more feedback if folks don't have to bring down the repos and set it up. -Alex On 10/12/16, 10:39 AM, "Christofer Dutz" wrote: >Hi Alex, > > >Currently there is no such place, where you can just go with the browser, >but just clone the flex-site repo and checkout the "asf-site" branch and >you should have the working version locally. > > >Just open index.html with your favorite browser :-) > > >At least I just checked exactly that path and it worked as expected. > > >Chris > > >Von: Alex Harui >Gesendet: Mittwoch, 12. Oktober 2016 18:31:05 >An: dev@flex.apache.org >Betreff: Re: [Website] Progress on the Website-Generation topic > >Is there a URL we can go to and see the results of this workflow? > >-Alex > >On 10/12/16, 5:48 AM, "Christofer Dutz" wrote: > >>Hi, >> >> >>I just wanted to post, that I have finished setting up a new version of >>the Website. The source is located in the "maven-site" branch of the >>"flex-site.git" repository. >> >> >>This is a Maven build which produces the Website using the >>maven-site-plugin and the reflow-site plugin to render a responsive >>version of the website using bootstrap (Seems that this is pretty similar >>to the original version). >> >> >>I migrated all the ".cmsPage" files I needed to Markdown format and >>removed unnecessary html code inside. I think the code is a lot cleaner >>and easier to maintain. >> >> >>Currently the site does look a little different than the original, but >>I'm no CSS guru. I invested about 5 full days in migrating things to the >>current point and think we should start discussing if fine-tuning makes >>sense (I don't see any sense in investing more time and then we decide >>not to use it) >> >> >>The current workflow is that you checkout the "maven-site" branch >>(eventually apply your changes) and do a "mvn clean site" build. This >>will produce the website content in the "target/site" directory. Here you >>can have a look at the content which is produced. If you are satisfied >>with your changes, you commit and push them and a buildbot build-job I >>configured (what was quite a task) will run the same build and push the >>generated content to the "asf-site" branch in the same git repo >>(Currently you should be able to have a look at the generated content, by >>checking out that branch). >> >> >>As soon as we are happy with the new version, all we have to do is to >>tell Infra to sync the "asf-site" branch with their website repo and the >>website is online. >> >> >>I also documented the procedure of auto-building the website on the >>website itself as an additional page under Documentation "Contributing to >>the Flex Website". >> >> >>So I'm ready for some feedback ;-) >> >> >>Chris >
AW: [Website] Progress on the Website-Generation topic
Hi Alex, Currently there is no such place, where you can just go with the browser, but just clone the flex-site repo and checkout the "asf-site" branch and you should have the working version locally. Just open index.html with your favorite browser :-) At least I just checked exactly that path and it worked as expected. Chris Von: Alex Harui Gesendet: Mittwoch, 12. Oktober 2016 18:31:05 An: dev@flex.apache.org Betreff: Re: [Website] Progress on the Website-Generation topic Is there a URL we can go to and see the results of this workflow? -Alex On 10/12/16, 5:48 AM, "Christofer Dutz" wrote: >Hi, > > >I just wanted to post, that I have finished setting up a new version of >the Website. The source is located in the "maven-site" branch of the >"flex-site.git" repository. > > >This is a Maven build which produces the Website using the >maven-site-plugin and the reflow-site plugin to render a responsive >version of the website using bootstrap (Seems that this is pretty similar >to the original version). > > >I migrated all the ".cmsPage" files I needed to Markdown format and >removed unnecessary html code inside. I think the code is a lot cleaner >and easier to maintain. > > >Currently the site does look a little different than the original, but >I'm no CSS guru. I invested about 5 full days in migrating things to the >current point and think we should start discussing if fine-tuning makes >sense (I don't see any sense in investing more time and then we decide >not to use it) > > >The current workflow is that you checkout the "maven-site" branch >(eventually apply your changes) and do a "mvn clean site" build. This >will produce the website content in the "target/site" directory. Here you >can have a look at the content which is produced. If you are satisfied >with your changes, you commit and push them and a buildbot build-job I >configured (what was quite a task) will run the same build and push the >generated content to the "asf-site" branch in the same git repo >(Currently you should be able to have a look at the generated content, by >checking out that branch). > > >As soon as we are happy with the new version, all we have to do is to >tell Infra to sync the "asf-site" branch with their website repo and the >website is online. > > >I also documented the procedure of auto-building the website on the >website itself as an additional page under Documentation "Contributing to >the Flex Website". > > >So I'm ready for some feedback ;-) > > >Chris
