Split requirements into target-versions

ppKrauss commented 2 years ago

As commented before, at this moment we have an ugly website, the "current version website" or "web site version 1.X". Some of its source code was at http://git.AddressForAll.org/site-v1

This git repository, and /docs requirements specification here, is about "website version 2".

Other development aspect commented before, .... is that we are organizing our time and investments in 3 moments:

Version 2.0.0 is only for test and discussions, we will publish it at http://teste.addressforall.org
Version 2.1.0 will be publish at http://addressforall.org , replacing the current website.
We have tight deadlines for that, and no special requirement about layout or performance. We need only to publish good multilingual content, and "plug to website" the first data visualization interfaces, like digital-guard/preservDataViz.
Will be a good web site for institutional content, and experimental for interfaces, APIs (microservice endpoints), downloads, etc.
Version 2.2.0 will be a "definitive replacement" of experimental parts, and can change layout (CSS). Will be the long-term, mature and stable layout and structure.
No deadline for it.

So, we can also summarize deadlines:

URGENT: to build v2.0.0 for tests!
April 2022: publish v2.1.0 as the official AddressForAll website.
... at some point in year 2022: publish v2.2.0 as the official AddressForAll website.

ppKrauss commented 2 years ago

The first package has been released as v2.0.0.
... Need minor corrections, that will close #12 and released as v2.0.1.

ppKrauss commented 2 years ago

now v2.0.1. It is a "test version", published only at http://teste2.addressforall.org/

Recapitulating

All releases at https://github.com/AddressForAll/site-v2/releases

(version 1 is the current website at the AddressForAll.org domain name)
... many month without relevant development...
v2.0.0 was the first delivery of work, day 2022-04-30;
v2.0.1 was the second delivery, yesterday (2022-07-15), and was the last evaluation-correction cycle of v2.0;
v2.0.2 will be the final delivery, scheduled for 2022-07-22;
v2.1.0 will be the new website (!), replacing the current (the v1). The v2.0.2 will receive only minor adaptations.

Observation. In this git issues the label "v2.2" is about a new website, a new work and new planning.

AddressForAll / site-v2

Split requirements into target-versions #7

Recapitulating