Robyn
- We have started setting up the multi-site Wordpress instance and a couple of other tools while we wait for the tools that require set up and negotiation
- We're on standby to coordinate the design meetings between Unfold and Jacqui - dates incoming as soon as we have these from the team.
- We are going to need to shift content briefs a bit so we don't waste your time - we need a signed off site map (at least) to get this going - usually we base content on the prototype so its tricky to brief on this right now as we are not sure of the final details. We are going to shift this timeline (currently due this week) and work on the briefs as soon as its feasible to get this done without causing disruption down the line. We'll keep your time in mind & get these to you as soon as possible.
- We would like content (written copy and images) to be wrapped up by the time we start dev (28 October ) - we use the content to ensure that the elements work as expected so the real stuff is always useful and makes sure that we have catered for all different types of content. If we need to move this out a bit to accommodate for the above shift, we'll do so. All site (main site and resource hub ) pages require content as well as resources in various formats. Ideal images and sizes is usually revealed at the prototype stage, so we'll see what's practical in this regard.
- We'll need categories for the main website and resources hub wrapped up by the time we start dev, this is also influence by the site structure so will give you a deadline once we have the main site and resource hub's site structure / wire frame wrapped up. LMS and details for Ecommerce can be handled separately.
- A decision about the site's languages will need to be finalised by the end of October.
- We have loaded budgets into Clockify, I had to adjust the naming convention to marry up with the costing so
Jane
The categories:
- Project management (which will include content briefs, meetings and retrospectives)
- Wireframe, design & style guide
- Development - Global Components
- Development - Site-specific Components on Main Website (including testing & Salesforce integration)
- Development - Site-specific Components on E-commerce Website (including testing)
- Development - Site-specific Components on Learn Website (including testing)
All the costed items are listed under these umbrellas so hopefully it makes sense and delivers what you need.
I'd like to get the bi-weekly check in's scheduled but believe that this makes sense once the briefs are in / dev is under way - if you feel we need to start this sooner, do let me know. If you have a preference on which day to meet, also let me know so I can block out the time and get these into our calendars sooner rather than later - the checkin is supposed to be short and focused on areas we are stuck, using Basecamp for the regular updates. I am therefore thinking of scheduling 20 minutes for these chats to start.
Thanks so much!
I think that's all folks!
* When you say you are shifting the content briefs deadlines, are you referring to this
Wordworks: briefed by Matogen, provide overall content structure and ensure Wordworks team members are equipped to supply content to Matogen | - | 2 weeks | 2 September - 13 September
* And when you say you would like all the content wrapped up, are you referring to this
Wordworks: briefed by Matogen and prepare all content and resources (with categorisation for user and access criteria) required for main website, resource hub and ecommerce | 6 | 6 weeks | 16 September -
25 October
can you give your preferences for a time for the regular project management meeting Robyn refers to. I'm the most flexible of us all I think though Tues & Wed afternoons and Thursdays are not reliably open.
Your understanding of the shifts is correct. Once we can get the site map signed off, the briefs can follow that format keeping in mind that things might shift on the prototype (possibly ) We'll brief you as best we can based on the signed off site map which is more detailed than usual so theoretically that should work well.
We need the content ready by the time we start building along with the signed off prototype so we can identify any gaps and makes sure that the content marry up with the plan.
We use the content to build out the site once the sections are built in the backend. Once content is in, the styling part of the job commences on our side. That's why the actual content is very useful and needed so we are styling for the real deal vs placeholder copy which can leave gaps or require changes that are not in line with the prototype further down the line.
I am mentioning shifts in both of these items so you don't have too little time to prepare on your side and we are able to give you a decent brief that is not open to a lot of change and therefore wasted time. All these processes rely on each other for the best outcome.
I hope that makes sense but do let me know if you would like more information or a quick chat.
I will coordinate our sessions asap, Thursday afternoon's (bi-weekly) can work if we go for a later meeting at say 4pm - would that be okay on your side? I think we can start these from early October (even though we may not have that much to discuss then) but you may have questions about the brief etc by that stage.
Lastly, I'd like to emphasise that sign-offs are needed at every stage of the process to allow us to proceed. This will be true throughout the various stages of the development journey.
Initial Pre-dev sign off