<commit_before># Playground for Designers

Set of pages that can be used by designers to work on design. Most of these pages are more like stubs and do not contains full functionality of the search application, they can contain just static HTML and CSS but no JavaScript functionality.

## Work Flows

There are basically two possible ways how to contribute to search web UI design.

- Make fork to your git repo, do _your thing_ and then send pull requests.
- Push changes directly to `master` branch of this project. The advantage of this approach is that automatic build will be started shortly after change push and once it is finished you could verify how the changes play out in live application. On the other hand it might require changes in some JS code as well. More on this below...

Generally, [css files][css_files] can be changes directly, however, if the change requires update of HTML (e.g. add new element, class, id, …) then keep in mind that most of the HTML is generated dynamically thus appropriate change in code is needed. In majority of the cases the HTML is generated by one of [soy templates][soy_templates], remember that once the template file is changed it needs to be compiled by [`compileClosureTemplates.sh`][compileClosureTemplates.sh] script and resulting `js` scripts (which are automatically located in [`src/main/javascript_sources/generated_templates`][generated_templates] folder) need to be pushed into GitHub repo to make sure they are propagated into our Jenkins CI build.

[css_files]: ../css
[soy_templates]: ../../../main/soy_templates
[compileClosureTemplates.sh]: ../../../../compileClosureTemplates.sh
[generated_templates]: ../../javascript_sources/generated_templates

## Available Stubs

### Search Results

Found at [search_results/index.html](./search_results/index.html).

This contains stub of the main `index.html` page with basic structure of the main HTML elements, specifically the top menu with logo, search field and filter buttons.

Then it contains element with search results and pagination. Normally, the page with search results contains ten items (if there are enough results available). In this stub there are only three items.

Note that the stub `index.html` contains links to all CSS files but many of them are commented out. This is because they do not contribute to any of the visible elements on the stub but I decided not to delete them in case you feel like exploring them as well.<commit_msg>fix link<commit_after># Playground for Designers

Set of pages that can be used by designers to work on design. Most of these pages are more like stubs and do not contains full functionality of the search application, they can contain just static HTML and CSS but no JavaScript functionality.

## Work Flows

There are basically two possible ways how to contribute to search web UI design.

- Make fork to your git repo, do _your thing_ and then send pull requests.
- Push changes directly to `master` branch of this project. The advantage of this approach is that automatic build will be started shortly after change push and once it is finished you could verify how the changes play out in live application. On the other hand it might require changes in some JS code as well. More on this below...

Generally, [css files][css_files] can be changes directly, however, if the change requires update of HTML (e.g. add new element, class, id, …) then keep in mind that most of the HTML is generated dynamically thus appropriate change in code is needed. In majority of the cases the HTML is generated by one of [soy templates][soy_templates], remember that once the template file is changed it needs to be compiled by [`compileClosureTemplates.sh`][compileClosureTemplates.sh] script and resulting `js` scripts (which are automatically located in [`src/main/javascript_sources/generated_templates`][generated_templates] folder) need to be pushed into GitHub repo to make sure they are propagated into our Jenkins CI build.

[css_files]: ../css
[soy_templates]: ../../../main/soy_templates
[compileClosureTemplates.sh]: ../../../../compileClosureTemplates.sh
[generated_templates]: ../../javascript_source/generated_templates

## Available Stubs

### Search Results

Found at [search_results/index.html](./search_results/index.html).

This contains stub of the main `index.html` page with basic structure of the main HTML elements, specifically the top menu with logo, search field and filter buttons.

Then it contains element with search results and pagination. Normally, the page with search results contains ten items (if there are enough results available). In this stub there are only three items.

Note that the stub `index.html` contains links to all CSS files but many of them are commented out. This is because they do not contribute to any of the visible elements on the stub but I decided not to delete them in case you feel like exploring them as well.
{'fraction_non_alphanumeric': 0.05841784989858012, 'fraction_numerical': 0.0, 'mean_word_length': 4.515659955257271, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1058022', 'n_tokens_mistral': 1165, 'n_tokens_neox': 1130, 'n_words': 720}