wassname/talk
1
0
Fork 0
mirror of https://github.com/wassname/talk.git synced 2026-07-28 11:27:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos and clarify

Browse Source
This commit is contained in:
David Erwin
2017-07-11 11:05:58 -04:00
parent 52d7ba8965
commit 1d9b627d73
2 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture-tags.md
+3 -1
View File
@@ -25,7 +25,9 @@ See [Plugin API Documentation](plugins-server.html#field-tags) for more informat
### Creating a Tag Definition
Tag Definitions must be created before tags can be used. This ensures that users cannot push arbitrary tags to hack the system. It also allows devs to specify the behavioral characteristics of the tag.
Tag Definitions must be created in order for the system to determine what tags are permitted on the server side.
Tag Definitions do not contain any logic themselves but provide information that other parts of the system can use to specify which models a tag can be applied to (models) and perform authorization logic (permissions).
Take the tag created by `coral-plugin-offtopic` as an example.
docs/architecture.md
+3 -3
View File
@@ -42,9 +42,9 @@ Now, ask these questions:
### Is it a Plugin?
Most work for Talk these days happens in the Plugin space. If the answers to any of these questions is Yes, then you're thinking of a Plugin.
Most work for Talk happens in the Plugin space. If the answers to any of these questions is Yes, then you're thinking of a Plugin.
* Does Talk's exiting Plugin APIs support the thing you want to build?
* Does Talk's existing Plugin APIs support the thing you want to build?
* Is this something that only some users will want/need?
* Is this something that we want devs to iterate on widely?
@@ -62,7 +62,7 @@ Note: we are stabilizing the process by which new Plugin API bindings are create
### Does it need updates to the Plugin API _and_ Core?
3) What, if any, changes need to be made to Core so that the API can be extended?
What, if any, changes need to be made to Core so that the API can be extended?
Quite often the only things missing from Core are things like _events_, _slots_, _CSS classes_, etc... Adding these is a great way to become a Core Contributor and break new ground as a Plugin Developer.