Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/imsky/awesome-manifestos

:pushpin: Interesting tech-related manifestos
https://github.com/imsky/awesome-manifestos

List: awesome-manifestos

awesome hacktoberfest

Last synced: 2 months ago
JSON representation

:pushpin: Interesting tech-related manifestos

Awesome Lists containing this project

README 

        
# 📌 Awesome Manifestos



[![Awesome](https://awesome.re/badge-flat2.svg)](https://awesome.re) [![Tweet](https://img.shields.io/twitter/url/http/shields.io.svg?style=social)](https://twitter.com/intent/tweet?url=https%3A%2F%2Fgithub.com%2Fimsky%2Fawesome-manifestos&via=imskyco&text=Awesome%20Software%20Manifestos)



**A collection of awesome manifestos.**



**[Ten Principles for Good Design](https://tenprinciples.design)** by Dieter Rams


  > Good design is as little design as possible



**[Choose Boring Technology](http://boringtechnology.club/)** by [Dan McKinley](https://mcfunley.com/)


  > We should generally pick the smallest set of tech that covers our problem domain, and lets us get the job done.



**[This Page is Designed to Last](https://jeffhuang.com/designed_to_last/)** by [Jeff Huang](https://jeffhuang.com/)


  > How do we make web content that can last and be maintained for at least 10 years?



**[Calm Technology](https://calmtech.com/)** by [Amber Case](https://www.caseorganic.com/)


  > How many are notifications are necessary? How and when should they be displayed?



**[Keep a Changelog](https://keepachangelog.com)** by [Olivier Lacan](https://olivierlacan.com/)


  > Changelogs are for humans, not machines.



**[The Twelve-Factor App](https://12factor.net/)** by [Adam Wiggins](https://adamwiggins.com/)


  > This document synthesizes all of our experience and observations on a wide variety of software-as-a-service apps in the wild.



**[The Rails Doctrine](https://rubyonrails.org/doctrine/)** by [David Heinemeier Hansson](https://dhh.dk/)


  > The chief accomplishment of Rails was to unite and cultivate a strong tribe around a wide set of heretical thoughts about the nature of programming and programmers.



**[HTML First](https://html-first.com/)** by [Tony Ennis](https://www.tonyennis.com/)


  > The main goal of HTML First is to substantially widen the pool of people who can work on web software codebases.



**[The NoJS Club](https://nojs.club/)** by [Karan Goel](https://goel.io/)


  > Not all websites need Javascript to be beautiful and usable.



**[NoYAML](https://noyaml.com/)** by [Geoffrey Huntley](https://ghuntley.com/)


  > Anyone who uses YAML long enough will eventually get burned



**[Immutable Web Apps](https://immutablewebapps.org/)** by [Gene Connolly](https://twitter.com/geneconnolly)


  > Immutable Web Applications are generated once and published once to a permanent location.



**[Local-first software](https://www.inkandswitch.com/local-first/)** by [Kleppmann](https://martin.kleppmann.com/), [Wiggins](https://adamwiggins.com/), [van Hardenberg](https://twitter.com/pvh), and [McGranaghan](https://markmcgranaghan.com/)


  > Cloud services defy long-term preservation. No Wayback Machine can restore a sunsetted web application.



**[Frameworkless movement](https://www.frameworklessmovement.org/)** by [Francesco Strazzullo](https://www.francescostrazzullo.info/)


  > Every time a team uses a framework, it also takes a risk.



**[Always Own Your Platform](http://www.alwaysownyourplatform.com/)** by [Sean Blanda](https://www.seanblanda.com/)


  > Stop giving away your work to people who don't care about it. Host it yourself. Distribute it via methods you control. Build your audience deliberately and on your own terms.



**[Publish on your Own Site, Syndicate Elsewhere (POSSE)](https://indieweb.org/POSSE)** by [IndieWeb](https://indieweb.org)


  > POSSE is an abbreviation for Publish (on your) Own Site, Syndicate Elsewhere, the practice of posting content on your own site first, then publishing copies or sharing links to third parties (like social media silos) with original post links to provide viewers a path to directly interacting with your content.



**[Functional Web App](https://fwa.dev/)** by LeRoux and Block


  > Functional Web App (FWA)...empowers developers with the flexibility of dynamic, full-stack applications paired with the ease of scaling a static website.



**[Against software development](http://www.rntz.net/post/against-software-development.html)** by [Michael Arntzenius](http://www.rntz.net/)


  > These days, for better or worse, software defines everyone's reality. Let's build one worth living in.



**[Trunk Based Development](https://trunkbaseddevelopment.com/)** by [Paul Hammant](https://paulhammant.com/)


  > Trunk-Based Development is a key enabler of Continuous Integration and by extension Continuous Delivery.



**[The stacking workflow](https://stacking.dev/)** by [Greg Foster](https://www.gregfoster.dev/)


  > Stacking parallelizes your development and code review workstreams, so you don't need to wait for your previous changes to be merged before building on top of them.



**[Conventional Commits](https://www.conventionalcommits.org)** by [Damiano Petrungaro](https://www.damianopetrungaro.com/) and [Ben Coe](https://twitter.com/benjamincoe)


  > The Conventional Commits specification is a lightweight convention on top of commit messages.



**[System Font Stack](https://systemfontstack.com/)** by [Tom MacWright](https://macwright.com/)


  > Webfonts were great when most computers only had a handful of good fonts pre-installed.



**[Semantic Versioning](https://semver.org/)** by [Tom Preston-Werner](https://tom.preston-werner.com/)


  > Under this scheme, version numbers and the way they change convey meaning about the underlying code and what has been modified from one version to the next.



**[Calendar Versioning](https://calver.org/)** by [Mahmoud Hashemi](https://sedimental.org/)


  > CalVer is a versioning convention based on your project's release calendar, instead of arbitrary numbers.



**[The Remote Manifesto](https://about.gitlab.com/company/culture/all-remote/)** by [Darren Murph](https://twitter.com/darrenmurph)


  > We believe that a world with more all-remote companies will be a more prosperous one, with opportunity more equally distributed.



**[Principles of Chaos Engineering](https://principlesofchaos.org/)** by [Lorin Hochstein](http://lorinhochstein.org/)


  > Even when all of the individual services in a distributed system are functioning properly, the interactions between those services can cause unpredictable outcomes.



**[The Reactive Manifesto](https://www.reactivemanifesto.org/)** by [Bonér](http://jonasboner.com/), [Farley](http://www.davefarley.net/), [Kuhn](https://rolandkuhn.com/), and [Thompson](https://twitter.com/mjpt777)


  > Systems built as Reactive Systems are more flexible, loosely-coupled and scalable.



**[The Software Defined Delivery Manifesto](https://sdd-manifesto.org/)** by [Christian Dupuis](https://twitter.com/cdupuis)


  > Delivery infrastructure is now programmable, and we will program it.



**[Stop breaking the Web](https://eightsquaredsoftware.com/articles/web.html)** by [Derek Schaab](https://eightsquaredsoftware.com/articles/web.html)


  > Rather than chasing after the latest features available only to those living on the bleeding edge of browser support, we should invest in making our creations open to all, consumable by all, and welcoming to all.



## Contributing



Contributions are always welcome, feel free to open a PR!



## License



awesome-manifestos is licensed under the [MIT license](./LICENSE).