Day 2 of the 100 D-Days Challenge
- Glossary document is updated with definitions for tens of various terms commonly used in UNA-verse.
- The How UNA Works document now has a brief overview video demonstrating the main UNA CMS concepts
- 41
Day 1 of the 100 D-Days Challenge
Introduction page of UNA Documentation is updated with a general description of UNA CMS, detailed explanation of what we mean by CMS and why one should choose UNA.
A new How UNA Works page added with brief overview of UNA functionality, what we mean by Context and Content modules, brief overview of the Core Apps in Studio and a few words on deployment. A video overview for this page coming tomorrow.
Today, we are starting a 100-day challenge to update and expand UNA CMS documentation. This is an open challenge for us. We are committed to completing it, and we ask you, the UNA community, to hold us accountable.
Why?
- UNA Documentation is poor. It’s outdated and very limited. We need to make it exceptional. Not just OK, or good… it should be amazing.
- We are tuning an AI model to provide support for UNA operators and developers. A good model requires up-to-date reference data.
- As we work on the Docs, we test everything thoroughly. In 100 days, we should have a stable release of UNA 14 ready, and this time around, it must be very well-tested.
- With community involvement, we will be able to not just write docs, but identify problems and work out new solutions.
Rules
- Every day of the next 100 days, including weekends, we will publish or update at least one new Docs page. On good days, we may be able to do more than one.
- Every day, we will start a discussion related to the published Doc and invite the community to suggest edits, ask questions, critique, and share opinions on the subject.
- Before publishing any new page, we will incorporate all relevant and useful updates posted in discussions into previously published docs.
If you have recommendations for specific pages that need updating, or requests for docs on any specific topic, please post in replies to this discussion.
It’s ON!
In UNA 13.1 we are focusing on improving general user experience, server performance and expanding UNA core API for the upcoming release of the new React/ReactNative frontend app.
System Enhancements:
- Extended core and module API - #4148
The API is extended significantly, providing new endpoints to securely share date with external apps. Over 250 commits dedicated to the API alone, covering everything from core settings, authentication and modules to design, navigation and languages.
- PUSH/Sockets server integration #4369
The new WebSockets server based on https://soketi.app providing highly performant (under 100ms) message delivery for web socket events. For example in UNA+NEO pairing we use it to update reaction counts in the feed without reloading the page or polling the server. In the Messenger we use it to exchange messages at scale.
- Service worker & site manifest file settings #4480
Improved site manifest and caching mechanism enabling shipping UNA as a Progressive Web App.
- Icons for info fields in profile #4389
Support for customisable icons for profile info fields.
- Connections page #4365
The new Connections section with Friends Suggestions, Friends, Friend Requests, Requested Friendship, Who to follow, Followers and Following pages. Actions in cards for each section adapted to the context of the page.
- Comments: partially hide long comments #4471
- Counters in connection menu items #4550
- New setting: to change number of results in profiles search auto-suggestion #4537
- New setting: viewport metatag value setting in Developer module #4383
- New setting: number of results count in Live search #4359
- Meta title in Pages builder separately from page heading #4548
- Custom placeholder text for empty blocks instead of the default 'Empty' string #4370
- Custom cover title #4407
- “Updates” tab in Apps Market in Studio now requires authorization #4464
- Developer debug mode in header.inc.php #4544
- Forms: check for unsubmitted data before leaving the page #4442 #4518
- New placeholder images for different file types #4398
- Quill editor: clear copy&pasted content from HTML #4349
- member.php (and other pages with login form) now using "/login" page layout #4381
- ACL: Use lang key for Price field #4347
- New UNA badge in bottom menu #4379
- Removed '#dpr' from URL when site is initially loaded on retina screen #4382
- Menus: Allow to filter out items depending on context #4340
- Iframely API #4335
Modules Enhancements:
- Accounts: export account language #4552
- Timeline: New 'Copy to clipboard' item in share menu #4536
- Timeline: labels field support #4469
- Timeline: block form submit while media is uploading #4447
- Timeline: show content with specific media types (audio, video, photo) #4422
- Timeline: allow to change visibility while editing timeline update #4411
- Timeline: new 'For you' feed with mixed Account + Hot feed content #4384
- Timeline: performance optimization #4367
- Market: Separate pages for each category #4492
- Notifications: default notification lifetime set ti 3 months with daily pruning #4541
- Notifications: subjects of email notifications are more descriptive now #4432
- Groups & Events: "Followed" page #4488
- Invitations: various enhancements #4543
- Tasks: profile icons in tasks list #4463
- Developer: Export/import for builders and settings states #4515
📦 The 31.1 package, update script, cumulative update script and the Spacenook Starter Kit are available for download at https://github.com/unaio/una/releases/tag/13.1.0
Testing and benchmarking UNA+NEO setup against most popular competing or comparable platforms now. Some are terrible, some are average and there are a few pretty good ones. We will beat every one of them, anyway.
Starting from UNA 13.1 you can create a page with Groups Feed - the timeline of all posts from groups followed by user. In this tutorial you can see how to make a new page with Groups Feed block, activate submenu, add a link and modify a link in main navigation.
The 13.1 update is imminent, and along with the framework changes we are preparing some platform changes, too. I'll elaborate on specifics in the next few days, but for now I'd like to discuss one question....
We think about making all UNA Pro Apps free to download and use, with a Pro plan (or payment for individual app) required only to enable auto-updates.
While it may not sound like anything controversial (who doesn't like free stuff!?), I think there may be a case for thinking that we aim to "trap" people into using an app and then having to pay to update. That's not the intention, however I can see how it may be interpreted that way. We should make sure to communicate that auto-updates are not free beforehand, naturally, but beyond that what do you think we should or shouldn't do to introduce this change? What would work best for you?
Our goal is to get more people to try whichever apps they want and get started with minimal constrains.
The 13.1 update is imminent, and along with the framework changes we are preparing some platform changes, too. I'll elaborate on specifics in the next few days, but for now I'd like to discuss one question....
We think about making all UNA Pro Apps free to download and use, with a Pro plan (or payment for individual app) required only to enable auto-updates.
While it may not sound like anything controversial (who doesn't like free stuff!?), I think there may be a case for thinking that we aim to "trap" people into using an app and then having to pay to update. That's not the intention, however I can see how it may be interpreted that way. We should make sure to communicate that auto-updates are not free beforehand, naturally, but beyond that what do you think we should or shouldn't do to introduce this change? What would work best for you?
Our goal is to get more people to try whichever apps they want and get started with minimal constrains.