H&D website v2 - Revision history

Karl at 17:01, 7 April 2022

2022-04-07T17:01:28Z

← Older revision		Revision as of 19:01, 7 April 2022
Line 99:		Line 99:
	\|-		\|-
	! March 2022		! March 2022
	\| backend work continues, front-end, design work starts		\| backend work continues, front-end, design work starts, expert session 1
	\|-		\|-
	! May 2022		! May 2022
	\| translations of essential texts and meta-texts		\| translations of essential texts and meta-texts, expert sessions 2 and 3
	\|-		\|-
	! June 2022		! June 2022
Line 111:		Line 111:
	\|-		\|-
	! August 2022		! August 2022
	\| ~~accessibility~~ audit ~~of new website~~, implementing changes		\| expert session 4 (audit), implementing changes
	\|}		\|}

Karl at 16:44, 7 April 2022

2022-04-07T16:44:30Z

← Older revision		Revision as of 18:44, 7 April 2022
Line 48:		Line 48:
	** convert image captions from mediawiki image uploads into alt text on front-end		** convert image captions from mediawiki image uploads into alt text on front-end
	*** machine learning => suggestions?		*** machine learning => suggestions?
	** Do a web audit with a professional (Eric?)
	** Document Mediawiki (how to use) and www-v2 code (how to develop)		** Document Mediawiki (how to use) and www-v2 code (how to develop)
	** ~~We should explore more ideas but we are very limited in our thinking here; so i am leaving an empty point:~~		** Conduct multiple knowledge sessions / expert feedback with different people
	** -		** Organize meetup with these people
	* GDPR & Web Analytics		* GDPR & Web Analytics
	** We use web analytics but our readers don't know => this is illegal		** We use web analytics but our readers don't know => this is illegal
Line 127:		Line 126:
	* H&D:		* H&D:
	** André (back, front, design)		** André (back, front, design)
	** Karl (front, design, ~~accessibility~~, ~~mediawiki i18n~~)		** Karl (front, design, back, organizing)
	** (~~anyone else wanna join?~~)		** Pernilla (network, organizing with experts)
			** Anja (design)
	** One dutch-speaking member of H&D for basic meta-text translations		** One dutch-speaking member of H&D for basic meta-text translations
	* External:		* External:
	** Eric~~, Loes' colleague (for the audit)~~		** Eric Groot Kormelink
			** Vasilis van Gemert
			** -
			** -
			** -
			** -

	~~Should someone else~~ also ~~be involved from the start~~ in brainstorming points of access together? Maybe there are things we are not considering here since we are able-bodied? A friendly consultant of sorts would be nice to be able to have during this process.		The idea is to have irregular knowledge sessions / feedback with different experts. At least 5 or so. These encounters can take the form of a meeting or also in writing. These encounters could feed into or build up a forthcoming meetup.

Karl at 10:34, 19 February 2022

2022-02-19T10:34:09Z

← Older revision		Revision as of 12:34, 19 February 2022
Line 103:		Line 103:
	\|-		\|-
	! May 2022		! May 2022
	\| ~~accessibility audit of working prototype,~~ translations of essential texts and meta-texts		\| translations of essential texts and meta-texts
	\|-		\|-
	! June 2022		! June 2022
Line 110:		Line 110:
	! July 2022		! July 2022
	\| pre-summer academy (hard deadline)		\| pre-summer academy (hard deadline)
			\|-
			! August 2022
			\| accessibility audit of new website, implementing changes
	\|}		\|}

Karl at 10:19, 19 February 2022

2022-02-19T10:19:39Z

← Older revision		Revision as of 12:19, 19 February 2022
Line 100:		Line 100:
	\|-		\|-
	! March 2022		! March 2022
	\| backend work continues, front-end work starts		\| backend work continues, front-end, design work starts
	\|-		\|-
	! May 2022		! May 2022

Karl at 10:18, 19 February 2022

2022-02-19T10:18:27Z

← Older revision		Revision as of 12:18, 19 February 2022
Line 73:		Line 73:
	* implement multi-language option in the frontend and routing		* implement multi-language option in the frontend and routing
	* translating meta texts such as navigation, buttons, error messages, etc...		* translating meta texts such as navigation, buttons, error messages, etc...
			* prepare message for untranslated texts (link to email suggested changnes / translatios)

	To discuss (not yet budgeted for):		To discuss (not yet budgeted for):

