Andrey Sitnik

localfirstnews

For contributing to upcoming newsletter issues.

4
0
4
public
Forked
View on GitHubWebsite

local-first-news-favicon

Local-First News

Local-First News was created as an open-contribution newsletter that makes it easy to stay on top of the rapidly-changing local-first software landscape.

Contributing

Anyone can contribute to the latest edition of Local-First News by creating a pull request with suggested edits to the markdown file for that week’s edition.

Guidelines

  • Newsletters are sent out on Thursdays at 12:00pm Eastern Time
    • Pull requests with contributions for that week’s edition can be made up to 10:00am Eastern Time on that Thursday.
  • Newsletter content will generally be limited to items released or published in the 7 days prior to that Thursday.
  • All contributions should be written in markdown.

There are three sections in each edition:

  1. News & Discussions
  2. Tools & Resources
  3. Apps

📰 News & Discussions section

This section is to surface:

  • Local-first focused events that happened or were announced in the last week, or will happen in the following week.
  • Articles/posts about local-first development published in the last week.
  • Discussions on public forums about interesting local-first issues that took place in the last week.

Contributions should use the following format:

### [Title](http://www.example.com)
Story or discussion summary.
  • Titles should descriptive and to the point.
  • Links should be to a publicly-accesible original source.
  • Story or discussion summaries should provide additional detail that would help readers decide if they want to read more.

Examples:

News — event:

### [Local-First Conf held in Berlin](https://www.localfirstconf.com/)
The first-ever developer conference dedicated to local-first software took place in Berlin on May 30th, with a tech expo day held on May 31st.

News — article:

### [Linear engineer shares how they scaled their sync engine](https://linear.app/blog/scaling-the-linear-sync-engine)
Tuomas Artman explains how Linear's real-time sync engine works with their application today.

Discussion:

### [The arbitrage opportunity for local-first in B2B SaaS](https://x.com/emerywells/status/1813265037454451039)
Twitter/X thread started by @emerywells on how apps with faster UI could dominate B2B markets.

🛠️ Tools & Resources section

This section is to surface:

  • New tools related to local-first development released in the last week.
  • Significant updates to existing tools released in the last week.
  • Useful resources made available in the last week.

Contributions should use the following format:

### [Tool name [optional: version number] or Resource title](https://www.example.com)
Tool or resource summary.
  • Tool names should be used as is. Include a version number if possible.
  • Links should be to the tool’s website, repo or changelog; or to the webpage where the resource is available.
  • Summaries should be descriptive and to the point.

Examples:

Tool:

### [TinyBase v5.1](https://tinybase.org/guides/releases/#v5-1)
TinyBase, a "reactive data store for local-first apps", adds server sync capabilities in this release.

Resource:

### [Architectures for Central Server Collaboration](https://mattweidner.com/2024/06/04/server-architectures.html)
Matthew Weidner models architectural techniques that can be used to create real-time collaborative apps using a central server.

👾 Apps section

This section is to surface apps built with a local-first approach. A wider discretion is applied regarding the app’s release date being in the prior week. Apps are likely to be includeed if they:

  • were released relatively recently
  • are not well-known
  • haven’t been featured in the newsletter before

Contributions should use the following format:

### [App name](http://www.example.com)
App summary.

[optional: _Technology used_]
  • App names should be used as is.
  • Links should be to the app’s website or GitHub page.
  • App summaries should be descriptive.
  • Optionally include technology used, with a focus on the local-first parts of their stack.

Example:

### [Fig](https://figwealth.io/)
Wealth planning tool for freelancers.

_Using PowerSync as sync engine._

Editorial discretion

Our objective is to accept submissions as-is. However, submissions may be edited to adhere to the above guidelines, and for length. Guidelines may be applied more stringently in weeks with a high number of submissions. Reasons for edits will be shared on pull requests.

@phillvdm and @cahofmeyr currently comprise the editorial team and can be reached on this repo or at hello@localfirstnews.com.

Community

New to local-first? The Local-First Software community is a great place to learn.

Sponsorship

This newsletter is currently sponsored by PowerSync

v0.3.3[beta]