Whiteboard Checklist

Last edited: 10/25/2016

Note: very soon you will be able to do an entire site copy of the Whiteboard prototype site, which will automatically copy over all of the back end database content, including monklets, pages, sections and test content. Stay tuned for that update within the next couple of weeks.

  1. (This may have already been done by Shane or Luke) FTP files from Whiteboard Prototype site to your site. Include all files/folders except .htaccess, comeback.php, mediafiles, monkcache[.db], monkcms.php, monkcode.txt, and monkinstall.php. If it hasn’t already been done, create an empty folder for mediafiles.
  2. CSS Phase: Make color/image changes to site based on project psd’s. I generally style the home page first and then style the remaining pages as I plug in the api modules. An alternative would be to plug in all of the api first and then go through and style everything.
  3. Sections: copy over from prototype site, make sure to put ”#” in sections that require description field for link.
  4. Monklets: copy over from prototype site (except for global default monklets)
  5. Htaccess: copy over 5 custom rules at bottom of .htaccess file. Replace “dwt002” with client short name as comment above the first custom rule explains. Modify the footer.php include on line 53 to show this new short name as the toplevel link. This allows the calendar links in the footer to point to the right place.
  6. Template manager: enter in all of the “mcms_”-prefixed templates into the template manager so they can be used in pages, blogs, etc. Choose the default sidebar for all of the templates except for the mcms_page_blog.php template, where you will use the “sidebar-blog” section.
  7. ARTICLES: create page called “Articles”, assign mcms_page_articlelist.php. Find out from client how many featured articles they want on the home page, and whether they want to use category, series or “publish as featured” to pull out home page articles. I generally use “category” and assign a category of “news” or “church-news” to articles that get displayed on the home page.
  8. SERMONS: create Sermons page and assign to mcms_page_sermons.php. Create four “Sermons by…” pages for the sort pages and assign the appropriate template to each. The sidebars should be hardcoded into the template, so you don’t need to choose a section for the sidebar.
  9. EVENTS: create an Events page and assign to mcms_page_eventlist.php. This will be the large calendar display of events. Style according to color scheme (or psd if you received a design for the calendar. I generally don’t get one.) If the client has required the RSVP module, make sure that the rsvp __registration__ tag is included in the ekk_events.php getcontent.
  10. BLOGS: Create a test blog and assign the mcms_page_blog.php template to it. Create test post content and style correctly.
  11. “ME” PAGES: if the client has requested this, make sure that the mcms_page_me.php is included. If not, remove this page. Test and style me pages.
  12. BOOKLIST: If requested, test and style. Remove mcms_page_booklist.php if it is not requested.
  13. Once site is fully at staging, post (or link to) Setup Guide so that client can begin modifying sections and adding content correctly.