docs(doc-15): add descriptions to Kittehub project table #42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don’t think adding an additional column for features is necessary.
Here are some thoughts:
from doc-13
@autokitteh.activity
: If we’re trying to minimize the use ofautokitteh.activity
, it doesn’t make sense to highlight it, especially since it's not a concept most users will immediately understand.subscribe
andnext_event
: As far as I know, these features aren’t present in Kittehub.Python vs Starlark: If it's important to distinguish between Python and Starlark implementations, I suggest using an emoji with a legend for clarity. For example:
Legend:
⭐️ - Implemented in Starlark
🐍 - Implemented in Python
...
| 🐍 Data Pipeline |
| ⭐️ GitHub Copilot Seats |
| 🐍 Google Forms to Jira |
| 🐍 Jira Assignee From Calendar |
| 🐍 Jira to Google Calendar |
| ⭐️ Pull Request Review Reminder (Purrr) |
| ⭐️ ReviewKitteh |
| 🐍 Task Chain |