Day Designer Idea
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Idea to replace the todo pages with a "Day Designer".
Rather than assembling just a list of tasks for the day, assemble
available activities into time slots.
First user has to define a day plan.
The day plan then has slots.
Most slots are text strings representing tasks for that one day.
There are also "empty slots" which point to one of:
- tasks
- habits
- cyclic
Cyclic categories are dated at the category level.
example:
5am
- hydrate
- drink tea
- sort emails
6am
- exercise
- cardio
7am
- get ready
- shower
- breakfast
8am
- prepare for work
- get dressed
5pm
- exercise
- weights and calesthenics
- stretch
6pm
- dinner
- make dinner
- do washing-up
- put on dishwasher
7pm
- activities
8pm
- chores
- get ready for bed
So compared to our current TODO pages we have two extra layers of
abstraction. I think we keep the old TODO pages aswell.
Contributor guide
No contributing guide indexed for this repository
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 names no files, tests, or entry points; begin by exploring the repository to locate the current TODO page implementation and its task, habit, and cyclic models. This is a broad design feature: done would require a defined day-plan and slot model, the Day Designer flow, and continued support for the existing TODO pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100