Yuhu🍾🎊🎉! We have a roadmap!

This is a proposed high-level roadmap for the Scribus templates repository. We welcome comments, ideas and any other help!

The project explained in 3 simple steps...

  • 1. Download. Choose among existing templates.
  • 2. Restyle. Add your own flavours, create your own styles and looks.
  • 3. Reload. Upload your own versions and contribute to the community!

Overall picture 🗺️

  1. Our end goal is a repository of templates (.zip files).
  2. Templates will be freely downloadable (no login); uploading will require a simple registration.
  3. Groups will provide the required infrastructure for users to work on collective templates (e.g. magazine layouts with multiple pages) or specific themes (e.g. greetings cards group).

1. Repository

The objective is to set up a system for collective designing

The main feature of the repository will be its file storage system. It needs to be indexable and scalable and ideally be able to automate file operations like bulk image optimization and processing. Security features should include antivirus and deterrence against hotlinking.


Users uploading modified versions of existing templates should be able to indicate the parent template and state whether changes are:

  • MAJOR - such templates will constitute “forks” and will have their own unique name.
  • MINOR - these templates will constitute “editions” and will have a unique edition name. The system should be able to automatically assign a name should it be required by the user.

E.g. where Flyo is the orignal parent template:

  • MAJOR: “Brochur, a Flyo fork.”
  • MINOR: “Flyo, Red edition.”

Database structure

All files will have:

  1. A unique name (e.g. “Brochur”)
  2. A description (e.g. “Brochur is a great flyer for businesses…”)
  3. A unique username (e.g. “Norbert”)
  4. One or more tags (e.g. #A4, #2-column, #Business)
  5. One or more images/template art
  6. A Child status
    1. If Child status is TRUE, name of the parent template (e.g. “Flyo”)
    2. If Child status is TRUE, type of change (MAJOR or MINOR)
      1. If change type is MAJOR, a unique fork name (e.g. “Brochur”)
      2. If change type is MINOR, a unique edition name (e.g. “Red”)
  7. A Scribus version number compatibility (e.g. “1.3”, “1.4”, “1.5”, “1.6”)
  8. Credits (e.g. “Photo by Meghan Holmes on Unsplash (, Oxygen Font by Vernon Adams (”)
  11. A draft status [release 2]

2. Profiles

The platform will allow anyone to showcase one's contributions and attract potential customers

Each user will have a simple profile page. The profile page should be professional as well as community facing.

Profile entries

  1. Avatar (picture file)
  2. Username (e.g. “Norbert”)
  3. Email address (hidden)
  4. Website
  5. Social
  6. “Available for hire” status
    1. If status is TRUE, a description box to showcase set of “Skills”
  7. Group membership [release 2]

3. Groups

Groups will provide the necessary environment for collaboration


  1. Albert wants to create a great collective magazine template. He creates a group and contributes the first template part. Billie joins the group and contributes the second template part. Charlotte joins the group and contributes the third template part. Finally, they collectively agree to merge all the parts, creating the final group template. They can restart the process within the same group for new designs.
  2. Xiaobao wants to share the templates she designed for her class activities with other teachers. She creates a group and submits her templates. Yulia joins the group and submits her own templates. Zadig translates Xiaobao templates for his own use, joins the group and uploads his translated versions.

These scenarios imply:

  • “Draft” status for templates. When publishing a template in draft mode, users need to provide a description for the intended next steps or reason for choosing the “draft” status.
  • A collective approval process.
  • Groups should have indicative task/wish boards for anyone wishing to take on assignments (e.g. “Todo: Design Table of Contents section”, “Help wanted: Activities for K-12 classes”…). Anyone can leave or take one wishes.
  • Group and sitewide message boards.

Group requirements

  1. Group name (e.g. “Desining the best magazine template ever”)
  2. Group description (e.g. “We’re on a mission to create the best, detailed magazine template in the history of desktop publishing”)
  3. Group logo (or icon?)
  4. Task/Wish list
  5. Message board
  6. Sitewide message board (?)