[Pillar] Content Drive
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
The content drive pillar encapsulates all the work needed to build our digital asset management (DAM) offering which is more usable, modern and attractive than our current content | search and site | search. It is envisioned as another google drive or box, which is the mental model our user want and can transfer into our DAM space.
Links
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 kickoff deck, Airfocus item DOT-145, Figma design, and linked vision and POC materials first. Before implementation, this pillar needs to be split into actionable work with named entry points and acceptance criteria; this issue is done only when a specific DAM slice and its completion checks are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100