Shelly will be working on an app for this under the DevOps Team Services umbrella but there may be work within the DevHub proper to enable it.

Describe the bug
I have a markdown file in a repository that has an image [image](../../something.svg)
It appears to work when i view the markdown file from Github, but in the Devhub the image is broken.

What it looks like

What it should look like

Desktop (please complete the following information):

• OS: Any
• Browser Any

Smartphone (please complete the following information):

• Device: Any
• OS: Any
• Browser Any

What's wrong

Devhub Logo as it is at https://developer.gov.bc.ca is not inline with gov standards.

What I'd expect

The border should be removed and the font color should be white.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

as per discussion #33

Is your feature request related to a problem? Please describe.
#224 integrated lunr but no ui changes exist yet

In some cases for a given collection/source, there is a natural entry point and or overview/index/abstract that is where users should/want to start. This may provide additional context for some of the resources/cards or may provide suggested navigation/order/path through the collection. There should be an obvious way to link to this overview from the card list view.

For example, for the Design System, the logical entry point is the "About" resource. As it happens, clicking the "About" card links to the design system page/site with side navigation that provides a sort of path through the content, but it is not explicit from the card list that About is the starting point. A simple thought would be that perhaps we could annotate overview/lead/entrypoint resources so they don't show as cards, but are displayed by clicking on the collection header?

Shelly will be working on an app for this under the DevOps Team Services umbrella but there may be work within the DevHub proper to enable it.

as mentioned in #217 the code has been authored and tested but not implemented. Opening a new issue to implement the file transformer plugin that was created in #217 AFTER #213 has been merged!

Originally posted by @patricksimonian in https://github.com/bcgov/devhub-app-web/issue_comments#issuecomment-449160137

Describe the bug
if a markdown file has a link
with
owner: bcgov
repo: foo

[my link](README.md)

the file transformer doesn't transform this correctly.

To Reproduce
what happens

