indieweb / indieweb/wordpress-indieweb
a more guided installation of sub-plugins
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 83
- Forks
- 18
- Avg merge
- 1h 13m
- Merged PRs (30d)
- 1
Description
@miklb wrote on his wiki page:
> I know GWG is working on improvements to the IndieWeb plugin,but right now it's emphasized in the wiki. It just directs people to download 10 more plugins, without doing anything. The ala carte plugins might be great for a seasoned user who wants choices to build IndieWeb into their existing site, but for someone just setting up WP it's overwhelming.
Perhaps we can guide the user a bit more, and explain why to install a plugin or when to skip one. I am using a very simple mechanism to show the plugin "install cards" without using an external class or script, for the OStatus plugin: https://github.com/pfefferle/wordpress-ostatus/blob/master/templates/settings-page.php
Perhaps we can use that to integrate the "install cards" between some more detailed install instructions. An orientation can be the http://indieweb.org/IndieMark
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the bundled installer and review the OStatus plugin's templates/settings-page.php example, then use the IndieMark orientation as the guide for the installation flow. Done means the installer provides more detailed guidance, explains why each sub-plugin is useful, and indicates when a user can skip one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- developer-experience, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100