15,534
edits
Changes
→For release 5.0 and above
{{languages}}
{{man note|How to make a genealogy website with |Using Gramps 4.x. and the [[Gramps_4.1_Wiki_Manual_2_Wiki_Manual_-_Reports_-_part_7#Narrated_Web_Site|Narrated Web Site]] report, from conception, to uploading your genealogical website to an internet service provider (ISP).}}
== Before you start ==
You can easily generate a nice looking web site website from within Gramps.
Before you start you should have an idea about the data you want to present on the website. If your complete family tree is large, the number of generated files can be '''huge''', and possibly take up a lot of file storage space.
==How to limit the amount of data==
If you have a large database, it is wise to start with a [[filter]] to limit the number of people: In the People view of Gramps, go to the View menu, and activate the Filter sidebar. Next, go to {{man menu|Edit --> Person Filter Editor}} menu, and make a suitable filter. Read the [[Gramps_4.1_Wiki_Manual_2_Wiki_Manual_-_Filters#Custom_Filter_Editor|help manual]] if necessary. Once a filter is defined, you can test it in the People view, by selecting the filter in the Filter Sidebar, and clicking find. You can combine filters (yes, it helps if you have experience with some basic and/or logic) until you have a selection of all the people you want on your website.
==Make a Home Page, Introduction Page, and more==
===How?===
{{out of date|stub}}<!--work differently in gramps 4 }}-->
Go to the Media View in Gramps, and click on the add icon. In the ''Select a media object'' dialog, you need to click on the option ''Internal Note'', and give a title, eg ''Home Page'', ''Footer'', ...
Choose a suitable directory where you want to generate your website locally. It is best to do this locally, and upload your website only afterwards.
In the '''Report Options''' tab, select the ''Filter'' you created previously if any. Change the ''Web site title:'' to something more meaningful to than "My Family Tree". Choose the ''StyleSheet'' you want (See [[Gramps_4.1_Wiki_Manual_2_Wiki_Manual_-_Reports_-_part_7#Report_Options|examples]]).
In the '''Page Generation''' tab, choose the internal notes you created above. It is recommended you "Suppress Gramps ID"'s, as visitors are not interested in this. Be careful with the option ''Include images and media objects''. '''Only choose this option if:
# You extensively use the private marker on sensitive data'''. {{man warn|Be careful with Sensitive data|Many people have unintentionally published private email conversations they stored for research reasons in Gramps, on the net without realizing.}}
The '''Privacy''' tab {{man menu|is one of the most important settings}}. Make it a habit to never include private data, and restrict the information on living people. It is recommended you leave the ''Years from death to consider living:'' as the default of a '''minimum of 30 years'''! This will lessen the issue of revealing sensitive data on the internet of living people that may have legal ramifications for you. A number of genealogists have found themselves in disputes due to publication of information on living people. You have been warned. Also Please also take into account your local legislation (eg:very strict privacy law in e.g. Italy, France, ...).
To create the report you select '''OK''' and Gramps starts generating your web page '''Narrated Web Site''' pages : this will take some time depending on the size of your family tree, as a lot of files and directories will be made. When completed you will be the owner of a complete structure ready to publish on the internet.
==Regeneration of your site==
Every time you change make changes to your database family tree you need to regenerate your site to see the changes. Although Gramps will regenerate the entire site, '''only the pages with changed dataNarrated Web Site''' will be different. You therefore need not republish all the website report to the internet again, but can limit yourself to only upload the changed pages. Specific tools to do this exist, like sitecopy. See furthersee those changes.
Although Gramps will regenerate the entire site, '''Limitationonly the pages with changed data''': If you upgrade Grampswill be different. You therefore need not republish all the website to the internet again, changes might have happened but can limit yourself to only upload the website generation, meaning all changed pages will have changed. Investigate Specific tools to do this before you upgradeexist, and consider the benefits of upgrading against this possible drawbacklike sitecopy. See further.
==Publishing==
{{stub}}<!--have not update below this-->
Now you can publish your work on the web.
*ftp/ssh: You can also use a wide range of ftp clients to upload your site. The easiest for new users is in GNOME/KDE, go to Remote Places, and click to add a new remote place. Choose the settings for your provider (ftp/ssh, login, password), and now you can drag and drop files in Nautilius/Konqueror, like on your own PC. You can also use one of the many specific ftp applications, like gFTP (it should be in the repositories of your distribution). Basically you transfer all the files to the server and that's it. However : as you have probably seen, you created with "NarrativeWeb" an awful lot of directories and files, so transferring the vast amount of files will take some time! If you update your site often, consider learning sitecopy!
== Examples of websitesNarrated Web Sites==Feel free to add your with Gramps generated website Narrated Web Site here. Please, remove missing links if you encounter those. Style is one of the Gramps styles, or custom.
{|{{prettytable}}
|-
|[http://users.telenet.be/frederik.de.richter/stamvaders.html De Richter]||Custom made ||Dutch || version 2.2.6
|[http://family.dave.org.uk/ Cross Family Tree]||Basic (Ash)||English||version 3.2.5-1
|-
|[httphttps://www.xs4allbosharst.nl/~bosharst/gramps/ Van den Bos - Van der Harst]||Basic (Spruce)||Dutch||version 4.12.14
|}
{{man note|Website gone?|Please remove those example website links that have gone.}}
== Comparison with other programs==
What if your database is really really huge? I did not try this yet, but you could split your data, say ''the descendants of Jacobus Roelants'' on one Lycos site and the other part of the family ''the descendants of Sebadiah Johansson '' on another Lycos site and so on. It should be fairly easy to install links to switch between sites, eg in the home page, as the directory structure Gramps generates does not change.
===Changing a word present on multiple pagesIntegrate with WordPress==={{stub}} Integrating GRAMPS and WordPress is a very straightforward activity. Not a lot of special skills or tools are required in order to make this integration work smoothly. A couple of points worth remembering (knowing?) first: *Don’t expect to update your GRAMPS data through WordPress. GRAMPS works best from a data collection and manipulation perspective as a stand alone PC application.*Neither database is ever truly linked in this integration;this is good for a number of reasons:**Your GRAMPS database can be secured (remain private)**Breaking one system doesn’t break everything; a good feature for those of us prone to checking our systems recovery processes regularly.*Websites are better for sharing information than they are for updating it. This is especially true if you have constrained network bandwidth, lots of different media and files of varying sizes including many that are BIG! These conditions probably encompass most people doing genealogy. So on to the integration… there are basically 5 major steps:
The patchs are available and attached to the feature request : [https://gramps-project.org/bugs/view.php?id==Code modifications==5530 #0005530]
===Alternate Code=For release 5.0 and above====
===Multilingual Web Site=How it works ?====
RewriteEngine on # rules for narrativeweb RewriteRule ^(.*)\.html$ http://%{HTTP_HOST}/index. php/tree?page=$1.html [QSA,R,L] RewriteRule ^(css/.*)\.css$ http://%{HTTP_HOST}/NAVWEB/$1.css [QSA,R,L] RewriteRule ^(thumb/.*)$ http://%{HTTP_HOST}/NAVWEB/$1 [QSA,R,L] RewriteRule ^((images|img|thumb)\/.*\.(jpeg|jpg|gif|png)$) http://%{HTTP_HOST}/NAVWEB/$1 [QSA,R,L]
{source} <pre?php $rep = "/var/www/NAVWEB/"; // You can place PHP like this $page = JRequest::getVar('page'); // for security reason, don't allow .. in path $pageok = str_replace("..", "", $page); if ($pageok == "") $pageok = "index.html"; include($rep.$pageok); ?>#/bin {/shsource}
==="Online maps" urls===
