One of the core areas of expertise of my software development company is selling web sites powered by the Plone Content Management System. The sites we sell have to be very custom in their look. Here are a few web sites that are examples of the types of customizations that we do. [url removed, login to view] They are very custom in the look and feel, but not very custom in the actual features. For example, they all have a dynamically generated menu, based on published content. Some of them have a splash page, which also exposes the menu. None of them use the Plone widgets, except for the search box. We're getting more requests than we can handle, so I need to find someone who can take two photoshop files (a homepage and a subpage) and convert it into a working Plone web site managed this way. I'd like to find someone to whom I can send a steady stream of projects. The first project will be implementing an already existing web site in Plone, given a link to the existing web site, and we will also provide access to its current implementation in Zope. The web site design will be almost exactly like: [url removed, login to view] ... with the following exceptions: 1. The menu on the left should be a bit cleaner-looking. 2. The actual HTML-implementation should be re-done to be cleaner. 3. There would also a set of new content to be loaded, which would be similar to what is currently there, and in some ways would be identical. 4. I would like to add a search box at the bottom of the left column No more room left here... see deliverables, also.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
3) Specifically, the home page of the deliverable must look exactly like the photoshop file for the homepage and the sub-page must look exactly like the photoshop file for the subpage (pixel-for-pixel). A normal person should not be able to tell the difference.
4. The web site must be developed in Plone, and the user, while logged in as an administrator, must be able to edit the pages as they browse (by clicking on the edit tab).
5. I will provide access to a staging machine on which Zope will be installed, as well as Plone, and the software must work on that staging machine.
6. Plone plug-ins may be used, with written approval. Python extensions may be used, with written approval. However, only relatively common, stable plugins will be allowed, and only very short Python extensions.
7. Instructions should be provided to install the files on a linux box with new, easily available, stable versions Zope and Plone.
This broadcast message was sent to all bidders on Monday Mar 6, 2006 1:10:16 PM:
Please also include the amount of time that you estimate this project will take (example: 2 weeks from receiving starting materials...)
A few more notes:
Please also note the following:
1. All "content" (text on the site) should be available for edit in the plone interface (not the ZMI). For example, if there is content on the homepage that is in a very custom layout, the sub-parts should be broken up and each exposed as content nodes in a "homepage_content" folder.
2. The "menu" should be generated by published content nodes, and should allow deep hierarchical expansion (so they should be able to create sub-folders, and sub-sub-folders, and sub-sub-sub folders, etc. and if they are published, and the folders above them are published they should appear in the menus.
3. There should be another "main" menu for administrative links (contact us, etc.), and those should reference a different part of the tree.
4. There should be an "admin" link in the footer.
* * *This broadcast message was sent to all bidders on Tuesday Mar 7, 2006 3:26:36 PM:
I changed the description of this project to add more details, here.
Linux, Zope, Plone 2.