griceturrble / recipes.riceprower.com Goto Github PK

Don't have time at present to fix it, leaving this as a note to self.

Failed run: https://github.com/GriceTurrble/recipes.riceprower.com/actions/runs/3670394957/jobs/6204907226

Need to update the certificate on the live server ASAP, or it can't be served at all:

Celery integration w/ RabbitMQ.

Reference: https://www.codementor.io/@ankurrathore/asynchronous-task-with-rabbitmq-celery-and-django-8904ceway

Invoices should be printable.

Images uploaded to comments in this issue (which will stay closed) are used as the source for the site.

If anyone has an issue with it, I'm happy to take stuff down and refactor.

Probably want to customize the recipe stats into something other than the built-in Material MkDocs cards:

This initial version was just a clunky way to get it working, but there needs to be an update.

• Needs to use a default option for "today".
• Should be able to work on all active projects, not just a requested one.
• Bug currently in trying to use Client.new_address, which does not exist (models.py code).

See about integrating the Invoices system with Bill.com APIs, so that generated invoices can trigger invoices to be sent.

Recipe data stores links to ingredients by type and uses those type names. However, sometimes it would be nice to have a custom name added to those ingredient types, so that it displays differently on the frontend from what it connects to on the back.

Would be a new text field (potentially a "plural" override text field as well) that contains a custom override name for the ingredient type.

Example: type "white sugar", override with the text "granulated sugar".

Observed on my phone:

Have to adjust the z-index of that search box. Probably just fiddle with it in the site styles.

• check if the same behavior occurs in desktop

Needs a little customization. The prose style must be messing with it.

Recipes are currently coded with set of ingredients, but not number of servings.

Need:

• Number of servings as an integer
• Potentially some extra text to go beside servings number to indicate what the thing is.

Example: 24 servings, text "cream puff" -> 24 cream puffs (auto pluralization would be nice as well)

Currently, all pages on the site are set to login permissions required (as well as recipe view permission, which is not on by default, even if a user found a way to register with the site).

Change would be making the RecipeList and RecipeDetail views public-facing, while adding a flag to Recipe model that allows them to be set to is_private. Doing so would hide them from non-logged-in members.

Debating whether to have some comment system on the site.

It's simple to enable Giscus and hook it in here, but commentors need GitHub accounts, which won't with so well for friends and family.

Disqus may work out better in that regard, but likely comes at a cost. Research needed.

Make it a little less bland.

https://heroicons.com/

Same creator as Tailwind.

Can entirely remove a dependency on FA if it works out.

When any ingredient is checked, show an "uncheck all" button that will, as it says, uncheck everything.

Currenty webpack strategy for bundling all CSS and JS produces a single bundle.js that, itself, creates the CSS styles for the site.

Found in practice that running this bundle with <script defer causes it to wait for some content to load, which is usually not that big a deal. However, in one case where a lot of content is being written onto the screen, the resulting page seems to be completely unstyled until after the content finishes loading. This does not seem like an ideal scenario.

Better to produce actual CSS files, have them cached in the browser to produce styles even as content is being written. leave the JS to the JS and the CSS in a different file.

Might need some research here to see if Webpack can accomplish what I want in this regard. Otherwise, may need to fall back to running PostCSS by itself in a separate step (which overall makes for a lengthier build process in dev, which was the main reason I started down this one-stop-shop strategy).

Making the chili today, logging the results.

(blocked by #1)