View this page "Possible Site Architecture"

[aagha]

I've created a page that allows us to discuss a possible site
architecture

Click on http://groups.google.com/group/stripeswebsite/web/possible-site-architecture
- or copy & paste it into your browser's address bar if that doesn't
work.

[aagha]

Updated with a more comprehensive site map

[jiffier]

Well, I personally think there should be 3 parts: Static content
(homepage, about, and things like that), then the dynamic content, and
then the admin area where people can manage the dynamic content). The
dynamic content is just text, and each page belongs to a section, and
you get a hierarchy of sections, for example: Documentation -> HOWTOS -
> URL mapping -> Dynamic mapping filter

[aagha]

More detail added

[aagha]

It seems like you're talking about implementation. I see no reason
the structure you're talking about can't be incorporated into the
proposed architecture--even using the dynamic content mechanism you're
mentioning.

We've not yet locked down a technology approach, so we could end up
with new code or Wordpress (or something else).

[Carlos Ramirez]

Nothing related to structure but i can help translating to spanish. It
would be nice to have access to Stripes in my native language. This
way we could deliver the contents to a wider audience. Java Web
Frameworks are popular in Latin America and i think there are plenty
of developers using it.

[evan.leonard]

This looks good. Have we identified a new home for this yet?
Morten volunteered on the mailing list to lead the implementation. It
would be great to get this rolling!

On Sep 2, 3:22 pm, aagha <ama...@gmail.com> wrote:
> More detail added
>
> Click onhttp://groups.google.com/group/stripeswebsite/web/possible-site-archi...

[aagha]

This would/could be very useful when we get to that point. Thanks for
the offer!

[aagha]

We haven't. I've been a bit concerned about moving forward due to all
the "keys to Stripes" discussion on the mail list.

I think the website should move forward regardless, as a new site/
presentation is, in my opinion, at least one thing that can be done to
help spread Stripes. That said, I'm not sure what kind of support is
available to get this ball rolling.

The site can be simple to do and roll out in WordPress should we want
to just get something up, but we'd need contributors (blogs, content,
vidcasts, etc...)--not sure who can step up to do that part.

Re the site structure itself, I'd love a lot more feedback. Is it too
much? Too little? Just right?

[Evan Leonard]

Maybe make some sub bullets under website for content and videos?

Evan

[Aurangzeb M. Agha]

Done.

[zapp]

What about exposing the extensions more?
I mean, if we want to have stable core with extensions built around
it, it should be easy to find them.
What on the front page have two large icons "Stripes Core version X.X"
and next to it "Stripes Extension version X.X"?
Perhaps Stripes Extensions should more of a bundle, where I believe we
right see the extensions as different kinds of plugins?
If they were bundled and have had some kind of quality assurance, I
believe it would be a great asset to have it divided so clearly on the
front page.

Just a thought...

Regards

Søren

On 21 Sep., 22:49, "Aurangzeb M. Agha" <a...@mltp.com> wrote:
> Done.
>

[aagha]

I really like the idea of "featuring" the extensions, but not sure
about bundling them. I personally would like to have the options of
choosing which bundles to use for an app I'm developing--that said, I
don't think there's anything wrong with having the option of having
*a* full extension bundle along with all the others that might be
broken out individually.

Aurangzeb

[aagha]

Added link to page moved to Google Docs.

Click on http://groups.google.com/group/stripeswebsite/web/possible-site-architecture