Generate cloneable document fragments for any static piece of markup
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 54
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the frag branch generates a cloneable document fragment for an entire template if it doesn't have any dynamic aspects. This should be done on a smaller scale where it make sense from a performance standpoint.
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 inspecting the frag branch and the template-generation path it changes. Identify how fully static markup is detected and compare that with smaller static pieces, then establish performance measurements before deciding which fragments should be cloneable. Done means the chosen static pieces use cloneable document fragments without changing dynamic template behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100