matomo-org / matomo-org/developer-documentation

Move blog articles into developer documentation

Open
#44 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Documentation enhancement
Dominant language
PHP
Stars
58
Forks
88
Avg merge
6d 3h
Merged PRs (30d)
13

Description

- [ ] [How to create a custom theme in Piwik](http://piwik.org/blog/2014/08/create-custom-theme-piwik-introducing-piwik-platform/)
- [x] [How to create a scheduled task](http://piwik.org/blog/2014/08/create-scheduled-task-introducing-piwik-platform/)
- [x] [How to create a widget](http://piwik.org/blog/2014/09/create-widget-introducing-piwik-platform/)
- [x] [How to add new pages and menu items to Piwik](http://piwik.org/blog/2014/09/add-new-page-menu-item-piwik-introducing-piwik-platform/)
- [x] [How to make your plugin configurable](http://piwik.org/blog/2014/09/make-plugin-configurable-introducing-piwik-platform/): merged into [Plugin Settings](http://developer.piwik.org/guides/plugin-settings)
- [x] [How to publish your plugin or theme on the Piwik Marketplace](http://piwik.org/blog/2014/09/publish-plugin-theme-piwik-marketplace-introducing-piwik-platform/)
- [ ] [How to create a command](http://piwik.org/blog/2014/10/how-to-create-a-command/)
- [ ] [Generating test data](http://piwik.org/blog/2014/10/generating-test-data/)
- [x] [How to make your plugin multilingual](http://piwik.org/blog/2014/10/how-to-make-your-plugin-multilingual-introducing-the-piwik-platform/)
- [x] [How to write UI tests for your plugin](http://piwik.org/blog/2015/02/write-ui-tests-plugin-introducing-piwik-platform/)
- [x] [How to verify user permissions](http://piwik.org/blog/2014/11/how-to-verify-user-permissions-introducing-piwik-platform/)
- [x] [How to write unit tests](http://piwik.org/blog/2014/11/how-to-write-unit-tests-for-your-plugin-introducing-the-piwik-platform/)
- [ ] How to expose new API methods (published soon)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the three unchecked linked articles about custom themes, commands, and test data, along with the developer documentation site. Move the applicable content from the blog into developer documentation, and consider the task done when the remaining checklist items are migrated or explicitly resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.