-
Notifications
You must be signed in to change notification settings - Fork 20
Description
@kidfribble and I met this weekend and discussed how to structure the new offlinefirst.org website. This is a long time coming, and I still owe you all a blog post based on the discussions we had in our first two Offline Camps (sorry @terichadbourne! Did not forget!). Our main goal is to make offlinefirst.org more collaborative, more owned by its community. We want to make it simpler to contribute to. At the same time, we want to keep it small and use it more like hub that references all the great projects from within and outside our community.
I will update this issue’s description based on @kidfribble and everyone else’s feedback
Structure
- welcome
- process
- resources
- news
- events
- contribute
Pages
Welcome
Shorter introduction followed by content excerpts from the other sections, to give it more of an page overview feel
Process
Offline First is an approach / design process. You start with the most constraint environment first etc etc. We were thinking to turn our process and best practices into a little guide, something like Dockyard’s Design Sprints guide. This will be well written, concise and always up-to-date.
Resources
Basically an awesome offline-first list. With sub categories like tools, technologies, tutorials, design patterns, case studies, bussines cases, etc.
news
In addition to what we have today we suggest to post links to interesting news all over the internet as they occur. We will of course keep our newsletter and keep links to past issues.
contribute
Here is where we want to describe how people can contribute to the Open Source movement. Not only by contributing to the website, but by giving talks themselves, organising meetups and events, sharing their Open Source code, etc.