Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

🌫️✨ Journal: Discovering Entries #6

Open
Tracked by #1
, #7
...
zspencer opened this issue Jan 29, 2024 · 0 comments
Open
Tracked by #1
, #7
...

🌫️✨ Journal: Discovering Entries #6

zspencer opened this issue Jan 29, 2024 · 0 comments
Labels
✨ feature Reduces Client's Burden or Grants them Benefits 🌫️ foggy Stuff we're not quite sure how to move forward with

Comments

@zspencer
Copy link
Member

No description provided.

@zspencer zspencer mentioned this issue Jan 29, 2024
Open
12 tasks
@zspencer zspencer changed the title Discovering Entries ✨ Journal: Discovering Entries Jan 29, 2024
@zspencer zspencer mentioned this issue Jan 29, 2024
Open
3 tasks
zspencer added a commit that referenced this issue Jan 29, 2024
@zspencer
🧹🥗 Journal: Add Entry#description field
a163c0b 
- #6

What I'm driving towards here is similar to
zinc-collective#2055, where a
`Journal::Entry` has an affordance for being opinionated about how it's
represented when linked to in search engines or peer-to-peer sharing; as
well as short text for when there are a several on `Journal#show`.
This was referenced Jan 29, 2024
Closed
Merged
zspencer added a commit to zinc-collective/convene that referenced this issue Jan 29, 2024
@zspencer
🥗 Journal: Writing Entries: Test adding Entry#summary
bd64503 
- zinc-collective#2
- zinc-collective#6
- zinc-collective#4

Clearly, when I started
zinc-collective#8 I used the
wrong name. It's not an `Entry#description`, it's an `Entry#summary`!

Perhaps that would have been more obvious had I started with the spec,
rather than the data model. Ah well, inside out and outside in are both
valid.
@zspencer zspencer mentioned this issue Jan 29, 2024
Merged
@zspencer zspencer changed the title ✨ Journal: Discovering Entries 🌫️✨ Journal: Discovering Entries Jan 29, 2024
@zspencer zspencer added ✨ feature Reduces Client's Burden or Grants them Benefits 🌫️ foggy Stuff we're not quite sure how to move forward with labels Jan 29, 2024
@zspencer zspencer mentioned this issue Jan 29, 2024
Open
zspencer added a commit that referenced this issue Jan 29, 2024
@zspencer
🥗 Journal: Writing Entries: Test adding Entry#summary
8f24440 
- #2
- #6
- #4

Clearly, when I started
#8 I used the
wrong name. It's not an `Entry#description`, it's an `Entry#summary`!

Perhaps that would have been more obvious had I started with the spec,
rather than the data model. Ah well, inside out and outside in are both
valid.
zspencer added a commit that referenced this issue Jan 29, 2024
@zspencer
🥗 Journal: Writing Entries: Test adding Entry#summary
56f0f2a 
- #2
- #6
- #4

Clearly, when I started
#8 I used the
wrong name. It's not an `Entry#description`, it's an `Entry#summary`!

Perhaps that would have been more obvious had I started with the spec,
rather than the data model. Ah well, inside out and outside in are both
valid.
zspencer added a commit that referenced this issue Jan 29, 2024
@zspencer
🥗 Journal: Writing Entries: Test adding Entry#summary
fdb42e8 
- #2
- #6
- #4

Clearly, when I started
#8 I used the
wrong name. It's not an `Entry#description`, it's an `Entry#summary`!

Perhaps that would have been more obvious had I started with the spec,
rather than the data model. Ah well, inside out and outside in are both
valid.
zspencer added a commit that referenced this issue Jan 29, 2024
@zspencer
🥗 Journal: Writing Entries: Test adding Entry#summary
d703b48 
- #2
- #6
- #4

Clearly, when I started
#8 I used the
wrong name. It's not an `Entry#description`, it's an `Entry#summary`!

Perhaps that would have been more obvious had I started with the spec,
rather than the data model. Ah well, inside out and outside in are both
valid.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
✨ feature Reduces Client's Burden or Grants them Benefits 🌫️ foggy Stuff we're not quite sure how to move forward with
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zspencer