![]() Is there any "Best practice" you could recommend to allow for a low-cost development of our Design into a scalable infrastructure that doesn't cost thousands a month for hosting etc. As well as "Save for later" and other functionalities that help better interaction with contentĪs we are overwhelmed with the choices it is really hard to determine what technology stack/choices we should make in order to keep it as lean and easy as possible without creating too much overhead. ![]() Create collections (collections of articles) and share them.Follow Creators, Subscribe to Authors/Organizations.Collaboration and live collaboration (like Google Docs).Translation flows and integration of machine translation suggestion.Peer-Review Feedback and Translation Feedback.Better Author / Organization / Publication pages.Some of the new functionalities we thought of to make consuming/sharing knowledge easier: The next generation of our knowledge-sharing platform should also have more functionalities as the current version is only an article publishing platform. Next.js came up often as a possible solution for our future "platform" but I am not sure, also I found Payload CMS in the process as WordPress seems to be not the right decision for us. We have now almost finalized the UI/UX Design in Figma with all the flows and functionalities for the future platform. We are an NGO and we got from a partner a new design for our knowledge-sharing platform.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |