I made some proposals on the mission statement.

Sounds in general all very good.

I know it's not your style, Nicolas; but what do you think about using Wordpress? With f.x. this theme
and a nicely made video at the top?

I got one question? Do we want a sheet like the chicken sheet open for everybody. I am split about it. On one hand it would make participation easy for everybody. on the other hand i dont like the idea of having everything open - this is mostly because i want to be able to do things black. And the split is even more fundamental. Because i am not sure that participation will automatically will become good and easy because you have openess.
So my suggestion would be that we have to homepages. One for the public - perhaps with some visuals as to have we are doing, and what we are doing. And one for our selves that we use in day to day life.

Other than that im mostly for keeping the ambitions at a low. Not doing to much descriptions, stating to many values.
I think there should be a web shop - which would favor a sollution with wordpress - or does wikiespace have such things to?
And i definetely think there should be some kind of interaction with people who wants to be a part of the work.

For me it is very important to just have one website. I would like the following features:

1. A general description of the history and ambition of the farm: What is the story of the farm? What is our approach to sustainability? How do we see interaction with local community, foodcoops etc. What productions do we want?
2. A calendar where we can post upcomming work weekends etc.
3. A blog where we can post random pictures and share experiences etc.
4. A shared to do list where we can describe our needs to the public, so they can help us out.
5. An option to subscribe to the work team email list.

My take on public/private: There are many projects at the farm that we can be 100% public about: the apples, the renovations of the house, the juice, the wine, the animals. If there are projects or aspects of projects that we dont want to share with the public, we simply dont include it on the website. Each project must decide for itself how it wants to describe itself.

Some of this will answer comments from the doc (mark as resolved if it does).

@andreaswolf
Regarding the estimates
This is what I think a fair estimate for the MVP (without your edits). Minimal Viable Product. There will definitely be more hours if we want to go beyond that simplistic format. It's however too early to estimate that.
Also this is actual work. I usually never put estimates for technological research required since it's not a cost specific for this project. But perhaps it makes sense here since we will most probably create other websites together.
By technological research I mean the work of getting up to date with the latest state of technology, researching for the latest software . If you'd use Wordpress that could be researching last themes and plugins for example. If you do full-stack dev like I do it's mostly research for different open-source technical components I can use in the code / app architecture.

Regarding using WP

You may ask a talented smith to make a knife for you and see their eyes glow with enthusiasm. Tell them what tools they should be using and they will strip your head off.

This means I'm open to discuss technicalities of what tech stack to use again but it does take time and efforts, and I find it to be counter productive as it's mostly a matter of opinions. The most important is to have someone we can trust for doing the nerdy aspect of the product development and do it well. I think you are able to do something with Wordpress. I myself do this with a more technical stack (that I would love to initiate you to).
Please ask if you'd like me to share more on the benefits of using the tech stack I use over Wordpress. But perhaps outside of this discussion that I believe should stay high level.

@nikolajbocher
Could you expand a bit on your will to have "just one website" and what you mean by that? IMHO comms + sells from the farm should be one website, the restaurant should be another, the co-working space yet another, and we should have one more to present the whole network and link to each venture / project (like Enspiral do). Having a different website for each allows to know who we are communicating to and serve the right content accordingly. It also allows to produces much cleaner / lighter user interfaces.

I think points 2. 3. and 4. are better tackled by external applications that are already existing. Regarding calendar, I think pragmatically that the main attraction potential for events is through Facebook. It's ok to double up with linking things up from the website (through the facebook API) though this is read-only, as facebook doesn't allow 3rd party apps to add events through the API.

@nicolaswormser
"one website" was a response to @amandaruth. I would like us not to have a public and a private website for the farm. I agree with you completely that the office, the restaurant and the whole network needs different sites.

By "external applications that are already existing" do you mean that they should not be integrated into the website?