Explore making the next day's file with a script or an agent

Open
#259 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
javascript, markdown

Research direction

Start by reading the existing “Start today's” behavior and the linked issues #258, #197, and #18 to understand file creation, carry-over, and templates. The issue lists design questions about execution, permissions, failures, network access, and whether the feature is needed; it does not name files or tests. Done means answering those questions and deciding whether to build anything.

Written by the indexing model from the issue text.

Description

enhancement P3

Exploratory and low priority: this could be quite involved, for a benefit that isn't yet clear.

Start today's makes today's file from the folder's latest, with every answer cleared.
Some pages need more than clearing to be ready for a new day: a page of today's observances, a reading for the day, or the to-dos that carry over (#258) by a rule of someone's own.
Those are written by hand each morning, or left out (#197 leaves out its celebrations page for this reason).

To explore: a way for a file to say how its next day's is made, for example in front matter:

---
title: Journal
type: workbook
next: next-day.md
---
  • next: next-day.md: instructions for an agent, which writes the new page.
  • next: next-day.js: a script run on the server, which is given the latest file and returns the new one.

Questions to answer before building anything:

  • What it can do, and what it's trusted with: a script on the server can do anything the server can.
  • Whether it runs on Start today's, on its own each morning, or only when asked.
  • What happens when it fails, or is slow, or there's no network.
  • How it relates to templates for new files (#18).
  • Whether the same need is met more simply, for example by #258's carry-over alone.

Came up in the review of #197.

Dominant language
JavaScript
Stars
0
Forks
1
Avg merge
2d 4h
Merged PRs (30d)
26

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jzheaux/reader

All issues in jzheaux/reader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.