![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Changes between Initial Version and Version 1 of Ticket #3123, comment 4
- Timestamp:
- 09/12/2017 06:43:05 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #3123, comment 4
initial v1 1 1 Well hello there ! 2 3 I've been interested in this since you opened it but I'm still waiting for some replies from the docs team to see how could I possibly suggest edits on the Handbooks as it's a totally different thing from Codex, so that kept me aside for a bit but it will be done !4 2 5 3 I was thinking as well to continue @Otto42 thought that maybe the `readme.txt` could be transfered inside the Handbook as well as there is the `Header` mockup there could be a full readme there as a base to have everything grouped up nice. 6 4 7 That being said Otto's comment confused me even more as I already have the meta-env here but I've got a bit confused on how to make a diff if it's a database change through either `plugin-directory` or `plugin-theme`. Except if you actually referring to adding a shortcode for example on the plugin itself so you could then display the readme.txt anywhere on the website.5 If you want it within the plugin as you say would a shortcode be an option? for example `[show-plugin-readme-example]` that would output what readme.txt currently has? I'm not sure what you mean exactly as even the .txt itself could be added on the version control even. 8 6 9 For now I'm adding the readme.txt up with the change adding the `Requires PHP` hoping for some replies from the docs team to see how can I get going with the Handbooks as well.7 I've made the proposals on the #docs channel and for now I'm adding the readme.txt up with the change adding the `Requires PHP` hoping for some replies from the docs team to see how we can get it going with the Handbooks as well.
