You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Michael Gentry <bl...@gmail.com> on 2017/05/04 11:56:09 UTC
Website FIles
I did a quick grep trying to find the website files, but didn't locate
them. Can anyone give me a hint? I think ASF would like us to add the
"Support Apache" link/logo [1] to our site (in the header).
Thanks,
mrg
[1] See how POI did it: http://poi.apache.org
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
I must be going blind because I looked at the CMS reference page yesterday
and missed it.
I wanted to run local because skeleton.html is a bit "odd" in the way it
includes the graphics/logos in the header -- solely through master.css:
<h2><a href="http://www.apache.org" title="The Apache Software
Foundation"><span>The Apache Software Foundation</span></a></h2>
Not even an image tag there, so I'll have to figure out the CSS needed to
prepend other logo. I expect that to take many attempts and wanted to
avoid a slew of commits.
Thanks,
mrg
On Sun, May 21, 2017 at 2:22 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
> > Is there a way to run the CMS locally to see what your change will look
> > like in advance or is it commit+pray?
>
> I used to be able to run it locally in the past. IIRC it took a while to
> setup. There are instructions here [1].
>
> > It looks like I'll need to modify skeleton.html and master.css, which
> > aren't as simple as editing Markdown.
>
> Judging from your commits from yesterday, you've already figured out how
> to use the staging environment [2] :) IMO that's an easier option than
> setting up Perl environment locally.
>
> Andrus
>
>
> [1] https://www.apache.org/dev/cmsref.html#faq-cms-command-
> line-build-tools
> [2] https://www.apache.org/dev/cmsref.html#staging
>
> > On May 20, 2017, at 7:11 PM, Michael Gentry <bl...@gmail.com> wrote:
> >
> > I'm just now getting to this ...
> >
> > Is there a way to run the CMS locally to see what your change will look
> > like in advance or is it commit+pray?
> >
> > It looks like I'll need to modify skeleton.html and master.css, which
> > aren't as simple as editing Markdown.
> >
> >
> > On Thu, May 4, 2017 at 8:53 AM, Andrus Adamchik <an...@objectstyle.org>
> > wrote:
> >
> >> I tried documenting the CMS process here:
> http://cayenne.apache.org/dev/
> >> cms-guide.html It is missing a few details, but has all the links.
> >>
> >> Andrus
> >>
> >>
> >>> On May 4, 2017, at 3:51 PM, Michael Gentry <bl...@gmail.com>
> wrote:
> >>>
> >>> I'll have to try tonight when I have my Apache credentials. Hopefully
> >> I'll
> >>> have access.
> >>>
> >>> Thanks!
> >>>
> >>> mrg
> >>>
> >>>
> >>> On Thu, May 4, 2017 at 8:14 AM, Aristedes Maniatis <ar...@maniatis.org>
> >> wrote:
> >>>
> >>>> https://cms.apache.org/cayenne/
> >>>>
> >>>>
> >>>>
> >>>> On 4/5/17 9:56pm, Michael Gentry wrote:
> >>>>> I did a quick grep trying to find the website files, but didn't
> locate
> >>>>> them. Can anyone give me a hint? I think ASF would like us to add
> the
> >>>>> "Support Apache" link/logo [1] to our site (in the header).
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> mrg
> >>>>>
> >>>>> [1] See how POI did it: http://poi.apache.org
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> -------------------------->
> >>>> Aristedes Maniatis
> >>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
> >>>>
> >>
> >>
>
>
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
Actually, what I said doesn't make sense. Did I mention I'm living in an
allergy fog these days? :-)
Even if the production site references the staging site, the robots.txt on
the staging site should discourage search engines from following it.
On Sun, May 21, 2017 at 9:13 AM, Michael Gentry <bl...@gmail.com> wrote:
> There is no robots.txt file on production, though, so the link will be
> found there. I'll update it.
>
>
> On Sun, May 21, 2017 at 9:08 AM, Andrus Adamchik <an...@objectstyle.org>
> wrote:
>
>>
>>
>> > On May 21, 2017, at 3:59 PM, Andrus Adamchik <an...@objectstyle.org>
>> wrote:
>> >
>> >>
>> >> On May 21, 2017, at 3:48 PM, Michael Gentry <bl...@gmail.com>
>> wrote:
>> >>
>> >> That's the main change. I also added a link to the Staging CMS site
>> since
>> >> I had to dig that up (didn't know it offhand).
>> >
>> > Exposing staging links publicly and adding more weight to them by
>> creating links from the main site will be bad for SEO (a link to a second
>> copy of the site will confuse Google as to which is the primary page). Wish
>> we had the ability to set <link rel="canonical"../> for each page to help
>> Google. So maybe remove the <a> tag from that link, and simply keep the
>> text?
>>
>> On the other hand, it seems that the CMS already takes care of it by
>> automatically placing a restrictive robots.txt on staging containing this:
>>
>> User-agent: *
>> Disallow: /
>>
>> So my worries may be misplaced, but since search engines are complete
>> blackboxes, you can never be 100% sure :)
>>
>> Andrus
>
>
>
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
There is no robots.txt file on production, though, so the link will be
found there. I'll update it.
On Sun, May 21, 2017 at 9:08 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
>
>
> > On May 21, 2017, at 3:59 PM, Andrus Adamchik <an...@objectstyle.org>
> wrote:
> >
> >>
> >> On May 21, 2017, at 3:48 PM, Michael Gentry <bl...@gmail.com>
> wrote:
> >>
> >> That's the main change. I also added a link to the Staging CMS site
> since
> >> I had to dig that up (didn't know it offhand).
> >
> > Exposing staging links publicly and adding more weight to them by
> creating links from the main site will be bad for SEO (a link to a second
> copy of the site will confuse Google as to which is the primary page). Wish
> we had the ability to set <link rel="canonical"../> for each page to help
> Google. So maybe remove the <a> tag from that link, and simply keep the
> text?
>
> On the other hand, it seems that the CMS already takes care of it by
> automatically placing a restrictive robots.txt on staging containing this:
>
> User-agent: *
> Disallow: /
>
> So my worries may be misplaced, but since search engines are complete
> blackboxes, you can never be 100% sure :)
>
> Andrus
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
> On May 21, 2017, at 3:59 PM, Andrus Adamchik <an...@objectstyle.org> wrote:
>
>>
>> On May 21, 2017, at 3:48 PM, Michael Gentry <bl...@gmail.com> wrote:
>>
>> That's the main change. I also added a link to the Staging CMS site since
>> I had to dig that up (didn't know it offhand).
>
> Exposing staging links publicly and adding more weight to them by creating links from the main site will be bad for SEO (a link to a second copy of the site will confuse Google as to which is the primary page). Wish we had the ability to set <link rel="canonical"../> for each page to help Google. So maybe remove the <a> tag from that link, and simply keep the text?
On the other hand, it seems that the CMS already takes care of it by automatically placing a restrictive robots.txt on staging containing this:
User-agent: *
Disallow: /
So my worries may be misplaced, but since search engines are complete blackboxes, you can never be 100% sure :)
Andrus
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
I'm fine with obfuscating the staging site to confuse search engines. I'll
do that later.
There are WAY too many board@ e-mails... I'm actually surprised I saw this
one from Sally. Most I just file away.
The location I put the support badge was largely lifted from the POI site.
I even lifted their graphic since the original one Sally posted didn't have
transparency information (all a white background, which didn't work in our
header).
On Sun, May 21, 2017 at 8:59 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
>
> > On May 21, 2017, at 3:48 PM, Michael Gentry <bl...@gmail.com> wrote:
> >
> > That's the main change. I also added a link to the Staging CMS site
> since
> > I had to dig that up (didn't know it offhand).
>
> Exposing staging links publicly and adding more weight to them by creating
> links from the main site will be bad for SEO (a link to a second copy of
> the site will confuse Google as to which is the primary page). Wish we had
> the ability to set <link rel="canonical"../> for each page to help Google.
> So maybe remove the <a> tag from that link, and simply keep the text?
>
> > Yes, the Board was requesting it. Are you still getting the board@
> e-mails?
>
> I do. I just don't have time to read all of them. :)
>
> > If so, look for the "[PMCs] Seeking your help for ASF's 18th
> > Anniversary" thread from Sally.
>
> Got it. Perhaps in the new design we'll find a better place for it. I
> guess for now it is fine where it is.
>
> > (And yes, it was back in March, but I'm
> > lagged -- allergy season and work haven't been my friend.)
>
> Sorry to hear about the allergies.
>
> Andrus
>
>
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
> On May 21, 2017, at 3:48 PM, Michael Gentry <bl...@gmail.com> wrote:
>
> That's the main change. I also added a link to the Staging CMS site since
> I had to dig that up (didn't know it offhand).
Exposing staging links publicly and adding more weight to them by creating links from the main site will be bad for SEO (a link to a second copy of the site will confuse Google as to which is the primary page). Wish we had the ability to set <link rel="canonical"../> for each page to help Google. So maybe remove the <a> tag from that link, and simply keep the text?
> Yes, the Board was requesting it. Are you still getting the board@ e-mails?
I do. I just don't have time to read all of them. :)
> If so, look for the "[PMCs] Seeking your help for ASF's 18th
> Anniversary" thread from Sally.
Got it. Perhaps in the new design we'll find a better place for it. I guess for now it is fine where it is.
> (And yes, it was back in March, but I'm
> lagged -- allergy season and work haven't been my friend.)
Sorry to hear about the allergies.
Andrus
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
That's the main change. I also added a link to the Staging CMS site since
I had to dig that up (didn't know it offhand).
Yes, the Board was requesting it. Are you still getting the board@
e-mails? If so, look for the "[PMCs] Seeking your help for ASF's 18th
Anniversary" thread from Sally. (And yes, it was back in March, but I'm
lagged -- allergy season and work haven't been my friend.)
mrg
On Sun, May 21, 2017 at 8:39 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
> I see the "Support Apache" logo appeared in the header. Was that the only
> change?
>
> I am curious - is "Support Apache" something that the Board asked us to do?
>
> I am asking, as ObjectStyle was going to donate the time of our designer
> in the nearest future to modernize Cayenne site. So I wanted to understand
> what are the minimal branding requirements.
>
> Andrus
>
> > On May 21, 2017, at 3:06 PM, Michael Gentry <bl...@gmail.com> wrote:
> >
> > You are right. A total PITA to set up! :-)
> >
> > I've got the update on the staging site if anyone wants to look/comment:
> >
> > http://cayenne.staging.apache.org/
> >
> > Thanks,
> >
> > mrg
> >
> >
> > On Sun, May 21, 2017 at 2:22 AM, Andrus Adamchik <andrus@objectstyle.org
> >
> > wrote:
> >
> >>> Is there a way to run the CMS locally to see what your change will look
> >>> like in advance or is it commit+pray?
> >>
> >> I used to be able to run it locally in the past. IIRC it took a while to
> >> setup. There are instructions here [1].
> >>
> >>> It looks like I'll need to modify skeleton.html and master.css, which
> >>> aren't as simple as editing Markdown.
> >>
> >> Judging from your commits from yesterday, you've already figured out how
> >> to use the staging environment [2] :) IMO that's an easier option than
> >> setting up Perl environment locally.
> >>
> >> Andrus
> >>
> >>
> >> [1] https://www.apache.org/dev/cmsref.html#faq-cms-command-
> >> line-build-tools
> >> [2] https://www.apache.org/dev/cmsref.html#staging
> >>
> >>> On May 20, 2017, at 7:11 PM, Michael Gentry <bl...@gmail.com>
> wrote:
> >>>
> >>> I'm just now getting to this ...
> >>>
> >>> Is there a way to run the CMS locally to see what your change will look
> >>> like in advance or is it commit+pray?
> >>>
> >>> It looks like I'll need to modify skeleton.html and master.css, which
> >>> aren't as simple as editing Markdown.
> >>>
> >>>
> >>> On Thu, May 4, 2017 at 8:53 AM, Andrus Adamchik <
> andrus@objectstyle.org>
> >>> wrote:
> >>>
> >>>> I tried documenting the CMS process here:
> >> http://cayenne.apache.org/dev/
> >>>> cms-guide.html It is missing a few details, but has all the links.
> >>>>
> >>>> Andrus
> >>>>
> >>>>
> >>>>> On May 4, 2017, at 3:51 PM, Michael Gentry <bl...@gmail.com>
> >> wrote:
> >>>>>
> >>>>> I'll have to try tonight when I have my Apache credentials.
> Hopefully
> >>>> I'll
> >>>>> have access.
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>> mrg
> >>>>>
> >>>>>
> >>>>> On Thu, May 4, 2017 at 8:14 AM, Aristedes Maniatis <ari@maniatis.org
> >
> >>>> wrote:
> >>>>>
> >>>>>> https://cms.apache.org/cayenne/
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On 4/5/17 9:56pm, Michael Gentry wrote:
> >>>>>>> I did a quick grep trying to find the website files, but didn't
> >> locate
> >>>>>>> them. Can anyone give me a hint? I think ASF would like us to add
> >> the
> >>>>>>> "Support Apache" link/logo [1] to our site (in the header).
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>>
> >>>>>>> mrg
> >>>>>>>
> >>>>>>> [1] See how POI did it: http://poi.apache.org
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> -------------------------->
> >>>>>> Aristedes Maniatis
> >>>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
> >>>>>>
> >>>>
> >>>>
> >>
> >>
>
>
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
Some random ASF sites I thought had nice-looking themes:
https://cordova.apache.org
http://wicket.apache.org
http://cloudstack.apache.org
http://jclouds.apache.org
http://shiro.apache.org
On Thu, May 25, 2017 at 9:16 AM, Michael Gentry <bl...@gmail.com> wrote:
> Well, the templates will need to utilize variables[1] and more, which is
> part of the "programming" of the site.
>
> [1] https://jekyllrb.com/docs/variables/
>
>
> On Thu, May 25, 2017 at 9:11 AM, Andrus Adamchik <an...@objectstyle.org>
> wrote:
>
>>
>> > On May 25, 2017, at 2:25 PM, Michael Gentry <bl...@gmail.com>
>> wrote:
>> >
>> > Are you going to try to find a pre-built theme or create one by hand? I
>> > think Andrus has ideas on this since he was talking about an ObjectStyle
>> > designer working on it.
>>
>> We haven't started brainstorming it yet. When we do, we'll certainly keep
>> the list posted.
>>
>> > Speaking of which, Andrus, will your designer be
>> > comfortable with Jekyll? There typically is a bit of "programming"
>> > involved in creating things.
>>
>> I don't expect any problems there. Worst case, myself and other Cayenne
>> programmers will take static HTML/CSS/JS and convert to Jekyll.
>>
>> Andrus
>
>
>
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
Well, the templates will need to utilize variables[1] and more, which is
part of the "programming" of the site.
[1] https://jekyllrb.com/docs/variables/
On Thu, May 25, 2017 at 9:11 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
>
> > On May 25, 2017, at 2:25 PM, Michael Gentry <bl...@gmail.com> wrote:
> >
> > Are you going to try to find a pre-built theme or create one by hand? I
> > think Andrus has ideas on this since he was talking about an ObjectStyle
> > designer working on it.
>
> We haven't started brainstorming it yet. When we do, we'll certainly keep
> the list posted.
>
> > Speaking of which, Andrus, will your designer be
> > comfortable with Jekyll? There typically is a bit of "programming"
> > involved in creating things.
>
> I don't expect any problems there. Worst case, myself and other Cayenne
> programmers will take static HTML/CSS/JS and convert to Jekyll.
>
> Andrus
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
> On May 25, 2017, at 2:25 PM, Michael Gentry <bl...@gmail.com> wrote:
>
> Are you going to try to find a pre-built theme or create one by hand? I
> think Andrus has ideas on this since he was talking about an ObjectStyle
> designer working on it.
We haven't started brainstorming it yet. When we do, we'll certainly keep the list posted.
> Speaking of which, Andrus, will your designer be
> comfortable with Jekyll? There typically is a bit of "programming"
> involved in creating things.
I don't expect any problems there. Worst case, myself and other Cayenne programmers will take static HTML/CSS/JS and convert to Jekyll.
Andrus
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
I think a personal GitHub site for prototyping would be fine. Let us know
where it is so we can fork, etc. :-)
Are you going to try to find a pre-built theme or create one by hand? I
think Andrus has ideas on this since he was talking about an ObjectStyle
designer working on it. Speaking of which, Andrus, will your designer be
comfortable with Jekyll? There typically is a bit of "programming"
involved in creating things.
On Thu, May 25, 2017 at 12:37 AM, Aristedes Maniatis <ar...@maniatis.org>
wrote:
> I have a 5 hour flight coming up next week. Should I use some of that time
> until my laptop battery runs out to create a new jekyll site and transfer a
> bit of the content over? No styling or anything, just a basic transfer of
> data ready for some design concept to be laid over the top.
>
> Is that useful? Is everyone happy with jekyll as a choice? Should I just
> make a new personal github repo and we can move it over somewhere else
> later?
>
> Ari
>
>
> On 25/5/17 8:24am, Michael Gentry wrote:
> > I just published the changes. Let me know if you encounter any issues.
> >
> > As to Ari's comment of only publishing static content, the ASF CMS
> dynamic
> > editing of our site using their CMS Bookmarklet isn't all that great, so
> I
> > don't think we'd really miss/lose anything by only publishing static
> > content. I'd prefer to edit and preview the live/local statically
> > generated content, personally, and publish when we think it is correct.
> >
> > Thanks,
> >
> > mrg
> >
> >
> >
> >
> > On Sun, May 21, 2017 at 7:20 PM, Aristedes Maniatis <ar...@maniatis.org>
> > wrote:
> >
> >> I'll chime in here that I love Jekyll and am currently moving my own
> site
> >> across to it. I used it also for our company intranet and (off topic) I
> >> highly recommend it for that purpose.
> >>
> >> If we do move to Jekyll, I'd be happy to do a bunch of the initial setup
> >> work. But I asked about Jekyll years ago to see if the Apache CMS
> supported
> >> it and the answer was no. So that would mean we'd need to only upload
> >> static content.
> >>
> >> Ari
> >>
> >>
> >> On 21/5/17 11:10pm, Andrus Adamchik wrote:
> >>> I'd be +1 on Jekyll. We can simply check in Jekyll-generated content to
> >> the site SVN as HTML/CSS/JS.
> >>>
> >>> Andrus
> >>>
> >>>> On May 21, 2017, at 4:06 PM, Michael Gentry <bl...@gmail.com>
> >> wrote:
> >>>>
> >>>> On Sun, May 21, 2017 at 8:39 AM, Andrus Adamchik <
> >> andrus@objectstyle.org>
> >>>> wrote:
> >>>>
> >>>>> I am asking, as ObjectStyle was going to donate the time of our
> >> designer
> >>>>> in the nearest future to modernize Cayenne site. So I wanted to
> >> understand
> >>>>> what are the minimal branding requirements.
> >>>>>
> >>>>
> >>>> If we are going to modernize the site, are we going to stick with
> Apache
> >>>> CMS (is that a requirement?) or perhaps go with a more popular and
> >> actively
> >>>> developed static site generator, such as Jekyll [1]? Two things I
> >> noticed
> >>>> when running ASF CMS locally compared to Jekyll:
> >>>>
> >>>> 1. I kept having to edit the produced HTML to localize the file: CSS
> >>>> references since /style.css won't work correctly. Jekyll handles this
> >>>> correct. Of course, maybe ASF CMS can support this and I don't know
> >> how to
> >>>> change it.
> >>>> 2. Jekyll has a server option that will monitor changes as you are
> >> editing
> >>>> and smartly regenerate your site, which is faster.
> >>>>
> >>>>
> >>>> [1] https://jekyllrb.com/ -- Also the static site generator used by
> >> GitHub
> >>>> Pages.
> >>>
> >>
> >>
> >> --
> >> -------------------------->
> >> Aristedes Maniatis
> >> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
> >>
> >
>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
That's a lot slower than I'd expect, but I have never built a "large"
Jekyll site. I'm not opposed to non-Jekyll -- we aren't hosting at GitHub,
so Jekyll isn't really a requirement. Perhaps it is time for Ari to chime
in since he's used Jekyll more.
FWIW, found this Hugo theme site which may give your designer some ideas or
a starting point (if using Hugo):
https://themes.gohugo.io
On Mon, Jul 10, 2017 at 8:00 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
> > What did they consider slow when building large sites? When doing a
> > complete build or when running the jekyll server interactively?
>
> Complete build. They mentioned their build taking 10-15 min.
>
> Andrus
>
>
> > On Jul 10, 2017, at 2:46 PM, Michael Gentry <bl...@gmail.com> wrote:
> >
> > I installed bundler per the Jekyll quickstart[1], namely:
> >
> > $ gem install jekyll bundler
> >
> > What did they consider slow when building large sites? When doing a
> > complete build or when running the jekyll server interactively?
> >
> > mrg
> >
> > [1] https://jekyllrb.com/docs/quickstart/
> >
> >
> >
> > On Mon, Jul 10, 2017 at 4:30 AM, Andrus Adamchik <andrus@objectstyle.org
> >
> > wrote:
> >
> >> This week I was going to talk to our designer about the new web site.
> Now
> >> trying to build Ari's prototype using the instructions in README.txt.
> Got
> >> stuck on Item #5:
> >>
> >>> 5. # bundler install
> >>
> >> -bash: bundler: command not found
> >>
> >> Do I need a special PATH for Jekyll?
> >>
> >> Coincidentally today we had a discussion with my team about a new site
> >> engine for bootique.io. And it was mentioned that Jekyll becomes pretty
> >> slow when building large sites. My colleagues recommended Hugo -
> >> https://gohugo.io/ , which is a similar engine. I don't have experience
> >> with either, but I thought I'd mention.
> >>
> >> Andrus
> >>
> >>
> >>
> >>> On May 31, 2017, at 2:15 AM, Aristedes Maniatis <ar...@maniatis.org>
> >> wrote:
> >>>
> >>> On 25/5/17 2:48pm, Andrus Adamchik wrote:
> >>>> A prototype of Jekyll-based system would certainly be cool to try.
> >>>
> >>> OK, it is in pretty good shape now and worth everyone having a look at:
> >>>
> >>> https://git-wip-us.apache.org/repos/asf/cayenne-website.git
> >>>
> >>> Clone that and follow the readme at the top. Remember that I'm not
> >> putting effort into styling, this is about the technology and working on
> >> cleaning up the copywriting. I've also used SCSS for all the
> stylesheets,
> >> which will make the job later of adding a theme much easier.
> >>>
> >>> If everyone is happy with what I've done, I'll keep going. There is a
> >> bit more tidying to be done and thinking about the navigation elements.
> >>>
> >>>
> >>> Ari
> >>>
> >>>
> >>> --
> >>> -------------------------->
> >>> Aristedes Maniatis
> >>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
> >>
> >>
>
>
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
> What did they consider slow when building large sites? When doing a
> complete build or when running the jekyll server interactively?
Complete build. They mentioned their build taking 10-15 min.
Andrus
> On Jul 10, 2017, at 2:46 PM, Michael Gentry <bl...@gmail.com> wrote:
>
> I installed bundler per the Jekyll quickstart[1], namely:
>
> $ gem install jekyll bundler
>
> What did they consider slow when building large sites? When doing a
> complete build or when running the jekyll server interactively?
>
> mrg
>
> [1] https://jekyllrb.com/docs/quickstart/
>
>
>
> On Mon, Jul 10, 2017 at 4:30 AM, Andrus Adamchik <an...@objectstyle.org>
> wrote:
>
>> This week I was going to talk to our designer about the new web site. Now
>> trying to build Ari's prototype using the instructions in README.txt. Got
>> stuck on Item #5:
>>
>>> 5. # bundler install
>>
>> -bash: bundler: command not found
>>
>> Do I need a special PATH for Jekyll?
>>
>> Coincidentally today we had a discussion with my team about a new site
>> engine for bootique.io. And it was mentioned that Jekyll becomes pretty
>> slow when building large sites. My colleagues recommended Hugo -
>> https://gohugo.io/ , which is a similar engine. I don't have experience
>> with either, but I thought I'd mention.
>>
>> Andrus
>>
>>
>>
>>> On May 31, 2017, at 2:15 AM, Aristedes Maniatis <ar...@maniatis.org>
>> wrote:
>>>
>>> On 25/5/17 2:48pm, Andrus Adamchik wrote:
>>>> A prototype of Jekyll-based system would certainly be cool to try.
>>>
>>> OK, it is in pretty good shape now and worth everyone having a look at:
>>>
>>> https://git-wip-us.apache.org/repos/asf/cayenne-website.git
>>>
>>> Clone that and follow the readme at the top. Remember that I'm not
>> putting effort into styling, this is about the technology and working on
>> cleaning up the copywriting. I've also used SCSS for all the stylesheets,
>> which will make the job later of adding a theme much easier.
>>>
>>> If everyone is happy with what I've done, I'll keep going. There is a
>> bit more tidying to be done and thinking about the navigation elements.
>>>
>>>
>>> Ari
>>>
>>>
>>> --
>>> -------------------------->
>>> Aristedes Maniatis
>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>>
>>
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
I installed bundler per the Jekyll quickstart[1], namely:
$ gem install jekyll bundler
What did they consider slow when building large sites? When doing a
complete build or when running the jekyll server interactively?
mrg
[1] https://jekyllrb.com/docs/quickstart/
On Mon, Jul 10, 2017 at 4:30 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
> This week I was going to talk to our designer about the new web site. Now
> trying to build Ari's prototype using the instructions in README.txt. Got
> stuck on Item #5:
>
> > 5. # bundler install
>
> -bash: bundler: command not found
>
> Do I need a special PATH for Jekyll?
>
> Coincidentally today we had a discussion with my team about a new site
> engine for bootique.io. And it was mentioned that Jekyll becomes pretty
> slow when building large sites. My colleagues recommended Hugo -
> https://gohugo.io/ , which is a similar engine. I don't have experience
> with either, but I thought I'd mention.
>
> Andrus
>
>
>
> > On May 31, 2017, at 2:15 AM, Aristedes Maniatis <ar...@maniatis.org>
> wrote:
> >
> > On 25/5/17 2:48pm, Andrus Adamchik wrote:
> >> A prototype of Jekyll-based system would certainly be cool to try.
> >
> > OK, it is in pretty good shape now and worth everyone having a look at:
> >
> > https://git-wip-us.apache.org/repos/asf/cayenne-website.git
> >
> > Clone that and follow the readme at the top. Remember that I'm not
> putting effort into styling, this is about the technology and working on
> cleaning up the copywriting. I've also used SCSS for all the stylesheets,
> which will make the job later of adding a theme much easier.
> >
> > If everyone is happy with what I've done, I'll keep going. There is a
> bit more tidying to be done and thinking about the navigation elements.
> >
> >
> > Ari
> >
> >
> > --
> > -------------------------->
> > Aristedes Maniatis
> > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
>
Re: Website FIles
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 7/11/17 8:42 AM, Aristedes Maniatis wrote:
> Speed for jekyll seems to be building about 100 pages in 3-4 seconds. But I don't have a bigger site to compare and test with. But I'm sure it depends on what you are doing on those pages.
I just checked this against the Cayenne site I created.
$ jekyll s --incremental
takes 28 seconds (to start up Jekyll for the first time and build the whole site)
Page edits after that take 14 seconds. Pretty sure it is my sidebar navigation implementation which is the slow part here since every page has to iterate through the whole site to build the menu.
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
I think we should not worry too much about the second group. At least not on the home page. We should mention in some form that Cayenne is an ORM of course, but beyond that the top priority should not be advertising us as "an ORM", but rather as "a better ORM" [*]. We just spoke with the designer, and I floated an idea of a slogan: "ORM with character".
Andrus
[*] BTW these days ORM competition is no longer raw JDBC, but rather SQL mappers like Jooq and Mybatis.
> On Jul 12, 2017, at 10:38 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
>> On the home page I think we need to replace most of the text with a more visual representation of what Cayenne is and why somebody would want to use it (Modeler, DB-first flow, transparent transactions, ObjectContext, featured extensions such as commitlog and crypto). Also we were thinking of creating a video tutorial for 4.0. This may also go on the home page.
>
> These are good ideas. Let's talk about who the audience is. I think they are:
>
> 1. People who already know Hibernate. Or Rails or some other lesser known ORM.
>
> 2. People who don't use any ORM at all and are new to the idea.
>
>
> There are some other speciality audiences (like people coming from WebObjects) which I think are so small as to not be important for the front page.
>
> I think the test will be how we can create a message to cover these two really different audiences.
>
>
> Cayenne ORM
> -----------
> * Make your application portable: avoid DB lock-in
> * Validation, control your data
> * Performance (hollow, paging)
> * Security and safety
> * Faster development, vastly easier refactoring
> * Type safety
>
>
> Enterprise features (this is 'not Hibernate')
> -------------------
> * ObjectContext
> * DB-first
> * transactions
> * Modeler
>
>
> Plugins
> -------
> * ROP
> * crypto
> * logging
> * etc
>
>
> What do you think of this structure?
Re: Website FIles
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 7/12/17 4:54 PM, Andrus Adamchik wrote:
>> Can we keep moving forward with the general concept?
> Absolutely. I am actually meeting with the designer later today and was going to use your prototype as the initial spec. I like the suggested structure with a bare minimum set of top-level menus and a more detailed menu in the footer. Most people will indeed be interested in download, docs or support.
Good. I think that's a very modern approach which I like. Use the footer for navigation, but keep some important calls to action in the header area.
> On the home page I think we need to replace most of the text with a more visual representation of what Cayenne is and why somebody would want to use it (Modeler, DB-first flow, transparent transactions, ObjectContext, featured extensions such as commitlog and crypto). Also we were thinking of creating a video tutorial for 4.0. This may also go on the home page.
These are good ideas. Let's talk about who the audience is. I think they are:
1. People who already know Hibernate. Or Rails or some other lesser known ORM.
2. People who don't use any ORM at all and are new to the idea.
There are some other speciality audiences (like people coming from WebObjects) which I think are so small as to not be important for the front page.
I think the test will be how we can create a message to cover these two really different audiences.
Cayenne ORM
-----------
* Make your application portable: avoid DB lock-in
* Validation, control your data
* Performance (hollow, paging)
* Security and safety
* Faster development, vastly easier refactoring
* Type safety
Enterprise features (this is 'not Hibernate')
-------------------
* ObjectContext
* DB-first
* transactions
* Modeler
Plugins
-------
* ROP
* crypto
* logging
* etc
What do you think of this structure?
> Will also need to accommodate the Apache boilerplate (logos, donate button), social and GitHub buttons.
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
> Can we keep moving forward with the general concept?
Absolutely. I am actually meeting with the designer later today and was going to use your prototype as the initial spec. I like the suggested structure with a bare minimum set of top-level menus and a more detailed menu in the footer. Most people will indeed be interested in download, docs or support.
On the home page I think we need to replace most of the text with a more visual representation of what Cayenne is and why somebody would want to use it (Modeler, DB-first flow, transparent transactions, ObjectContext, featured extensions such as commitlog and crypto). Also we were thinking of creating a video tutorial for 4.0. This may also go on the home page.
Will also need to accommodate the Apache boilerplate (logos, donate button), social and GitHub buttons.
Andrus
> On Jul 12, 2017, at 7:14 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
> On 7/12/17 10:22 AM, Michael Gentry wrote:
>> FWIW, on my 2011 iMac (HD, not SSD):
>>
>> ~40s without --incremental
>> ~25s with --incremental
>>
>
> Other than these speed issues (we can certainly make it faster if we can optimise the way the menu is constructed)... what does everyone think of the website itself?
>
> Can we keep moving forward with the general concept?
>
> Ari
>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 7/12/17 10:22 AM, Michael Gentry wrote:
> FWIW, on my 2011 iMac (HD, not SSD):
>
> ~40s without --incremental
> ~25s with --incremental
>
Other than these speed issues (we can certainly make it faster if we can optimise the way the menu is constructed)... what does everyone think of the website itself?
Can we keep moving forward with the general concept?
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
FWIW, on my 2011 iMac (HD, not SSD):
~40s without --incremental
~25s with --incremental
Re: Website FIles
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 7/11/17 4:18 PM, Andrus Adamchik wrote:
> Worked for me after "sudo gem install jekyll bundler". Also had to change the run command for jekyll to this due to some dependency versions mismatch:
>
> bundle exec jekyll s --incremental
>
> No idea what "bundle exec" means, but it works. Time of a second run is 19 sec.
Bundler is the ruby dependency management tool. So this executes the jekyll application using the dependencies (gems) installs for that specific project rather than those installed in your system. Frankly the Ruby bundling system is a huge pain....
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
> On Jul 11, 2017, at 1:42 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
> On 7/10/17 6:30 PM, Andrus Adamchik wrote:
>> -bash: bundler: command not found
>>
>> Do I need a special PATH for Jekyll?
>
> Did you get it working?
Worked for me after "sudo gem install jekyll bundler". Also had to change the run command for jekyll to this due to some dependency versions mismatch:
bundle exec jekyll s --incremental
No idea what "bundle exec" means, but it works. Time of a second run is 19 sec.
>> Coincidentally today we had a discussion with my team about a new site engine for bootique.io. And it was mentioned that Jekyll becomes pretty slow when building large sites. My colleagues recommended Hugo - https://gohugo.io/ , which is a similar engine. I don't have experience with either, but I thought I'd mention.
>
> I looked at a few of these a while ago and found jekyll the most popular (and therefore supported) by a large margin.
>
> Speed for jekyll seems to be building about 100 pages in 3-4 seconds. But I don't have a bigger site to compare and test with. But I'm sure it depends on what you are doing on those pages.
As an example I was pointed to these stats (A popular Russian Java podcast site, about 140 pages) :
https://travis-ci.org/razbor-poletov/razbor-poletov.github.com/builds
Though of course this is Travis. It can be slow for any number of reasons unrelated to the script. And 2 min is by no means *unbearably* slow.
Andrus
Re: Website FIles
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 7/10/17 6:30 PM, Andrus Adamchik wrote:
> -bash: bundler: command not found
>
> Do I need a special PATH for Jekyll?
Did you get it working?
> Coincidentally today we had a discussion with my team about a new site engine for bootique.io. And it was mentioned that Jekyll becomes pretty slow when building large sites. My colleagues recommended Hugo - https://gohugo.io/ , which is a similar engine. I don't have experience with either, but I thought I'd mention.
I looked at a few of these a while ago and found jekyll the most popular (and therefore supported) by a large margin.
Speed for jekyll seems to be building about 100 pages in 3-4 seconds. But I don't have a bigger site to compare and test with. But I'm sure it depends on what you are doing on those pages.
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
This week I was going to talk to our designer about the new web site. Now trying to build Ari's prototype using the instructions in README.txt. Got stuck on Item #5:
> 5. # bundler install
-bash: bundler: command not found
Do I need a special PATH for Jekyll?
Coincidentally today we had a discussion with my team about a new site engine for bootique.io. And it was mentioned that Jekyll becomes pretty slow when building large sites. My colleagues recommended Hugo - https://gohugo.io/ , which is a similar engine. I don't have experience with either, but I thought I'd mention.
Andrus
> On May 31, 2017, at 2:15 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
> On 25/5/17 2:48pm, Andrus Adamchik wrote:
>> A prototype of Jekyll-based system would certainly be cool to try.
>
> OK, it is in pretty good shape now and worth everyone having a look at:
>
> https://git-wip-us.apache.org/repos/asf/cayenne-website.git
>
> Clone that and follow the readme at the top. Remember that I'm not putting effort into styling, this is about the technology and working on cleaning up the copywriting. I've also used SCSS for all the stylesheets, which will make the job later of adding a theme much easier.
>
> If everyone is happy with what I've done, I'll keep going. There is a bit more tidying to be done and thinking about the navigation elements.
>
>
> Ari
>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 25/5/17 2:48pm, Andrus Adamchik wrote:
> A prototype of Jekyll-based system would certainly be cool to try.
OK, it is in pretty good shape now and worth everyone having a look at:
https://git-wip-us.apache.org/repos/asf/cayenne-website.git
Clone that and follow the readme at the top. Remember that I'm not putting effort into styling, this is about the technology and working on cleaning up the copywriting. I've also used SCSS for all the stylesheets, which will make the job later of adding a theme much easier.
If everyone is happy with what I've done, I'll keep going. There is a bit more tidying to be done and thinking about the navigation elements.
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
A prototype of Jekyll-based system would certainly be cool to try.
Andrus
> On May 25, 2017, at 7:37 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
> I have a 5 hour flight coming up next week. Should I use some of that time until my laptop battery runs out to create a new jekyll site and transfer a bit of the content over? No styling or anything, just a basic transfer of data ready for some design concept to be laid over the top.
>
> Is that useful? Is everyone happy with jekyll as a choice? Should I just make a new personal github repo and we can move it over somewhere else later?
>
> Ari
>
>
> On 25/5/17 8:24am, Michael Gentry wrote:
>> I just published the changes. Let me know if you encounter any issues.
>>
>> As to Ari's comment of only publishing static content, the ASF CMS dynamic
>> editing of our site using their CMS Bookmarklet isn't all that great, so I
>> don't think we'd really miss/lose anything by only publishing static
>> content. I'd prefer to edit and preview the live/local statically
>> generated content, personally, and publish when we think it is correct.
>>
>> Thanks,
>>
>> mrg
>>
>>
>>
>>
>> On Sun, May 21, 2017 at 7:20 PM, Aristedes Maniatis <ar...@maniatis.org>
>> wrote:
>>
>>> I'll chime in here that I love Jekyll and am currently moving my own site
>>> across to it. I used it also for our company intranet and (off topic) I
>>> highly recommend it for that purpose.
>>>
>>> If we do move to Jekyll, I'd be happy to do a bunch of the initial setup
>>> work. But I asked about Jekyll years ago to see if the Apache CMS supported
>>> it and the answer was no. So that would mean we'd need to only upload
>>> static content.
>>>
>>> Ari
>>>
>>>
>>> On 21/5/17 11:10pm, Andrus Adamchik wrote:
>>>> I'd be +1 on Jekyll. We can simply check in Jekyll-generated content to
>>> the site SVN as HTML/CSS/JS.
>>>>
>>>> Andrus
>>>>
>>>>> On May 21, 2017, at 4:06 PM, Michael Gentry <bl...@gmail.com>
>>> wrote:
>>>>>
>>>>> On Sun, May 21, 2017 at 8:39 AM, Andrus Adamchik <
>>> andrus@objectstyle.org>
>>>>> wrote:
>>>>>
>>>>>> I am asking, as ObjectStyle was going to donate the time of our
>>> designer
>>>>>> in the nearest future to modernize Cayenne site. So I wanted to
>>> understand
>>>>>> what are the minimal branding requirements.
>>>>>>
>>>>>
>>>>> If we are going to modernize the site, are we going to stick with Apache
>>>>> CMS (is that a requirement?) or perhaps go with a more popular and
>>> actively
>>>>> developed static site generator, such as Jekyll [1]? Two things I
>>> noticed
>>>>> when running ASF CMS locally compared to Jekyll:
>>>>>
>>>>> 1. I kept having to edit the produced HTML to localize the file: CSS
>>>>> references since /style.css won't work correctly. Jekyll handles this
>>>>> correct. Of course, maybe ASF CMS can support this and I don't know
>>> how to
>>>>> change it.
>>>>> 2. Jekyll has a server option that will monitor changes as you are
>>> editing
>>>>> and smartly regenerate your site, which is faster.
>>>>>
>>>>>
>>>>> [1] https://jekyllrb.com/ -- Also the static site generator used by
>>> GitHub
>>>>> Pages.
>>>>
>>>
>>>
>>> --
>>> -------------------------->
>>> Aristedes Maniatis
>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>>>
>>
>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Aristedes Maniatis <ar...@maniatis.org>.
I have a 5 hour flight coming up next week. Should I use some of that time until my laptop battery runs out to create a new jekyll site and transfer a bit of the content over? No styling or anything, just a basic transfer of data ready for some design concept to be laid over the top.
Is that useful? Is everyone happy with jekyll as a choice? Should I just make a new personal github repo and we can move it over somewhere else later?
Ari
On 25/5/17 8:24am, Michael Gentry wrote:
> I just published the changes. Let me know if you encounter any issues.
>
> As to Ari's comment of only publishing static content, the ASF CMS dynamic
> editing of our site using their CMS Bookmarklet isn't all that great, so I
> don't think we'd really miss/lose anything by only publishing static
> content. I'd prefer to edit and preview the live/local statically
> generated content, personally, and publish when we think it is correct.
>
> Thanks,
>
> mrg
>
>
>
>
> On Sun, May 21, 2017 at 7:20 PM, Aristedes Maniatis <ar...@maniatis.org>
> wrote:
>
>> I'll chime in here that I love Jekyll and am currently moving my own site
>> across to it. I used it also for our company intranet and (off topic) I
>> highly recommend it for that purpose.
>>
>> If we do move to Jekyll, I'd be happy to do a bunch of the initial setup
>> work. But I asked about Jekyll years ago to see if the Apache CMS supported
>> it and the answer was no. So that would mean we'd need to only upload
>> static content.
>>
>> Ari
>>
>>
>> On 21/5/17 11:10pm, Andrus Adamchik wrote:
>>> I'd be +1 on Jekyll. We can simply check in Jekyll-generated content to
>> the site SVN as HTML/CSS/JS.
>>>
>>> Andrus
>>>
>>>> On May 21, 2017, at 4:06 PM, Michael Gentry <bl...@gmail.com>
>> wrote:
>>>>
>>>> On Sun, May 21, 2017 at 8:39 AM, Andrus Adamchik <
>> andrus@objectstyle.org>
>>>> wrote:
>>>>
>>>>> I am asking, as ObjectStyle was going to donate the time of our
>> designer
>>>>> in the nearest future to modernize Cayenne site. So I wanted to
>> understand
>>>>> what are the minimal branding requirements.
>>>>>
>>>>
>>>> If we are going to modernize the site, are we going to stick with Apache
>>>> CMS (is that a requirement?) or perhaps go with a more popular and
>> actively
>>>> developed static site generator, such as Jekyll [1]? Two things I
>> noticed
>>>> when running ASF CMS locally compared to Jekyll:
>>>>
>>>> 1. I kept having to edit the produced HTML to localize the file: CSS
>>>> references since /style.css won't work correctly. Jekyll handles this
>>>> correct. Of course, maybe ASF CMS can support this and I don't know
>> how to
>>>> change it.
>>>> 2. Jekyll has a server option that will monitor changes as you are
>> editing
>>>> and smartly regenerate your site, which is faster.
>>>>
>>>>
>>>> [1] https://jekyllrb.com/ -- Also the static site generator used by
>> GitHub
>>>> Pages.
>>>
>>
>>
>> --
>> -------------------------->
>> Aristedes Maniatis
>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>>
>
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
I just published the changes. Let me know if you encounter any issues.
As to Ari's comment of only publishing static content, the ASF CMS dynamic
editing of our site using their CMS Bookmarklet isn't all that great, so I
don't think we'd really miss/lose anything by only publishing static
content. I'd prefer to edit and preview the live/local statically
generated content, personally, and publish when we think it is correct.
Thanks,
mrg
On Sun, May 21, 2017 at 7:20 PM, Aristedes Maniatis <ar...@maniatis.org>
wrote:
> I'll chime in here that I love Jekyll and am currently moving my own site
> across to it. I used it also for our company intranet and (off topic) I
> highly recommend it for that purpose.
>
> If we do move to Jekyll, I'd be happy to do a bunch of the initial setup
> work. But I asked about Jekyll years ago to see if the Apache CMS supported
> it and the answer was no. So that would mean we'd need to only upload
> static content.
>
> Ari
>
>
> On 21/5/17 11:10pm, Andrus Adamchik wrote:
> > I'd be +1 on Jekyll. We can simply check in Jekyll-generated content to
> the site SVN as HTML/CSS/JS.
> >
> > Andrus
> >
> >> On May 21, 2017, at 4:06 PM, Michael Gentry <bl...@gmail.com>
> wrote:
> >>
> >> On Sun, May 21, 2017 at 8:39 AM, Andrus Adamchik <
> andrus@objectstyle.org>
> >> wrote:
> >>
> >>> I am asking, as ObjectStyle was going to donate the time of our
> designer
> >>> in the nearest future to modernize Cayenne site. So I wanted to
> understand
> >>> what are the minimal branding requirements.
> >>>
> >>
> >> If we are going to modernize the site, are we going to stick with Apache
> >> CMS (is that a requirement?) or perhaps go with a more popular and
> actively
> >> developed static site generator, such as Jekyll [1]? Two things I
> noticed
> >> when running ASF CMS locally compared to Jekyll:
> >>
> >> 1. I kept having to edit the produced HTML to localize the file: CSS
> >> references since /style.css won't work correctly. Jekyll handles this
> >> correct. Of course, maybe ASF CMS can support this and I don't know
> how to
> >> change it.
> >> 2. Jekyll has a server option that will monitor changes as you are
> editing
> >> and smartly regenerate your site, which is faster.
> >>
> >>
> >> [1] https://jekyllrb.com/ -- Also the static site generator used by
> GitHub
> >> Pages.
> >
>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
Re: Website FIles
Posted by Aristedes Maniatis <ar...@maniatis.org>.
I'll chime in here that I love Jekyll and am currently moving my own site across to it. I used it also for our company intranet and (off topic) I highly recommend it for that purpose.
If we do move to Jekyll, I'd be happy to do a bunch of the initial setup work. But I asked about Jekyll years ago to see if the Apache CMS supported it and the answer was no. So that would mean we'd need to only upload static content.
Ari
On 21/5/17 11:10pm, Andrus Adamchik wrote:
> I'd be +1 on Jekyll. We can simply check in Jekyll-generated content to the site SVN as HTML/CSS/JS.
>
> Andrus
>
>> On May 21, 2017, at 4:06 PM, Michael Gentry <bl...@gmail.com> wrote:
>>
>> On Sun, May 21, 2017 at 8:39 AM, Andrus Adamchik <an...@objectstyle.org>
>> wrote:
>>
>>> I am asking, as ObjectStyle was going to donate the time of our designer
>>> in the nearest future to modernize Cayenne site. So I wanted to understand
>>> what are the minimal branding requirements.
>>>
>>
>> If we are going to modernize the site, are we going to stick with Apache
>> CMS (is that a requirement?) or perhaps go with a more popular and actively
>> developed static site generator, such as Jekyll [1]? Two things I noticed
>> when running ASF CMS locally compared to Jekyll:
>>
>> 1. I kept having to edit the produced HTML to localize the file: CSS
>> references since /style.css won't work correctly. Jekyll handles this
>> correct. Of course, maybe ASF CMS can support this and I don't know how to
>> change it.
>> 2. Jekyll has a server option that will monitor changes as you are editing
>> and smartly regenerate your site, which is faster.
>>
>>
>> [1] https://jekyllrb.com/ -- Also the static site generator used by GitHub
>> Pages.
>
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
I'd be +1 on Jekyll. We can simply check in Jekyll-generated content to the site SVN as HTML/CSS/JS.
Andrus
> On May 21, 2017, at 4:06 PM, Michael Gentry <bl...@gmail.com> wrote:
>
> On Sun, May 21, 2017 at 8:39 AM, Andrus Adamchik <an...@objectstyle.org>
> wrote:
>
>> I am asking, as ObjectStyle was going to donate the time of our designer
>> in the nearest future to modernize Cayenne site. So I wanted to understand
>> what are the minimal branding requirements.
>>
>
> If we are going to modernize the site, are we going to stick with Apache
> CMS (is that a requirement?) or perhaps go with a more popular and actively
> developed static site generator, such as Jekyll [1]? Two things I noticed
> when running ASF CMS locally compared to Jekyll:
>
> 1. I kept having to edit the produced HTML to localize the file: CSS
> references since /style.css won't work correctly. Jekyll handles this
> correct. Of course, maybe ASF CMS can support this and I don't know how to
> change it.
> 2. Jekyll has a server option that will monitor changes as you are editing
> and smartly regenerate your site, which is faster.
>
>
> [1] https://jekyllrb.com/ -- Also the static site generator used by GitHub
> Pages.
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
On Sun, May 21, 2017 at 8:39 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
> I am asking, as ObjectStyle was going to donate the time of our designer
> in the nearest future to modernize Cayenne site. So I wanted to understand
> what are the minimal branding requirements.
>
If we are going to modernize the site, are we going to stick with Apache
CMS (is that a requirement?) or perhaps go with a more popular and actively
developed static site generator, such as Jekyll [1]? Two things I noticed
when running ASF CMS locally compared to Jekyll:
1. I kept having to edit the produced HTML to localize the file: CSS
references since /style.css won't work correctly. Jekyll handles this
correct. Of course, maybe ASF CMS can support this and I don't know how to
change it.
2. Jekyll has a server option that will monitor changes as you are editing
and smartly regenerate your site, which is faster.
[1] https://jekyllrb.com/ -- Also the static site generator used by GitHub
Pages.
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
> On May 21, 2017, at 3:39 PM, Andrus Adamchik <an...@objectstyle.org> wrote:
>
>> I've got the update on the staging site if anyone wants to look/comment:
>>
>> http://cayenne.staging.apache.org/
I guess the main limitation of using staging for site review is that a single review would block any other updates to the site, and has a risk of going live prematurely. Shouldn't be a big problem in practice, as the updates happen rarely, usually around a release time. But notifying everybody will be important in this scenario.
Andrus
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
I see the "Support Apache" logo appeared in the header. Was that the only change?
I am curious - is "Support Apache" something that the Board asked us to do?
I am asking, as ObjectStyle was going to donate the time of our designer in the nearest future to modernize Cayenne site. So I wanted to understand what are the minimal branding requirements.
Andrus
> On May 21, 2017, at 3:06 PM, Michael Gentry <bl...@gmail.com> wrote:
>
> You are right. A total PITA to set up! :-)
>
> I've got the update on the staging site if anyone wants to look/comment:
>
> http://cayenne.staging.apache.org/
>
> Thanks,
>
> mrg
>
>
> On Sun, May 21, 2017 at 2:22 AM, Andrus Adamchik <an...@objectstyle.org>
> wrote:
>
>>> Is there a way to run the CMS locally to see what your change will look
>>> like in advance or is it commit+pray?
>>
>> I used to be able to run it locally in the past. IIRC it took a while to
>> setup. There are instructions here [1].
>>
>>> It looks like I'll need to modify skeleton.html and master.css, which
>>> aren't as simple as editing Markdown.
>>
>> Judging from your commits from yesterday, you've already figured out how
>> to use the staging environment [2] :) IMO that's an easier option than
>> setting up Perl environment locally.
>>
>> Andrus
>>
>>
>> [1] https://www.apache.org/dev/cmsref.html#faq-cms-command-
>> line-build-tools
>> [2] https://www.apache.org/dev/cmsref.html#staging
>>
>>> On May 20, 2017, at 7:11 PM, Michael Gentry <bl...@gmail.com> wrote:
>>>
>>> I'm just now getting to this ...
>>>
>>> Is there a way to run the CMS locally to see what your change will look
>>> like in advance or is it commit+pray?
>>>
>>> It looks like I'll need to modify skeleton.html and master.css, which
>>> aren't as simple as editing Markdown.
>>>
>>>
>>> On Thu, May 4, 2017 at 8:53 AM, Andrus Adamchik <an...@objectstyle.org>
>>> wrote:
>>>
>>>> I tried documenting the CMS process here:
>> http://cayenne.apache.org/dev/
>>>> cms-guide.html It is missing a few details, but has all the links.
>>>>
>>>> Andrus
>>>>
>>>>
>>>>> On May 4, 2017, at 3:51 PM, Michael Gentry <bl...@gmail.com>
>> wrote:
>>>>>
>>>>> I'll have to try tonight when I have my Apache credentials. Hopefully
>>>> I'll
>>>>> have access.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> mrg
>>>>>
>>>>>
>>>>> On Thu, May 4, 2017 at 8:14 AM, Aristedes Maniatis <ar...@maniatis.org>
>>>> wrote:
>>>>>
>>>>>> https://cms.apache.org/cayenne/
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 4/5/17 9:56pm, Michael Gentry wrote:
>>>>>>> I did a quick grep trying to find the website files, but didn't
>> locate
>>>>>>> them. Can anyone give me a hint? I think ASF would like us to add
>> the
>>>>>>> "Support Apache" link/logo [1] to our site (in the header).
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> mrg
>>>>>>>
>>>>>>> [1] See how POI did it: http://poi.apache.org
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> -------------------------->
>>>>>> Aristedes Maniatis
>>>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>>>>>>
>>>>
>>>>
>>
>>
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
You are right. A total PITA to set up! :-)
I've got the update on the staging site if anyone wants to look/comment:
http://cayenne.staging.apache.org/
Thanks,
mrg
On Sun, May 21, 2017 at 2:22 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
> > Is there a way to run the CMS locally to see what your change will look
> > like in advance or is it commit+pray?
>
> I used to be able to run it locally in the past. IIRC it took a while to
> setup. There are instructions here [1].
>
> > It looks like I'll need to modify skeleton.html and master.css, which
> > aren't as simple as editing Markdown.
>
> Judging from your commits from yesterday, you've already figured out how
> to use the staging environment [2] :) IMO that's an easier option than
> setting up Perl environment locally.
>
> Andrus
>
>
> [1] https://www.apache.org/dev/cmsref.html#faq-cms-command-
> line-build-tools
> [2] https://www.apache.org/dev/cmsref.html#staging
>
> > On May 20, 2017, at 7:11 PM, Michael Gentry <bl...@gmail.com> wrote:
> >
> > I'm just now getting to this ...
> >
> > Is there a way to run the CMS locally to see what your change will look
> > like in advance or is it commit+pray?
> >
> > It looks like I'll need to modify skeleton.html and master.css, which
> > aren't as simple as editing Markdown.
> >
> >
> > On Thu, May 4, 2017 at 8:53 AM, Andrus Adamchik <an...@objectstyle.org>
> > wrote:
> >
> >> I tried documenting the CMS process here:
> http://cayenne.apache.org/dev/
> >> cms-guide.html It is missing a few details, but has all the links.
> >>
> >> Andrus
> >>
> >>
> >>> On May 4, 2017, at 3:51 PM, Michael Gentry <bl...@gmail.com>
> wrote:
> >>>
> >>> I'll have to try tonight when I have my Apache credentials. Hopefully
> >> I'll
> >>> have access.
> >>>
> >>> Thanks!
> >>>
> >>> mrg
> >>>
> >>>
> >>> On Thu, May 4, 2017 at 8:14 AM, Aristedes Maniatis <ar...@maniatis.org>
> >> wrote:
> >>>
> >>>> https://cms.apache.org/cayenne/
> >>>>
> >>>>
> >>>>
> >>>> On 4/5/17 9:56pm, Michael Gentry wrote:
> >>>>> I did a quick grep trying to find the website files, but didn't
> locate
> >>>>> them. Can anyone give me a hint? I think ASF would like us to add
> the
> >>>>> "Support Apache" link/logo [1] to our site (in the header).
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> mrg
> >>>>>
> >>>>> [1] See how POI did it: http://poi.apache.org
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> -------------------------->
> >>>> Aristedes Maniatis
> >>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
> >>>>
> >>
> >>
>
>
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
> Is there a way to run the CMS locally to see what your change will look
> like in advance or is it commit+pray?
I used to be able to run it locally in the past. IIRC it took a while to setup. There are instructions here [1].
> It looks like I'll need to modify skeleton.html and master.css, which
> aren't as simple as editing Markdown.
Judging from your commits from yesterday, you've already figured out how to use the staging environment [2] :) IMO that's an easier option than setting up Perl environment locally.
Andrus
[1] https://www.apache.org/dev/cmsref.html#faq-cms-command-line-build-tools
[2] https://www.apache.org/dev/cmsref.html#staging
> On May 20, 2017, at 7:11 PM, Michael Gentry <bl...@gmail.com> wrote:
>
> I'm just now getting to this ...
>
> Is there a way to run the CMS locally to see what your change will look
> like in advance or is it commit+pray?
>
> It looks like I'll need to modify skeleton.html and master.css, which
> aren't as simple as editing Markdown.
>
>
> On Thu, May 4, 2017 at 8:53 AM, Andrus Adamchik <an...@objectstyle.org>
> wrote:
>
>> I tried documenting the CMS process here: http://cayenne.apache.org/dev/
>> cms-guide.html It is missing a few details, but has all the links.
>>
>> Andrus
>>
>>
>>> On May 4, 2017, at 3:51 PM, Michael Gentry <bl...@gmail.com> wrote:
>>>
>>> I'll have to try tonight when I have my Apache credentials. Hopefully
>> I'll
>>> have access.
>>>
>>> Thanks!
>>>
>>> mrg
>>>
>>>
>>> On Thu, May 4, 2017 at 8:14 AM, Aristedes Maniatis <ar...@maniatis.org>
>> wrote:
>>>
>>>> https://cms.apache.org/cayenne/
>>>>
>>>>
>>>>
>>>> On 4/5/17 9:56pm, Michael Gentry wrote:
>>>>> I did a quick grep trying to find the website files, but didn't locate
>>>>> them. Can anyone give me a hint? I think ASF would like us to add the
>>>>> "Support Apache" link/logo [1] to our site (in the header).
>>>>>
>>>>> Thanks,
>>>>>
>>>>> mrg
>>>>>
>>>>> [1] See how POI did it: http://poi.apache.org
>>>>>
>>>>
>>>>
>>>> --
>>>> -------------------------->
>>>> Aristedes Maniatis
>>>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>>>>
>>
>>
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
I'm just now getting to this ...
Is there a way to run the CMS locally to see what your change will look
like in advance or is it commit+pray?
It looks like I'll need to modify skeleton.html and master.css, which
aren't as simple as editing Markdown.
On Thu, May 4, 2017 at 8:53 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
> I tried documenting the CMS process here: http://cayenne.apache.org/dev/
> cms-guide.html It is missing a few details, but has all the links.
>
> Andrus
>
>
> > On May 4, 2017, at 3:51 PM, Michael Gentry <bl...@gmail.com> wrote:
> >
> > I'll have to try tonight when I have my Apache credentials. Hopefully
> I'll
> > have access.
> >
> > Thanks!
> >
> > mrg
> >
> >
> > On Thu, May 4, 2017 at 8:14 AM, Aristedes Maniatis <ar...@maniatis.org>
> wrote:
> >
> >> https://cms.apache.org/cayenne/
> >>
> >>
> >>
> >> On 4/5/17 9:56pm, Michael Gentry wrote:
> >>> I did a quick grep trying to find the website files, but didn't locate
> >>> them. Can anyone give me a hint? I think ASF would like us to add the
> >>> "Support Apache" link/logo [1] to our site (in the header).
> >>>
> >>> Thanks,
> >>>
> >>> mrg
> >>>
> >>> [1] See how POI did it: http://poi.apache.org
> >>>
> >>
> >>
> >> --
> >> -------------------------->
> >> Aristedes Maniatis
> >> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
> >>
>
>
Re: Website FIles
Posted by Andrus Adamchik <an...@objectstyle.org>.
I tried documenting the CMS process here: http://cayenne.apache.org/dev/cms-guide.html It is missing a few details, but has all the links.
Andrus
> On May 4, 2017, at 3:51 PM, Michael Gentry <bl...@gmail.com> wrote:
>
> I'll have to try tonight when I have my Apache credentials. Hopefully I'll
> have access.
>
> Thanks!
>
> mrg
>
>
> On Thu, May 4, 2017 at 8:14 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
>> https://cms.apache.org/cayenne/
>>
>>
>>
>> On 4/5/17 9:56pm, Michael Gentry wrote:
>>> I did a quick grep trying to find the website files, but didn't locate
>>> them. Can anyone give me a hint? I think ASF would like us to add the
>>> "Support Apache" link/logo [1] to our site (in the header).
>>>
>>> Thanks,
>>>
>>> mrg
>>>
>>> [1] See how POI did it: http://poi.apache.org
>>>
>>
>>
>> --
>> -------------------------->
>> Aristedes Maniatis
>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>>
Re: Website FIles
Posted by Michael Gentry <bl...@gmail.com>.
I'll have to try tonight when I have my Apache credentials. Hopefully I'll
have access.
Thanks!
mrg
On Thu, May 4, 2017 at 8:14 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> https://cms.apache.org/cayenne/
>
>
>
> On 4/5/17 9:56pm, Michael Gentry wrote:
> > I did a quick grep trying to find the website files, but didn't locate
> > them. Can anyone give me a hint? I think ASF would like us to add the
> > "Support Apache" link/logo [1] to our site (in the header).
> >
> > Thanks,
> >
> > mrg
> >
> > [1] See how POI did it: http://poi.apache.org
> >
>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
Re: Website FIles
Posted by Aristedes Maniatis <ar...@maniatis.org>.
https://cms.apache.org/cayenne/
On 4/5/17 9:56pm, Michael Gentry wrote:
> I did a quick grep trying to find the website files, but didn't locate
> them. Can anyone give me a hint? I think ASF would like us to add the
> "Support Apache" link/logo [1] to our site (in the header).
>
> Thanks,
>
> mrg
>
> [1] See how POI did it: http://poi.apache.org
>
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A