Karl at 09:58, 19 February 2022

2022-02-19T09:58:20Z

← Older revision		Revision as of 11:58, 19 February 2022
Line 35:		Line 35:
	* Design and layout		* Design and layout
	** add a search function to the frontend, to query the wiki-backend		** add a search function to the frontend, to query the wiki-backend
			** add edit button
	** re-think how top navigation works, both on wiki level as well as on frontend side (see Concepts problem)		** re-think how top navigation works, both on wiki level as well as on frontend side (see Concepts problem)
	** integrate more the ''wiki bits'' (metadata) of MediaWiki into the frontend, eg show article’s last change timestamp, article’s history, if the article you are reading has been referenced in another article (within the wiki), etc; this can be put under “transparency”		** integrate more the ''wiki bits'' (metadata) of MediaWiki into the frontend, eg show article’s last change timestamp, article’s history, if the article you are reading has been referenced in another article (within the wiki), etc; this can be put under “transparency”

Karl at 09:56, 19 February 2022

2022-02-19T09:56:43Z

← Older revision		Revision as of 11:56, 19 February 2022
Line 36:		Line 36:
	** add a search function to the frontend, to query the wiki-backend		** add a search function to the frontend, to query the wiki-backend
	** re-think how top navigation works, both on wiki level as well as on frontend side (see Concepts problem)		** re-think how top navigation works, both on wiki level as well as on frontend side (see Concepts problem)
			** integrate more the ''wiki bits'' (metadata) of MediaWiki into the frontend, eg show article’s last change timestamp, article’s history, if the article you are reading has been referenced in another article (within the wiki), etc; this can be put under “transparency”
	** new design and stylesheet		** new design and stylesheet
	** text-only version		** text-only version
Line 56:		Line 57:

	To discuss (not yet budgeted for):		To discuss (not yet budgeted for):
	* integrate more the ''wiki bits'' (metadata) of MediaWiki into the frontend, eg show article’s last change timestamp, article’s history, if the article you are reading has been referenced in another article (within the wiki), etc; this can be put under “transparency”
	* explore a new solution for hosting/servinng audio and video		* explore a new solution for hosting/servinng audio and video
	* better integration to the rest of the software that H&D setup and or built in these years: etherpad, livestream, mailing-list, etc		* better integration to the rest of the software that H&D setup and or built in these years: etherpad, livestream, mailing-list, etc

Karl at 09:54, 19 February 2022

2022-02-19T09:54:47Z

← Older revision		Revision as of 11:54, 19 February 2022
Line 52:		Line 52:
	* GDPR & Web Analytics		* GDPR & Web Analytics
	** We use web analytics but our readers don't know => this is illegal		** We use web analytics but our readers don't know => this is illegal
			** "This website collects user data about page visits so that H&D is able to make reports to its funders"

Karl at 09:42, 19 February 2022

2022-02-19T09:42:11Z

← Older revision		Revision as of 11:42, 19 February 2022
Line 32:		Line 32:
	** server side rendering: HTML pages are rendered when they are created or edited in the wiki jnstead of on every request		** server side rendering: HTML pages are rendered when they are created or edited in the wiki jnstead of on every request
	** better error handling when something goes wrong in the wiki (eg it does not bring the frontend website completely down, as it happens now)		** better error handling when something goes wrong in the wiki (eg it does not bring the frontend website completely down, as it happens now)
	** text-only version		** text-only version / with git integration
	* Design and layout		* Design and layout
	** add a search function to the frontend, to query the wiki-backend		** add a search function to the frontend, to query the wiki-backend

Karl at 09:38, 19 February 2022

2022-02-19T09:38:16Z

← Older revision		Revision as of 11:38, 19 February 2022
Line 45:		Line 45:
	** remove unnecessary javascript; (navigation and for adding an image slideshow)		** remove unnecessary javascript; (navigation and for adding an image slideshow)
	** convert image captions from mediawiki image uploads into alt text on front-end		** convert image captions from mediawiki image uploads into alt text on front-end
			*** machine learning => suggestions?
	** Do a web audit with a professional (Eric?)		** Do a web audit with a professional (Eric?)
	** Document Mediawiki (how to use) and www-v2 code (how to develop)		** Document Mediawiki (how to use) and www-v2 code (how to develop)