-
Currently, internal INTERSECT logic does not utilize protocol headers at all, but serializes metadata and the message "payload" (the actual scientific data) into a single JSON blob. So an actual "mess…
-
I really love this idea, and would love to see it useful not just for posts, but I can understand that posts it s a good starting point.
-
How can a collection of different content types can be unwrap?
our json preview looks like this
```id": "activities",
"name": "Activities",
"type": "Array",
"localized": fals…
-
This is an inconsistency someone raised with us in the process of documenting the contents list component as part of the design documentation work:
Inconsistent position in source order. The placemen…
-
### What needs to happen?
- Remove the existing "Plugins" page.
- Improve plugin content by restructuring the categories (remove duplicate VFS mentions, clarify the technical plugin section).
- Upd…
-
We should only allow uploading...
```js
export const SUPPORTED_TYPES = [
'text/html',
'application/json',
'image/jpeg',
'image/gif',
'image/png',
'image/svg+xml',
'video/mp4',…
-
Currently, we can list content types in sites and lists, but when using quite some content types that inherit from the same content type (e.g. `Site Page X` inherits from `Site Page Y` which inherits …
-
API endpoints can serve different content types, e.g., `application/json`, `text/plain` etc. Clients can ask a service to respond with one or more specific accepted content types.
It would be nice …
-
https://webmention.net/draft/#request-verification
This would help in expanding per media type rules
-
A great suggestion from Sebastien on gitter last night that's worth tracking
> Someone should add some helper in C# so that we could define a class like MyCustomer.cs which would have content parts…