You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the user story?
Users who visit our www.citizenos.com website see the "Use platform" button. They might scroll a little up and down on the landing page, but without further investigation on what the platform is about, they are searching this information from the platform (this User behavior came out from the website user-interviews). That is why we have discussed and decided to publish product call-to-action and USP info on the website and move Product info (features, decision-making life cycle, demo videos, help center (??) etc) on the front page of the platform.
For that we need beautiful design from @kevincrepin where it could sit there.
What is the requested feature?
Before creating product info page on the platform, there are some questions and a food for thought regarding that:
There should be a section on the front page for that (not logged-in view) -- something that is easily findable and catchy. Clicking on the "Learn more about the platform" or something like that, it should open separate page (but where? On the website?). This page should give an overview about WHAT one can do in COS and HOW.
In logged-in view it can be little bit more hidden, as Users who already create an account, should know more about COS (that´s an assumption -- I don´t have any evidence for that!). BUT there should be still an option to go and read about what is possible to do on our platform and how. One place where to put it is on the left menu:
Additional information.
Please share your thoughts and ideas about how to solve it. Very much appreciated!
The text was updated successfully, but these errors were encountered:
@anettlinno I have to put up a BIG warning here, our platform is not made to be as a CMS so it is not very dynamic and easy to create sub-pages with a lot of text content. I'd rather think that depending on the content that should go there we could have similar integration like we have with our help-center, using iframes or some other methods to share the data between sites.
I suggest we discuss it before we get @kevincrepin to design the solution
@ilmartyrk thank you for the warning and I agree that if the current HC solution is the best one (HC content is located on the website) then we could do the same with the Product info page as well. In that case we would need three separate designs:
Product info on the log-out view on the platform. There could be one chunk that is dedicated for that information
Product info on the log-in view on the platform
Product info on the website which is separate from the "Product" page info (as the idea is that on the website we have call-to-action info and on the platform we have "how to use" info)
@oksks and @MeelikaH are already designing website´s Product page info and this could be launched separately from the Product page info on the platform. I agree that product info on the platform needs further discussion and brainstorming.
What is the user story?
Users who visit our www.citizenos.com website see the "Use platform" button. They might scroll a little up and down on the landing page, but without further investigation on what the platform is about, they are searching this information from the platform (this User behavior came out from the website user-interviews). That is why we have discussed and decided to publish product call-to-action and USP info on the website and move Product info (features, decision-making life cycle, demo videos, help center (??) etc) on the front page of the platform.
For that we need beautiful design from @kevincrepin where it could sit there.
What is the requested feature?
Before creating product info page on the platform, there are some questions and a food for thought regarding that:
Additional information.
Please share your thoughts and ideas about how to solve it. Very much appreciated!
The text was updated successfully, but these errors were encountered: