Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

We conducted a brainstorm session on web site and e-presence needs and solutions, which generated a lot of input.


Problems noted:

1.1. newcomers versus 'congregation' balance needs to be better on the website

1.2. single website presence

1.3. same size of website for different devices

1.4. information about programs are not current (missing vision, processes)

1.5. need to address: privacy, accessibility, cookies

1.6. other online media

1.7. changes in information structure

 

Suggestions:

1.1.

    1. newcomers: top half of home page
    2. very visible demo links
    3. 'why openehr' needs to be addressed on home page; e.g. Seref's blog post (basic block approach: 'how to store data', 'how to define content' - inspiration from Marand website)
    4. consider 'portal's approach i.e. home page for devs, clinicians etc
    5. endorsements by using orgs visible on home page

1.2.

    1. unify information in different places (contact info)
    2. remove / redirect openehrfoundation website, change design of members website so it looks it belongs to main website

1.3.

    1. create version of website for different devices

1.4.

    1. news for each program, define road map for each program
    2. define processes of work in each program so people can get involved
    3. blog syndication, make it part of program pages

1.5.

    1. find out about accessibility regulations
    2. make link to CKM more obvious

1.6.

    1. outgoing links to stackoverflow openEHR references
    2. connect to LinkedIn discussions (how?)
    3. manage youtube, facebook

1.7.

    1. events news should only be future events (past events on another page)
    2. get subdomains versus /xxx rationalised


Decisions:

  • connect members.openehr.org to main site
  • curate members.openehr.org
  • move website and mailing lists to new Hetzner server
  • put together a requirements statement
  • method of usability testing
  • web content committee
  • mailing lists on new server + mhonarc for mailing list archive
  • ensure news authors have login
  • No labels