Proposal to create/transfer "spicy-sections" repo
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
We have been (esp big props to @jonathantneal) at work the last several weeks trying to put things into good order to have a pretty solid take in the oui branch of our spicy-sections repository. As we demonstrated a few weeks ago, this involves a lot of changes
- Changes the name from
<spicy-sections>to<oui-panelset> - Moves nearly all of the attribute relationships into the shadow dom
- Provides well specified parts for the shadow dom
- Changes the CSS property/value to be simple and intuitive/close to what we would probably propose
- Fixes a problem we had with testing setup
- Rewrites all of the tests to this model
- Creates some nice gh-pages hosted documentation
Along the way, however, we struck upon a fairly significant new open question/debate. We have noted this directly in the readme itself with appropriate recommendations relating to use. Despite that, we believe the best thing to do is to move this work at this stage into the openui repo and work together to address them.
We're asking for : a) Consensus to do that - and b) specifics about how (we could transfer the repo, but then I suppose we have to merge into main first - or we can fresh commit that branch into a new repo here and put a note on the old repo - or ...?)
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 spicy-sections oui branch, its README, rewritten tests, and gh-pages documentation. Read the linked issue 65 before assessing the open question. Done means reaching consensus on whether to move the work and documenting the chosen repository-transfer approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100