[my link](https://developer.gov.bc.ca/README.md)

Expected behavior
it should transfomr url using repo owner and name

[my link](https://github.com/repo/owner/blob/master/README.md)

or something like that?

Since #214, Siphon has the ability to source website and convert them into graphql nodes.

There is no documentation explaining this however.

Describe the solution you'd like
It would be awesome to be able to just request a specific file from a repo using a github URI or some other type of configuration

Describe alternatives you've considered
The only alternative would be to register the repo with a massive inline ignore configuration to ignore everything but the file described

OR

To register the repo with a (currently non-existant) include configuration

Additional context
Something like this in the registry would be amazing..

sourceType: github
sourceProperties:
  name: myrepo
  owner: owner
  file(s): https://github.com/bcgov/devhub-app-web/blob/master/docs/Readme.md

Devhub Repo should have a pull request template

https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/

Add documentation explaining how to use siphon collections

Right now the registry only allows for one persona per resource, It'd be great if we could allow an array of personas

Is your feature request related to a problem? Please describe.
There is some scattered content in the devhub about github but not a clear collection. With the collections #174 feature available. We can pull in a whole bunch of resources to describe the github in government journey

Describe the solution you'd like
A collection of github for gov resources

Describe the bug
getting prop type errors

To Reproduce
Steps to reproduce the behavior:

1. Go to home page
2. open dev tools
3. See error

Expected behavior
no prop type errors

Screenshots

index.js:2177 Warning: Failed prop type: Invalid prop `actions[0].icon` supplied to `ActionsRibbon`, expected a ReactNode.
    in ActionsRibbon (created by Component Card Component)
    in Component Card Component (created by Github Cards Component)
    in div (created by Toggle)
    in div (created by Toggle)
    in Toggle (created by Github Cards Component)
    in div (created by Github Cards Component)
    in section (created by Github Cards Component)
    in Github Cards Component (at pages/index.js:46)
    in Flag (at pages/index.js:106)
    in div (at pages/index.js:105)
    in div (at pages/index.js:102)
    in main (at pages/index.js:60)
    in div (created by Layout)
    in Layout (created by Connect(Layout))
    in Connect(Layout) (at pages/index.js:55)
    in Index (created by Connect(Index))
    in Connect(Index) (created by PageRenderer)
    in PageRenderer (created by JSONStore)
    in JSONStore (created by EnsureResources)
    in ScrollContext (created by EnsureResources)
    in RouteUpdates (created by EnsureResources)
    in EnsureResources (created by RouteHandler)
    in RouteHandler (created by Root)
    in div (created by FocusHandlerImpl)
    in FocusHandlerImpl (created by Context.Consumer)
    in FocusHandler (created by RouterImpl)
    in RouterImpl (created by LocationProvider)
    in LocationProvider (created by Context.Consumer)
    in Location (created by Context.Consumer)
    in Router (created by Root)
    in Root
    in FlagsProvider (created by ConnectedFlagsProvider)
    in ConnectedFlagsProvider
    in Provider
    in _default (created by HotExported_default)
    in AppContainer (created by HotExported_default)
    in HotExported_default

It looks like gatsby version 2 has been released. Gatsby's site no longer offers v1 documentation. This is a good cue for us to migrate to the latest version. There are huge performance benefits to be had with the migration
gatsbyjs.org/blog/2018-09-17-gatsby-v2

gatsbyjs.org/docs/migrating-from-v1-to-v2

make sure to update gatsby-remark-autolink-headers package version to latest (it is specifically using an outdated version to work with gatsby v1)

Previously we had 4 cards across, and no second row. We should revert to that layout or something equally sensible.

Documentation should have a template markdown file that can be referenced or copied, specifically a markdown file with the front matter properties that are required for devhub to consume the markdown content.

Is your feature request related to a problem? Please describe.
The devhub has a lot of content now. It sure would be great if we could search through it!

Describe the solution you'd like
A search bar

Describe alternatives you've considered
No search bar?

It would be nice to spruce up the header displays in the card list view so that they can provide more visual appeal and cues to users.

For example, we could support icons to indicate the "type" of a collection (tutorial, guide, component set/library).

Connected to the "overview" issue, we could also contemplate having "fat/informational headers" - maybe even expandable to show a snippet of the overview information...Also maybe collection "metrics" (# content items, etc.)

Describe the bug
It recommends authoring all plugins as async plugins which is not the case anymore. Sync and Async plugins can be used in serial order.

Is your feature request related to a problem? Please describe.
When you load the devhub up. it takes some times for the cards to render and so there is a flicker.

Describe the solution you'd like
perhaps we can enable a loading spinner indicator while the cards are being rendered

local development installation instructions are out of date

The template can be broken down into smaller components as an effort to reduce code debt.

As per #180, there is no documentation to explain how to do this.

To differentiate between "types" of collection, we should support specificying a "type" (and/or icon) that would be dispalyed alongside the heard title and descrition in the card list view.

We should dig into having multiple templates for pages generated in the framework. The first use case would be for collections "overviews" where we would prefer something other than the current "sidebar" nav as a way to move between / visualize pages in the collection.

Is your feature request related to a problem? Please describe.
After seeing the welcome to devhub jumbotron it'd be nice if it didn't render subsequent times

It would help usability to have hoverable tool tips for each of the action buttons on the cards so it's clear to users what will happen when they click one.

Taking a look at the filtering components, they are duplicated for mobile views, these can be refactored to be inside of the layout component to clean things up and reduce code debt

Hello, Taiga world!

Is your feature request related to a problem? Please describe.
I guess the problem could be is that the author attribute in markdown frontmatter or a twitter card or open graph OR some other type of metadata spec is assumed to be a github user.

Describe the solution you'd like
It would be nice if we could better annotate the type of author a user is
EG:

• twitterCard
  <meta name="twitter:author" content="github:patricksimonian">
• openGraph
  <meta name="og:author" content="github:patricksimonian">
• frontmatter in markdown

---
author: gravatar:[email protected]
---

Additional context
I think allowing for this convention opens the door for many new exciting ways of integrating an author into the devhub. We could potentially pull profile data from different sources such as gravatar, github, and so on.

Describe the bug
I'm unable to reference an image in my markdown front matter by relative path or absolute path

To Reproduce

Sample Markdown

---
author: patricksimonian
description: description
title: title
image: /docs/images/myimage.png || ./images/myimages.png
---
markdown content below

Expected behavior
I'd expect that when this is transformed into an <img src="...">, when viewing the resource as a card, that the path to the image is properly processed with the original source location of the markdown file/repo

ie: <img src="https://www.github.com/owner/repo/blob/docs/images/myimage.png?raw=true">

Extra Info

This appears to be working correctly if an image is loaded via a twitter card?

Is your feature request related to a problem? Please describe.
It can be hard to discern what front matter I need to add to my markdown files.

Describe the solution you'd like
A graphical interface where I can select/edit the front matter properties I want which then is converted into valid markdown front matter I can copy and paste

Describe alternatives you've considered
Reading Documentation

Additional context
This is ultra low priority, but just keeping it out there as a thought.