Files
0xbathangandJulesFILIOT 26630f3486 chore: rebrand Vac to Logos Research & update docusaurus-preset
* Update index.md

removed vac for logos research

* Update community.mdx

removing vac mentions

* Update contribute.md

minor style fixes

* Update principles.md

removing vac

* Update research.md

remove vac mentions

* Update rfcprocess.md

remove vac references

* Update rln.md

changed waku references to Logos Messaging - someone with more tech knowledge should check if accurate and examples are still relevant

unified language (mix of US and UK English used before)

* Update rln.md

updated style and changed "logos messaging" to "logos"

* Update security.md

removed vac references

* Update vips.md

changed nescience and vac references

* Update vsus.md

changed out vac references and reworded some things

* Update vsus.md

* Update vsus.md

* chore:  replace Vac references by Logos Research

Replace remaining references of Vac by Logos Research.

* chore: replace visible refs of rfc.vac.dev by lip.logos.co

* chore: update twitter links

* fix: pin docusaurus packages versions

* chore: use theme aware logo

* chore: bump `logos-docusaurus-preset` -- updates assets/metadata

New version of the `@acid-info/logos-docusaurus-preset` package updates the following:
- title/tagline/URL rebranded to "Logos Research" (research.logos.co); navbar logo gains srcDark for theme-aware switching (black in light mode, off-white in dark mode)
- all SVGs/ICO replaced with Logos lambda mark; off-white variants for dark contexts

* chore(/principles): update link top status.app principles

* chore: bump `@acid-info/logos-docusaurus-preset` package version

* chore: bump `@acid-info/logos-docusaurus-preset` package version

* chore: bump `@acid-info/logos-docusaurus-preset` package version

---------

Co-authored-by: JulesFILIOT <dev@julesfiliot.com>
2026-05-08 16:39:45 +09:00

5.9 KiB

hide_table_of_contents
hide_table_of_contents
true

Contribute

How to contribute

Get in touch with us by joining our Discord, opening a thread in our forum, or opening issues / PRs on GitHub.

Also, see our current job openings.

What to contribute

We are interested in both research and code contributions.

For code contributions, see our "good first issue" lists for various Vac-related code bases: