Define scope for new joomla.org template

[crystalenka]

[crystalenka]

@HLeithner Could you please write a little more here about what your needs are from the JXT with this? What are the expectations from the template team from us?

[crystalenka]

From Harald:

• which properties do we have

• which subsites should be affected by the new template

• based on all sites we have we need all "components/subparts" we need to design, (ex. topmenu, side menu, login module, forms, boxes, error messages, special layouts for download page or api docu....)

• how many people do we need?

• which typ of people do we need

  • programmer
  • designer
  • tester
  • conceptionist
  • a11y people
    ....

• How to find the people? Magazine article? (I may also have a designer would do it)

• what should be the timeframe (milestones)

• do we need a living design style guide (I expect yes)

• do we use a css framework (bootstrap, tailwind, our own)?

• needs the brand manuel to be updated? https://joom.la/JoomlaBrandManual at least the side must fit this Manuel

• technical stuff

  • footer/header for all sites? cdn? server side include?
  • joomla child templates for sub sites?
  • how to integrate into non joomla sites (docs.joomla.org, programmers docu, internal docu, forum, Pull request download page,...)
  • cdn or non cdn?
  • central image management?
  • central banner server?
  • security? do we need jsst at some point?

define the selection process who/why/when the design is selected? do we need some kind of pitch for this?

I'm pretty sure I missed many things, but most important is a structure and a tool we use to organise all this. I would suggest a github repo with projects. maybe using code for documentation or the wiki function in github. (we plan to use mkdocs for programmers documentation and internal documentation ex https://internal.joomla.org/ maybe we add the template documentation to the internal documentation I think that would make sense)