danielbrendel / hortusfox-web

Self-hosted collaborative plant management system for your local environment
https://www.hortusfox.com
MIT License
628 stars 34 forks source link

Implementation of a wiki/knowledgebase #283

Open Appoxo opened 5 days ago

Appoxo commented 5 days ago

Description of your request

Small wiki. Sort of like for the notes but instead decoupled from the specific plant.

Describe the solution you'd like

Another entry in the status bar for a wiki Why another location for information? Because if I send the plant to the graveyard/history all knowledge of the plant is lost. This could also help with redundant/outdated information if several types of the same plant (e.g. after splitting/cloning) exists. This could be linked with the calendar and the plant page. Calendar could show shopping time (e.g Ginger planting is for my region in April) Plant page could show a hyperlink to the wiki page based on Genus and/or species (maybe with an optional admin setting to disable that matching)

How I would use it:

The wiki could be created with a markdown WYSIWYG editor/render and some small formatting options like github does in the issue page: grafik

Option A: An entry could be created from scratch by having to enter the genus and optionally a species. Option B: An entry could also be created from existing plants and a tool tip could offer me a suggestion for an entry Option C (in case both do not apply): Create an orphaned entry

The page could offer attribute-like entries like:

Beyond the genus entry are sub entries for the species which could deviate from the main genus. Those entries inherit the entries from the main genus. Optionally another text-color could indicate if the value is inherited or not

The presentation of the page could show the genus and species in one single page with species separated as sub-sections or like a drop-down menu from the genus page

Describe alternatives you've considered

Alternative would be doing it in another notes app/service. But that would sadly not be connected with HortusFox beyond web-links :/

Additional context

Crude mock-up I made with the browser-dev settings: grafik grafik

danielbrendel commented 4 days ago

Hi,

thank you for your suggestion! I actually think having at least some small, toggable knowledge base feature would be really great. But I personally would like to have it to be very generic, so it can reach a broad audience.

This is what I imagine under the term "generic":

Now the main problem would be to link "types of plants" and then have it automatically set for new plants of a specific type. The easiest approach would be via the cloning feature. Because in its current form HortusFox does not really support something like "creating a genus/species as a top category". Cloning would be the way to go here.

I think I'll start with a base feature like mentioned above and then we can iterate on that and see how it will turn out.

Thank you for your suggestion and I'm really excited to turn it into reality! Message ID: @.***>

Appoxo commented 4 days ago

Sounds like a solid starter plan.

Maybe the knowledge base can be matched with regex?

The scientific name should be consistent across languages anyway. If the app ignores capitalizatiom it should be able to match the term set in a plant (if it's available and configured). If no name in the specified name it would create a new entry <somewhere™>