CODESIGN2 / CODESIGN2/CODESIGN2.github.io
case-studies layout needed
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Need case-study layout to show-off some prior work.
* How to keep relevant ?
* Short-piffy catch-all attempt
* write from each of 3 customer profiles
* showcase specific to service heading on dedicated service page
* How to give enough information to assist without bombarding and overloading ?
* Additional Iconography Needed?
* Balancing doing what is right, vs sticking to what we can legally disclose (likely needs a lawyer)
* Monitoring usage
* Don't want to spend hours breeding unicorn features that are never or sparsely used
* Can this be integrated into existing sales / on-boarding process and documentation?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by turning the listed case-study content questions into a concrete layout proposal for the static site. Resolve how customer profiles, service-specific showcases, iconography, legal disclosure, and usage monitoring fit together; done means the case-study layout and its content boundaries are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- design, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100