Skip to content

Commit 98278a8

Browse files
author
Tobia Di Pisa
authored
Renaming MapStore2 to MapStore in user and dev guides (#3529)
* Renaming MapStore2 to MapStore in user and dev guides * Renaming few missing occurrences * Fixing occurrence in mkdocs.yml
1 parent 805f67a commit 98278a8

34 files changed

Lines changed: 97 additions & 97 deletions

docs/developer-guide/API-usage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
# MapStore2 API usage
2-
You can include MapStore2 in your application and interact with it via its JavaScript API
1+
# MapStore API usage
2+
You can include MapStore in your application and interact with it via its JavaScript API
33

44
## How to use
55

docs/developer-guide/application-tutorial.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
Writing a new MapStore2 based application can be done following these steps:
2-
* create a new folder for the application, inside the MapStore2 directory tree (e.g. web/client/examples/myapp), and the following folder structure:
1+
Writing a new MapStore based application can be done following these steps:
2+
* create a new folder for the application, inside the MapStore directory tree (e.g. web/client/examples/myapp), and the following folder structure:
33

44
```
55
+-- myapp
@@ -219,7 +219,7 @@ module.exports = {
219219

220220
```
221221

222-
Now the application is ready, to launch it in development mode, you can use the following command (launch it from the MapStore2 main folder):
222+
Now the application is ready, to launch it in development mode, you can use the following command (launch it from the MapStore main folder):
223223

224224
```
225225
./node_modules/.bin/webpack-dev-server --config web/client/examples/myapp/webpack.config.js --progress --colors --port 8081 --content-base web/client/examples/myapp

docs/developer-guide/building-and-deploying.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ To create the final war, you have several options:
1919

2020
### Building the documentation
2121

22-
MapStore2 uses JSDoc to annotate the components, so the documentation can be automatically generated using [docma](http://onury.github.io/docma/).
22+
MapStore uses JSDoc to annotate the components, so the documentation can be automatically generated using [docma](http://onury.github.io/docma/).
2323
Please see http://usejsdoc.org/ for further information about code documentation.
2424

2525
Refer to the existing files to follow the documentation style:

docs/developer-guide/code-conventions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Code conventions
2-
In order to preserve quality, maintainability and testability when you develop in MapStore 2 you should follow the following rules and best practices.
2+
In order to preserve quality, maintainability and testability when you develop in MapStore you should follow the following rules and best practices.
33

44
# TL;DR
55
- Access to the state using state selectors

docs/developer-guide/configuration-files.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# Configuring MapStore2
1+
# Configuring MapStore
22

3-
MapStore2 (and every application developed with MapStore2) allows customization through configuration.
3+
MapStore (and every application developed with MapStore) allows customization through configuration.
44
Several configuration files (at development and / or run time) are available to configure all the different aspects of an application.
55

66
* [Application Configuration](../local-config)

docs/developer-guide/contributing-guidelines.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
Your pull request must:
44

5-
* Follow MapStore 2's coding style.
5+
* Follow MapStore's coding style.
66

77
* The new components have to be tested.
88

@@ -19,9 +19,9 @@ Your pull request must:
1919
* Be possible to merge automatically.
2020

2121

22-
### Follow MapStore 2's coding style
22+
### Follow MapStore's coding style
2323

24-
MapStore 2 follows a strict coding style, enforced by [ESLint](http://eslint.org/) rules.
24+
MapStore follows a strict coding style, enforced by [ESLint](http://eslint.org/) rules.
2525

2626
The set of used rules can be found in the [.eslintrc](https://github.com/geosolutions-it/MapStore2/blob/master/.eslintrc) file, in the root folder of the project.
2727

@@ -66,7 +66,7 @@ http://editorconfig.org/#download) site links to plugins for various editors.
6666
### Pass the integration tests run automatically by the Travis CI system
6767

6868
The integration tests contain a number of automated checks to ensure that the
69-
code follows the MapStore 2 style and does not break tests or examples. You
69+
code follows the MapStore style and does not break tests or examples. You
7070
can run the integration tests locally using the `test` target:
7171

7272
$ npm test

docs/developer-guide/custom-search-service.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Custom search service
2-
MapStore2 Searchbox uses [OpenStreetMap Nominatim](https://wiki.openstreetmap.org/wiki/Nominatim) service but you can set it up to use your own WFS service.
2+
MapStore Searchbox uses [OpenStreetMap Nominatim](https://wiki.openstreetmap.org/wiki/Nominatim) service but you can set it up to use your own WFS service.
33
The results will be fetched from every service you set, plus OSM Nominatim, and displayed in the order you specified.
44

55
## How to use

docs/developer-guide/developing-with-mapstore-2-intro.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# Developing with MapStore2
1+
# Developing with MapStore
22

3-
This section is about developing your own application using the MapStore2 framework.
3+
This section is about developing your own application using the MapStore framework.
44

55
* [Project Structure](../project-structure)
66
* [Front-end Technologies](../reactjs-and-redux-introduction)
@@ -18,11 +18,11 @@ This section is about developing your own application using the MapStore2 framew
1818

1919
## Useful references
2020

21-
If you want to create an application based on MapStore2 you can use the [Project Creation Script](project-creation-script).
21+
If you want to create an application based on MapStore you can use the [Project Creation Script](project-creation-script).
2222

23-
If you want to learn how to develop a simple MapStore2 based application you can follow the [tutorial](application-tutorial)
23+
If you want to learn how to develop a simple MapStore based application you can follow the [tutorial](application-tutorial)
2424

25-
If you want to learn how to develop a plug-in based MapStore2 based application you can follow the [plugins tutorial](../plugins-architecture#building-an-application-using-plugins)
25+
If you want to learn how to develop a plug-in based MapStore based application you can follow the [plugins tutorial](../plugins-architecture#building-an-application-using-plugins)
2626

2727
## Other references
2828

docs/developer-guide/developing.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Developing with MapStore
22

3-
Due to the dual nature of the project (Java backend and JavaScript frontend) building and developing using the MapStore 2 framework requires two distinct set of tools
3+
Due to the dual nature of the project (Java backend and JavaScript frontend) building and developing using the MapStore framework requires two distinct set of tools
44

55
* [Apache Maven](https://maven.apache.org/) for Java
66
* [NPM](https://www.npmjs.com/) for JavaScript.
@@ -9,7 +9,7 @@ A basic knowledge of both tools is required.
99

1010
# Developing and debugging the framework
1111

12-
To start developing the MapStore 2 framework you have to:
12+
To start developing the MapStore framework you have to:
1313

1414
* download developer tools and frontend dependencies locally:
1515

@@ -31,7 +31,7 @@ The HomePage contains links to the available demo applications.
3131

3232
## Frontend debugging
3333

34-
The development instance uses file watching and live reload, so each time a MapStore 2 file is changed, the browser will reload the updated application.
34+
The development instance uses file watching and live reload, so each time a MapStore file is changed, the browser will reload the updated application.
3535

3636
Use your favourite editor / IDE to develop and debug on the browser as needed.
3737

@@ -123,7 +123,7 @@ if you want to change the default port for mapstore back-end you have to edit `p
123123

124124
## Frontend testing
125125

126-
To run the MapStore 2 frontend test suite you can use:
126+
To run the MapStore frontend test suite you can use:
127127

128128
`npm test`
129129

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
The LeafletDraw plugin and the MapStore2 theme are linked via rawgit.com but in production it should be used a proper CDN.
1+
The LeafletDraw plugin and the MapStore theme are linked via rawgit.com but in production it should be used a proper CDN.
22
Once you have a stable version:
3-
- upload the [LeafletDraw plugin](http://rawgit.com/Leaflet/Leaflet.draw/v0.2.4/dist/) and the [MapStore2 theme](https://github.com/geosolutions-it/MapStore2-theme/tree/master/theme/default) on your CDN
3+
- upload the [LeafletDraw plugin](http://rawgit.com/Leaflet/Leaflet.draw/v0.2.4/dist/) and the [MapStore theme](https://github.com/geosolutions-it/MapStore2-theme/tree/master/theme/default) on your CDN
44
- edit the [index.html](https://github.com/geosolutions-it/MapStore2/blob/master/web/client/index.html) file to use your published resources.

0 commit comments

Comments
 (0)