Build a Website

We are a non-profit, community theater located in Texas (DFW area). We have a current website written in Wordpress. We are migrating to a new format and seeking developers with a clear understanding of what we want. The new website must only use HTML and JavaScript – no PHP, MySQL, or anything else - to make it work in its current location and be portable to a micro instance on Amazon. Therefore doing it within WordPress or trying to do it in another CMS won’t work. If this is not your skill set, please ignore this opportunity. We have had many people try to convince us to adapt. Below are specific instruction from our IT specialist to help you understand how the project will move forward. We have our own Graphic Design team and use Adobe CC for all components. As a non-profit 501(c)3 charity, we wish the website design to follow this fundamental description: To allow a visitor to become part of the story. Like the proverbial kid in a candy store, faced with an inviting array of ways to be involved. The new website should tell the entire story, but tell it from many different perspectives. It allows the visitor to enter the story however they prefer: to learn why we were founded, to view samples of play, classes and performances, to examine measurable impact or financial stability and to see who is involved. The goal when a person visits a our new website is to gather information for contacting the visitor and to obtain permission to use it for further communication. We want to produce an action that reaffirms commitment and advances our organizational goal, igniting advocacy, creating awareness of an event, or yes, generating an actual contribution. Why is contributing listed last here? Because the gratifying rise in online giving should not obscure the fact that donors, especially the most ardent, visit our website far more frequently than they give a gift. Thus the function of the new website is to maintain high interest in our theater through timely stories and frequent opportunities for involvement. If this is something you agree with, then please move on to the next parameter that we hope will define the scope of work... or at least the "rules of engagement." 1. To make the new website compatible with the existing ticketing system, it should be done entirely in HTML and JavaScript. My preference is that you use only jQuery and jQuery UI as external JavaScript libraries, but I’ll be happy to consider alternatives if they offer sufficient benefits, features, and quality. 2. For security reasons, your initial development work will be in the development environment that we set up. 3. Initially your work will have to peacefully coexist on the same server with our existing WordPress and use it appropriately as the ticketing system. To do this you’ll create your own [login to view URL] page and place all of your other work in the subdirectory of your choice immediately under the server root. While the name of the subdirectory can be arbitrarily chosen, that name should be selected in consultation to reflect well upon the Artisan. It should also not be the same as one of the standard WordPress directories. 4. The configuration of Apache is such that it will load your [login to view URL] page instead of the current [login to view URL], and thus your work will take control of the server once it’s in place. To ease current and future integration and deployment, all links to pages that you develop will be relative, while all links to pages in WordPress will be absolute and refer to griddlebone.artisanct.com. For example, a link to the current calendar in WordPress should be [login to view URL] 5. When your work is ready for testing, it will be simple for us to deploy it to the new testing environment, [login to view URL], and once tested it will be just as easy for us to deploy it to the current artisanct.com. We have everything set up to do continuous delivery from the command line at our discretion.