Second instance of Deck or possibility to hide boards
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Hello all,
I am looking for a solutionto a problem that comes from having a lot of boards in one instance.
One approach could be to have a second deck app installed. I would clone the app, adjust the database table names and give it a got - or would that be more comlicated ?
Second idea is, to have some boards hidden, and introduce a board that functions as a table of contents with links to the hidden decks.
Before I start modifying code which brings along all sorts of problems with the release of a new version, I would like to know if any of these have been planned to be integrated in future releases. Thanks.
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
The issue proposes either a second Deck instance with separate database table names or hidden boards linked from a table-of-contents board. No files, tests, or entry points are mentioned; first clarify which approach is wanted and define its behavior before locating the relevant code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100