feat(faq): add user-facing FAQ entries and organize into sections#168
Open
TimeToBuildBob wants to merge 2 commits intoActivityWatch:masterfrom
Open
feat(faq): add user-facing FAQ entries and organize into sections#168TimeToBuildBob wants to merge 2 commits intoActivityWatch:masterfrom
TimeToBuildBob wants to merge 2 commits intoActivityWatch:masterfrom
Conversation
Add general FAQ entries from the website (activitywatch.github.io#42): - What is ActivityWatch? - Is it really free? - Platform support - Privacy/data storage - RescueTime comparison (with link to detailed blog post) - Custom tracking/extensibility Organize into General and Technical sections for better navigation. Existing technical entries preserved as-is in the Technical section. Follow-up from activitywatch.github.io#42 discussion per @ErikBjare request.
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to 148fd68 in 7 seconds. Click for details.
- Reviewed
126lines of code in1files - Skipped
0files when reviewing. - Skipped posting
0draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
Workflow ID: wflow_bc3xYoewWzoU4YmD
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
Greptile SummaryAdds comprehensive user-facing FAQ entries covering ActivityWatch basics (what it is, pricing, platform support, privacy, RescueTime comparison, and extensibility) and reorganizes the FAQ page into General and Technical sections. The new content aligns with the website homepage FAQ for consistency and addresses common questions from potential users.
Confidence Score: 4/5
Important Files Changed
Last reviewed commit: 148fd68 |
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds user-facing FAQ entries to the Sphinx docs FAQ page and organizes it into General and Technical sections.
New entries (General section):
Changes to existing content:
~~~instead of---) for proper section hierarchyContext:
Test plan
:ref:) resolve correctlyImportant
Adds new user-facing FAQ entries and reorganizes existing content into General and Technical sections in
src/faq.rst.src/faq.rst: "What is ActivityWatch?", "Is ActivityWatch really free?", "What platforms does ActivityWatch support?", "Does ActivityWatch track my data privately?", "How does ActivityWatch compare to RescueTime?", "Can I extend ActivityWatch with custom tracking?".---to~~~for proper section hierarchy.This description was created by
for 148fd68. You can customize this summary. It will automatically update as commits are pushed.