Getting the ball rolling.

[ScArcher2]

Hey,

I'd like to help get the ball rolling on the new website if I can.
I didn't know about this group until today. I don't know what's been
done, but I'm willing to help in any way I can.
I've been on IRC for a few years, but I haven't really followed the
mailing list until recently.

If no one has started on a prototype yet I wouldn't mind mocking
something up. I'm not a designer, so I would most likely use plain
html and then rework it after someone gets a design together. The main
thing I was thinking is

I saw this list under pages related to the stripes project and I had a
few questions to add to them (or possible answers).

Should Stripes source code be moved to a Google Code project?
- What are the advantages to moving stripes to a Google Code project?
- What are the disadvantages?

Should all Stripes extensions be Google Code projects?
What is the patch review & approval process for Stripes to be?
Who has access to the DNS for stripesframework.org?
- Ben has access.
Where will the new website be hosted?
- Could we just host it on the same box we're hosting the current
website on? I think it's a linux box that we can deploy our site to.

[aagha]

Thanks for the note. Please see my comments below.

On Sep 28, 8:13 am, ScArcher2 <scott.arc...@gmail.com> wrote:
> Hey,
>
> I'd like to help get the ball rolling on the new website if I can.

Awesome. Thanks for the offer to help--I welcome it!

> I didn't know about this group until today. I don't know what's been
> done, but I'm willing to help in any way I can.

Right now, just some (light) discussion about the website's site
architecture--I'd love your feedback on the structure I threw
together.

> I've been on IRC for a few years, but I haven't really followed the
> mailing list until recently.
>
> If no one has started on a prototype yet I wouldn't mind mocking
> something up. I'm not a designer, so I would most likely use plain
> html and then rework it after someone gets a design together. The main
> thing I was thinking is

This is a good idea. I've been thinking about a mechanism for how to
put the site together so it's simple and easy to maintain, and
WordPress comes to mind (a friend also recommended Joomla). I'm not
sure how flexible WP is, but I know some folks who swear by it for
even large sites. Thoughts?

>
> I saw this list under pages related to the stripes project and I had a
> few questions to add to them (or possible answers).
>
> Should Stripes source code be moved to a Google Code project?
>  - What are the advantages to moving stripes to a Google Code project?
>  - What are the disadvantages?

This question was put in by me in response to some folks feeling that
the code base for Stripes was too difficult to contribute too--in fact
I think someone specifically recommended Google Code. I suspect the
bigger issue is having an owner (ala Ben) who's able and willing to
make changes/commits regularly.

> Should all Stripes extensions be Google Code projects?
> What is the patch review & approval process for Stripes to be?
> Who has access to the DNS for stripesframework.org?
>  - Ben has access.
> Where will the new website be hosted?
>  - Could we just host it on the same box we're hosting the current
> website on? I think it's a linux box that we can deploy our site to.

Definitely possible--who owns the account on the box and who pays the
monthly fees?

[ScArcher2]

>I'd love your feedback on the structure I threw together.

I like the structure. It looks like you've got all the areas covered.
I talked to a friend of mine who does web design and marketing.

He recommended we consider the "goals" for the website.
Who will be using the site and what will information will they be
looking for.
We could then optimize the main page so that it's easy for those
people to find information quickly.

I think we have

Users new to stripes interesting in learning what it is and why they
should use it.
Users who simply want to download the latest version of stripes.
Users who want to access reference documentation (javadocs, taglibs,
etc)
Users who want to know how to do something (How do I use xxxxx
technology with stripes). (Spring, Jquery, JPA, etc).
Users who want to contribute / participate in development.

I think your structure what I'm talking about really just applies to
the "home" page.

>This is a good idea. I've been thinking about a mechanism for how to
>put the site together so it's simple and easy to maintain, and
>WordPress comes to mind (a friend also recommended Joomla). I'm not
>sure how flexible WP is, but I know some folks who swear by it for
>even large sites. Thoughts?

