Page tree

Theme Package

View Complete Methodology

The fastest path to a turn-key, fully branded wiki.


Starting with your existing logo, color palette, and stock art or image gallery (from your organization's corporate identity or branding standards guide), Brikit will do the rest.

After collecting design goals and related information from you, we'll build your complete theme package. This includes:

  • creative brief connecting the design with your identity goals
  • ready-to-upload theme 
  • content exports for your landing page and a typical second-level page, including site menu, default page layout, header, and footer
  • status review and training session every review and feedback cycle
  • up to six design revision cycles

Before we begin the review cycles, your team will:

  • do self-guided learning of Confluence and Theme Press, or
  • purchase training

Covered by the Service Terms Agreement (sorry, no alterations or substitutions).

Complete package: $16,500

Service Description

 Full Process

Here's how it works:

1Theme kickoff initial interviewBrikit & You1
2Create your demonstration portal to guide the processBrikit 
3Provide your identity package and related materialsYou 
4Review identity materials and create a tailored written questionnaireBrikit 
5Think about and answer the written questionnaireYou 
6Sign off on identity package (fonts & licensing, color palette, target software versions)You 
7Review questionnaire, branding, and perception goalsBrikit2
8Prepare your design brief and initial theme build, including sample content for landing and secondary pages at minimumBrikit 
9 Review 1 (tour and training session)Brikit & You3
10Review and Feedback Cycle 1You 
11Theme revision1Brikit 
12Deploy theme and sample content to your portalBrikit 
13 Review 2 (status update and training session)Brikit & You4
14Review and Feedback Cycle 2You 
15Theme revision 2Brikit 
16Full browser testing - (Chrome, Safari, Firefox, IE8, IE9, IE10)Brikit 
17 Review 3 (status update and training session)Brikit & You6
18Review and Feedback Cycle 3You 
19Theme revision 3Brikit 
20 Deliver theme and sample content to you Brikit 
21Install theme and sample content on your serverYou 
22 Review 4 (status update and training session)Brikit & You7
23Review and Feedback Cycle 4You 
24Theme revision 4Brikit 
25 Review 5 (status update and training session)Brikit & You9
26Review and Feedback Cycle 5You 
27Theme revision 5Brikit 
28 Review 6 (status update and training session)Brikit & You10
29Review and Feedback Cycle 6You 
30Final Theme revision 6Brikit 
31 Final theme and sample content delivery Brikit11
32Update theme and sample content on your serverYou 
33Handoff meeting and Q&A sessionBrikit & You 

Ground Rules

With your guidance, our design team will complete the following checklist to create your Theme Package. The full process typically takes 12-14 weeks from start to finish. A couple of notes:

  • Each review cycle is open for one week
  • All deliverables will be deployed to, and available on your private demonstration portal
  • Work-in-progress theme and demo content will be available for installation on your servers after Review 3
  • If needed, you may put the process on "vacation hold" for up to one year
  • If you need assistance developing your identity package, we can pause the process at the appropriate step and provide support through Service Punchcards

The Theme Package process and Service Punchcard requests and tracking will be supported with your private portal (Confluence spaces) on our servers, which includes up to three user accounts. Your portal will be maintained for one year after completion of last service package or punchcard. User accounts inactive for six months will be automatically disabled (simply contact us to reactivate).


To make the Theme Package as cost-effective as possible, the process is tightly defined (see above). If needed, additional assistance is available through Service Punchcards for the following items that are not included:

  • Information design (defining spaces, permissions, etc., also called "information architecture")
  • Content creation, editing, or migration
  • Site buildout outside of: site home page, secondary landing page, menu, and footer
  • Identity/Brand Material build out (color palette and logos, for example)
  • Training
  • Work performed on your servers (for example: installing/configuring the Theme Package deliverables, VPN and user account setup, reviewing content, add-on installation, troubleshooting, and other work performed on your servers)


Sometimes the unexpected happens, and changes to the above process are needed. Here are common variations we've encountered and their associated costs:

  • Additional vacation holds (half a Service Punchcard)
  • Revise your theme if your identity materials change after sign off (one Service Punchcard)
  • Change target Confluence version after sign off (half a Service Punchcard)
  • Additional review cycle (most commonly used when identity materials change late in the process, half a Service Punchcard)
  • Additional year of maintaining your portal (half a Service Punchcard)
  • Additional user account to your portal (half a Service Punchcard per year)