My 2 cents:
I think the blue and yellow theme is the better of the two. For some
reason, the blue and green theme does not work for me.

Grails is a full-stack, convention-over-configuration web framework that
emphasizes developer productivity, rapid development, and seamless
integration with Groovy, Java, and the broader JVM ecosystem.

/Mattias

Den ons 19 mars 2025 kl 23:21 skrev Ricardo Vargas <ricvar...@gmail.com>:

> I agree with Gianluca,
>
> I'd love to see Grails back in green too!
>
> I'd also add to the selling points:
>
> - Build full-stack applications fast and easily.
>
> Ricardo V.
>
>
>
>
>
> On Wed, Mar 19, 2025 at 9:48 PM Gianluca Sartori <g.sart...@gmail.com>
> wrote:
>
> > I would love to see Grails 7 getting in touch with its origins to pave
> > its legacy.
> > The original green should get back, with the complementary orange links,
> > supporting the new rounded logo.
> >
> > On the selling proposition, I would give the following priorities:
> >
> > *1. Enterprise grade*
> >     - 20 years of evolution and refinement
> >     - Security first, built on top of giants: Spring Framework 6,
> Hibernate
> > 6, Jakarta EE 10, Java 21 (And we don't use Log4J... XD just kidding)
> >     - Deploy on-premises and on the cloud with solid performances
> >
> > *2. Easy to learn*
> >     - Less code, more results with the Apache Groovy programming language
> >     - Quick onboarding of new developers
> >     - Access to the complete documentation
> >
> > *3. Made to last*
> >     - Leverage the huge availability of Java libraries and tools
> >     - Updated to the latest web technologies
> >     - Used by "BIG NAMES HERE IF WE CAN"
> >
> >
> > Gianluca Sartori
> >
> > On Wed, 19 Mar 2025 at 18:33, James Fredley <jamesfred...@apache.org>
> > wrote:
> >
> > > - What do we want new visitors to immediately understand about the
> > > framework?
> > >
> > > Apache Grail is a convention over configuration, Don’t Repeat Yourself
> > > (DRY), full stack framework similar to Rails and Django, built on the
> > > enterprise foundation of Spring Boot and Hibernate with a nearly two
> > decade
> > > history.
> > >
> > > It harnesses the power of the Apache Groovy language and the extensive
> > use
> > > of Domain Specific Languages (DSLs) in the Java ecosystem.
> > >
> > > - What do you think Grails’ unique selling propositions are today? -
> What
> > > makes it stand out in 2025?
> > >
> > > Rapid application development
> > > convention over configuration
> > > scaffolding
> > > solid performance
> > > enterprise maturity
> > > strong integration with Java ecosystems, especially Spring Boot/Spring
> > > Framework and Jakarta EE 10
> > > "framework of frameworks," allowing the use of Spring and Hibernate
> > > frameworks
> > >
> > > - Most crucially... what color(s) should Grails.org use in 2025?
> > >
> > > I like both the green and the orange designs with the blue header.  The
> > > green somewhat associates it with https://spring.io/ and the
> historical
> > > green from
> > > https://web.archive.org/web/20170630001932/http://www.grails.org/
> > >
> > > I do like the blue usage on https://start.grails.org/ with the orange
> > > logo at the bottom.
> > >
> > > James
> > >
> > > On 2025/03/19 16:57:43 James Fredley wrote:
> > > > Posting here on behalf of Martyn Duffy:
> > > >
> > > > Hey everyone, I wanted to share an initial take on a new Grails
> landing
> > > page. Would love your feedback on how to best capture the essence of
> > Grails:
> > > >
> > > > What do we want new visitors to immediately understand about the
> > > framework?
> > > >
> > > > What do you think Grails’ unique selling propositions are today?
> > > >
> > > > What makes it stand out in 2025?
> > > >
> > > > Most crucially... what color(s) should Grails.org use in 2025?
> > > >
> > > > See Green vs Orange Mockups:
> > >
> >
> https://drive.google.com/drive/folders/1XV-dwssnRcN1O5lxzD4Y9nbd2H4ORcuZ?usp=sharing
> > > >
> > > > Would appreciate any thoughts - especially from those who’ve been
> > > building with Grails for a while - thanks!
> > > >
> > > >
> > >
> >
>

Reply via email to