|
Visit our blog
News & EventsNew www.springframework.org site is live!I'm happy to announce that a new, enhanced www.springframework.org is now live! The site, sporting a new look and driven by a dynamic content management engine, should serve the needs of the Spring community much better. Expect the look and feel, as well as the capabilities of the site, to continue to evolve. This was a lot of work. Thanks to Interface21
for sponsoring the installation, design and hosting of the new site.
This site will sit on the same host as the Spring Framework Support
foums. Thanks to Contegix LLC for providig excellent managed hosting, and subsidizing the bandwidth. |
Upcoming Training04/15 - 04/18:
Bangalore Rich Web Applications with Spring Enterprise Integration with Spring 04/16 - 04/19:
Wien Plus: Hibernate with Spring, Core Spring.NET, Groovy & Grails Newsletter SubscriptionOur monthly newsletter is packed full of techniques, tutorials, tips and tricks to get you on your way to Spring nirvana. View Archive |
Comments
criticism
I must admit that I found the previous version more clear. The new font is smaller (less readable) and the first I see on the left side are the Upcoming events instead of the main navigation links.
Switching the navigation with the events would already help, I think.
Aside of that it is a good idea to put the site on top of a CMS, even though it is a PHP CMS :-). Less time spent in site update is more time spent with improving the Springframework.
Good luck and thanks for a great piece of software.
Gaudy graphics!
I liked the soft colors of the previous springframework site much better. And the graphics look really gaudy.
Beautiful
Very beautiful new interface. Much easier to use. Thanks.
What's the skinny on the new engine?
Can you elaborate on the new dynamic content management engine? Spring based, open source, easy to use? Is this something Interface21 wrote?
See comment below from Colin
See comment below from Colin in response to Matt.
> -----Message d'origine-----
> De : springframework-user-admin@lists.sourceforge.net
> [mailto:springframework-user-admin@lists.sourceforge.net] De
> la part de Colin Sampaleanu
> Envoyé : jeudi 5 mai 2005 22:45
> À : springframework-user@lists.sourceforge.net
> Cc : springframework-developer@lists.sourceforge.net
> Objet : Re: [Springframework-user] Re:
> [Springframework-developer] New www.springframework.org site is live!
>
>
> The CMS here is Drupal.
>
> It's certainly possible to handle historical URLs, and some
> already are.
> Most of the site is handled dynamically by Drupal, but
> /dtd
> and
> /buttons
> is redirected internally (invisibly) by Apache to the new
> http://static.springframework.org
> site meant for completely static content like online
> documentation. It
> was critical to do this to not break DTD URLs and existing
> button links
> using the images directly from the Spring website.
>
> There is a question of what to do this for however. The old static
> structure was somewhat adhoc and simplistic. If you look at
> your example
>
> http://www.springframework.org/docs/api/org/springframework/we
> b/servlet/mvc/SimpleFormController.html
> there's no product name (spring base library vs. webflow vs whatever
> other lib) in there, and there's no version number. Under the new
> structure, this is available as
>
> http://static.springframework.org/spring/docs/1.1.5/api/org/sp
> ringframework/web/servlet/mvc/SimpleFormController.html
>
> Colin
>
> Matt Raible wrote:
>
> > Nice work guys - now we just need to get you to write the CMS using
> > Spring. ;-) I'm guessing this site uses Plone like the
> > springframework.com site?
> >
> > One request: is it possible to put in some smart redirection so that
> > old URLs still resolve? For example:
> >
> > http://www.springframework.org/docs/api/org/springframework/web/
> > servlet/mvc/SimpleFormController.html
> >
> > I imagine there's lots of articles and such that link to the
> > documentation and now those links might not resolve.
> >
> > http://www.w3.org/Provider/Style/URI.html ;-)
> >
> > Thanks,
> >
> > Matt
> >
> >
Why Drupal?
I find it interesting that a group centered around Java frameworks would choose a CMS engine based on PHP. I'm not making a judgement, just wondering what the thought process was.
Less time spent on CMS tasks = more time spent on Spring projects? Drupal was the best tool for the job and Interface21 doesn't intend to extend this site with it's own code? Interface21 has PHP experience that I don't know about?
Just wondering, framework guys don't do anything by accident. Maybe there's something to be learned here.
We have very finite resources
We have a very finite amount of resources which are frankly better spent on enhancing parts of Spring that are of use to the largest audience, not on modifying or implementing a CMS. While we did have to spend a decent amount of time tweaking the theme to our satisfaction, and inputing the old content, equivalent or more effort of this type would have been requiered with any solution. On the other hand, Drupal out of the box comes with all the functionality we need, so we didn't have to spend any of those scarce resources on development or customization of the product itself. It's that simple.
Of course we went through a complete process of figuring out our requirements and looking for the best product to meet those requirements, now. The "now" part is very important. I have a feeling that in a year's time at least some of the products like Daisy, Magnolia, eXo, Lenya, etc. will have evolved to the point where they they would make better sense than Drupal.