azpect/Potion
1
1
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

FEATURE: Recipe of The Week #24

New Issue
Closed
opened 2025-07-16 19:40:33 -07:00 by azpect · 1 comment
azpect commented 2025-07-16 19:40:33 -07:00
Owner
Copy Link

User Story: As a user, I would like to see a display on the home page with a recipe selected as the recipe of the week. This is not terribly important, but a cool feature nonetheless.

Dev Notes

Not sure on the implementation, but I think my tech spec notes have some details:

  • Recipe of The Week
    • Fetch the most performing recipe of the last 7 days and all of the required meta data
      • Most views (W: 0.1)
      • Most makes (W: 0.5)
      • Most likes (W: 0.3)
      • Most reviews (W: 0.4)
      • Highest avg rating (W: 0.2/star, 0.0 - 1.0)
    • Direct a user to the recipes display page
    • Telemetry data to collect clicks for each recipe

I think this should be calculated every week, maybe midnight on Sunday with data from the preivous week, to display for the next week. Just not sure how to schedule jobs...

**User Story:** As a user, I would like to see a display on the home page with a recipe selected as the *recipe of the week.* This is not terribly important, but a cool feature nonetheless. ##### Dev Notes Not sure on the implementation, but I think my tech spec notes have some details: - [ ] Recipe of The Week - [ ] Fetch the most performing recipe of the last 7 days and all of the required meta data - [ ] Most views (W: 0.1) - [ ] Most makes (W: 0.5) - [ ] Most likes (W: 0.3) - [ ] Most reviews (W: 0.4) - [ ] Highest avg rating (W: 0.2/star, 0.0 - 1.0) - [ ] Direct a user to the recipes display page - [ ] Telemetry data to collect clicks for each recipe I think this should be calculated every week, maybe midnight on Sunday with data from the preivous week, to display for the next week. Just not sure how to schedule jobs...
azpect commented 2025-07-26 23:35:56 -07:00
Author
Owner
Copy Link

This feature was completed in #35 and updated in #36. The review data is not used, and should be updated when reviews are release, but for now, this issue will be closed.

This feature was completed in #35 and updated in #36. The review data is not used, and should be updated when reviews are release, but for now, this issue will be closed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Infrastructure
Improve infrastructure
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Priority
PostLaunch
The priority is for post launch
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
azpect
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: azpect/Potion#24
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?