Showing posts with label document. Show all posts
Showing posts with label document. Show all posts

Sunday, 31 October 2010

Group meeting


...don't do it, being an artist would have been a much better idea

So...3 days of work left before the presentation, by then we should have finished;

  • the powerpoint presentation and the narrative
  • the document for client hand-over
  • the design of the boards for the ARCH exhibition, and
  • time to eat and sleep
As a group we went through a draft document, noting points of concern as we went along whilst providing a more precise structure to the document. Issues that were raised during todays discussion were,

  1. Li would attend the lecture tomorrow instead of Gris
  2. Gris and Sarah would head the university presentation with all group members responding to questions baed on their input in the questions topic
  3. All work would be given to Tim for Carolyn's review by Tuesday morning (at the very latest)
  4. All revised work from Carolyn's meeting would be sent to Tim on Wednesday, by 1pm to allows the group to discuss the presentation and its narrative along with the production of the boards
  5. We would print and bind the final booklet on Friday
  6. We would print the boards and mount them on Friday
Unresolved issues;
  1. Who attends Sundays presentation at All Hallows
  2. Who are the speakers at this presentation

Saturday, 30 October 2010

Document revision

A revision of the document will be sent out for review before tomorrows meeting. If all could look through it and send through their draft information before the meeting that would beneficial to the discussion.

Saturday, 23 October 2010

Network simplification

Any views /objections to these simplified networking diagrams, layout, legibility of diagrams, amount of information etc.?







Friday, 22 October 2010

Funding document skeleton proposal

Another thing to think about over the weekend is the structure of the document(s) we will produce. I previously suggested two documents for the hand-in:
  1. a funding document - including a business plan, context of organisation strategy, a template for individual funding proposals and timeline of suggestive proposals (if possible)
  2. a process document - including documentation of working techniques (participation, meetings, discussions with external parties, events, blog etc.), all of the options, their testing, possible avenues of funding for these options and how we produced their business plan

I have produced a skeleton contents list for the funding document and it would be great to get everyones opinion on additions and subtractions of it: (all text in this colour will be completed by the church in relation to what amount of funding they are looking for in relation to sets of proposals we provide)
  1. Vision of the church - What funding / time is required to create this vision, why is the church applying for funding
  2. Overview of the church - What is the churches ethos - What the church provides the community with, activities, solace, belonging - The relevance of the church within the community and why it is important to retain and expand upon the social uses of the spaces
  3. Analysis of the church - The proposed organisational strategy / business plan of the church, their analysis of local community centres and religious institutions, SWOT (strengths weaknesses, opportunities, threats) analysis, PEST (political, economic, social, technological) analysis of the area, the expertise of the church in relation to the prior analysis
  4. Funding requirements - Financial breakdown of the company, past funding schemes / grants applied for / received, what the proposed funding / grant would be used for, the proposed outcomes from the funding and a timeline for of the proposal
  5. Implementation - How this work would be carried out and how the work would be sustained
  6. Conclusion - What outcomes wold be expected from this
  7. People / Acknowledgements - An image of the PCC and small descriptions of them and their interests

Everyones opinions on the structure of the document is critical to getting this right, so comments should be made on the proposals please. I will look at the layout of the process document over the weekend if I have time.

Sunday, 17 October 2010

Funding document graphical style

Binding style

Open bind / string bind - Allowing for adjustments to page layouts of each section. Making the document extendable after the hand over



Document size

I have a personal preference for an A4 Portrait Document. More manageable for the client, business like and friendly to pick up and read than and A4, I feel that the portrait page format is more elegant than landscape page format.


Chapter division / Specialism division

Colourful inlays (rainbow coloured if possible) - These will divide the document into community, site and building interventions



Page layout

Jan Tschichold (just a suggestion, if anyone prefers a different grid system, please mention it) - Simplicity and proportion should enhance the reading of the drawing, there should be a consistency to page layouts with a simple grid layout forming the basis of the design, this grid can be broken to highlight important images / diagrams. The design below is only an indication of how it could be done, I probably would alter the position of the grid slightly, although its a classic document grid



Graphics

Line-drawings - Clean black and white diagrams for the most simple drawings (if applicable, may better to use polychromatic diagrams instead of monochromatic depictions)












Swatch palette

A swatch palette has not been defined yet...although I would suggest that we a colourful and friendly palette based loosely on a rainbow spectrum. I don't think they should be overly saturated or desaturated colours. Tentatively I would suggest the following 7 colours (that should be enough for all the diagrams we will produce) These colours would be combined with a clean line drawing (such as those above)


Example of the palette in a drawing


Hand-over extendability

CD / DVD of document and the programme files



Fonts

Minion Pro (Body text) and Gentium Book (Chapter titles) - Just a suggestion because I think we need to be considering this now. my preference for this document is a serifed font, giving historical connotations to what is produced and also a sense of progressive knowledge (and they're really nice fonts and i have the font families for each)

Minion pro


Gentium book

I'm quite happy to talk to all about their suggestions for the document style as this is quite early and i'm sure everyone wants to create something that is coherent and essentially professional and pretty