Document the development of plugins
Nobody has claimed this yet.
- Dominant language
- Nunjucks
- Stars
- 547
- Forks
- 726
- Avg merge
- 2h 23m
- Merged PRs (30d)
- 3
Description
Is there any documentation on the development of plugins? If not, is there a plan to create some?
At the moment I'm thinking of developing a plugin that looks for files with a specific extensions and then processes them before adding the processed data to the data that is available in the templates. Is there anything about something like that? Thanks!
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the Eleventy documentation and the related issue #395 to determine what plugin-development guidance already exists. Define coverage for plugins that find files by extension, process them, and expose the result to templates; done means that workflow is documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100