The current front page does not fulfill modern web site standards and should be redesigned. We are already using Bootstrap so something like this could be viable: https://getbootstrap.com/docs/4.4/examples/jumbotron/

Acceptance criteria

• Web site front page redesigned and taken to production

The gem we use to deploy the web site https://github.com/laurilehmijoki/s3_website is no longer maintained. Need to think about an alternative technology and migration.

The first issue seems to be the platform not getting its updates anymore. The build is failing in the apt-get update section.

See https://travis-ci.org/github/iluwatar/java-design-patterns-web

Text on the website is not aligned which create bad impact on user

In issue #18 we fixed the patterns showing up more than once, but another problem came up. Some patterns now show in the wrong language e.g. Singleton displayed in Chinese. At the moment we support showing only English versions and the other ones can be filtered out.

The instructions at https://github.com/iluwatar/java-design-patterns/wiki/07.-Working-with-the-web-site should be moved into this web site's wiki and updated.

Categories and tags of the patterns have grown organically and currently it's not as clear classification as we would want. In this issue we are going to:

• Create clear set of categories
• Create clear set of tags
• Apply these to the existing patterns
• Update user instructions how these are applied to new patterns

Issue moved from iluwatar/java-design-patterns#764

When I select desired categories and tags, read about one of provided patterns and want to return to the same filtered patterns list, I have to move back in a browser history (because the "Patterns" link in the main menu loads the page from scratch). Further, checkboxes save their states except for "categories" and "tags" chekboxes themselves and all patterns are loading, so I have to click on one of checkboxes to apply filtering.
Maybe returning to a filtered list can be simplified.

Also, how about selecting tags alter category amount indicators and vice versa, so each indicator shows a number of links you will actually see if toggle on corresponding category/tag?

We want to present the design patterns better as the current does not reach its goal of explaining how the pattern works in a simplest possible way. I'm hugely inspired by https://github.com/kamranahmedse/design-patterns-for-humans repository.

Let's do this by adding 'Explanation' section to the patterns' README.md file. For an example see http://java-design-patterns.com/patterns/bridge/.

Let's track the issue progress here with the following checklist that indicates the patterns where explanation section is already available.

[ ] abstract-document
[x] abstract-factory
[ ] acyclic-visitor
[x] adapter
[ ] aggregator-microservices
[x] ambassador
[ ] api-gateway
[ ] async-method-invocation
[ ] balking
[x] bridge
[x] builder
[ ] business-delegate
[ ] bytecode
[ ] caching
[ ] callback
[x] chain
[x] circuit-breaker
[ ] collection-pipeline
[ ] command
[x] commander
[x] composite
[ ] converter
[ ] cqrs
[ ] dao
[ ] data-bus
[ ] data-locality
[ ] data-mapper
[ ] data-transfer-object
[x] decorator
[ ] delegation
[ ] dependency-injection
[ ] dirty-flag
[ ] double-checked-locking
[ ] double-dispatch
[ ] eip-aggregator
[ ] eip-message-channel
[ ] eip-publish-subscribe
[ ] eip-splitter
[ ] eip-wire-tap
[ ] event-aggregator
[ ] event-asynchronous
[ ] event-driven-architecture
[ ] event-queue
[ ] event-sourcing
[ ] execute-around
[ ] extension-objects
[x] facade
[ ] factory-kit
[x] factory-method
[ ] faq.md
[ ] feature-toggle
[ ] fluentinterface
[ ] flux
[x] flyweight
[ ] front-controller
[ ] guarded-suspension
[ ] half-sync-half-async
[ ] hexagonal
[ ] intercepting-filter
[ ] interpreter
[ ] iterator
[ ] layers
[ ] lazy-loading
[ ] leader-election
[ ] marker
[x] master-worker-pattern
[ ] mediator
[ ] memento
[ ] model-view-controller
[ ] model-view-presenter
[ ] module
[ ] monad
[ ] monostate
[ ] multiton
[ ] mute-idiom
[ ] mutex
[ ] naked-objects
[ ] null-object
[ ] object-mother
[ ] object-pool
[ ] observer
[ ] page-object
[ ] partial-response
[ ] pipeline
[ ] poison-pill
[x] priority-queue
[ ] private-class-data
[ ] producer-consumer
[ ] promise
[ ] property
[x] prototype
[x] proxy
[ ] queue-load-leveling
[ ] reactor
[ ] reader-writer-lock
[ ] repository
[ ] resource-acquisition-is-initialization
[x] retry
[ ] semaphore
[ ] servant
[x] serverless
[ ] service-layer
[ ] service-locator
[x] singleton
[x] spatial-partition
[ ] specification
[ ] state
[ ] step-builder
[ ] strategy
[ ] template-method
[ ] thread-pool
[ ] throttling
[ ] tls
[ ] tolerant-reader
[x] trampoline
[ ] twin
[x] typeobjectpattern
[ ] unit-of-work
[ ] value-object
[ ] visitor

