Difference between revisions of "User:Andre/BS-future"

From Publication Station
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=to do =
* CategoryTree Bug - working on solving it
* Editions
#2: Education
#3: Radical Reframing
Change python script and wiki category pages


==Work plan==
A bit strange, as order is #2, #3


* schedule - prep


==Development of an web overview page==
* people: Andre, Lucia, Noemi and Bo (WdKA Graphic Design 1st year students)
* duration: 3 days
* dates (possible): any 3 days for week from 18-22April(Andre unavailable on 18) and 11-15April (less advisable date)
* fees: Lucia 1600€; Andre (2days)
* deadline: end of April


===issue 2,3===
* dates: 9-13May
* duration: 4 days
* possible modes collaboration:
** students from wdka + Lucia + publishing lab interns; active collaboration from Publishing lab (?)
** external designers + Lucia(?)
* deadline: end of June finished


-----




=Beyond Social Re-design plan =
March 2016.


==Iris==
* Teachers start using the wiki
* Past minors have been uploading their work.


==Graphic Design students collaborations==
==Development of a front-end overview page==
* use: editorial module as a design content
* people: Andre, Anja Nomi, and Bo (WdKA Graphic Design 1st year students), Arjen (19th 13:00-17:00 and the whole day on the 21st)
* duration: 3 days
* dates (possible): 19-21 April
* deadline: end of April
* time: 9:00-17:00
* room: BL-1.1


==plan - dates==
=== detailed briefing ===
* development week to 11- 22 april?
* What information should be present about BS
Andre can do: 11,12 + 19,20,21
* What information should be present about each issue
* What image should be used to represent each issue
* Are there any style/design guidelines or inspiration
* Responsive design


==front-end==
===workshop structure===
* Day 1: presentation of project, how's it working, aims, prototype front-end a few design option, prototype code, editors feedback (1 hour)
* Day 2: implementation of design and code
* Day 3: tests, refinement, editors feedback (1 hour)


'''Identity - for issue 2''' (student from Y1 GD involvement)
===wishlist===
* random image from the issue.


'''Page structure'''  (student from Y1 GD involvement):
==Front-end design for issue 2,3==  
# splash page - about
* dates: 9-13May
# menu page - containing:
* duration: 4 days
## image links to each issue
* possible modes collaboration:
## meta information (about)
** students from wdka + Lucia + publishing lab interns; active collaboration from Publishing lab (?)
 
** external designers + Lucia(?)
'''Front-end architecture''' - issue based architecture (7days = 65 hours) - April with Lucia.
* deadline: end of June finished
* new issues added to the wiki
 
Iris will make scheme/plan
Andre will respond with plan
 
* (Not for next issue) content structure - text or image prominence - how is an article displayed - (5 days)
 
==backend==
Arjen will become administrator
 
==print==
 
==back-end (wiki)==
* wiki administrator: Arjen (creating categories, monitoring) - 4 hours
* teachers professionalization workshop - K3 - to make students editors
 
==right own==
* <span style="background:yellow;font-weight:bold">category for issue 3 - "Radical Reframing"</span>
** category issue as names - difficult - use captions
* <span style="background:yellow;font-weight:bold">change in name from issue 2 to "Social Art and Design Education"</span>


* Issue titles
** 2: Education
** 3: Radical Reframing


* pages:
** index page,
** article page.


------
For issue 2: article titles and images from article appear next to each other in index.   


=system for BS publishing=
<span style="background:yellow;font-weight:bold">
In order to stream line the process of publishing BS it is important to have a clear map of the aspects and strategies involved in publishing.</span>


==Models of publishing issues==
==Image based template==
* freezing -
* image based template: html structure, css, JS, added category in wiki (that identifies this)
* ongoing the current issue
* duration 3days.
* ongoing for all issues


simplify


focus on the current issue
==misc changes==
* include category "issue 3" wiki and accommodate it to the front end.
* change name of issue 2
* metadata page ofr each issue to exist in a wiki page - so it can scrapped to the frontend
* Andre will do it

Latest revision as of 13:43, 7 April 2016

to do

  • CategoryTree Bug - working on solving it
  • Editions
#2: Education
#3: Radical Reframing

Change python script and wiki category pages

A bit strange, as order is #2, #3

  • schedule - prep



Beyond Social Re-design plan

March 2016.


Development of a front-end overview page

  • people: Andre, Anja Nomi, and Bo (WdKA Graphic Design 1st year students), Arjen (19th 13:00-17:00 and the whole day on the 21st)
  • duration: 3 days
  • dates (possible): 19-21 April
  • deadline: end of April
  • time: 9:00-17:00
  • room: BL-1.1

detailed briefing

  • What information should be present about BS
  • What information should be present about each issue
  • What image should be used to represent each issue
  • Are there any style/design guidelines or inspiration
  • Responsive design

workshop structure

  • Day 1: presentation of project, how's it working, aims, prototype front-end a few design option, prototype code, editors feedback (1 hour)
  • Day 2: implementation of design and code
  • Day 3: tests, refinement, editors feedback (1 hour)

wishlist

  • random image from the issue.

Front-end design for issue 2,3

  • dates: 9-13May
  • duration: 4 days
  • possible modes collaboration:
    • students from wdka + Lucia + publishing lab interns; active collaboration from Publishing lab (?)
    • external designers + Lucia(?)
  • deadline: end of June finished
  • Issue titles
    • 2: Education
    • 3: Radical Reframing
  • pages:
    • index page,
    • article page.

For issue 2: article titles and images from article appear next to each other in index.


Image based template

  • image based template: html structure, css, JS, added category in wiki (that identifies this)
  • duration 3days.


misc changes

  • include category "issue 3" wiki and accommodate it to the front end.
  • change name of issue 2
  • metadata page ofr each issue to exist in a wiki page - so it can scrapped to the frontend
  • Andre will do it