Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
Meta
Meta
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 125
    • Issues 125
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MoodleNet
  • MetaMeta
  • Wiki
  • small decisions made during front end workshop with outlandish

Last edited by Mayel de Borniol Sep 26, 2018
Page history

small decisions made during front end workshop with outlandish

The following issues came up, and were resolved, during our front-end development workshop with Outlandish (19th-21st Sept 2018)

  • Share functionality for MVP should give URL (c.f. sharing tweets on Twitter)
  • User profiles should include 'recent activity' (likes, resources added, etc.)
  • The name of who added a resource should be removed, for two reasons:
    • It's not a popularity contest
    • If someone leaves a community, it should be clear that they've already 'donated' their added resource to the community
  • Using tags in the main search field will allow for 'faceted search' (i.e. narrowing down original search terms)
  • No closed communities, just 'open' and 'moderated' (we can allow 'private' groups in paid for versions - like private GitHub repos)
  • Deal with difference between feed and notifications by allowing users to turn off notifications for types of feed items
  • By following someone you're adding their recent activity to your notifications
  • Include 'likes' in search by showing relevant items at the top of results
  • Discussions and comments on resources should appear in search results
  • On the desktop version, users can filter search results in the right-hand pane
  • We'll have a 'default' MoodleNet community for new sign-ups, which includes FAQs and getting-started guidance
  • We need pre-MVP user testing around:
    • Sign-up
    • Search
    • Notifications

Other things that were raised that are close to being decided:

  • Instead of using emoji ID we could use usernames as unique identifier
  • Uploading resources could be a premium feature to begin with
  • Colour-coded primary/secondary buttons - e.g. 'Add to Moodle' vs 'Add to collection'
Clone repository
  • Federation testing plan
  • HQ user testing plan
  • How to file bugs
  • List of intentions of MoodleNet users (verb based)
  • Localisation
  • OER metadata
  • Policies by user "rank"
  • Taxonomies and common metadata values
  • activitypub and activitystreams
  • apis
  • backends and controllers
  • databases and models
  • discussions
  • elixir app structure
  • front ends
View All Pages