Web Developer for New Site

Startup seeks an experienced web developer to create our new website. The website must have the following attributes: * The site should make it easy to create and send a daily personalized, attractive and unique, HTML- or text-formatted email to each subscriber. * Daily e-mails will be prepared based on data submitted by multiple authors, who enter their content via a non-public area on the web site. * Subscribers select preferences on website, and e-mail content is generated based on their preferences without human intervention. * Highlights from that day are featured on the homepage of the website, with all former content easily accessible in archives. * Subscribers must be able to easily browse/search all content on the site. * Subscribers must be able to use our website (create a profile, subscribe to the email, change preferences, unsubscribe) without any human intervention. Please see our wireframe draft and spec for more details. We are searching for an expert developer to use WordPress, Joomla!, or Drupal. We would like to be able to make small modifications on our own after the website is complete, so hopefully the design will allow for that. **To apply**: Send us your resume, a description of your experience with one or all three of the CMS's listed and why that makes you a great candidate, and why, based on what little you know about our site, you would pick one of the three systems over the others. ## Deliverables Revised Spec 11/10/11, accompanies the PPT Summary I want to create a daily e-mail newsletter. This will require a database of user information and preferences, automated billing, and e-mailing features. The site should also have a searchable subscriber-only section with archived content and other content uploaded periodically. The logic will not be technically complex, but each user will receive a unique e-mail constructed based on his own preferences. Product Information The product is a daily e-mail newsletter, plus access to some paid content on the site. The site should make it easy to create and send an attractive and unique, HTML- or text-formatted email to the each subscriber. E-mails will be prepared based on data submitted by multiple authors, who enter their content via a non-public area on the web site. Past stories (containing 100% of available information) should be available on the site, and searchable/browsable. Generic Homepage (Slide 1) ? **Navigation bar**: HTML links to: login, subscribe, about this website, for dummies, what's hot. The navigation bar should appear on each user page. ? **Search function:** 1. "select sport" OR "select state." 2. If chose select sport then next drop-down to appear below: "select team." OR If chose select state then next dropdown to appear below "select city." For #2 there should always be a "select all" option. After their final selection, user is taken to a page that has all desired content about that team or city listed in chronological order with the most recent stories on top. ? Search engine. ? **Top stories:** These are generated by the top user preferences. The admin/editor/author must have the ability to over-ride to avoid redundant stories. ? If possible in the future we may want to add columns to this page. Search Results (Slides 2-3) ? This page should appear clean and easy to read. ? After the first three stories are posted in full, below should appear the HTML links to older headlines. They should be listed chronologically, and only have the 20 most recent stories from the most recent season. After that should be a link to older archives and previous seasons, and a search engine box as a reminder to the user that they can search more specifically. ? **If searching archives by sport or team:** when user selects to go to older archives, the archives are sorted by season, after selecting HTML link to season, all results are shown in links, which takes the user to the desired story. ? **If searching archives by city:** when user selects to go to older archives, the archives are sorted by year, after selecting HTML link to a year, they are taken to a page that includes all HTML links organized by team. Subscription (Slides 7-9) ? **User should be able to subscribe and unsubscribe without human intervention.** ? Selection of sport/team: After a user selects a sport, a pop-up appears with checkboxes. All of the teams that we cover are listed and the checkboxes are auto selected. On the top of the pop-up there is an "unselect all" button. Users can un-select specific teams, or all, as they choose. ? Selection of state/city: After a user selects a state, a pop-up appears with checkboxes. All of the cities that we cover in that state are listed and the checkboxes are auto selected. On the top of the pop-up there is an "unselect all" button. Users can un-select specific cities, or all, as they choose. ? After subscribing user is taken to their personalized homepage. ? We are not planning to add the billing component until later, but it would be nice to have the infrastructure readily available. ? All subscription data gathered enters a database that can be easily accessed. ? The measurement that the user selects on the slide ruler for how much they care about a team is the metric the site will use to generate the user's personal e-mail and their personal homepage. User Login Page (Slide 10) ? Preferably a moodle to login, but otherwise directed to this page. ? User should have ability to retrieve their password and username through e-mail with no human intervention. ? There should also be a link under the login box to subscribe. ? After logging in the user should be taken to their personalized homepage. ? The navigation bar should now include a link to the user's profile page. My Account Page (Slide 12) ? User should be able to unsubscribe, change their email preferences, their personal information, and their password without human intervention. General Notes about Admin/Editor/Author Pages: ? If possible we would like to login via the same moodle on the homepage that users use. ? Not public pages. ? All author entries should be automatically error-checked for issues such as misspellings and special (poorly displaying) characters. ? The system should keep a running total of entries (either games or events) entered by each author, in order to facilitate payment. ? If any in-season sport's content has not been entered, the site emails designated administrator addresses. ? The system should remember which author wrote each entry. ? For each sport in each year, the site should allow admins to set starting and ending dates for the season. Admin Homepage (Slide 14) ? Admin has access to all stories and ability to edit everything. ? Admin has ability to create new admins, editors, and authors. ? Admin has ability to grant specific permissions to authors and editors. For example, the admin can grant the editor access to post and edit all stories, whereas the author is only granted permission to post and edit his own stories. ? Once the admin selects the name of an author/editor from a drop-down menu, selected privileges appear below in a field with check boxes. Option to add or change privileges (check boxes next to desired privileges I.e. to enter stories, to access admin pages, etc.). Editor Homepage (Slide 15) ? Access to all posts to edit, as well as ability to create new posts. ? On the editor homepage: stories posted within the last 24 hours are showcased in full, with ability to click a link to edit them. When link is clicked, editor is taken to the same page that stories are entered on, but all of the information is already inputted. ? Below the stories from the last 24 hours are HTML links to the stories from the past week. ? The rest of the stories are archived. ? Ability to search for posts by author. Author Homepage (Slide 16) ? On the author homepage: stories posted within the last 24 hours are showcased in full, only able read them. ? Ability to access and edit former posts written by the author himself. Author Story Entry (Slide 17) - Enter new Games or Events (see below data fields for each) Author Game Input Interface Select Sport: [drop down menu; selection populates team menus] Selection persists until changed. Date: [autopopulate with today's date] Winning Team: [dropdown], Score: [number entry], Checkbox for "Home Team" Losing Team: [dropdown], Score: [number entry], Checkbox for "Home Team" (Optional) Headline: [one-line text box] If Headline is not specified, the default should read: "[Winning Team] beats [Losing Team], [Score1] - [Score2]" (Optional) Comments: [free-entry text box] (Optional) Play #1: [one-line text box] (Optional) Play #1 Video URL: [one-line text box] (Optional) Play #2: [one-line text box] (Optional) Play #2 Video URL: [one-line text box] [Click a button to submit info to database and clear fields beginning with "Winning Team"] Note: In the future, we may want to populate the game data fields automatically from an XML feed. This does not need to be implemented in the initial version, but please leave open the possibility. Author Event Entry (Slide 18) To clarify, an event might be something like "Team X's star player was injured." Select Sport: (same as above) Date: [autopopulate with today's date] Team 1: (same as above) Team 2: Optional (same as above) Headline: (same as above) (Optional) Comments: (same as above) (Optional) URL: [one-line text box] [Click a button to submit info to database] **General notes:** ? The system should track each team's win/loss record and apply some logic to it for placement in the email. Important Questions and Thoughts Moving Forward: **Things we will need to access, but aren't quite sure what it should look like yet. Will we access it directly from database or will it filter into an admin page?** ? User information including a user's profile, billing information, and billing history. Ability to credit/charge users manually if necessary. ? Statistics: we will need to be able to access certain statistics including: number of users, gender breakdown, regional breakdown, age breakdown, absolute number of page views, ranking of most selected pages and teams. This information needs to be easily downloadable to excel. ? We would like the admin to be able to grant different permissions to different authors and editors-what will this look like?