Skip to content
NEXLOCK FIELD GUIDEAbout & updates

What’s new and how the wiki stays current

See the current release information, source-backed facts and recent published change summaries.

2 min read5 sectionsStudio 1.0.0
Looking for something else?Explore all guides
In this guide1 / 5
01

Read the public update journal

Open What’s New from the website navigation at /whats-new for release highlights, improvements, fixes and announcements across Studio and Companion. Its posts and feed contain the announcements chosen by the site owner. The dedicated What’s New guide explains the filters, links and availability labels.

02

Details connected to the website

The supported-printer table, active calibration goals, single-stud values, slicer names/links and default Companion port use the same configuration as the app. Library and filament snapshot counts, Companion package details and change summaries are rebuilt from the published source data.

The software hub also checks the same-site stable Companion release feed when opened. If that refresh fails, it keeps the release verified with this website build and says the refresh was unavailable. It never guesses an external download or reports a failed connection as successful.

03

Detailed guides need reviewed changes

Step-by-step explanations are maintained alongside the feature they describe. The build verifies article references, navigation coverage, current calibration definitions and the Companion download’s integrity. Maintainers must update the relevant guide when a workflow changes.

These mechanisms keep configuration details synchronized and help catch missing documentation; they do not claim that software can automatically infer a correct guide for every future feature. The content below reflects the source included in this deployment.

04

Website and Companion releases are separate

Studio and Companion use product versions that change when a major update is announced. Companion updates use an increasing internal build number to choose the correct package even when the product version stays the same. Use the actual current values when reporting an issue.

Recent website changes

Admin operations and account entry (v1.0.0)

  • Reorganize Studio Admin into Operations, Publishing, Insights and Administration with role-aware navigation, actionable queues and a cleaner responsive dashboard.
  • Include registered self-hosted accounts in the member directory; add account-state filters and scoped security actions for administrators and moderators.
  • Delegate ordinary-member beta admissions and invitations to administrators while retaining owner control of global access policy and staff roles.
  • Add read-only system readiness and searchable, permission-scoped activity history without exposing credentials or private audit payloads.

Account pages, beta invitations and member controls (v1.0.0)

  • Center and simplify login, signup and account recovery with a consistent responsive account card over the original colorful brick-pattern background.
  • Add personal, expiring beta invite links with verified-email matching, one-time acceptance and owner revocation.
  • Add owner controls for account suspension/reactivation, signing out all devices and member-controlled recovery emails, with security history and owner lockout protection.

Nexlock accounts and login access (v1.0.0)

  • Add verified email/password signup, sign-in and recovery alongside Google, with account settings for connected login methods.
  • Preserve existing account IDs and private work; require authenticated linking and retain a working login method when disconnecting Google.
  • Add Public, Beta and Closed access modes in Studio Admin, with server-side enforcement and owner/staff access during closure.
  • Prepare SMTP configuration for verification and recovery messages; email-dependent flows remain unavailable until delivery is configured.

Dokploy deployment preparation (v1.0.0)

  • Add a production Node Docker build on port 3000, persistent SQLite and private object storage, checked forward migrations and exclusive volume ownership.
  • Add verified OpenID Connect login with protected sessions and sign-out, while ignoring hosting identity headers in self-hosted builds.
  • Prepare offline data transfer, backups and explicit account identity linking; retain beta access rules, private-record boundaries and immutable Companion downloads.
  • Document Dokploy configuration and release checks without deploying, changing product versions or publishing a journal post.

Beta readiness and account safeguards (v1.0.0)

  • Add owner-managed beta requests, approvals, revocation, cohorts, welcome instructions and known issues, with server-side admission checks.
  • Separate new legacy records and browser drafts by account while preserving the original shared archive for owner review.
  • Add private-upload quotas, abandoned-upload cleanup and account export/deletion request tracking.
  • Prepare website CI, dependency health checks, backup/restore rehearsal, approved-source rollback guidance and a full supported-configuration acceptance register.

Code maintenance and performance (v1.0.0)

  • Reuse current Designer geometry for appearance and print-process edits, while preserving fit validation, explicit retries, cancellation and safe source reselection.
  • Reduce admin settings reads and share landing-page settings during each server render without retaining stale publications across requests.
  • Repair legacy request size/error handling and part-result filtering so newer records for other parts cannot hide matching results.
  • Remove unreachable library rendering and the obsolete installer; add a pinned Windows-compatible setup command, ordered standalone checks and regression coverage.

Prepared for the current Nexlock workflow. Source review dates and data snapshots retain their own context; a digital check does not certify a physical print.