storm icon indicating copy to clipboard operation
storm copied to clipboard

added storm wiki frontend with themes

Open jaigouk opened this issue 1 year ago • 1 comments

why

  • wish to choose dark / light themes
  • sometimes, search engine may not return results. and there are search engines that are specialised for a research case. I want to be able to choose them before I send request.
  • ollama also can fail. So I want to have an option to "fallback" and continue.

changes

  • themes: dracula soft dark color and other light and dark themes
  • engines: duckduckgo, searxng and arxiv
  • llm: ollama, anthropic
  • users can change search engine before triggering search
  • users can save primary and fallback llm in settings
  • save result files as '*.md'
  • add date to to top of the result file
  • added arize-phoenix to trace.
  • added github ci file to test fallback options for search and llm
  • change number of display columns
  • pagination in sidebar

note

because this frontend is using "fallbacks", I thought it would be better to have separate example instead of overwriting the existing demo_light.

screenshots

storm-wiki-dark-theme-setting storm-wiki-dark-llm-setting
storm-wiki-dark-search-setting storm-wiki-dark-article-new
storm-wiki-dark-article-list storm-wiki-dark-create

dark and light theme

storm-wiki-dark-article storm-wiki-solarized-article

jaigouk avatar Aug 02 '24 07:08 jaigouk

once we have more llms and search engines in lm.py and rm.py, I will update the code to dapt to the changes

jaigouk avatar Aug 02 '24 11:08 jaigouk

i guess my PR is not valid because it is not one of following cases.

Pull requests for additional language model support to knowledge_storm/lm.py.
Pull requests for additional retrieval model/search engine support to knowledge_storm/rm.py.
Pull requests for new features to frontend/demo_light to assist other developers.

renamed the folder name to demo_light.

jaigouk avatar Aug 03 '24 03:08 jaigouk

@shaoyijia when you have time, could you check the rules that are saved in the official repository? it seems there some rules and my PR is violating some rules.

jaigouk avatar Aug 04 '24 18:08 jaigouk

@jaigouk we have no GitHub actions / rules to auto close PRs configured for this repo.

Yucheng-Jiang avatar Aug 04 '24 19:08 Yucheng-Jiang

Could you open this PR again? I have time today to work on merging it, though I don't have clue why it's automatically closed.

shaoyijia avatar Aug 04 '24 22:08 shaoyijia

@shaoyijia @Yucheng-Jiang I guess this is from my side. I mirrored github storm repo with my gitea instance. I will clean things up and open up a PR again in the weekend. sorry for bothering you with this. current changes include "category". https://github.com/jaigouk/storm_wiki because i wanted to group articles in a folder.

Screenshot 2024-08-05 at 17 49 42

Screenshot 2024-08-05 at 17 48 59

Screenshot 2024-08-05 at 17 49 28

Screenshot 2024-08-05 at 17 55 20

jaigouk avatar Aug 05 '24 15:08 jaigouk

Glad you figured it out. No worries and thanks for helping with this enhancement!

On Mon, Aug 5, 2024 at 8:38 AM Jaigouk Kim @.***> wrote:

@shaoyijia https://github.com/shaoyijia @Yucheng-Jiang https://github.com/Yucheng-Jiang I guess this is from my side. I mirrored my storm repo from my gitea instance. I will clean things up and open up a PR again in the weekend. sorry for bothering you with this. current changes include "category" concept. https://github.com/jaigouk/storm_wiki because i wanted to group articles in a folder.

— Reply to this email directly, view it on GitHub https://github.com/stanford-oval/storm/pull/123#issuecomment-2269366593, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQAMA2TPBYCHK2BTJHDEXI3ZP6L6BAVCNFSM6AAAAABL37KPXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRZGM3DMNJZGM . You are receiving this because you were mentioned.Message ID: @.***>

shaoyijia avatar Aug 05 '24 16:08 shaoyijia