codefornl / clarity Goto Github PK

When we add volumes to the Dockerfile, users can map local directories to the docker container, making it easier to develop live.

According to the specifications, _links should be structured like this:

{
    "_links": {
        "self": { "href": "/example_resource" }
    }
}

Instead of

{
    "_links": {
        "self": "/example_resource"
    }
}

I want use cases to have multiple categories

As a curator I'd like to add links to my text areas, for example the cbase description and descriptions of projects. Is it perhaps possible to use markdown or something for these fields?

Information about the page, what is does, and more.

update create tables sql

Can we please provide a fallback to application/json when a browser is used to access the api?

SSL Certificate problems in Safari and CURL. Think need to include the whole chain.

footer mentions clarity_slim (which redirects here). Change into clarity.

Currently, the accepted values for language seem free text. It would be good if this could follow a standard, preferably https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes (2 letters instead of 3) and maybe even the Accept- and Content-Language code as set in the w3c standards?

The latter are desribed in rfc 1766
https://www.ietf.org/rfc/rfc1766.txt

use eloquent instead of pdo directly
checkout: https://www.codecourse.com/lessons/slim-3-authentication/759

Social media preview images not working. og:image tag seems to be there, but isn't working. Maybe because of SSL certificate problems?

• I want multiple organizations [] per use case instead of one
• I want organization to be an object with at least name and id
• I want to be able to browse use cases for a organization

As a curator I want to have my own logo on top of the page

As a curator I want to have my own link behind the logo on top of the page

Currently there is no default if you forget to set the BASE_URI environment variable. By adding an ENV entry to the Dockerfile, it will always fall back to default, making it easier for frontend development to onboard.