Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENHANCEMENT] update readme to explain what parts are "legacy" #884

Closed
Pomax opened this issue Dec 18, 2023 · 2 comments
Closed

[ENHANCEMENT] update readme to explain what parts are "legacy" #884

Pomax opened this issue Dec 18, 2023 · 2 comments

Comments

@Pomax
Copy link

Pomax commented Dec 18, 2023

Description

The readme currently says "This repository houses the JavaScript SDK for use with Optimizely Feature Experimentation and Optimizely Full Stack (legacy)." but going to the docs over on https://docs.developers.optimizely.com/feature-experimentation/docs/javascript-node-sdk makes it seem pretty clear that this is not a legacy project at all, but the only way to officially do Node based server side optimizely work.

It would be great to explicitly open with what use cases are considered legacy, and what their current counterparts are, before diving into the real README.md

Benefits

clarity in docs.

Detail

No response

Examples

No response

Risks/Downsides

No response

@Pomax Pomax changed the title [ENHANCEMENT] update readme to explain _what_ is legacy [ENHANCEMENT] update readme to explain what parts are "legacy" Dec 18, 2023
@raju-opti
Copy link
Contributor

Hello @Pomax , actually what is intended is the "Optimizely Full Stack" product is legacy, and "Optimizely Feature Experimentation" is the latest version of the "full stack" experimentation product. . It is not intended to mean that this project itself is legacy. We will look to improve the readme to reflect this. Thanks for bringing this up.

@mikechu-optimizely
Copy link
Contributor

Thanks for the 👍. Closing...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants