Skip to content
This repository was archived by the owner on Feb 18, 2021. It is now read-only.
This repository was archived by the owner on Feb 18, 2021. It is now read-only.

Additional candidate metadata #6

@aalmiray

Description

@aalmiray

I know gvm-sdk simply consume data comign from gvm's server side however I thought this would be a good place to start this discussion. Say someone builds a griffon client for gvm-sdk (hint, hint 😉); in order to make the app more appealing one would think it may display a logo and some other additional data that the gvm REST API does not expose (yet). Specifically I'm thinking of (at least) the following items:

  • name. We've got this already, that's the candidate name.
  • logo. Qualified list of URLs with small, medium, large, huge as qualifiers for example.
  • summary. One liner stating the candidate's purpose.
  • description. A few paragraphs (up to 3 maybe) in render friendly format (markdown perhaps?) with further details on the candidate.
  • url.

WDYT?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions