The document describes two approaches for starting a project based on an STK static prototype: fixing prototype iterations and WGet prototype iterations. The fixing prototype iterations approach involves developing according to a shared prototype location and reflecting changes in a running instance. The WGet prototype iterations approach involves a developer assembling a prototype from plain STK and exchanging it with a designer through email before implementing changes. Both approaches involve discussing obstacles with the designer and implementing structural changes.

1. How to start a project based on STK’s
static prototype
Christian Ringele
17.09.2010
Magnolia International
1
Magnolia is a registered trademark used by permission
Version 1.0

2. Two approaches
• Fix prototype iterations
• WGet prototype iterations
2
Magnolia is a registered trademark used by permission
Version 1.0

3. Fix prototype iterations
• First delivery by experienced designer
• Shared location of prototype as in SVN
• Implementation starts according the first prototype
• Implementation state reflects the prototype
• Information exchanges are based on a running instance
3
Magnolia is a registered trademark used by permission
Version 1.0

4. WGet prototype iterations
• First delivery by developer, assembled from plain STK prototype
• Exchange is possible on ‘back and forward’ mail approach
• Implementation starts according the developers assembly
• Implementation state is base for the next prototype (WGet)
• Information exchanges are based on WGet extractions
4
Magnolia is a registered trademark used by permission
Version 1.0

5. One iteration: Fix prototype
• Development is started according to the prototype (svn)
• All template adaptions are made if possible
• Running instance is updated (theme pointing to svn)
• Obstacles for the developer are discussed with the designer
-> structural changes in html are decided
• AND/OR
• Appearing design bugs (content variations) are discussed with the
designer
-> structural changes in html are decided
• Designer changes all discussed adaptions in the prototype (check
in)
5
Magnolia is a registered trademark used by permission
Version 1.0

6. One iteration: WGet prototype
• WGet extraction is sent to the designer
• Designer sends back the new design
• New design (css & JS) is used by Developer
• Obstacles for the designer are discussed with the developer
-> structural changes in html are decided
• AND/OR
• Appearing design bugs (content variations) are discussed with the
designer
-> structural changes in html are decided
• All discussed structural changes are implemented by the
developer (extraction ready)
6
Magnolia is a registered trademark used by permission
Version 1.0

7. Questions ?
7
Magnolia is a registered trademark used by permission
Version 1.0

8. Thank you!
8
Magnolia is a registered trademark used by permission
Version 1.0