Changes between Version 55 and Version 56 of Projects/Design

12/01/14 07:48:41 (9 years ago)
Pat Tressel



  • Projects/Design

    v55 v56  
    219219It's also partly for Sahana -- for you to propose a different way of presenting information, maybe more appropriate than what we have for a particular purpose.  Sahana is mainly about getting help to people who need it, so if you can make an advance in usability through your new theme, you're contributing to that goal.
    221 ==== What to do for this task ====
    223 Please read the whole [#Developinganewtheme Developing a new theme] section.
    225 Since this is a theme, the page layouts, navigation elements, colors, and user interaction are the most important part.
    227 Make three pages of different types, one each from the three sets of options that follow.  See the list of page types in the [#Developinganewtheme Developing a new theme] section, which points to examples of each kind of page.  Again, ignore the "look and feel" of those examples -- just look at the sort of data they are trying to display.
    229 * Either a ''homepage'', or a ''dashboard'' for some type of resource, e.g. projects, or people, or organizations, or...
    230 * A page that shows information for a single resource, such as one project or one organization. Examples of such pages are the ''component view'' pages or the ''profile'' pages, but you can invent another way to show the information.
    231 * Any other type of page, e.g. a ''create form'' or ''list view''.
    233 You can include more pages if they are important to your site's purpose (or you'd like to show your accomplishments!).
    235 Use active elements like menus, buttons, popups, etc.  If it's important to the theme, have the active elements do something.  (For instance, if you want to try a page with tabs for components, make clicking the tabs change which tab's data is shown.  If you use a checkbox to show or hide options, have checking it actually show or hide the options.)
    237 You don't need to include a lot of fake data.  For instance, if you make a list view, there's no need to have more than two rows.  If you make a component view that has tabs, you don't need a lot of tabs.  Just include enough to show the layout you want for the page that contains the tabs, and for the info in each tab.  If you want to try bootstrap "cards", just put one or two in each card container.