The Helix PACT is:
- Product Experience
#p - Architecture & Technology
#a - Culture & Team
#c - Tools of the trade
#t
We will work as meritocracy, input from others, and reviewing PRs and contributing to other projects is a top priority.
If we don't have a good reason why something should be private, it should be public. All new repos, live on public github.
We are a diverse team in every respect.
Get-togethers and hackathons only.
Code wins. Everybody codes. Commits.
Well designed, beautiful output.
In that order.
Always.
As global as the web with regards to languages, delivery, and performance
Things are fast. <300ms fast. always.
Everything is a resource, every change an event.
Everything has an API, REST of course.
period.
The software is secondary, what we build is a service
Discussions and decisions are open, asynchronous and archived.
Results of commits can be seen in a production environment in 60 seconds or less.
Consumer-grade quality can't allow false (non-viable) MVPs
Listen closely to customer and user feedback. Measure qualitatively and quantitatively.
Whether he wants it or not, the dictator has the last word on product and architecture
If we don’t make a wrong decision once in six months, we are not ambitious enough. (Or self-critical)
The goal of the service is not to deliver features, but to get jobs done for our users and customers.
Use behance and other marketplaces to source content, design, and apps.
URI, CSS, Client Code, Server Code.
JavaScript → Native Client Code, Server Code.
Start with spark authoring experience.
See what others do right now in authoring.
Enter your domain name, import, done.
Run your site with content variants, code variants, or configuration variants at any time
On the server-side JavaScript and Python are used for the respectively intuitive payloads.
Native.
Anything that smells like a structured document by default stored in markdown in github
Simple formatting, powerful expressions.
Output is assembled on request.
Make maximum use of available services.
Create content, compose content, transform content, deliver content
Are King.
Less code is better. Actively manage the dependency graph to an absolute minimum.
a.k.a. polished, but tweakable.
Content must not contain display logic. Display logic must not contain content. Binary content should be re-renderable.
Support for simple local development is imperative. Low entry barrier.
Power content, workflows, designs, and operations.
Is where we document big decisions and trade-offs.
We communicate ideas through writing and status through issue trackers and automated dashboards
All Markdown documents should read well and logically when viewed through Github's view interface.
Let's design interfaces that are bold now, we can go back to safe and boring later on.