Add some solutions
This commit is contained in:
parent
7f17b07afd
commit
e6fcb9021f
|
@ -15,7 +15,7 @@ We've learned that reducing the size of tech solutions, in turn reduces their co
|
|||
|
||||
*We* are me, [Benjamin Balder Bach](https://overtag.dk/), and any freelance friends that I work with in this new setting.
|
||||
|
||||
## Values and methods {{< icon "bulb" >}}
|
||||
## Values and methods {{< icon "bulb" >}}{#methods}
|
||||
|
||||
Here are the most important methods and principles that we work with:
|
||||
|
||||
|
|
|
@ -2,10 +2,46 @@
|
|||
title: "Solutions"
|
||||
---
|
||||
|
||||
## From idea to product
|
||||
|
||||
We solve problems and build solutions using our [Values and Methods]({{< ref "/#methods" >}}).
|
||||
|
||||
Whatever we build, we use rapid methods. We want to spend your time and your users' time to gather feedback and continuously iterate on the product until everyone is happy.
|
||||
|
||||
## Ongoing projects
|
||||
|
||||
We are currently working with others on a number of projects:
|
||||
|
||||
## GovStack Consent Building Block
|
||||
### Zetkin App
|
||||
|
||||
## Zetkin Foundation
|
||||
Building new prototypes and comparive studies for Python API backend design.
|
||||
|
||||
## django-consent
|
||||
https://zetkin.org/
|
||||
|
||||
### django-consent
|
||||
|
||||
> (...) Ideally, we should step back from our immediate short-term development issues and imagine how we would want our own data to be handled. By assuming the real user's perspective, we can identify better models and solutions for consent management where the management part is seen as the user's ability to manage their own consent.
|
||||
|
||||
https://github.com/django-denmark/django-consent
|
||||
|
||||
### WIP: "ilovedocs"
|
||||
|
||||
> Ilovedocs is an experiment to dream up a new documentation language and framework. It's a fresh take on documentation, based on experiences from other frameworks.
|
||||
>
|
||||
> With Ilovedocs, we can address shortcomings of popular documentation frameworks by borrowing successful concepts and avoiding unsuccessful concepts, such as shortcomings in markup language and bundled features. We do this by open sourcing the "software specification" or "design docs" for what we want, before someone will hopefully go and build it.
|
||||
|
||||
## Previous projects
|
||||
|
||||
### Digitala Ombudsvalet (Zetkin Foundation)
|
||||
|
||||
16 Swedish districts voted in a digital election made possible by a voting system tailored to 1) increase awareness among political party members to their party candidates and their politics, 2) increase voter participation, 3) be a trust-worthy voting system, tamper-proof etc. We designed new features for the system and worked hand-in-hand with election organizers and committees throughout the election and until the final results were in.
|
||||
|
||||
### GovStack Consent Building Block
|
||||
|
||||
We participated in GovStack's Consent Building Block by facilitating the technical tools to move quickly from architectural decisions to OpenAPI spec and to a CRUD-based reference implementation. We build CI and consulted on API endpoint and data models.
|
||||
|
||||
> The Consent Building Block enables services for individuals to approve the use of their Personal Data by defining the principles, functions, and architecture of an information system. For organisations that process Personal Data, it provides the ability to know the individual's will and legitimately process such Personal Data.
|
||||
|
||||
https://govstack.gitbook.io/bb-consent
|
||||
|
||||
[More...](https://overtag.dk/v2/projects/)
|
||||
|
|
|
@ -24,3 +24,9 @@ a {
|
|||
color: #00e;
|
||||
text-decoration: none;
|
||||
}
|
||||
|
||||
blockquote {
|
||||
color: #444;
|
||||
border-left: 4px solid #aaa;
|
||||
padding-left: 10px;
|
||||
}
|
Loading…
Reference in a new issue