[Feature request] Custom CSS field
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- css, javascript
- Domain
- frontend
Research direction
Start by reviewing the linked custom footer content commit and the settings implementation to understand how that field is stored and rendered. Add a custom CSS setting that permits simple style overrides without the existing sanitization blocking them; done means users can enter CSS in settings and see it applied to the base style.
Written by the indexing model from the issue text.
Description
I see in the latest pre-release version of streama that there is an option for custom footer content. I was hoping to be able to use this field to add a few custom CSS styles but it looks like the input is being sanitized.
I would love to see a custom CSS field in the settings that would allow for some simple custom tweaks to the (already excellent!) base style.
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 978
- PR merge metrics
- No merged PRs in 30d
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.
More from streamaserver/streama
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
streamaserver/streama#1164 ·
-
API calls Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
streamaserver/streama#1162 · 10 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamaserver/streama#1161 ·
-
Java issue Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamaserver/streama#1160 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
streamaserver/streama#1157 · 1 comment ·
All issues in streamaserver/streama
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100