Skip to content

Commit 76853df

Browse files
Update instructions, after fetching they were causing some problems
1 parent dee0b38 commit 76853df

File tree

2 files changed

+6
-296
lines changed

2 files changed

+6
-296
lines changed

inst/user_doc/user_instructions.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ pagetitle: fieldactivity
1111
In order to use the application, you should have a site account registered. If you don’t have an account yet, see the contact section for requesting one, otherwise you should be able to fill in the provided sitename and password to login.
1212

1313

14-
![Login page](loginpage.png)
14+
![Login page](images_user_instructions/loginpage.png)
1515

1616

1717

@@ -22,21 +22,21 @@ The UI of the application is simple, but we will provide an overview of what fun
2222
1. Change the language between English and Finnish.
2323
2. Check the sitename you have logged in with. Next to this field, by pressing plus sign (+), it gives an option to logout.
2424

25-
![Overview of layout of the application](Layout.png)
25+
![Overview of layout of the application](images_user_instructions/Layout.png)
2626

2727

2828
3. Change the shown subset of the events based on the type of events, block and year.
2929

3030
As a default, all of the events from all of the (available) blocks and years are visible for the user. With the first option menu, the user is able to select which type of events she wants to keep visible on the summary table. With the second and third option menus, the user can pick the block and the year respectively to be displayed. If there are multiple events displayed, on the bottom of the table there is a navigation tool to switch the shown page.
3131

32-
![Summary table of the events](Eventtable.png)
32+
![Summary table of the events](images_user_instructions/Eventtable.png)
3333

3434

3535
### Filling in events
3636
Options for filling in the event will open, when pressing the *Add event* button. Start filling in the management event information by first choosing the block wherein the event has occurred, the name of this activity/event and a date for when it was conducted. One may also provide a short description that will be visible in the event table and later on give a quick reminder to which occurrence the event was related.
3737

3838

39-
![Adding a new event](Addevent.png)
39+
![Adding a new event](images_user_instructions/Addevent.png)
4040

4141
After choosing the type of activity, one should fill in the data about this activity. Different types of activities have different fields to be filled in, for example, after choosing tillage one should fill in the type of tillage, how the tillage was implemented and what the depth of the tillage was. Required option fields are marked with a star sign (*).
4242

@@ -51,7 +51,7 @@ Here are some notes that generally apply to all of the activities and that are g
5151
- **Events can be modified after saving them**, so there is no need to stress about doing something irreversible.
5252

5353

54-
![Example of the view for filling in the (tilling) event](eventexample_1.png)
54+
![Example of the view for filling in the (tilling) event](images_user_instructions/eventexample_1.png)
5555

5656

5757
### Clone event
@@ -82,4 +82,4 @@ You may contact us, if you are facing one or several of the following situations
8282
- You want to request a feature that is currently not available
8383
- You want to know more about the app
8484

85-
Regarding the new features and bug fixes, you can also fill in a github issue [**here**](https://github.com/Ottis1/fieldactivity/issues) without contacting us.
85+
Regarding the new features and bug fixes, you can also fill in a github issue [**here**](https://github.com/PecanProject/fieldactivity/issues) without contacting us.

inst/user_instructions.html

Lines changed: 0 additions & 290 deletions
This file was deleted.

0 commit comments

Comments
 (0)