-
Notifications
You must be signed in to change notification settings - Fork 83
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
Please make Product Screenshots and Animations on LRDC available on Blueprints #882
Comments
hey @YoshikazuShimizu — we'll upload these into the Blueprints page after the holidays, in the meantime check this thread from the marketing slack channel for a way to get the product screenshots. |
thank you @plhnk and understood the process! |
Hey @plhnk. Many "screenshots" on lrdc are not of a specific/real product and serve as poc mockups. Should we create a new page for this type of asset or include them in a "Mockups" section on the Product Screenshot page? |
hm good point @abelhancock — what do you think would be a good way to organize these? @YoshikazuShimizu if you have ideas, please share — also if you wouldn't mind giving us some info on how you're using these, that would be helpful too! |
Bump — @YoshikazuShimizu can you please share how these are being used / shared? @abelhancock let's move forward with creating a new top-level category at the same level as Product Screenshots — per our chat let's use |
@plhnk sorry for the delay and thank you for the reminder. |
Can I help with something here @plhnk ? |
yes — please move it w/ @abelhancock ! |
Hi team,
Could you add Product Screenshots and Animations that are used on LRDC into the Blueprints?
I found lots of them are missing on blueprints, such as
https://www.liferay.com/en/solutions/intranets
https://www.liferay.com/en/solutions/headless-apis
https://www.liferay.com/en/solutions/b2b-commerce
https://www.liferay.com/en/solutions/industries/insurance
Also, if there are DXP 7.3 product screenshots, it'd be great if you could add them too.
Thank you,
Yoshi
The text was updated successfully, but these errors were encountered: