lionleaf / lionleaf/dwitter

Draft?

Open
#407 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
803
Forks
68
PR merge metrics
No merged PRs in 30d

Description

I know the whole point is to keep it short and simple, but unlike human languages 140 chars of code can sometimes require quite a bit of hacking which takes more time and effort.

A draft mode would be nice for this purpose - currently a have a few text files floating around i'm hacking on that I copy and paste back and forth but aren't submission worthy.

Just discovered Dwitter btw and I love the concept :smile: I am hooked

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No file, test, or entry point is named. Start by tracing how submissions are created and stored, then determine how an unpublished draft would be distinguished from a submission and where users would edit it; done means users can save, resume, and keep a draft out of published submissions.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.