You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Andrus Adamchik <an...@objectstyle.org> on 2017/07/10 08:30:52 UTC

Re: Website FIles

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>.
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 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/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 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