15,536
edits
Changes
→For release 5.0 and above
{{languages}}
== 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 have present on the website. If you are not careful, and generate a webpage from your complete databasefamily tree is large, the amount number of generated files can be '''huge''', as well as taking 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 [http://gramps-project[Gramps_4.org/gramps2_Wiki_Manual_-manual/2.2/en/ch03s10.html_Filters#tools-util-cfe 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==
===What?===
Before you use the plugin ''NarrativeWebNarrated Web Site report'', you should make some custom pages with the information not yet in Gramps: <!-- already part of report in Gramps 4? -->
* a Home page: the starting page of the website
* Introduction Page: page where you can give an introduction of your research, ...
* Publisher info: extra information on you, the publisher of the page, to appear on every page
{{man note|Note that |Gramps works with stylesheets[https://en.wikipedia.org/wiki/Style_sheet_%28web_development%29 style sheets], so the exact ordering, and look of the website is all contained in '''one''' file, the stylesheetstyle sheet, eg narrative.css. You should at this moment NOT concern yourself about style, only content, and some basic markup (paragraphs, italic/bold text, div sections, ...).}}
===How?===
{{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'', ...
Next, you select the new media object, and edit it (double click or Edit button). Everything you write in the Note tab of the media object, will appear on your webpage if you select this media object during the website generation.
If you know html, you can just type the text with the needed html codes. If you do not know html, consider making a page with a web editor like Bluefish, Quanta Plus, ... . These contain icons to dynamically create webpages. The html text created like this can then be copied in the note section of your ''Home Page'' Gramps media object.
{{man tip|Tip: |if you are experienced have experience with stylesheets, you can use specific div tags in your pages, and edit the style sheet to contain your custom tags.}}
==Choosing the layout==
Gramps has some nice standard layout schemes. Those are kept provides seven built in so-called cascading style sheets (.css files). In Gramps 2.2.x, six are suppliedfor you to choose from to determine the appearance or your web pages. You are free to edit these files can choose between Basic (other lettertypesAsh, Blue, Cypress, other coloursLilac, Peach or Spruce color schemes), Mainz, or Nebraska styles...There is also the option of not including a stylesheet (No style sheet).
Whatever the style you choose, after generation, it will default to the ''narrative-screen.css'' file which will can be placed found in the dir you indicate. If you have some experience with websites you can easily customise this one file and without changing the content files, your web pages will be completely changed to the form, colours, etc. that you specified. Do backup these changes, as you might easily regenerate your website and overwrite this file by error<code>css</code> directory.
If you make a nice custom style sheet, please you would like to share with other Gramps users. You can do this by adding a link to your webpage in the examples below and adding to your custom css file and ensuring that its copyright is creative commons alike, and attaching to an feature request or you can send it to the developers on: gramps-devel <at> lists.sourceforge.netto be added.
==Generate the pages==
In the Report menu, choose {{man menu|Reports > Web Page--Pages >Narrative Narrated Web Site...}}.
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''' tab, set select the filter you created. Choose a ''Filter'GOOD'you created previously if any. Change the '' Web site title for your webpage. Choose file extension: html (the rest is for experienced users), Set character encoding '' to something more meaningful to Unicode (only use other encoding if you have very specific reasons)than "My Family Tree". Choose the style you want and set the copyright notice (use the footer for specific extra legalese necessary in your country). ''StyleSheet'Think about copyright!''' Ancestor graph generation relates to the how many ancestors will be visible on the people pages in a nice graphyou want (See [[Gramps_4. Try different settings for this2_Wiki_Manual_-_Reports_-_part_7#Report_Options|examples]]).
In the '''Page Generation Tab''' tab, choose the internal notes you created, as related above. I suggest It is recommended you suppress the GRAMPS "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:# your Your Hosting site can be VERY bighas enough file storage space.# you You extensively use the private marker on sensitive data'''. {{man warn|Be careful with Sensitive data|Many people have burnt themselves with this option, publishing unintentionally published private email conversations they stored for research reasons in Gramps, on the net without realizing.}}
The '''Privacy Tab '''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. I suggest It is recommended you set leave the ''years to restrict Years from person's deathto consider living:'' to as the default of a '''minimum of 25 30 years'''! This will prevent grave mistakes having sour consequenceslessen the issue of revealing sensitive data on the internet of living people that may have legal ramifications for you. Many 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, ...).
==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}} align="center"|- bgcolor="#8DA7D6" align="center" |'''!Site'''||'''Style'''||'''Language'''||'''Comment'''
|-
|[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.02.24
|}
{{man note|Website gone?|Please remove those example website links that have gone.}}
== Comparison with other programs==
There are two types of genealogy websites: static and dynamic. Static pages are ideal if you are limited with webspace, or want full control over your data. You have a genealogical database on your PC, and you select the data you want on a website, you upload this, and you are finished. Gramps website generation belongs in this category.
Dynamic websites have all the genealogical data on a server, and dynamically offer webpages, typically with javascript. This normally requires more disk space, however due to compression of the data, this might not be too bad. Dynamic websites are a great tool to collaborate on genealogical research with other people, as you normally have the option to change the data from within the website. For example, [httphttps://www.phpgedviewwebtrees.net/ PhpGedviewindex.php/en/ webtrees] is an open source project offering exactly this. A possible disadvantage is that for this too work, your service provider must offer you sufficient bandwith, or otherwise serving pages can be slow.
The beauty of open source is that you can choose the environment to work with, and the environment to generate your website with. The benefits of collaborating should also not be exaggerated, however, it might be a good idea to offer in the footer of your Gramps generated website the option to send you feedback, like the example on [https://web.archive.org/web/20061011043802/http://developers.gramps-project.org/tiki-index.php?page=MissingInformationReport this page].
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===
===Animal pedigree===
You can use Gramps for generating an [[Animal_pedigree|Animal Pedigree]] !