I think I'd rather look at setting up our website using stripes.
We could use the stripes layout stuff and generate html. As far as
updating it we could put it in subversion and maintain it there.
Maybe even have it automatically update nightly.

I'm not opposed to Wordpress, but I think it would be cool to use the
framework to build the site.

>Definitely possible--who owns the account on the box and who pays the
monthly fees?

I think the box is provided by a company free of charge. I know Ben
has the account information as well as a few others.

[aagha]

Comments below...

On Sep 29, 7:48 am, ScArcher2 <scott.arc...@gmail.com> wrote:
> >I'd love your feedback on the structure I threw together.
>
> I like the structure. It looks like you've got all the areas covered.
> I talked to a friend of mine who does web design and marketing.
>
> He recommended we consider the "goals" for the website.
> Who will be using the site and what will information will they be
> looking for.
> We could then optimize the main page so that it's easy for those
> people to find information quickly.
>
> I think we have
>
> Users new to stripes interesting in learning what it is and why they
> should use it.
> Users who simply want to download the latest version of stripes.
> Users who want to access reference documentation (javadocs, taglibs,
> etc)
> Users who want to know how to do something (How do I use xxxxx
> technology with stripes). (Spring, Jquery, JPA, etc).
> Users who want to contribute / participate in development.

Agreed. I think this is a great break-down.

>
> I think your structure what I'm talking about really just applies to
> the "home" page.

Sorry, I don't follow.

>
> >This is a good idea.  I've been thinking about a mechanism for how to
> >put the site together so it's simple and easy to maintain, and
> >WordPress comes to mind (a friend also recommended Joomla).  I'm not
> >sure how flexible WP is, but I know some folks who swear by it for
> >even large sites.  Thoughts?
>
> I think I'd rather look at setting up our website using stripes.
> We could use the stripes layout stuff and generate html. As far as
> updating it we could put it in subversion and maintain it there.
> Maybe even have it automatically update nightly.
>
> I'm not opposed to Wordpress, but I think it would be cool to use the
> framework to build the site.

I think this is a great point.

However, re sections of the site which will have blogs/content, do you
recommend writing an entire blogging platform with user account
management and permissions from scratch?

>
> >Definitely possible--who owns the account on the box and who pays the
>
> monthly fees?
>
> I think the box is provided by a company free of charge. I know Ben
> has the account information as well as a few others.

Good to know. This is a bridge we can cross when we get to it.

[ScArcher2]

> I think your structure what I'm talking about really just applies to the "home" page.

What I meant to say is the structure looks good.
On the main page, when you go to stripesframework.org, we need to
focus on getting users the information they need quickly and easily.
I just want to make sure we focus on who will be using the site when
we're building it.

> do you recommend writing an entire blogging platform with user account management and permissions from scratch?

Absolutely not. If the site has dynamic content that will need to be
updated frequently the best solution would be content management.
I was assuming that most content would be static in nature.
I've used Wordpress and I really like it.


I'm really excited about this stuff moving forward!
Let me know what I can do to help.

[Evan Leonard]

Great to see the activity on this - thanks for stepping up!

re: using stripes for the site, while this sounds like a nice idea, it would probably be more useful to the community to focus the effort around the content of the site rather than the behind the scenes platform. It sounds like there's agreement to use something like WP for the dynamic portions, but then I'd also add, don't bother using stripes for the static portions - they are, after all, static! I think this approach would likely be the most "bang for the buck"

Evan

[aagha]

@ScArcher2, I'd love to get your perspective on the comment by Evan,
below.

What do you think using Stripes buys us? Please note: I'm not opposed
to the idea--just seeking input.

[ScArcher2]

If the site is static I'd really just use stripes and the layout tags
with static html "jsps".
We could always add content or pull in content from other locations if
it's done with stripes.

But based on what I've read I think we'd be better off with Wordpress.

[Evan Leonard]

Sounds good, if you're doing the work, really it's up to you!

Looking forward to seeing what you creat

Evan

Sent from my iPhone