Suggestion: Create Wiki page for integrating Bootstrap
Open
Nobody has claimed this yet.
documentation
- Dominant language
- PHP
- Stars
- 11.2k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
While browsing through the issues, I found that most Bootstrap-related issues are referring to the same two things:
- isRemoteEnabled
- box-sizing
So I'm suggesting to create a dedicated wiki page for that - even more since adding third-party CSS frameworks into PDF's is probably going to get more popular (not less).
Some more questions I would be interested in:
- When adding Bootstrap (one way or the other), will the final PDF include the entire Bootstrap code? Or is there some magic in place that removes unused styles? If no, Google (Lighthouse) recommends https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules
- What's your recommended approach? Do you have a rule of thumb if it's better to copy just the styles you need, or really try to add Bootstrap?
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
Review the existing Bootstrap-related issues mentioned in the report and the current wiki content before drafting a dedicated integration page. Cover the questions about isRemoteEnabled, box-sizing, unused Bootstrap styles, and recommended usage; done means the wiki page gives clear, supported guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bootstrap, css, php
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100