open-product-management VS product

Open Product Mgmt by Product Hired master advice hub: https://github.com/ProductHired/open-product-management This one has fallen out of being updated but still has some good organization for specific areas.

This index of articles helped me a lot to understand the shift in my role and especially how much of it needs to be tied to business outcomes, not just feature usage. The content can vary but I really like how it's a lot of perspectives from different people on the PM practice and role and lets you decide what aspects make sense to focus on.

There are so many resources. Here are some which are compiled by someone. 285 Free Resources for Product Management Top 75+ Resources for Product Managers "Open Product Management", a massive resource center by Product Hired

You could do a repo for static content, something like https://github.com/ProductHired/open-product-management but I'm not really sure how to effectively link that (I guess you could match to branches for code?

read these https://www.hbspm101.com/readings & https://github.com/ProductHired/open-product-management

We’re excited to walk our first steps toward semantic search. We can’t wait to hear your thoughts on integrating Meilisearch as a vector store. You can give your feedback in this Github discussion.

Looks good in fact! We will eventually let users use third-party API like OpenAi and Hugging Face to compute the embedding of the documents and queries. You can try our first prototype if you want.

Hey @jiripospisil,

Indeed Meilisearch does not offer an aggregation feature yet although it will be possible to get stats for the `min` and `max` values of a faceted field in the next version (v1.1)

Please tell us more about what you mean by aggregation and why it is critical for your use-case by creating a discussion on Github here (https://github.com/meilisearch/product/discussions) or by proposing a new idea on our public portal here (https://roadmap.meilisearch.com) if you don't have a Github account.

Thank you!

If you remove the URLs from indexation, it'll generally save a ton of place and will be much, much faster to index. We are thinking about not indexing URLs by default; you can help us by explaining your use case here -> https://github.com/meilisearch/product/discussions/553

Just a detail, if you're making a `du -sh` on your computer, the size on the disk will stay unchanged because we are doing soft deletion ;). Don't worry. It will be physically deleted after a while if you need it in the future.

If you kept the default configuration of Meilisearch, the maximum size of the HTTP payload is 100Mb (for security). You change it here -> https://docs.meilisearch.com/learn/configuration/instance_op...

addDocumentsInBatches() is just an helper to send your big json array into multiple parts, not absolutely sure you'll need it. (Code -> https://github.com/meilisearch/meilisearch-js/blob/807a6d827...)

I advise you to fill out a discussion on our product repository for us to evaluate your needs, and use case and then see what we plan about that.