Opened 12 years ago

Closed 12 years ago

#3 closed task (fixed)

Get a webpage

Reported by: seanegan Owned by: joekepley
Milestone: Component: webpage
Version: 2.0 Keywords:
Cc:

Description

It would be nice if we got a webpage.

Change History (22)

comment:1 Changed 12 years ago by seanegan

  • Status changed from new to assigned

comment:2 Changed 12 years ago by seanegan

  • Owner changed from seanegan to sgarrity
  • Status changed from assigned to new

comment:3 Changed 12 years ago by sgarrity

Website planning is happening on the PidginWebsite wiki page.

comment:4 Changed 12 years ago by joekepley

I've created wireframes and added a discussion page at [WebsiteWireframes]

comment:5 Changed 12 years ago by lschiere

I really like the proposal for the help search and bug submission. I'm guessing that we would not have a separate wiki for support? Two wikis sounds like it is asking for one of them to be neglected, much as the SF forums are now.

The Home page looks good. The downloads section also looks good. I'm not sure we would have much in the way of alternates though beyond the source itself.

In your site map, you have a section for developer blogs in both "About" and "latest news." Do we want this duplication?

I like the support page. A good search would be awesome.

comment:6 Changed 12 years ago by joekepley

I'm guessing that we would not have a separate wiki for support?

I would try to keep to one wiki if possible and figure out a way to segment the dev- and user-related articles by convention. The only down side I see to having them together is that the support search would also return some dev-centric articles. I'm not sure if that's a good thing or a bad thing.

In your site map, you have a section for developer blogs in both "About" and "latest news." Do we want this duplication?

I was thinking of the Team page in the about section as something more akin to the 'contact info' page on the current site, perhaps with a bit more bio information. The 'Dev Blogs' page would be more like the current 'planet' site - an aggregation of articles from developers' blogs. So I don't think the duplication is a big deal. In one case it's part of the contact info, and in the other it's there to provide context to the posts.

I like the support page. A good search would be awesome.

The idea here would be to implement Google Co-op across all of the relevant sites (manual, wiki, maybe even mailing lists, blogs, or IRC transcripts if they're around). This would probably require some tweaking but I'm hoping we could get something rigged up that returns relevant results most of the time.

comment:7 Changed 12 years ago by seanegan

  • Owner changed from sgarrity to joekepley

comment:8 Changed 12 years ago by joekepley

  • Status changed from new to assigned

comment:9 Changed 12 years ago by lschiere

I have not heard an update on this in ages. Where do we stand?

comment:10 Changed 12 years ago by nosnilmot

<nosnilmot> any news on the website?
<seanega1> The designer was, like, getting married last week. But they're gonna get us something usable by the 4th

(Congratulations Joe!)

comment:11 Changed 12 years ago by joekepley

It's actually, Sam, one of our designers, who was getting married. He'll be back in the office tomorrow.

Our rough plan right now is to get a design put together and implemented in eZ Publish, and to get as many of the features implemented as our production schedule allows. Right now I'm guessing that this will amount to getting the home page put together, all of the text-only pages, and static stub pages for some of the fancier things like the support and etc.

comment:12 Changed 12 years ago by rlaager

  • Milestone 2.0.0 deleted

This isn't a 2.0.0 blocker, I don't think.

comment:13 Changed 12 years ago by joekepley

  • pending set to 0

Sam has completed a set of design comps. I've posted them at WebsiteDesignComps .

If there are no major objections, we'll begin working on implementing these.

comment:14 Changed 12 years ago by sgarrity

Looks great. Nice work.

comment:15 Changed 12 years ago by lschiere

I like the look of these.

comment:16 Changed 12 years ago by joekepley

Hi all,

Based on the responses here, I've had my team go forward with the buildout on our development server (url coming shortly).

We'll need to either get access to your production server to deploy the site, or know who to send the package to in order to deploy it. (For future changes, it would probably be best for us to at least have FTP access).

We're using eZ Publish for the main body of the site, so the hosting environment will need to meet the system requirements for eZ Publish 3.9.1. There's nothing too unusual there for a dedicated Linux/Apache? box, but one thing we keep running into is that Red Hat ES4 froze their PHP version at 4.3.9, and recent versions of eZ require PHP 4.4.x

Let me know who to contact and I can work directly with them to make sure that we can deploy smoothly.

Thanks, Joe

comment:17 Changed 12 years ago by lschiere

I will not open FTP up. It is a significant security risk, in that it does not handle passwords well. I can grant a shell account to one person if necessary.

We are on a Linux box. I have mysql 5.0.32-7etch1 apache 2.2.3-4 using the prefork mpm. and both php4 and php5. I will set it up so that php4 handles the 000-default site (www.pidgin.im). php4 is at version 4.4.2-1.1. I'd rather be able to get rid of php4, but it appears that eZ Publish does not support php5.

It appears from this that the site will be a combination of mysql and php4 files, if we were to give you a branch in our mtn repository for the php, html, and images, would that be sufficient? Presumably the mysql component is something I can set up for you.

comment:18 Changed 12 years ago by lschiere

Scratch that, I cannot install php4 and php5 in parrallel, using packages. I just thought I had because I had a php4 config file laying from when it was installed. I've downgraded to php4, but I really dislike this requirement.

comment:19 Changed 12 years ago by joekepley

I will not open FTP up. It is a significant security risk, in that it does not handle passwords well. I can grant a shell account to one person if necessary.

That's preferable for us as well. We use ssh with key-only authentication whereever possible. I can provide a public key.

Scratch that, I cannot install php4 and php5 in parrallel, using packages.

Unfortunately, the official eZ Pub installs are indeed bound to php4. eZ systems is skipping php 5 entirely and targeting the eZp 4.x branch at php 6. There's a community effort to provide a php 5 compatible port. I've heard good reports on it but I'm not sure how complete it is, or how diligent the authors are at tracking the main release.

On our servers, I've dealt with this by running php4 as a module (libapache2-mod-php4) , and php5 as a CGI (php5-cgi) through FastCGI (libapache2-mod-fcgid). None of the php5 apps I'm using require php to be run as a module (ez does), so this allows both php4 and php5 to run on the same apache2 install (under different vhosts) and perform well. I'm not sure about etch, but I'm able to maintain this scenario on an Ubuntu Edgy server using apt (no custom compiles), so I would imagine that it would work on etch as well.

comment:20 Changed 12 years ago by lschiere

I have set up blend@…, send me a public key (lschiere@…) and you'll be good to go.

switching to php4 didn't break anything we are currently doing, so I just left it at that.

comment:21 Changed 12 years ago by doconnor

Can this ticket be considered closed, fixed?

comment:22 Changed 12 years ago by lschiere

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!