Jekyll front matter is used to add attributes to web pages on our web site. All the patterns have their front matter defined in README.md but description is missing from there. description is used to add HTML meta tag to the pattern's web page as can be seen here: https://github.com/iluwatar/java-design-patterns/blob/gh-pages/_includes/head.html#L8

In this task we add description front matter to all patterns so that Google finds the pages better. Let's track the progress with the following checklist.

[ ] abstract-document
[ ] abstract-factory
[ ] acyclic-visitor
[ ] adapter
[ ] aggregator-microservices
[ ] ambassador
[ ] api-gateway
[ ] async-method-invocation
[ ] balking
[ ] bridge
[ ] builder
[ ] business-delegate
[ ] bytecode
[ ] caching
[ ] callback
[ ] chain
[ ] collection-pipeline
[ ] command
[ ] commander
[ ] composite
[ ] converter
[ ] cqrs
[ ] dao
[ ] data-bus
[ ] data-locality
[ ] data-mapper
[ ] data-transfer-object
[ ] decorator
[ ] delegation
[ ] dependency-injection
[ ] dirty-flag
[ ] double-checked-locking
[ ] double-dispatch
[ ] eip-aggregator
[ ] eip-message-channel
[ ] eip-publish-subscribe
[ ] eip-splitter
[ ] eip-wire-tap
[ ] event-aggregator
[ ] event-asynchronous
[ ] event-driven-architecture
[ ] event-queue
[ ] event-sourcing
[ ] execute-around
[ ] extension-objects
[ ] facade
[ ] factory-kit
[ ] factory-method
[ ] faq.md
[ ] feature-toggle
[ ] fluentinterface
[ ] flux
[ ] flyweight
[ ] front-controller
[ ] guarded-suspension
[ ] half-sync-half-async
[ ] hexagonal
[ ] intercepting-filter
[ ] interpreter
[ ] iterator
[ ] layers
[ ] lazy-loading
[ ] leader-election
[ ] marker
[ ] master-worker-pattern
[ ] mediator
[ ] memento
[ ] model-view-controller
[ ] model-view-presenter
[ ] module
[ ] monad
[ ] monostate
[ ] multiton
[ ] mute-idiom
[ ] mutex
[ ] naked-objects
[ ] null-object
[ ] object-mother
[ ] object-pool
[ ] observer
[ ] page-object
[ ] partial-response
[ ] pipeline
[ ] poison-pill
[ ] priority-queue
[ ] private-class-data
[ ] producer-consumer
[ ] promise
[ ] property
[ ] prototype
[ ] proxy
[ ] queue-load-leveling
[ ] reactor
[ ] reader-writer-lock
[ ] repository
[ ] resource-acquisition-is-initialization
[ ] retry
[ ] semaphore
[ ] servant
[ ] serverless
[ ] service-layer
[ ] service-locator
[ ] singleton
[ ] spatial-partition
[ ] specification
[ ] state
[ ] step-builder
[ ] strategy
[ ] template-method
[ ] thread-pool
[ ] throttling
[ ] tls
[ ] tolerant-reader
[ ] trampoline
[ ] twin
[ ] typeobjectpattern
[ ] unit-of-work
[ ] value-object
[ ] visitor

Some patterns show up more than once, an example of this is the adapter and singleton pattern

Not smart enough to fix it but looking in /pages/pattern line 11 site.pages probably has a duplicate. Not sure where this is being populated.

The plan was outlined in issue #3. In this task we will implement the language selector component that switches languages on the fly on the web site.

In this task we formulate a technical plan how support for multiple languages is achieved. Based on the plan, the overall task can be subdivided into smaller pieces.

This issue is for learning purpose please ignore.

On page https://java-design-patterns.com/patterns/ some patterns like adapter and strategy are shown twice.