transofmer: current state : make relations more clear
This commit is contained in:
parent
821ea76b01
commit
30dd7618bf
1 changed files with 4 additions and 1 deletions
|
@ -75,12 +75,15 @@ Nevertheless, we see a lot of other cases that can benefit, if the primary goals
|
|||
## User Interface
|
||||
|
||||
### Current situation
|
||||
|
||||
#### Frontend
|
||||
The admin user interface in v1.0.0 lets one choose to which object type all post get transformed to. The options are:
|
||||
* [x] Note (default) — Should work with most platforms.
|
||||
* [ ] Article — The presentation of the "Article" might change on different platforms.
|
||||
* [ ] WordPress Post-Format — Maps the WordPress Post-Format to the ActivityPub Object Type.
|
||||
|
||||
Currently, only one hard-coded transformer exists in `includes/transformer/class post.php` ([Source](https://github.com/Automattic/wordpress-activitypub/blob/master/includes/transformer/class-post.php)).
|
||||
#### Backend
|
||||
Currently, all this functionality is handled via one hard-coded transformer in `includes/transformer/class post.php` ([Source](https://github.com/Automattic/wordpress-activitypub/blob/master/includes/transformer/class-post.php)) and the actual logic that assigns the type is somewhere else.
|
||||
|
||||
```php
|
||||
/**
|
||||
|
|
Loading…
Reference in a new issue