From d96ab7c86798c692890ead5c54475fdabb5f83c9 Mon Sep 17 00:00:00 2001 From: Andrew Manning Date: Sat, 26 Nov 2016 20:29:53 -0700 Subject: Update wiki context help. Modify context page element focus feature to do nothing if the target DOM element is not found. --- doc/context/en/profiles/help.html | 35 ++++++++ doc/context/en/settings/account/help.html | 35 ++++++++ doc/context/en/settings/channel/help.html | 35 ++++++++ doc/context/en/settings/tokens/help.html | 23 +++++ doc/context/en/wiki/help.html | 2 +- doc/member/AdvancedSearch.md | 53 ++++++++++++ doc/member/accounts_profiles_channels_basics.bb | 19 +++++ doc/member/addons.bb | 104 +++++++++++++++++++++++ doc/member/bbcode.html | 108 ++++++++++++++++++++++++ doc/member/bugs.bb | 31 +++++++ doc/member/channels.bb | 39 +++++++++ doc/member/checking_account_quota_usage.bb | 20 +++++ doc/member/cloud.bb | 27 ++++++ doc/member/cloud_desktop_clients.bb | 21 +++++ doc/member/connecting_to_channels.bb | 19 +++++ doc/member/diaspora_compat.bb | 68 +++++++++++++++ doc/member/faq_admins.bb | 78 +++++++++++++++++ doc/member/first-post.bb | 3 + doc/member/overview.bb | 26 ++++++ doc/member/permissions.bb | 82 ++++++++++++++++++ doc/member/profiles.bb | 37 ++++++++ doc/member/registration.bb | 35 ++++++++ doc/member/remove_account.bb | 27 ++++++ doc/member/roles.md | 66 +++++++++++++++ doc/member/tags_and_mentions.bb | 69 +++++++++++++++ doc/member/toc.html | 25 ++++++ doc/member/webpages.bb | 93 ++++++++++++++++++++ doc/toc.html | 2 +- view/js/main.js | 22 ++--- 29 files changed, 1192 insertions(+), 12 deletions(-) create mode 100644 doc/context/en/profiles/help.html create mode 100644 doc/context/en/settings/account/help.html create mode 100644 doc/context/en/settings/channel/help.html create mode 100644 doc/context/en/settings/tokens/help.html create mode 100644 doc/member/AdvancedSearch.md create mode 100644 doc/member/accounts_profiles_channels_basics.bb create mode 100644 doc/member/addons.bb create mode 100644 doc/member/bbcode.html create mode 100644 doc/member/bugs.bb create mode 100644 doc/member/channels.bb create mode 100644 doc/member/checking_account_quota_usage.bb create mode 100644 doc/member/cloud.bb create mode 100644 doc/member/cloud_desktop_clients.bb create mode 100644 doc/member/connecting_to_channels.bb create mode 100644 doc/member/diaspora_compat.bb create mode 100644 doc/member/faq_admins.bb create mode 100644 doc/member/first-post.bb create mode 100644 doc/member/overview.bb create mode 100644 doc/member/permissions.bb create mode 100644 doc/member/profiles.bb create mode 100644 doc/member/registration.bb create mode 100644 doc/member/remove_account.bb create mode 100644 doc/member/roles.md create mode 100644 doc/member/tags_and_mentions.bb create mode 100644 doc/member/toc.html create mode 100644 doc/member/webpages.bb diff --git a/doc/context/en/profiles/help.html b/doc/context/en/profiles/help.html new file mode 100644 index 000000000..41f00fe64 --- /dev/null +++ b/doc/context/en/profiles/help.html @@ -0,0 +1,35 @@ +
+
General
+
+ Once you have registered an account at the matrix you have also created a profile and a channel. +
+
Account
+
+ You have one account. This consists of your email account and your password. With your account you access your + profile and your channel.Think of your account as the way you authenticate at one Hubzilla site. It lets you + do things, such as creating profiles and channels with which you can connect to other people. +
+
Profile
+
+ You have surely registered with some other internet services, such as forums or online communities. For all of them + you provided some information about yourself, such as date of birth, country, age and the likes. Unlike other + services Hubzilla offers you the advantage of creating + many more profiles. That way you are able to distinguish between profiles targeted specially at everyone + (your public profile), your work mates, your family and your partner.Think of your profile as the basic + information about yourself you tell other people. +
+
Channel
+
+ During the registration you created your first channel. Yes, besides several profiles you are able to have + several channels. This might be a bit confusing in the beginning, but let's clear things up. You already have + created one channel. You can use this one for the public, to communicate with people about every day life. But + perhaps you are an avid book reader and many people are bored by that. So you open a second channel just + for the book lovers, where you all can talk about books as much as you like. Obviously this is a new stream of + posts, with a new profile (... or new profiles ...) and completely different contacts. Some connections + might exist in both channels, but there will be some that are exclusive to only one of both. You yourself just + switch between both of them just like you would in real life switch when talking to people you meet on the street + or people you meet specially to talk about books. You can even connect to yourself, or better: to your other + channel. :)Think of a channel as different spaces dedicated to different topics where you meet with different + people. +
+
\ No newline at end of file diff --git a/doc/context/en/settings/account/help.html b/doc/context/en/settings/account/help.html new file mode 100644 index 000000000..41f00fe64 --- /dev/null +++ b/doc/context/en/settings/account/help.html @@ -0,0 +1,35 @@ +
+
General
+
+ Once you have registered an account at the matrix you have also created a profile and a channel. +
+
Account
+
+ You have one account. This consists of your email account and your password. With your account you access your + profile and your channel.Think of your account as the way you authenticate at one Hubzilla site. It lets you + do things, such as creating profiles and channels with which you can connect to other people. +
+
Profile
+
+ You have surely registered with some other internet services, such as forums or online communities. For all of them + you provided some information about yourself, such as date of birth, country, age and the likes. Unlike other + services Hubzilla offers you the advantage of creating + many more profiles. That way you are able to distinguish between profiles targeted specially at everyone + (your public profile), your work mates, your family and your partner.Think of your profile as the basic + information about yourself you tell other people. +
+
Channel
+
+ During the registration you created your first channel. Yes, besides several profiles you are able to have + several channels. This might be a bit confusing in the beginning, but let's clear things up. You already have + created one channel. You can use this one for the public, to communicate with people about every day life. But + perhaps you are an avid book reader and many people are bored by that. So you open a second channel just + for the book lovers, where you all can talk about books as much as you like. Obviously this is a new stream of + posts, with a new profile (... or new profiles ...) and completely different contacts. Some connections + might exist in both channels, but there will be some that are exclusive to only one of both. You yourself just + switch between both of them just like you would in real life switch when talking to people you meet on the street + or people you meet specially to talk about books. You can even connect to yourself, or better: to your other + channel. :)Think of a channel as different spaces dedicated to different topics where you meet with different + people. +
+
\ No newline at end of file diff --git a/doc/context/en/settings/channel/help.html b/doc/context/en/settings/channel/help.html new file mode 100644 index 000000000..41f00fe64 --- /dev/null +++ b/doc/context/en/settings/channel/help.html @@ -0,0 +1,35 @@ +
+
General
+
+ Once you have registered an account at the matrix you have also created a profile and a channel. +
+
Account
+
+ You have one account. This consists of your email account and your password. With your account you access your + profile and your channel.Think of your account as the way you authenticate at one Hubzilla site. It lets you + do things, such as creating profiles and channels with which you can connect to other people. +
+
Profile
+
+ You have surely registered with some other internet services, such as forums or online communities. For all of them + you provided some information about yourself, such as date of birth, country, age and the likes. Unlike other + services Hubzilla offers you the advantage of creating + many more profiles. That way you are able to distinguish between profiles targeted specially at everyone + (your public profile), your work mates, your family and your partner.Think of your profile as the basic + information about yourself you tell other people. +
+
Channel
+
+ During the registration you created your first channel. Yes, besides several profiles you are able to have + several channels. This might be a bit confusing in the beginning, but let's clear things up. You already have + created one channel. You can use this one for the public, to communicate with people about every day life. But + perhaps you are an avid book reader and many people are bored by that. So you open a second channel just + for the book lovers, where you all can talk about books as much as you like. Obviously this is a new stream of + posts, with a new profile (... or new profiles ...) and completely different contacts. Some connections + might exist in both channels, but there will be some that are exclusive to only one of both. You yourself just + switch between both of them just like you would in real life switch when talking to people you meet on the street + or people you meet specially to talk about books. You can even connect to yourself, or better: to your other + channel. :)Think of a channel as different spaces dedicated to different topics where you meet with different + people. +
+
\ No newline at end of file diff --git a/doc/context/en/settings/tokens/help.html b/doc/context/en/settings/tokens/help.html new file mode 100644 index 000000000..d37a0fd2b --- /dev/null +++ b/doc/context/en/settings/tokens/help.html @@ -0,0 +1,23 @@ +
+
Guest Access Tokens
+
+ In order to facilitate sharing of private resources with non-members or members of federation nodes with limited identification discovery, Hubzilla should provide members with a mechanism to create and manage temporary ("throwaway") logins, aka "Zot Access Tokens". These tokens/credentials may be used to authenticate to a hubzilla site for the sole purpose of accessing privileged or access controlled resources (files, photos, posts, webpages, chatrooms, etc.). +
+
Create a token
+
+ The form to create/edit accepts three parameters, a human readable name, a password or access token, and an + optional expiration. Once expired, the access token is no longer valid, may no longer be used, and will be + automatically purged from the list of temporary accounts. The password field in the create/edit forms + displays the text of the access token and not an obscured password. +
+
Share a token
+
+ We do not specify mechanisms for sharing these tokens with others. Any communication method may be used. Any tokens you have created are added to the Access Control List selector and may be used anywhere that Access Control Lists are provided. + + Example: A visitor arrives at your site. She has an access token you have provided, and attempts to visit one of your photo albums (which is restricted to be viewed only by yourself and one temporary identity). Permission is denied. + + The visitor now selects "Login" from the menu navigation bar. This presents a login page. She enters the name and password you have provided her, and she can now view the restricted photo album. + + Alternatively, you may share a link to a protected file by adding a parameter "&zat=abc123" to the URL, where the string "abc123" is the access token or password for the temporary login. No further negotiation is required, and the file is presented. +
+
\ No newline at end of file diff --git a/doc/context/en/wiki/help.html b/doc/context/en/wiki/help.html index 314a9d60b..a42914c17 100644 --- a/doc/context/en/wiki/help.html +++ b/doc/context/en/wiki/help.html @@ -1,7 +1,7 @@
General
Each wiki is a collection of pages, composed as Markdown-formatted text files.
-
Wiki List
+
Wiki List
Wikis owned by the channel that you have permission to view are listed in the side panel.
Page History
Every revision of a page is saved to allow quick reversion. Click the History tab to view a history of page revisions, including the date and author of each. The revert button will load the selected revision but will not automatically save the page.
diff --git a/doc/member/AdvancedSearch.md b/doc/member/AdvancedSearch.md new file mode 100644 index 000000000..a67c1fc1f --- /dev/null +++ b/doc/member/AdvancedSearch.md @@ -0,0 +1,53 @@ +Advanced Directory Search +========================= + + +Advanced Directory Search is enabled in "Expert Mode" from your Settings => Additional features page. + +On the Directory page an option named "Advanced" will apear in the "Find Channels" widget (typically in the sidebar). Clicking "Advanced" will open another search box for entering advanced search requests. + +Advanced requests include + +* name=xxx +[Channel name contains xxx] + +* address=xxx +[Channel address (webbie) contains xxx] + +* locale=xxx +[Locale (typically 'city') contains xxx] + +* region=xxx +[Region (state/territory) contains xxx] + +* postcode=xxx +[Postcode or zip code contains xxx] + +* country=xxx +[Country name contains xxx] + +* gender=xxx +[Gender contains xxx] + +* marital=xxx +[Marital status contains xxx] + +* sexual=xxx +[Sexual preference contains xxx] + +* keywords=xxx +[Keywords contain xxx] + +There are many reasons why a match may not return what you're looking for, as many channels do not provide detailed information in their default (public) profile, and many of these fields allow free-text input in several languages - and this may be difficult to match precisely. For instance you may have better results finding somebody in the USA with 'country=u' (along with some odd channels from Deutschland and Bulgaria and Australia) because this could be represented in a profile as US, U.S.A, USA, United States, etc... + +Future revisions of this tool may try to smooth over some of these difficulties. + +Requests may be joined together with 'and', 'or', and 'and not'. + +Terms containing spaces must be quoted. + +Example: + + name="charlie brown" and country=canada and not gender=female + +#include doc/macros/main_footer.bb; diff --git a/doc/member/accounts_profiles_channels_basics.bb b/doc/member/accounts_profiles_channels_basics.bb new file mode 100644 index 000000000..63b13f036 --- /dev/null +++ b/doc/member/accounts_profiles_channels_basics.bb @@ -0,0 +1,19 @@ +[size=large][b]Accounts, Profiles and Channels[/b][/size] + +Once you have registered an [i]account[/i] at the matrix you have also created a [i]profile[/i] and a [i]channel[/i]. + +[b]Account[/b] +You have [i]one[/i] account. This consists of your email account and your password. With your account you access your profile and your channel. +[i]Think of your account as the way you authenticate at one $Projectname site. It lets you do things, such as creating profiles and channels with which you can connect to other people.[/i] + +[b]Profile[/b] +You have surely registered with some other internet services, such as forums or online communities. For all of them you provided some information about yourself, such as date of birth, country, age and the likes. [observer=1]If you like you can see your profile here: [baseurl]/profile/[observer.webname] and edit it by clicking on the pencil icon next to your avatar image. [/observer] +Unlike other services $Projectname offers you the advantage of creating [i]many more profiles[/i]. That way you are able to distinguish between profiles targeted specially at everyone (your public profile), your work mates, your family and your partner. +[i]Think of your profile as the basic information about yourself you tell other people.[/i] + +[b]Channel[/b] +During the registration you created your first [i]channel[/i]. Yes, besides several profiles you are able to have several channels. This might be a bit confusing in the beginning, but let's clear things up. You already have created one channel. You can use this one for the public, to communicate with people about every day life. But perhaps you are an avid book reader and many people are bored by that. So you open a [i]second channel[/i] just for the book lovers, where you all can talk about books as much as you like. Obviously this is a new stream of posts, with a new profile (... or new profile[i]s[/i] ...) and completely different contacts. Some connections might exist in both channels, but there will be some that are exclusive to only one of both. You yourself just switch between both of them just like you would in real life switch when talking to people you meet on the street or people you meet specially to talk about books. You can even connect to yourself, or better: to your other channel. :) +[i]Think of a channel as different spaces dedicated to different topics where you meet with different people.[/i] + +#include doc/macros/main_footer.bb; + diff --git a/doc/member/addons.bb b/doc/member/addons.bb new file mode 100644 index 000000000..b83b3276a --- /dev/null +++ b/doc/member/addons.bb @@ -0,0 +1,104 @@ +[h3]Plugins/Addons[/h3] +[list=1] +[*] abcjsplugin - Create musical scores in your posts +[*] adultphotoflag - prevents nsfw photos from being displayed in public albums +[*] b2tbtn - provide button to go directly to top of page if you are scrolled a long way down +[*] bbmath - use complex math expressions in your posts +[*] bookmarker - replace #^ with bookmark link in posts +[*] buglink - provide a bug reporting icon in the lower-left corner of every page +[*] calc - a scientific calculator +[*] cdav - CalDAV/CardDAV server +[*] chess - cross domain identity aware interactive chess games +[*] chords - generate fingering charts and alternatives for every known guitar chord +[*] custom_home - set a custom page as the hub start page +[*] dfedfix - fixes some federation issues with Diaspora releases around aug-sep 2015 +[*] diaspora - Diaspora protocol emulator +[*] diaspost - crosspost to a Diaspora account (different from the Diaspora protocol emulator) +[*] dirstats - show some interesting statistics generated by the driectory server +[*] docs - alternate documentation pages +[*] donate - provides a project donation page +[*] dwpost - crosspost to Dreamwidth +[*] embedphotos - tool to embed photos from your albums in a post +[*] extcron - use an external cron service to run your hub's scheduled tasks +[*] flattrwidget - provides a "Flattr Us" button +[*] flip - create upside down text +[*] fortunate - displays random quote (fortune cookie). Requires setting up a fortune server. +[*] friendica - Friendica (DFRN) protocol. Under development. +[*] frphotos - import photo albums from Friendica +[*] gnusoc - GNU-Social (OStatus) protocol. Under development. +[*] hexit - headecimal conversion tool +[*] hubwall - send an admin email to all hub accounts +[*] ijpost - crosspost to Insanejournal +[*] irc - connect to IRC chatrooms +[*] jappixmini - XMPP chat +[*] jsupload - upload multiple photos to photo albums at once. +[*] keepout - prevents nearly all use of site when not logged in, more restrictive than 'block public' setting +[*] ldapauth - login via account on LDAP or Windows Active Directory domain +[*] libertree - crosspost to Libertree +[*] likebanner - create a "like us on red#matrix" banner image +[*] ljpost - crosspost to LiveJournal +[*] logrot - logfile rotation utility +[*] mahjongg - Chinese puzzle game +[*] mailhost - when using multiple channel clones, select one to receive email notifications +[*] metatag - provide SEO friendly pages +[*] mayan_places - set location field to a random city in the Mayan world +[*] morechoice - additional gender/sexual-preference choices for profiles (not safe for work) +[*] moremoods - Additional mood options +[*] morepokes - additional poke options (not safe for work) +[*] msgfooter - provide legal or other text on each outgoing post +[*] noembed - use noembed.com as an addition to Hubzilla's native oembed functionality (currently broken) +[*] nofed - prevent "federation" of channel posts, maintains all interaction on your site +[*] nsabait - add random terrorism related hashtags to your posts +[*] nsfw - Highly recommended plugin to collpase posts with inappropriate content +[*] openclipatar - choose a profile photo from hundreds of royalty free images +[*] openstreetmap - render locations and maps using OpenStreetMap +[*] piwik - open source website analytics +[*] planets - set location field to a random planet from Star Wars +[*] pumpio - crosspost to Pump.io +[*] qrator - generate QR code images +[*] rainbowtag - display your tag and category clouds in colours +[*] randpost - post/reply bot based on and requires fortunate +[*] redfiles - import file storage from redmatrix +[*] redphotos - import photo albums from redmatrix +[*] redred - Crosspost to another Red Matrix or Hubzilla channel +[*] rtof - Crosspost to Friendica +[*] sendzid - add 'zid' auth parmaters to all outbound links, not just in-network links +[*] skeleton - sample addon/plugin to demonstrate plugin development +[*] smiley_pack - extend the built-in smilie (emoticon) support +[*] smileybutton - provides a smiley selector on the post window +[*] startpage - set a personal preferred page to redirect after logging in. +[*] statistics_json - Diaspora statistics generator +[*] statusnet - GNU-social and StatusNet crosspost [zrl=[baseurl]/help/addons_gnusocial]Posting To Gnu Social[/zrl] +[*] std_embeds - allow unfiltered embeds for popular providers like youtube, vimeo and soundcloud +[*] superblock - Highly recommended - completely block an offensive channel from your stream +[*] testdrive - Turns your hub into a test drive site with accounts that expire after a trail period. +[*] tictac - 3D tic-tac-toe +[*] torch - flashlight app +[*] tour - feature tour for new members +[*] twitter - crosspost to Twitter +[*] upload_limits - discover what server setting (there are a few) may be causing large photo uploads to fail +[*] visage - show visitors to your channel +[*] wholikesme - provides a page to display what connections have 'liked' your posts the most +[*] webRTC - use an external server (mayfirst.org) to negotiate webRTC hookups +[*] wppost - crosspost to WordPress (or other wordpress XMLRPC service) +[*] xmpp - XMPP chat based on converse.js +[/list] + +[h3]Addon Repositories[/h3] + +We [b]strongly recommend[/b] that authors of addons publish/submit them to the project addon repository. This has several advantages. Project developers can easily fix security flaws and make changes to comply with recent changes in core code. Addons provided in third-party repositories are considered untrusted. If the project core code changes in an incompatible way, there may be no alternative but to physically remove or rename the addon files in order to get your site working again. Often only the plugin/addon author can help you regain control of your website, and project developers are unable to assist you; because by definition your site configuration has been modified in ways that we cannot easily test or verify. + +For these reasons we [b]strongly recommend[/b] that you do NOT install addons from third-party repositories. + +We also recognise that some developers prefer working on their own and do not wish their code to be mingled with the project repository for a variety of reasons. These developers can ease troubleshooting and debugging by providing a README file in their respective code repository outlining the process for submitting patches and bug fixes. It is also recommended that these projects provide both a 'dev' (development) and 'master' (production) branch which tracks the current project branches of those names. This is because dev and master are often not compatible from the viewpoint of library interfaces. It is also highly recommended that your repository versions are tagged and moved forward within 24 hours of project releases. This is a major inconvenience for everybdy involved, and can present downtime for production sites while this process is being carried out; which is one more reason why we [b]strongly recommend[/b] that addons be submitted to the project addon repository and that you do NOT install such third-party addons. + + +[url=https://github.com/redmatrix/hubzilla-addons]https://github.com/redmatrix/hubzilla-addons[/url] Main project addon repository + +[url=https://github.com/23n/red-addons]https://github.com/23n/red-addons[/url] Oliver's repository (mayan_places and flip) + + + +#include doc/macros/main_footer.bb; + + diff --git a/doc/member/bbcode.html b/doc/member/bbcode.html new file mode 100644 index 000000000..7a2c969eb --- /dev/null +++ b/doc/member/bbcode.html @@ -0,0 +1,108 @@ +

BBcode reference

+
+

+
    +
  • [b]bold[/b] - bold
    +
  • [i]italic[/i] - italic
    +
  • [u]underlined[/u] - underlined
    +
  • [s]strike[/s] - strike
    +
  • [color=red]red[/color] - red
    +
  • [url=https://zothub.com]$Projectname[/url] $Projectname
    +
  • [img]https://zothub.com/images/default_profile_photos/rainbow_man/48.jpg[/img] Image/photo
    +
  • [img float=left]https://zothub.com/images/default_profile_photos/rainbow_man/48.jpg[/img] Image/photo
    +
    +
  • [img float=right]https://zothub.com/images/default_profile_photos/rainbow_man/48.jpg[/img] Image/photo
    +
    +
  • [code]code[/code] code
    +
  • [code=xxx]syntax highlighted code[/code] supported languages php, css, mysql, sql, abap, diff, html, perl, ruby, vbscript, avrc, dtd, java, xml, cpp, python, javascript, js, json, sh
    +
  • [quote]quote[/quote]
    quote

    +
  • [quote=Author]Author? Me? No, no, no...[/quote]
    Author wrote:
    Author? Me? No, no, no...

    +
  • [nobb] may be used to escape bbcode.

+ +
You can make lists with:
+
    +
  • [list]
    +
  • [list=1]
    +
  • [list=i]
    +
  • [list=I]
    +
  • [list=a]
    +
  • [list=A]
    +
  • [ul]
    +
  • [ol]
    +
  • [dl]
    +
  • [dl terms="biumlh"] — where style of the terms can be any combination of: +
    +
    b
    bold
    +
    i
    italic
    +
    u
    underline
    +
    m
    monospace
    +
    l
    large
    +
    h
    horizontal — like this defintion list
    +
    +
    • + +
For example:
[ul]
[*] First list element
[*] Second list element
[/ul]

Will render something like:
+
    +
  • First list element
    +
  • Second list element
+ +or

[dl terms="b"]
[*= First element term] First element description
[*= Second element term] Second element description
[/dl]

Will render something like:

+
+
First element term
First element description
+
Second element term
Second element description
+

+ + +
There's also:
+
    +
  • [hr]
    +
  • [video]video URL[/video]
    +
  • [audio]audio URL[/audio]
    +
  • [table]
    +
  • [th]
    +
  • [td]
    +
  • [tr]
    +
  • [center]
    +
  • [font=courier]some text[/font] some text
    +

+
Tables? Yes!

[table border=1]
[tr]
[th]Tables now[/th]
[/tr]
[tr]
[td]Have headers[/td]
[/tr]
[/table]

Tables now
Have headers

All sizes,
From the [size=xx-small] - xx-small.
To the [size=xx-large] - xx-large.
To fit exactly 20px use [size=20].

+ +

$Projectname specific codes

+
    +
  • [©] © This works for many HTML entities
    • +
  • [zrl]https://zothub.com[/zrl] Magic-auth version of [url] tag
    • +
  • [zmg]https://zothub.com/some/photo.jpg[/zmg] Magic-auth version of [img] tag
    • + +
  • [observer=1]Text to display if observer is authenticated in the matrix[/observer]
    • +
  • [observer=0]Text to display if observer is not authenticated in the matrix[/observer]
    • +
  • [observer.baseurl] website of observer
    • +
  • [observer.url] channel URL of observer
    • +
  • [observer.name] name of observer
    • +
  • [observer.address] address (zot-id) of observer
    • +
  • [observer.photo] profile photo of observer
    • + +
  • [spoiler] for hiding spoilers

    • + +
  • [rpost=title]Text to post[/rpost] The observer will be returned to their home hub to enter a post with the specified title and body. Both are optional
    • +
  • [qr]text to post[/qr] - create a QR code (if the qrator plugin is installed).
    • +
  • [toc] - create a table of content in a webpage. Please refer to the original jquery toc to get more explanations. +
      +
    • Optional param: 'data-toc'. If ommited the default is 'body'
      • +
    • Optional param: 'data-toc-headings'. If ommited the default is 'h1,h2,h3'
      • +
    • Full example: [toc data-toc='div.page-body' data-toc-headings='h1,h2']
      • +
    +
    • +
+
+

These require a suitable map plugin/addon such as openstreetmap or else the result will be blank

+
    +
  • [map] Generate an inline map using the current browser coordinates of the poster, if browser location is enabled
    +
  • [map=latitude,longitude] Generate a map using global coordinates.
    +
  • [map]Place Name[/map] Generate a map for a given named location. The first matching location is returned. For instance "Sydney" will usually return Sydney, Australia and not Sydney, Nova Scotia, Canada unless the more precise location is specified. It is highly recommended to use the post preview utility to ensure you have the correct location before submitting the post.
    +
+ +#include doc/macros/main_footer.bb; +
+ + + diff --git a/doc/member/bugs.bb b/doc/member/bugs.bb new file mode 100644 index 000000000..f50337648 --- /dev/null +++ b/doc/member/bugs.bb @@ -0,0 +1,31 @@ +[h2]Bugs, Issues, and things that go bump in the night...[/h2] +[h3]Something went wrong! Who is charge of fixing it?[/h3] + +[b]Hubzilla Community Server[/b] + +Hubzilla Community Server is open source software which is maintained by "the community" - essentially unpaid volunteers. + +The first thing you need to do is talk to your hub administrator - the person who runs and manages your site. They are in the unique position of having access to the internal software and database and [b]logfiles[/b] and will need to be involved in fixing your problem. Other people "on the net" can't really help with this. The first thing the hub administrator needs to do is look at their logs and/or try to reproduce the problem. So try to be as helpful and courteous as possible in helping them look into the problem. + +To find your hub administrator (if you don't know who they are) please look at [url=[baseurl]/siteinfo]this page[/url]. If they have not provided any contact info on that page or provided an "Impressum" there, see [url=[baseurl]/siteinfo/json]this site info summary[/url] under the heading "admin:". + +[h3]I'm a hub administrator; what do I do?[/h3] + +The software instructions which provide this server are open source and are available for your inspection. If an error message was reported, often one can do a search on the source files for that error message and find out what triggered it. With this information and the site logfiles it may be possible to figure out the sequence of events leading to the error. There could also be other sites involved, and the problem may not even be on your site but elsewhere in the network. Try to pin down the communication endpoints (hubs or sites) involved in the problem and contact the administrator of that site or those sites. Please try and provide an event time of when things went wrong so it can be found in the logs. Work with the other administrator(s) to try and find the cause of the problem. Logfiles are your friend. When something happens in the software that we didn't expect, it is nearly always logged. + +[h3]The white screen of death[/h3] + +If you get a blank white screen when doing something, this is almost always a code or syntax error. There are instructions in your .htconfig.php file for enabling syntax logging. We recommend all sites use this. With syntax logging enabled repeat the sequence which led to the error and it should log the offending line of code. Hopefully you will be able to fix the problem with this information. When you do, please submit the fix "upstream" so that we can share the fix with the rest of the project members and other communities. This is a key benefit of using open source software - we share with each other and everybody benefits. + +[h3]I'm stumped. I can't figure out what is wrong.[/h3] + +At this point it might be worthwhile discussing the issue on one of the online forums. There may be several of these and some may be more suited to your spoken language. As a last resort, try "Channel One", which is in English. + +If the community developers can't help you right away, understand that they are volunteers and may have a lot of other work and demands on their time. At this point you need to file a bug report. You will need an account on github.com to do this. So register, and then visit https://github.com/redmatrix/hubzilla/issues +. Create an issue here and provide all the same information that you provided online. Don't leave out anything. + +Then you wait. If it's a high profile issue, it may get fixed quickly. But nobody is in charge of fixing bugs. If it lingers without resolution, please spend some more time investigating the problem. Ask about anything you don't understand related to the behaviour. You will learn more about how the software works and quite possibly figure out why it isn't working now. Ultimately it is somebody in the community who is going to fix this and you are a member of the community; and this is how the open source process works. + + +Other developers working to fix the problem may need to find out more, so do your homework and document what is happening and everything you've tried. Don't say "I did xyz and it didn't work." That doesn't tell us anything. Tell us precisely what steps you took and what you expected the result to be, and precisely what happened as a result. If there were any error messages, don't say "there was an error message". Tell us exactly what the message said. Tell us what version you're running and any other details that may be unique about your site configuration. + \ No newline at end of file diff --git a/doc/member/channels.bb b/doc/member/channels.bb new file mode 100644 index 000000000..eca8dd0e6 --- /dev/null +++ b/doc/member/channels.bb @@ -0,0 +1,39 @@ +[h2]Channels[/h2] + +[h3]What are channels?[/h3] + +Channels are simply collections of content stored in one place. A channel can represent anything. It could represent you, a website, a forum, photo albums, anything. For most people, their first channel with be "Me". + +The most important features for a channel that represents "me" are: +[ul] +[*]Secure and private "spam free" communications + +[*]Identity and "single-signon" across the entire network + +[*]Privacy controls and permissions which extend to the entire network + +[*]Directory services (like a phone book) +[/ul] +In short, a channel that represents yourself is "me, on the internet". + +[h3]Creating channels[/h3] + +You will be required to create your first channel as part of the sign up process. You can also create additonal channels from the "Select channel" link. + +You will be asked to provide a channel name, and a short nick name. For a channel that represents yourself, it is a good idea to use your real name here to ensure your friends can find you, and connect to your channel. The short nickname will be used to generate a "webbie". This is a bit like a username, and will look like an email address, taking the form nickname@domain. You should put a little thought into what you want to use here. Imagine somebody asking for your webbie and having to tell them it is "llamas-are_kewl.123". "llamasarecool" would be a much better choice. + +Once you have created your channel, you will be taken to the settings page, where you can configure your channel, and set your default permissions. + +Once you have done this, your channel is ready to use. At [observer=1][observer.url][/observer][observer=0]example.com/channel/username[/observer] you will find your channel "stream". This is where your recent activity will appear, in reverse chronological order. If you post in the box marked "share", the entry will appear at the top of your stream. You will also find links to all the other communication areas for this channel here. The "About" tab contains your "profile", the photos page contain photo albums, and the events page contains events share by both yourself and your contacts. + +[h3]The grid, permissions and delegation[/h3] + +The "Grid" page contains all recent posts from across $Projectname network, again in reverse chronologial order. The exact posts that appear here depend largely on your permissions. At their most permissive, you will receive posts from complete strangers. At the other end of the scale, you may see posts from only your friends - or if you're feeling really anti-social, only your own posts. + +As mentioned at the start, many other kinds of channel are possible, however, the creation procedure is the same. The difference between channels lies primarily in the permissions assigned. For example, a channel for sharing documents with colleagues at work would probably want more permissive settings for "Can write to my "public" file storage" than a personal account. For more information, see the [zrl=[baseurl]/help/roles]permissions section[/zrl]. + +You can also delegate control of your channels' posts and connections, but not its configurations, to another channel. That is done by editing a connection and assigning it the permission to administer your channel's resources. + +#include doc/macros/main_footer.bb; + + diff --git a/doc/member/checking_account_quota_usage.bb b/doc/member/checking_account_quota_usage.bb new file mode 100644 index 000000000..ca7e070ad --- /dev/null +++ b/doc/member/checking_account_quota_usage.bb @@ -0,0 +1,20 @@ +[b]Checking your account quota usage (service limits usage)[/b] + +Your hub might implement service class limits, assigning limits to the total size of file, photo, channels, top-level posts, etc., that can be created by an account holder for a specific service level. + +Here's how you can quickly check how much of your assigned quota you're currently using: + +[b]Check file storage quota levels[/b] +Visit the following URL in your browser: +[observer=1][observer.baseurl]/filestorage/[observer.webname][/observer] +[observer=0]example.com/filestorage/username[/observer] + +[b]Check uploaded photos storage quota levels[/b] +[observer=1][observer.baseurl]/photos/[observer.webname][/observer] +[observer=0]example.com/photos/username[/observer] + +Example: +[observer=1][observer.baseurl]/filestorage/[observer.webname][/observer] +[observer=0]example.com/filestorage/username[/observer] + +#include doc/macros/main_footer.bb; diff --git a/doc/member/cloud.bb b/doc/member/cloud.bb new file mode 100644 index 000000000..2ad22806b --- /dev/null +++ b/doc/member/cloud.bb @@ -0,0 +1,27 @@ +[b]Personal Cloud Storage[/b] + +$Projectname provides an ability to store privately and/or share arbitrary files with friends. + +You may either upload files from your computer into your storage area, or copy them directly from the operating system using the WebDAV protocol. + +On many public servers there may be limits on disk usage. + +[b]File Attachments[/b] + +The quickest and easiest way to share files is through file attachments. In the row of icons below the status post editor is a tool to upload attachments. Click the tool, select a file and submit. After the file is uploaded, you will see an attachment code placed inside the text region. Do not edit this line or it may break the ability for your friends to see the attachment. You can use the post permissions dialogue box or privacy hashtags to restrict the visibility of the file - which will be set to match the permissions of the post your are sending. + +To delete attachments or change the permissions on the stored files, visit [observer.baseurl]/cloud/{{username}}" replacing {{username}} with the nickname you provided during channel creation. + +[b]Web Access[/b] + +Your files are visible on the web at the location "cloud/{{username}}" to anybody who is allowed to view them. If the viewer has sufficient privileges, they may also have the ability to create new files and folders/directories. + +[b]WebDAV access[/b] + +See: [zrl=[baseurl]/help/cloud_desktop_clients]Cloud Desktop Clients[/zrl] + +[b]Permissions[/b] + +When using WebDAV, the file is created with your channel's default file permissions and this cannot be changed from within the operating system. It also may not be as restrictive as you would like. What we've found is that the preferred method of making files private is to first create folders or directories; then visit "filestorage/{{username}}"; select the directory and change the permissions. Do this before you put anything into the directory. The directory permissions take precedence so you can then put files or other folders into that container and they will be protected from unwanted viewers by the directory permissions. It is common for folks to create a "personal" or "private" folder which is restricted to themselves. You can use this as a personal cloud to store anything from anywhere on the web or any computer and it is protected from others. You might also create folders for "family" and "friends" with permission granted to appropriate privacy groups. + +#include doc/macros/main_footer.bb; diff --git a/doc/member/cloud_desktop_clients.bb b/doc/member/cloud_desktop_clients.bb new file mode 100644 index 000000000..2f099527f --- /dev/null +++ b/doc/member/cloud_desktop_clients.bb @@ -0,0 +1,21 @@ +[b]Cloud Desktop Clients[/b] + +[b]Windows Clients[/b] + +[li][zrl=[baseurl]/help/dav_windows]Windows Internal Client[/zrl][/li] + + +[b]Linux Clients[/b] + +[li][zrl=[baseurl]/help/dav_mount]Command Line as a Filesystem[/zrl][/li] +[li][zrl=[baseurl]/help/dav_dolphin]Dolphin[/zrl][/li] +[li][zrl=[baseurl]/help/dav_konqueror]Konqueror[/zrl][/li] +[li][zrl=[baseurl]/help/dav_nautilus]Nautilus[/zrl][/li] +[li][zrl=[baseurl]/help/dav_nemo]Nemo[/zrl][/li] + + +[b]Server Notes[/b] + +Note: There have been reported issues with clients that use "chunked transfer encoding", which includes Apple iOS services, and also the "AnyClient" and "CyberDuck" tools. These work fine for downloads, but uploads often end up with files of zero size. This is caused by an incorrect implemention of chunked encoding in some current FCGI (fast-cgi) implementations. Apache running with PHP as a module does not have these issues, but when running under FCGI you may need to use alternative clients or use the web uploader. At the time of this writing the issue has been open and no updates provided for at least a year. If you encounter zero size files with other clients, please check the client notes; as there are occasional configuration issues which can also produce these symptoms. + +#include doc/macros/cloud_footer.bb; diff --git a/doc/member/connecting_to_channels.bb b/doc/member/connecting_to_channels.bb new file mode 100644 index 000000000..291323f75 --- /dev/null +++ b/doc/member/connecting_to_channels.bb @@ -0,0 +1,19 @@ +[b]Connecting To Channels[/b] + +Connections in $Projectname can take on a great many different meanings. But let's keep it simple, you want to be friends with somebody like you are familiar with from social networking. How do you do it? + +First, you need to find some channels to connect to. There are two primary ways of doing this. Firstly, setting the "Can send me their channel stream and posts" permission to "Anybody in this network" will bring posts from complete strangers to your matrix. This will give you a lot of public content and should hopefully help you find interesting, entertaing people, forums, and channels. + +The next thing you can do is look at the Directory. The directory is available on every $Projectname website which means searching from your own site will bring in results from the entire network. You can search by name, interest, location and keyword. This is incomplete, so we'll improve this paragraph later. + +To connect with other $Projectname channels: + +Visit their profile by clicking their photograph in the directory, matrix, or comments, and it will open their channel home page in the channel viewer. At the left hand side of the screen, you will usually see a link called "connect". Click it, and you're done. Depending on the settings of the channel you are connecting to, you may need to wait for them to approve your connection, but no further action is needed on your part. Once you've initiated the connection, you will be taken to the connection editor. This allows you to assign specific permissions for this channel. If you don't allow any permissions, communication will be very limited. There are some quick links which you can use to avoid setting individual permissions. To provide a social network environment, "Full Sharing" is recommended. You may review the settings that are applied with the quick links to ensure they are suitable for the channel you are connecting with and adjust if necessary. Then scroll to the bottom of the page and click "Submit". + +You may also connect with any channel by visiting the "Connections" page of your site or the Directory and typing their "webbie" into the "Add New Connection" field. Use this method if somebody tells you their webbie and you wish to connect with them. A webbie looks like an email address; for example "bob@example.com". The process is the same as connecting via the "Connect" button - you will then be taken to the connection editor to set permissions. + +[b]Premium Channels[/b] + +Some channels are designated "Premium Channels" and may require some action on your part before a connection can be established. The Connect button will for these channels will take you to a page which lists in detail what terms the channel owner has set. If the terms are accepted, the connection will then proceed normally. In some cases, such as with celebrities and world-reknowned publishers, this may involve payment. If you do not agree to the terms, the connection will not proceed, or it may proceed but with reduced permissions allowed on your interactions with that channel. + +#include doc/macros/main_footer.bb; diff --git a/doc/member/diaspora_compat.bb b/doc/member/diaspora_compat.bb new file mode 100644 index 000000000..f27a63b9d --- /dev/null +++ b/doc/member/diaspora_compat.bb @@ -0,0 +1,68 @@ +[h3]Diaspora Compatibility[/h3] + +The Diaspora Protocol addon allows a site to communicate using the Diaspora protocol, which allows communications and connections to be made with Diaspora members (and also Friendica members, since that network also provides the Diaspora Protocol). + +This addon is available in the 'basic' and 'standard' server configurations. It is not available with and the plugin is disabled completely when you are using the 'pro' server configuration. The reason for this is that the Diaspora protocol is not very sophisticated and many $projectname features do not work well with it. + +Members will have to be aware of limitations of the protocol or limit their own activities to those which are compatible with Diaspora. The 'pro' server configuration is free from these limitations and you may use all of the project features and abilities without regard for how they translate to other networks. Many features are unique to $Projectname and are supported by the "Zot" protocol, which is our native communications language between servers/hubs. + +If you are using a configuration which allows direct Diaspora communications you should be aware of the limitations presented here. + +[ul] +[*]Private mail retraction (unsend) is not possible for Diaspora connections. + +[*]Private posts and their associated comments are sent in plaintext email notifications in Diaspora and Friendica. This is a major privacy issue and affects any private communications you have where *any* member of the conversation is on another network. Be aware of it. + +[*]Access control only works on posts and comments. Diaspora members will get permission denied trying to access any other access controlled hubzilla objects such as files, photos, webpages, chatrooms, etc. In the case of private photos that are linked to posts, they will see a "prohibited sign" instead of the photo. Diaspora has no concept of private media and provides an illusion of photo privacy by using obscured URLs rather than protecting the photo from snooping by unauthorised viewers. + +There is no workaround except to make your media resources public (to everybody on the internet). + + +[*]Edited posts will not be delivered. Diaspora members will see the original post/comment without edits. There is no mechanism in the protocol to update an existing post. We cannot delete it and submit another invisibly because the message-id will change and we need to keep the same message-id on our own network. The only workaround is to delete the post/comment and do it over. (If this is a post, this will delete any existing likes/comments). We may eventually provide a way to delete the out of date copy only from Diaspora and keep it intact on networks that can handle edits. + +[*]Nomadic identity ($projectname 'standard' only) will not work with Diaspora. We may eventually provide an **option** which will allow you to "start sharing" from all of your clones when you make the first connection. The Diaspora person does not have to accept this, but it will allow your communications to continue if they accept this connection. Without this option, if you go to another server from where you made the connection originally or you make the connection before creating the clone, you will need to connect with them again from the new location. + +[*]Post expiration is not supported on Diaspora. We may provide you an option to not send expiring posts to that network. In the future this may be provided with a remote delete request. + +[*]End-to-end encryption is not supported. We will translate these posts into a lock icon, which can never be unlocked from the Diaspora side. + +[*]Message verification will eventually be supported. + +[*]Multiple profiles are not supported. Diaspora members can only see your default profile. + +[*]Birthday events will not appear in Diaspora. Other events will be translated and sent as a post, but all times will either be in the origination channel's timezone or in GMT. We do not know the recipient's timezone because Diaspora doesn't have this concept. + +[*]We currently allow tags to be hijacked by default. An option is provided to allow you to prevent the other end of the network from hijacking your tags and point them at its own resources. + +[*]Community tags will not work. We will send a tagging activity as a comment. It won't do anything. + +[*]Privacy tags (@!somebody) will not be available to Diaspora members. These tags may have to be stripped or obscured to prevent them from being hijacked - which could result in privacy issues. + +[*]Plus-tagged hubzilla forums should work from Diaspora. + + +[*]You cannot use Diaspora channels as channel sources. + + +[*]Dislikes of posts will be converted to comments and you will have the option to send these as comments or not send them to Diaspora (which does not provide dislike). Currently they are not sent. + +[*]We will do the same for both likes and dislikes of [b][i]comments[/i][/b]. They can either be sent as comments or you will have the ability to prevent them from being transmitted to Diaspora. Currently they are not sent. + +[*]Emojis are currently untranslated. + +[*]"observer tags" will be converted to empty text. + + +[*]Embedded apps will be translated into links. + + +[*]Embedded page design elements (work in progress) will be either stripped or converted to an error message. + +[*]Diaspora members will not appear in the directory. + + +[*]There are differences in oembed compatibility between the networks. Some embedded resources will turn into a link on one side or the other. + +[/ul] + +#include doc/macros/main_footer.bb; diff --git a/doc/member/faq_admins.bb b/doc/member/faq_admins.bb new file mode 100644 index 000000000..0b54a41de --- /dev/null +++ b/doc/member/faq_admins.bb @@ -0,0 +1,78 @@ +[size=large][b]$Projectname FAQ[/b][/size] + +[toc] + +[h3]Is there a way to change the Admin account?[/h3] +[h3]Is there a way to have multiple administrators?[/h3] +Yes, but it's a bit messy at the moment as it is not yet exposed in the UI. To make an account an administrative account, +one needs to add 4096 to the account_roles entry in the account table of the database. Likewise, to remove administrative permissions, +one must subtract 4096 from the account roles. + +[h3]I can log in, but there are no posts or webpages[/h3] + +Most likely, your item table has crashed. Run the MySQL command [code]repair table item;[/code] + +[h3]Login doesn't work, immediately after login, the page reloads and I'm logged out[/h3] + +Most likely, your session table has crashed. Run the MySQL command [code]repair table session;[/code] + +[h3]When I switch theme, I sometimes get elements of one theme superimposed on top of the other[/h3] + +a) store/[data]/smarty3 isn't writeable by the webserver. Make it so. + +b) You're using Midori, or with certain themes, Konqueror in KHTML mode. + +[b]My network tab won't load, it appears to be caused by a photo or video[/h3] + +Your PHP memory limit is too low. Increase the size of the memory_limit directive in your php.ini + +Contrary to popular belief, the number of users on a hub doesn't make any difference to the required memory limit, rather, the content +of an individuals matrix counts. Streams with lots of photos and video require more memory than streams with lots of text. + +[h3]I have no communication with anybody[/h3] + +You're listening on port 443, but do not have a valid SSL certificate. Note this applies even if your baseurl is http. +Don't listen on port 443 if you cannot use it. It is strongly recommended to solve this problem by installing a browser +valid SSL certificate rather than disabling port 443. + +[h3]How do I update a non-Git install?[/h3] +1) Backup .htconfig.php +2) Backup everything in store/ +3) Backup any custom changes in mod/site/ and view/site +3) Delete your existing installation +4) Upload the new version. +5) Upload the new version of themes and addons. +6) Restore everything backed up earlier. + +[h3]What do I need to do when moving my hub to a different server[/h3] + +1) Git clone on the new server. Repeat the process for any custom themes, and addons. +2) Rsync .htconfig.php +3) Rsync everything in store/ +4) Rsync everything in mod/site/ and view/site (these will only exist if you have custom modules) +5) Dump and restore DB. + +[h3]How do I reinstall an existing hub on the same server?[/h3] + +1) [code]git reset --hard HEAD[/code] will reset all files to their upstream defaults. This will not reset any local files that do not also exist upstream. Eg, if you have local changes to mod/channel.php, this will reset them - but will not reset any changes in mod/site/channel.php +2) If you absolutely must reinstall - for example, if you need to upgrade operating system - follow the steps for moving to a different server, but instead of using rsync, backup and restore some other way. + +Do not reinstall a hub with a fresh database and fresh .htconfig.php unless as a very last resort. Creating a temporary account and ask for help via a support channel for non-trivial reinstalls is preferable to reinstalling fresh. + +[h3]How do I set the default homepage for logged out viewers?[/h3] + +Use the custom_home addon available in the main addons repository. + +[h3]What do the different directory mode settings mean?[/h3] +[code]// Configure how we communicate with directory servers. +// DIRECTORY_MODE_NORMAL = directory client, we will find a directory (all of your member's queries will be directed elsewhere) +// DIRECTORY_MODE_SECONDARY = caching directory or mirror (keeps in sync with realm primary [adds significant cron execution time]) +// DIRECTORY_MODE_PRIMARY = main directory server (you do not want this unless you are operating your own realm. one per realm.) +// DIRECTORY_MODE_STANDALONE = "off the grid" or private directory services (only local site members in directory) +[/code] +- The default is NORMAL. This off-loads most directory services to a different server. The server used is the config:system/directory_server. This setting MAY be updated by the code to one of the project secondaries if the current server is unreachable. You should either be in control of this other server, or should trust it to use this setting. +- SECONDARY. This allows your local site to act as a directory server without exposing your member's queries to another server. It requires extra processing time during the cron polling, and is not recommended to be run on a shared web host. +- PRIMARY. This allows you to run a completely separate 'Network' of directory servers with your own Realm. By default, all servers are on the RED_GLOBAL realm unless the config:system/directory_realm setting is overridden. [i]Do not use this unless you have your own directory_realm.[/i] +- STANDALONE. This is like primary, except it's a 'Network' all on it's own without talking to any other servers. Use this if you have only one server and want to be segregated from the Red#Matrix directory listings. + +#include doc/macros/main_footer.bb; diff --git a/doc/member/first-post.bb b/doc/member/first-post.bb new file mode 100644 index 000000000..cf6ed5b49 --- /dev/null +++ b/doc/member/first-post.bb @@ -0,0 +1,3 @@ +[size=large]Your first posting[/size] + +... to be written ... diff --git a/doc/member/overview.bb b/doc/member/overview.bb new file mode 100644 index 000000000..0dc71aa96 --- /dev/null +++ b/doc/member/overview.bb @@ -0,0 +1,26 @@ +[h2]Documentation for hub members[/h2] +While many features and capabilities of Hubzilla are familiar to people who have used social networking sites and blogging software, there are also quite a few new concepts and features that most people have not encountered before. Some of the new ideas are related to the [b]decentralized[/b] nature of the grid; others are associated with the advanced [b]permissions system[/b] that is necessary to protect your data privacy. The purpose of this guide is to help you understand how to create, configure, and use your nomadic identity. +[h3]Getting started[/h3] +[zrl=[baseurl]/help/registration]Account Registration[/zrl] +[zrl=[baseurl]/help/accounts_profiles_channels_basics]You at $Projectname: accounts, profiles and channels in short[/zrl] +[zrl=[baseurl]/help/profiles]Profiles[/zrl] +[zrl=[baseurl]/help/channels]Channels[/zrl] +[zrl=[baseurl]/help/roles]Permission roles and Channel types[/zrl] +[zrl=[baseurl]/help/first-post]Your first posting[/zrl] +[zrl=[baseurl]/help/connecting_to_channels]Connecting To Other Channels[/zrl] +[zrl=[baseurl]/help/permissions]Permissions And Encryption: You Are In Control[/zrl] +[zrl=[baseurl]/help/cloud]Cloud Storage[/zrl] +[zrl=[baseurl]/help/remove_account]Remove Channel or Account[/zrl] +[h3]Members help[/h3] +[zrl=[baseurl]/help/tags_and_mentions]Tags and Mentions[/zrl] +[zrl=[baseurl]/help/webpages]Web Pages[/zrl] +[zrl=[baseurl]/help/bbcode]BBcode reference for posts and comments[/zrl] +[zrl=[baseurl]/help/checking_account_quota_usage]Checking Account Quota Usage[/zrl] +[zrl=[baseurl]/help/cloud_desktop_clients]Cloud Desktop Clients[/zrl] +[zrl=[baseurl]/help/AdvancedSearch]Advanced Directory Search[/zrl] +[zrl=[baseurl]/help/addons]Help With Addons[/zrl] +[zrl=[baseurl]/help/diaspora_compat]Diaspora Communications Compatibility (Diaspora and Friendica)[/zrl] +[zrl=[baseurl]/help/faq_members]FAQ For Members[/zrl] +[zrl=[baseurl]/help/bugs]Bugs, Issues, and things that go bump in the night...[/zrl] + +#include doc/macros/main_footer.bb; diff --git a/doc/member/permissions.bb b/doc/member/permissions.bb new file mode 100644 index 000000000..0721c763d --- /dev/null +++ b/doc/member/permissions.bb @@ -0,0 +1,82 @@ +[h1]Permissions[/h1] +Permissions in $Projectname are more complete than you may be used to. This allows us to define more fine graded relationships than the black and white "this person is my friend, so they can do everything" or "this person is not my friend, so they can't do anything" permissions you may find elsewhere. + +[b]Permission Roles[/b] + +When you create a channel we allow you to select different 'roles' for that channel. These create an entire family of permissions and privacy settings that are appropriate for that role. Typical roles are "Social - mostly public", "Social - mostly private", "Forum - public" and many others. These bring a level of simplicity to managing permissions. Just choose a role and appropriate permissions are automatically applied. You can also choose 'Custom/Expert mode' and change any individual permission setting in any way you desire. + + +[b]Default Permission Limits[/b] + +There are a large number of individual permissions. These control everything from the ability to view your stream to the ability to chat with you. Every permission has a limit. The scope of these permissions varies from "Only me" to "Everybody on the internet" - though some scopes may not be available for some permissions. The limit applies to any published thing you create which has no privacy or access control. For example if you publish a photo and didn't select a specific audience with permission to view it, we apply the limit. These limits apply to everything within that permission rule, so you cannot apply a limit to one photo. The limit applies to all your photos. If all your photos are visible to everybody on the internet and you reduce the limit only to friends, [b]all[/b] of your photos will now be visible only to friends. + +[b]Access Control[/b] + +Access Control is the preferred method of managing privacy in [i]most[/i] cases, rather than using permission limits. This creates lists of either connections or privacy groups (or both) and uses the access list to decide if a permission is allowed. An access list is attached to everything you publish. Unlike permission limits, if you change the access control list on a single photo, it doesn't affect any of your other photos. You can use privacy groups and a "default access control list" to create and automate the management of access control lists to provide any level of privacy you desire on anything you publish. + +We highly recommend that you use the "typical social network" settings when you create your first channel, as it allows others to communicate with you and help you out if you have difficulty. You will find that these settings allow you as much privacy as you desire - when you desire it; but also allow you to communicate in public if you choose to. You are free to use much more private settings once you have learned your way around. + + +[dl terms="l"] +[*= The scopes of permissions are:] +[dl terms="i"] + [*= Nobody Except Yourself ] This is self explanatory. Only you will be allowed access. + + [*= Only those you specifically allow ] By default, people you are not connected to, and all new contacts will have this permission denied. You will be able to make exceptions for individual channels on their contact edit screen. + + [*= Anybody in your address book ] Anybody you do not know will have this permission denied, but anybody you accept as a contact will have this permission approved. This is the way most legacy platforms handle permissions. + + [*= Anybody On This Hub ] Anybody with a channel on the same hub/website as you will have permission approved. Anybody who is registered at a different hub will have this permission denied. + + [*= Anybody in this network ] Anybody in $Projectname will have this permission approved. Even complete strangers. However, anybody not logged in/authenticated will have this permission denied. + + [*= Anybody authenticated ] This is similar to "anybody in this network" except that it can include anybody who can authenticate by any means - and therefore [i]may[/i] include visitors from other networks. + + [*= Anybody on the internet ] Completely public. This permission will be approved for anybody at all. +[/dl] +[*= The individual permissions are:] +[dl terms="i"] + [*= Can view my "public" stream and posts. ] This permision determines who can view your channel "stream" that is, the non-private posts that appear on the "home" tab when you're logged in. + + [*= Can view my "public" channel profile. ] This permission determines who can view your channel's profile. This refers to the "about" tab + + [*= Can view my "public" photo albums. ] This permission determines who can view your photo albums. Individual photographs may still be posted to a more private audience. + + [*= Can view my "public" address book. ] This permission determines who can view your contacts. These are the connections displayed in the "View connections" section. + + [*= Can view my "public" file storage. ] This permission determines who can view your public files stored in your cloud. + + [*= Can view my "public" pages. ] This permission determines who can view your public web pages. + + [*= Can send me their channel stream and posts. ] This permission determines whose posts you will view. If your channel is a personal channel (ie, you as a person), you would probably want to set this to "anyone in my address book" at a minimum. A personal notes channel would probably want to choose "nobody except myself". Setting this to "Anybody in the network" will show you posts from complete strangers, which is a good form of discovery. + + [*= Can post on my channel page ("wall"). ] This permission determines who can write to your wall when clicking through to your channel. + + [*= Can comment on my posts. ] This permission determines who can comment on posts you create. Normally, you would want this to match your "can view my public stream and posts" permission + + [*= Can send me private mail messages. ] This determines who can send you private messages (zotmail). + + [*= Can post photos to my photo albums. ] This determines who can post photographs in your albums. This is very useful for forum-like channels where connections may not be connected to each other. + + [*= Can forward to all my channel contacts via post tags. ] Using @- mentions will reproduce a copy of your post on the profile specified, as though you posted on the channel wall. This determines if people can post to your channel in this way. + + [*= Can chat with me (when available). ] This determines who can join the public chat rooms created by your channel. + + [*= Can write to my "public" file storage. ] This determines who can upload files to your public file storage, or 'cloud'. + + [*= Can edit my "public" pages. ] This determines who can edit your webpages. This is useful for wikis or sites with multiple editors. + + [*= Can administer my channel resources. ] This determines who can have full control of your channel. This should normally be set to "nobody except myself". +[/dl][/dl] +[i]Note:[/i] +Plugins/addons may provide special permission settings, so you may be offered additional permission settings beyond what is described here. + +If you have set any of these permissions to "only those I specifically allow", you may specify indivudal permissions on the connnection edit screen. + +[b]Affinity[/b] + +The connection edit screen offers a slider to select a degree of friendship with the connnection (this tool is enabled through the "Extra Features" tab of your Settings page). Think of this as a measure of how much you like or dislike them. 1 is for people you like, whose posts you want to see all the time. 99 is for people you don't care for, and whose posts you might only wish to look at occasionally. Once you've assigned a value here, you can use the affinity tool on the matrix page to filter content based on this number. + +The slider on the matrix page has both a minimum and maximum value. Posts will only be shown from people who fall between this range. Affinity has no relation to permissions, and is only useful in conjunction with the affinity tool feature. + +#include doc/macros/main_footer.bb; diff --git a/doc/member/profiles.bb b/doc/member/profiles.bb new file mode 100644 index 000000000..513bf5fed --- /dev/null +++ b/doc/member/profiles.bb @@ -0,0 +1,37 @@ +[b]Profiles[/b] + +$Projectname has unlimited profiles. You may use different profiles to show different "sides of yourself" to different audiences. This is different to having different channels. Different channels allow for completely different sets of information. You may have a channel for yourself, a channel for your sports team, a channel for your website, or whatever else. A profile allows for finely graded "sides" of each channel. For example, your default public profile might say "Hello, I'm Fred, and I like laughing". You may show your close friends a profile that adds "and I also enjoy dwarf tossing". + +You always have a profile known as your "default" or "public" profile. This profile is always available to the general public and cannot be hidden (there may be rare exceptions on privately run or disconnected sites). You may, and probably should restrict the information you make available on your public profile. + +That said, if you want other friends to be able to find you, it helps to have the following information in your public profile... + +[ul][*]Your real name or at least a nickname everybody knows +[*]A photo of you +[*]Your location on the planet, at least to a country level.[/ul] + +In addition, if you'd like to meet people that share some general interests with you, please take a moment and add some "Keywords" to your profile. Such as "music, linux, photography" or whatever. You can add as many keywords as you like. + +To create an alternate profile, first go to [zrl=[baseurl]/settings/features]Settings > Additional Features[/zrl] and enable "Multiple Profiles" there, otherwise you won't have the ability to use more than just your default profile. + +Then select "Edit Profiles" from the menu of your $Projectname site. You may edit an existing profile, change the profile photo, add things to a profile or create a new profile. You may also create a "clone" of an existing profile if you only wish to change a few items but don't wish to enter all the information again. To do that, click on the profile you want to clone and choose "Clone this profile" there. + +In the list of your profiles, you can also choose the contacts who can see a specific profile. Just click on "Edit visibility" next to the profile in question (only available for the profiles that are not your default profile) and then click on user images to add them to or remove them from the group of people who can see this profile. + +Once a profile has been selected, when the person views your profile, they will see the private profile you have assigned. If they are not authenticated, they will see your public profile. + +There is a setting which allows you to publish your profile to a directory and ensure that it can be found by others. You can change this setting on the "Settings" page. + +If you do not wish to be found be people unless you give them your channel address, you may leave your profile unpublished. + +[b]Keywords and Directory Search[/b] + +On the directory page, you may search for people with published profiles. Currently, only the name field and the keywords are searched. You may also include such keywords in your default profile - which may be used to search for common interests with other members. Keywords are used in the channel suggestion tool and although they aren't visible in the directory, they are shown if people visit your profile page. + +On your Connnections page and in the directory there is a link to "Suggestions" or "Channel Suggestions", respectively. This will find channels who have matching and/or similar keywords. The more keywords you provide, the more relevant the search results that are returned. These are sorted by relevance. + +See Also + +[zrl=[baseurl]/help/AdvancedSearch]Advanced Searching[/zrl] + +#include doc/macros/main_footer.bb; diff --git a/doc/member/registration.bb b/doc/member/registration.bb new file mode 100644 index 000000000..f656eeaa6 --- /dev/null +++ b/doc/member/registration.bb @@ -0,0 +1,35 @@ +[size=large][b]Registration[/b][/size] + +Not all $Projectname sites allow open registration. If registration is allowed, you will see a "Register" link immediately below the login prompts on the site home page. Following this link will take you to the site Registration page. On some sites it may redirect you to another site which allow registrations. As all $Projectname sites are linked, it does not matter where your account resides. + +[b]Your Email Address[/b] + +Please provide a valid email address. Your email address is never published. This address will be used to activate your account, to (optionally) send email notifications for incoming messages or items, [i]and to recover lost passwords[/i]. + +[b]Password[/b] + +Enter a password of your choice, and repeat it in the second box to ensure it was typed correctly. As $Projectname offers a decentralised identity, your account can log you in to many other websites. + +[b]Terms Of Service[/b] + +Click the link to read the site's [zrl=[baseurl]/help/TermsOfService]Terms of Service[/zrl]. Once you've read them, tick the box in the register form to confirm. + +[b]Register[/b] + +Once you have provided the necessary details, click the 'Register' button. Some sites may require administrator approval before the registration is processed, and you will be alerted if this is the case. Please watch your email (including spam folders) for your registration approval. + +[b]Create a Channel[/b] + +Next, you will be presented with the "Add a channel" screen. Normally, your first channel will be one that represents you - so using your own name (or psuedonym) as the channel name is a good idea. The channel name should be thought of as a title, or brief description of your channel. The "choose a short nickname" box is similar to a "username" field. We will use whatever you enter here to create a channel address, which other people will use to connect to you, and you will use to log in to other sites. This looks like an email address, and takes the form nickname@siteyouregisteredat.xyz + +When your channel is created you will be taken straight to your settings page where you can define permissions, enable features, etc. All these things are covered in the appropriate section of the helpfiles. + +See Also +[zrl=[baseurl]/help/accounts_profiles_channels_basics]The Basics about Identities within $Projectname[/zrl] +[zrl=[baseurl]/help/accounts]Accounts[/zrl] +[zrl=[baseurl]/help/profiles]Profiles[/zrl] +[zrl=[baseurl]/help/permissions]Permissions[/zrl] +[zrl=[baseurl]/help/remove_account]Remove Account[/zrl] + +#include doc/macros/main_footer.bb; + diff --git a/doc/member/remove_account.bb b/doc/member/remove_account.bb new file mode 100644 index 000000000..704f0b94c --- /dev/null +++ b/doc/member/remove_account.bb @@ -0,0 +1,27 @@ +[b]Remove Channel or Account[/b] + +[b]Remove Channel[/b] + +Go to the bottom of your channel settings page or visit the URL: + + [baseurl]/removeme + +You will need to confirm your password and the channel you are currently logged into will be removed. + +This is irreversible. + +If you have identity clones on other hubs this only removes by default the channel instance which exists on this hub. + +[b]Remove Account[/b] + +Go to the bottom of your account settings page or visit the URL: + + [baseurl]/removeaccount + +You will need to confirm your password and the account you are currently logged into will be removed. + +This is irreversible. + +All your channels will be deleted. If you have identity clones on other hubs this only removes by default the channels instances which exists on this hub. + +#include doc/macros/main_footer.bb; diff --git a/doc/member/roles.md b/doc/member/roles.md new file mode 100644 index 000000000..a7608ff90 --- /dev/null +++ b/doc/member/roles.md @@ -0,0 +1,66 @@ +Account Permission Roles +======================== + + +##Social + +**Mostly Public** + +The channel is a typical social networking profile. By default posts and published items are public, but one can over-ride this when creating the item and restrict it. You are listed in the directory. Your online presence and connections are visible to others. + + +**Restricted** + +By default all posts and published items are sent to your 'Friends' privacy group and not made public. New friends are added to this privacy group. You can over-ride this and create a public post or published item if you desire. You are listed in the directory. Your online presence (for chat) and your connections (friends) are visible to your profile viewers. + +**Private** + +By default all posts and published items are sent to your 'Friends' privacy group. New friends are added to this privacy group. You can over-ride this and create a public post or public item if you desire. You are NOT listed in the directory. Only your connections can see your other connections. Your online presence is hidden. + + +##Forum + +**Mostly Public** + +The channel is a typical forum. By default posts and published items are public. Members may post by @mention+ or wall-to-wall post. Posting photos and other published items is blocked. The channel is visible in the directory. Members are added automatically. + + +**Restricted** + +By default all posts and published items are sent to the channel's 'Friends' privacy group. New friends are added to this privacy group. Members may post by @mention+ or wall-to-wall post, but posts and replies may also be seen by other receipients of the top-level post who are not members. The channel is visible in the directory. Members must be manually added by the forum owner. + +**Private** + +By default all posts and published items are sent to your 'Friends' privacy group. New friends are added to this privacy group. The owner can over-ride this and create a public post or public item if desired. Members cannot. You are NOT listed in the directory. Only your connections can see your other connections. Your online presence is hidden. Members must be manually added by the forum owner. Posting by @mention+ is disabled. Posts can only be made via wall-to-wall posts, and sent to members of the 'Friends' privacy group. They are not publicly visible. + + +##Feed + + +**Public** + +Similiar to Social - Mostly Public, but tailored for RSS feed sources. Items may be freely republished and sourced. Online presence is meaningless, therefore hidden. New connections are automatically approved. + + +**Restricted** + +Not listed in directory. Online presence is meaningless, therefore hidden. Feed is published only to members of the 'Friends' privacy group. New connections are automatically added to this privacy group. Members must be manually approved by the channel owner. + + +##Special + +**Celebrity/Soapbox** + +Listed in directory. Communications are by default public. Online presence is hidden. No commenting or feedback of any form is allowed, though connections have the ability to "like" your profile. + + +**Group Repository** + +A public forum which allows members to post files/photos/webpages. + + +##Custom/Expert Mode + +Set all the privacy and permissions manually to suit your specific needs. + +#include doc/macros/main_footer.bb; diff --git a/doc/member/tags_and_mentions.bb b/doc/member/tags_and_mentions.bb new file mode 100644 index 000000000..29dfe0fbe --- /dev/null +++ b/doc/member/tags_and_mentions.bb @@ -0,0 +1,69 @@ +[b]Tags And Mentions[/b] + +Like many other platforms, Red uses a special notation inside messages to indicate "tags" or contextual links to other entities. + +[b]Mentions[/b] + +Channels are tagged by simply preceding their name with the @ character. + +[code] +@Jack +[/code] + +When you start to mention somebody, it will create an auto-complete box to select from your immediate connections. Select one as appropriate. + +If the person mentioned is in the list of recipients for the post, they will receive a tag notification. + + +[b]Deliverable Mentions[/b] + +Some connections in the mention auto-complete box behave differently than others. If you mention a channel which provides "re-delivery of mentions" it will also send the post to all of that channel's default delivery connections. This is how one posts to "forums". The auto-complete box will provide two entries for these channels, one will mention just the channel. The other will invoke re-delivery and be listed as the channel's "network". + +[code] +@Gardening - mention the Gardening forum +[/code] + +[code] +@Gardening+ - mention the Gardening Forum and also post to the Gardening "network" (e.g. all the forum members; if you have permission to do so) +[/code] + + + +[b]Private Mentions[/b] + +If you wish to restrict a post to a single person or a number of people, you can do this by selecting channels or privacy groups from the privacy tool. You can also just tag them with a privacy tag. A privacy tag is a name preceded by the two characters @! - and in addition to tagging these channels, will also change the privacy permissions of the post to only include them. You can have more than one privacy tag, for instance @!bob and @!linda will send the post only to Bob and Linda. This mechanism over-rides the privacy selector. + +You may also tag privacy groups which are "public". When you create or edit a privacy group, there is a checkbox to allow the group members to be seen by others. If this box is checked for a group and you tag (for instance) @!Friends - the post will be restricted to the Friends group. Check that the group is public before doing this - as there is no way to take back a post except to delete it. The group name will appear in the post and will alert members of that group that they are members of it. + + +[b]Mentions and Comments[/b] + +The above mechanisms only apply to "top-level" posts you create. Mentioning a channel with any of the above mechanisms has no effect in comments, except that the mentioned channel may receive a notification if they were already included as a recipient in the conversation. + + + + +[b]Topical Tags[/b] + +Topical tags are indicated by preceding the tag name with the # character. This will create a link in the post to a generalised site search for the term provided. For example, #[zrl=https://friendicared.net/search?tag=cars]cars[/zrl] will provide a search link for all posts mentioning 'cars' on your site. Topical tags are generally a minimum of three characters in length. Shorter search terms are not likely to yield any search results, although this depends on the database configuration. + +Topical tags are also not linked if they are purely numeric, e.g. #1. If you wish to use a numeric hashtag, please add some descriptive text such as #[zrl=https://friendicared.net/search?tag=2012-elections]2012-elections[/zrl]. + + +[b]Spaces in Tags and Mentions[/b] + +Where possible please use the auto-complete window to select tag and mention recipients, because it will generate a coded tag which uniquely identifies one channel. Names are sometimes ambiguous. However, you can "manually" tag a channel by matching the channel name or address. + +[code] +@Robert Johnson +[/code] + +will tag Robert Johnson, but we can only match one space. If the name was "Blind Lemon Jefferson" it won't be found unless you enclose the entire name in double quotes or change the spaces to underscores. + +[code] +@"Blind Lemon Jefferson" +@Blind_Lemon_Jefferson +[/code] + +are both equivalent. +#include doc/macros/main_footer.bb; diff --git a/doc/member/toc.html b/doc/member/toc.html new file mode 100644 index 000000000..6963c5ba9 --- /dev/null +++ b/doc/member/toc.html @@ -0,0 +1,25 @@ +

Member Guide

+ diff --git a/doc/member/webpages.bb b/doc/member/webpages.bb new file mode 100644 index 000000000..2b909dc63 --- /dev/null +++ b/doc/member/webpages.bb @@ -0,0 +1,93 @@ +[b]Creating Web Pages[/b] + +Hubzilla enables users to create static webpages. To activate this feature, enable the web pages feature in your Additional Features section. + +Once enabled, a new tab will appear on your channel page labelled "Webpages". Clicking this link will take you to the webpage editor. +Pages will be accessible at mydomain/page/username/pagelinktitle + +The "page link title" box allows a user to specify the "pagelinktitle" of this URL. If no page link title is set, we will set one for you automatically, using the message ID of the item. + +Beneath the page creation box, a list of existing pages will appear with an "edit" link. Clicking this will take you to an editor, similar to that of the post editor, where you can make changes to your webpages. + +See also: + +[zrl=[baseurl]/help/webpage-element-import]Webpage element import tool[/zrl] + +[b]Using Blocks[/b] + +Blocks can be parts of webpages. The basic HTML of a block looks like this +[code] +
+ Block Content +
+ +[/code] + +If a block has text/html content type it can also contain menu elements. Sample content of +[code] +

HTML block content

+ [menu]menuname[/menu] + +[/code] +will produce HTML like this +[code] +
+

HTML block content

+
+ +
+
+ +[/code] + +Via the $content macro a block can also contain the actual webpage content. For this create a block with only +[code] + $content + +[/code]as content. + +To make a block appear in the webpage it must be defined in the page layout inside a region. +[code] + [region=aside] + [block]blockname[/block] + [/region] + +[/code] + +The block appearance can be manipulated in the page layout. + +Custom classes can be assigned +[code] + [region=aside] + [block=myclass]blockname[/block] + [/region] + +[/code] +will produce this HTML +[code] +
+ Block Content +
+ +[/code] + +Via the wrap variable a block can be stripped off its wrapping
tag +[code] + [region=aside] + [block][var=wrap]none[/var]blockname[/block] + [/region] + +[/code] +will produce this HTML +[code] + Block Content + +[/code] + + +#include doc/macros/main_footer.bb; + diff --git a/doc/toc.html b/doc/toc.html index ac21959cf..90f0cbaeb 100644 --- a/doc/toc.html +++ b/doc/toc.html @@ -1,6 +1,6 @@ diff --git a/view/js/main.js b/view/js/main.js index 96adf0be3..e78725931 100644 --- a/view/js/main.js +++ b/view/js/main.js @@ -444,16 +444,18 @@ function contextualHelp() { } function contextualHelpFocus(target, openSidePanel) { - if (openSidePanel) { - $("main").addClass('region_1-on'); // Open the side panel to highlight element - } - else { - $("main").removeClass('region_1-on'); - } - $('html,body').animate({ scrollTop: $(target).offset().top - $('nav').outerHeight(true) - $('#contextual-help-content').outerHeight(true)}, 'slow'); - for (i = 0; i < 3; i++) { - $(target).fadeTo('slow', 0.1).fadeTo('slow', 1.0); - } + if($(target).length) { + if (openSidePanel) { + $("main").addClass('region_1-on'); // Open the side panel to highlight element + } + else { + $("main").removeClass('region_1-on'); + } + $('html,body').animate({ scrollTop: $(target).offset().top - $('nav').outerHeight(true) - $('#contextual-help-content').outerHeight(true)}, 'slow'); + for (i = 0; i < 3; i++) { + $(target).fadeTo('slow', 0.1).fadeTo('slow', 1.0); + } + } } function updatePageItems(mode, data) { -- cgit v1.2.3 From 165a6d34b2c3869ca3f5244a81a612ee549afbc7 Mon Sep 17 00:00:00 2001 From: Andrew Manning Date: Sat, 26 Nov 2016 20:48:05 -0700 Subject: Update webpages and wiki context help --- doc/context/en/webpages/help.html | 4 ++-- doc/context/en/wiki/help.html | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/context/en/webpages/help.html b/doc/context/en/webpages/help.html index af57ee88a..a4817e4bf 100644 --- a/doc/context/en/webpages/help.html +++ b/doc/context/en/webpages/help.html @@ -3,6 +3,6 @@
You can create modular, identity-aware websites composed of shareable elements.
Pages
This page lists your "pages", which are assigned URLs where people can visit your site. The structure of pages are typically described by an associated layout, and their content is constructed from a collection of blocks.
-
Website import tool
-
The website import tool allows you import multiple webpage elements (pages, layouts, blocks) either from an uploaded zip file or from an existing cloud files folder. Read more...
+
Website portation tools
+
The website portation tools allows you import/export multiple webpage elements (pages, layouts, blocks). You can import either from an uploaded zip file or from an existing cloud files folder. You can export to either a zip file containing a select group of webpage elements in a form compatible with the import tool, or you can export directly to a cloud files folder. Read more...
\ No newline at end of file diff --git a/doc/context/en/wiki/help.html b/doc/context/en/wiki/help.html index a42914c17..5ac9b22ae 100644 --- a/doc/context/en/wiki/help.html +++ b/doc/context/en/wiki/help.html @@ -7,4 +7,6 @@
Every revision of a page is saved to allow quick reversion. Click the History tab to view a history of page revisions, including the date and author of each. The revert button will load the selected revision but will not automatically save the page.
Pages
The list of pages in the wiki are listed in the Wiki Pages panel. Prior to saving page edits using the Page control dropdown menu, you may enter a custom message to be displayed in the Page History viewer along with the revision.
+
Channel Content Tabs
+
The channel content tabs are links to other content published by the channel. The About tab links to the channel profile. The Photos tab links to the channel photo galleries. The Files tab links to the general shared files published by the channel.
\ No newline at end of file -- cgit v1.2.3 From 713a34c68e242c5bee927f3de41fffaeb2842bf1 Mon Sep 17 00:00:00 2001 From: Andrew Manning Date: Sun, 27 Nov 2016 08:34:23 -0700 Subject: Restructured main table of contents to link to fewer pages with more content. The admin, dev, and member guides are single pages each having a table of contents at the top that is represented in condensed form in the main navigation sidebar. Section links are used to navigate between content sections for simplicity and fewer page loads. --- doc/about/about_hubzilla.html | 24 ++ doc/admin/administrator_guide.html | 346 +++++++++++++++++++++++++++ doc/developer/developer_guide.html | 473 +++++++++++++++++++++++++++++++++++++ doc/member/member_guide.html | 18 ++ doc/member/toc.html | 25 -- doc/toc.html | 110 ++++++++- 6 files changed, 965 insertions(+), 31 deletions(-) create mode 100644 doc/about/about_hubzilla.html create mode 100644 doc/admin/administrator_guide.html create mode 100644 doc/developer/developer_guide.html create mode 100644 doc/member/member_guide.html delete mode 100644 doc/member/toc.html diff --git a/doc/about/about_hubzilla.html b/doc/about/about_hubzilla.html new file mode 100644 index 000000000..ec3c69307 --- /dev/null +++ b/doc/about/about_hubzilla.html @@ -0,0 +1,24 @@ +

Table of Contents

+ + + +
+ +

Project

+

+ Hubzilla is a decentralized communication network, which aims to provide communication that is censorship-resistant, privacy-respecting, and thus free from the oppressive claws of contemporary corporate communication giants. These giants function primarily as spy networks for paying clients of all sorts and types, in addition to monopolizing and centralizing the Internet; a feature that was not part of the original and revolutionary goals that produced the World Wide Web.

Hubzilla is free and open source.  It is designed to scale from a $35 Raspberry Pi, to top of the line AMD and Intel Xeon-powered multi-core enterprise servers.  It can be used to support communication between a few individuals, or scale to many thousands and more.

Hubzilla aims to be skill and resource agnostic. It is easy to use by everyday computer users, as well as by systems administrators and developers.

How you use it depends on how you want to use it.

It is written in the PHP scripting language, thus making it trivial to install on any hosting platform in use today. This includes self-hosting at home, at hosting providers such as Media Temple and Dreamhost, or on virtual and dedicated servers, offered by the likes of Linode,  GreenQloud or Amazon AWS.

In other words, Hubzilla can run on any computing platform that comes with a web server, a MySQL-compatible database, and the PHP scripting language.

Along the way, Hubzilla offers a number of unique goodies:

Single-click user identification: meaning you can access sites on Hubzilla simply by clicking on links to remote sites. Authentication just happens automagically behind the scenes. Forget about remembering multiple user names with multiple passwords when accessing different sites online.

Cloning: of online identities. Your online presence no longer has to be tied to a single server, domain name or IP address.  You can clone and import your identity (or channel as we call it) to another server (or, a hub as servers are known in Hubzilla).  Now, should your primary hub go down, no worries, your contacts, posts*, and messages* will automagically continue to be available and accessible under your cloned channel. (*: only posts and messages as from the moment you cloned your channel)

Privacy: Hubzilla identities (Zot IDs) can be deleted, backed up/downloaded, and cloned.  The user is in full control of their data. Should you decide to delete all your content and erase your Zot ID, all you have to do is click on a link and it's immediately deleted from the hub.  No questions, no fuss. +

+ +

Features

+

+ Hubzilla in a Nutshell

TL;DR

Hubzilla provides distributed web publishing and social communications with decentralised permissions.

So what exactly are "decentralised permissions"? They give me the ability to share something on my website (photos, media, files, webpages, etc.) with specific people on completely different websites - but not necessarily everybody on those websites; and they do not need a password on my website and do not need to login to my website to view the things I've shared with them. They have one password on their own website and "magic authentication" between affiliated websites in the network. Also, as it is decentralised, there is no third party which has the ability to bypass permissions and see everything in the network.

Hubzilla combines many features of traditional blogs, social networking and media, content management systems, and personal cloud storage into an easy to use framework. Each node in the grid can operate standalone or link with other nodes to create a super-network; leaving privacy under the control of the original publisher.

Hubzilla is an open source webserver application written originally in PHP/MySQL and is easily installable by those with basic website administration skills. It is also easily extended via plugins and themes and other third-party tools.

Hubzilla Features


Hubzilla is a general-purpose web publishing and communication network, with several unique features.  It is designed to be used by the widest range of people on the web, from non-technical bloggers, to expert PHP programmers and seasoned systems administrators.

This page lists some of the core features of Hubzilla that are bundled with the official release.  As with most free and open source software, there may be many other extensions, additions, plugins, themes and configurations that are limited only by the needs and imagination of the members.

Built for Privacy and Freedom

One of the design goals of Hubzilla is to enable easy communication on the web, while preserving privacy, if so desired by members. To achieve this goal, Hubzilla includes a number of features allowing arbitrary levels of privacy:

Affinity Slider

When adding connnections in Hubzilla, members have the option of assigning "affinity" levels (how close your friendship is) to the new connection.  For example, when adding someone who happens to be a person whose blog you follow, you could assign their channel an affinity level of "Acquaintances".

On the other hand, when adding a friend's channel, they could be placed under the affinity level of "Friends".

At this point, Hubzilla Affinity Slider tool, which usually appears at the top of your "Matrix" page, adjusts the content on the page to include those within the desired affinity range. Channels outside that range will not be displayed, unless you adjust the slider to include them.

The Affinity Slider allows instantaneous filtering of large amounts of content, grouped by levels of closeness.

Connection Filtering

You have the ability to control precisely what appears in your stream using the optional "Connection Filter". When enabled, the Connection Editor provides inputs for selecting criteria which needs to be matched in order to include or exclude a specific post from a specific channel. Once a post has been allowed, all comments to that post are allowed regardless of whether they match the selection criteria. You may select words that if present block the post or ensure it is included in your stream. Regular expressions may be used for even finer control, as well as hashtags or even the detected language of the post.  

Access Control Lists

When sharing content, members have the option of restricting who sees the content.  By clicking on the padlock underneath the sharing box, one may choose desired recipients of the post, by clicking on their names.

Once sent, the message will be viewable only by the sender and the selected recipients.  In other words, the message will not appear on any public walls.

Access Control Lists may be applied to content and posts, photos, events, webpages, chatrooms and files.

Single Sign-on

Access Control Lists work for all channels in the grid due to our unique single sign-on technology. Most internal links provide an identity token which can be verified on other Hubzilla sites and used to control access to private resources. You login once to your home hub. After that, authentication to all Hubzilla resources is "magic".


WebDAV enabled File Storage

Files may be uploaded to your personal storage area using your operating system utilities (drag and drop in most cases). You may protect these files with Access Control Lists to any combination of Hubzilla members (including some third party network members) or make them public.

Photo Albums

Store photos in albums. All your photos may be protected by Access Control Lists.

Events Calendar

Create and manage events and tasks, which may also be protected with Access Control Lists. Events can be imported/exported to other software using the industry standard vcalendar/iCal format and shared in posts with others. Birthday events are automatically added from your friends and converted to your correct timezone so that you will know precisely when the birthday occurs - no matter where you are located in the world in relation to the birthday person. Events are normally created with attendance counters so your friends and connections can RSVP instantly.

Chatrooms

You may create any number of personal chatrooms and allow access via Access Control Lists. These are typically more secure than XMPP, IRC, and other Instant Messaging transports, though we also allow using these other services via plugins.      

Webpage Building

Hubzilla has many "Content Management" creation tools for building webpages, including layout editing, menus, blocks, widgets, and page/content regions. All of these may be access controlled so that the resulting pages are private to their intended audience.

Apps

Apps may be built and distributed by members. These are different from traditional "vendor lockin" apps because they are controlled completely by the author - who can provide access control on the destination app pages and charge accordingly for this access. Most apps in Hubzilla are free and can be created easily by those with no programming skills.

Layout

Page layout is based on a description language called Comanche. Hubzilla is itself written in Comanche layouts which you can change. This allows a level of customisation you won't typically find in so-called "multi-user environments".

Bookmarks

Share and save/manage bookmarks from links provided in conversations.    


Private Message Encryption and Privacy Concerns

Private mail is stored in an obscured format. While this is not bullet-proof it typically prevents casual snooping by the site administrator or ISP.  

Each Hubzilla channel has it's own unique set of private and associated public RSA 4096-bit keys, generated when the channels is first created. This is used to protect private messages and posts in transit.

Additionally, messages may be created utilising "end-to-end encryption" which cannot be read by Hubzilla operators or ISPs or anybody who does not know the passcode.

Public messages are generally not encrypted in transit or in storage.  

Private messages may be retracted (unsent) although there is no guarantee the recipient hasn't read it yet.

Posts and messages may be created with an expiration date, at which time they will be deleted/removed on the recipient's site.  


Service Federation

In addition to addon "cross-post connectors" to a variety of alternate networks, there is native support for importation of content from RSS/Atom feeds and using this to create special channels. Also, an experimental but working implementation of the Diaspora protocol allows communication with people on the Friendica and Diaspora decentralised social networks. This is currently marked experimental because these networks do not have the same level of privacy and encryption features and abilities as Hubzilla and may present privacy risks.

There is also experimental support for OpenID authentication which may be used in Access Control Lists. This is a work in progress. Your Hubzilla hub may be used as an OpenID provider to authenticate you to external services which use this technology.

Channels may have permissions to become "derivative channels" where two or more existing channels combine to create a new topical channel.

Privacy Groups

Our implementation of privacy groups is similar to Google "Circles" and Diaspora "Aspects". This allows you to filter your incoming stream by selected groups, and automatically set the outbound Access Control List to only those in that privacy group when you post. You may over-ride this at any time (prior to sending the post).  


Directory Services

We provide easy access to a directory of members and provide decentralised tools capable of providing friend "suggestions". The directories are normal Hubzilla sites which have chosen to accept the directory server role. This requires more resources than most typical sites so is not the default. Directories are synchronised and mirrored so that they all contain up-to-date information on the entire network (subject to normal propagation delays).  


TLS/SSL

For Hubzilla hubs that use TLS/SSL, client to server communications are encrypted via TLS/SSL.  Given recent disclosures in the media regarding widespread, global surveillance and encryption circumvention by the NSA and GCHQ, it is reasonable to assume that HTTPS-protected communications may be compromised in various ways. Private communications are consequently encrypted at a higher level before sending offsite.

Channel Settings

When a channel is created, a role is chosen which applies a number of pre-configured security and privacy settings. These are chosen for best practives to maintain privacy at the requested levels.  

If you choose a "custom" privacy role, each channel allows fine-grained permissions to be set for various aspects of communication.  For example, under the "Security and Privacy Settings" heading, each aspect on the left side of the page, has six (6) possible viewing/access options, that can be selected by clicking on the dropdown menu. There are also a number of other privacy settings you may edit.  

The options are:

- Nobody except yourself.
- Only those you specifically allow.
- Anybody in your address book.
- Anybody on this website.
- Anybody in this network.
- Anybody authenticated.
- Specific people you provide a Guest Access Token to in order to access a specific item.
- Anybody on the Internet.


Public and Private Forums

Forums are typically channels which may be open to participation from multiple authors. There are currently two mechanisms to post to forums: 1) "wall-to-wall" posts and 2) via forum @mention tags. Forums can be created by anybody and used for any purpose. The directory contains an option to search for public forums. Private forums can only be posted to and often only seen by members.


Account Cloning

Accounts in Hubzilla are referred to as nomadic identities, because a member's identity is not bound to the hub where the identity was originally created.  For example, when you create a Facebook or Gmail account, it is tied to those services.  They cannot function without Facebook.com or Gmail.com.  

By contrast, say you've created a Hubzilla identity called tina@Hubzillahub.com.  You can clone it to another Hubzilla hub by choosing the same, or a different name: liveForever@SomeHubzillaHub.info

Both channels are now synchronized, which means all your contacts and preferences will be duplicated on your clone.  It doesn't matter whether you send a post from your original hub, or the new hub.  Posts will be mirrored on both accounts.

This is a rather revolutionary feature, if we consider some scenarios:

- What happens if the hub where an identity is based suddenly goes offline?  Without cloning, a member will not be able to communicate until that hub comes back online (no doubt many of you have seen and cursed the Twitter "Fail Whale").  With cloning, you just log into your cloned account, and life goes on happily ever after.

- The administrator of your hub can no longer afford to pay for his free and public Hubzilla hub. He announces that the hub will be shutting down in two weeks.  This gives you ample time to clone your identity(ies) and preserve yourHubzilla relationships, friends and content.

- What if your identity is subject to government censorship?  Your hub provider may be compelled to delete your account, along with any identities and associated data.  With cloning, Hubzilla offers censorship resistance.  You can have hundreds of clones, if you wanted to, all named different, and existing on many different hubs, strewn around the internet.  

Hubzilla offers interesting new possibilities for privacy. You can read more at the <<Private Communications Best Practices>> page.

Some caveats apply. For a full explanation of identity cloning, read the <HOW TO CLONE MY IDENTITY>.

Multiple Profiles

Any number of profiles may be created containing different information and these may be made visible to certain of your connections/friends. A "default" profile can be seen by anybody and may contain limited information, with more information available to select groups or people. This means that the profile (and site content) your beer-drinking buddies see may be different than what your co-workers see, and also completely different from what is visible to the general public.

Account Backup

Red offers a simple, one-click account backup, where you can download a complete backup of your profile(s).  

Backups can then be used to clone or restore a profile.

Account Deletion

Accounts can be immediately deleted by clicking on a link. That's it.  All associated content is then deleted from the grid (this includes posts and any other content produced by the deleted profile). Depending on the number of connections you have, the process of deleting remote content could take some time but it is scheduled to happen as quickly as is practical.

Content Creation

Writing Posts

Hubzilla supports a number of different ways of adding rich-text content. The default is a custom variant of BBcode, tailored for use in Hubzilla. You may also enable the use of Markdown if you find that easier to work with. A visual editor may also be used. The traditional visual editor for Hubzilla had some serious issues and has since been removed. We are currently looking for a replacement.

When creating "Websites", content may be entered in HTML, Markdown, BBcode, and/or plain text.

Deletion of content
Any content created in Hubzilla remains under the control of the member (or channel) that originally created it.  At any time, a member can delete a message, or a range of messages.  The deletion process ensures that the content is deleted, regardless of whether it was posted on a channel's primary (home) hub, or on another hub, where the channel was remotely authenticated via Zot (Hubzilla communication and authentication protocol).

Media
Similar to any other modern blogging system, social network, or a micro-blogging service, Hubzilla supports the uploading of files, embedding of videos, linking web pages.

Previewing/Editing
Post can be previewed prior to sending and edited after sending.

Voting/Consensus
Posts can be turned into "consensus" items which allows readers to offer feedback, which is collated into "agree", "disagree", and "abstain" counters. This lets you gauge interest for ideas and create informal surveys.


Extending Hubzilla

Hubzilla can be extended in a number of ways, through site customisation, personal customisation, option setting, themes, and addons/plugins.

API

An API is available for use by third-party services. This is based originally on the early Twitter API (for which hundreds of third-party tools exist). It is currently being extended to provide access to facilities and abilities which are specific to Hubzilla. Access may be provided by login/password or OAuth and client registration of OAuth applications is provided. +

+ +

Zot protocol

+

+ What is Zot?

Zot is the protocol that powers Hubzilla, providing three core capabilities: Communications, Identity, and Access Control.

The functionality it provides can also be described as follows:

- a relationship online is just a bunch of permissions
- the internet is just another folder

Communications

Zot is a revolutionary protocol which provides decentralised communications and identity management across the grid. The resulting platform can provide web services comparable to those offered by large corporate providers, but without the large corporate provider and their associated privacy issues, insatiable profit drive, and walled-garden mentality.

Communications and social networking are an integral part of the grid. Any channel (and any services provided by that channel) can make full use of feature-rich social communications on a global scale. These communications may be public or private - and private communications comprise not only fully encrypted transport, but also encrypted storage to help protect against accidental snooping and disclosure by rogue system administrators and internet service providers.

Zot allows a wide array of background services in the grid, from offering friend suggestions, to directory services. You can also perform other things which would typically only be possibly on a centralized provider - such as "Wall to Wall" posts. Private/multiple profiles can be easily created, and web content can be tailored to the viewer via the Affinity Slider.

You won't find these features at all on other decentralized communication services. In addition to providing hub (server) decentralization, perhaps the most innovative and interesting Zot feature is its provision of decentralized identity services.

Identity

Zot's identity layer is unique. It provides invisible single sign-on across all sites in the grid.

It also provides nomadic identity, so that your communications with friends, family, and or anyone else you're communicating with won't be affected by the loss of your primary communication node - either temporarily or permanently.

The important bits of your identity and relationships can be backed up to a thumb drive, or your laptop, and may appear at any node in the grid at any time - with all your friends and preferences intact.

Crucially, these nomadic instances are kept in sync so any instance can take over if another one is compromised or damaged. This protects you against not only major system failure, but also temporary site overloads and governmental manipulation or censorship.

Nomadic identity, single sign-on, and Hubzilla's decentralization of hubs, we believe, introduce a high degree of degree of resiliency and persistence in internet communications, that are sorely needed amidst global trends towards corporate centralization, as well as mass and indiscriminate government surveillance and censorship.

As you browse the grid, viewing channels and their unique content, you are seamlessly authenticated as you go, even across completely different server hubs. No passwords to enter. Nothing to type. You're just greeted by name on every new site you visit.

How does Zot do that? We call it magic-auth, because Hubzilla hides the details of the complexities that go into single sign-on logins, and nomadic identities, from the experience of browsing on the grid.  This is one of the design goals of Hubzilla: to increase privacy, and freedom on the web, while reducing the complexity and tedium brought by the need to enter new passwords and user names for every different sight that someone might visit online.

You login only once on your home hub (or any nomadic backup hub you have chosen). This allows you to access any authenticated services provided anywhere in the grid - such as shopping, blogs, forums, and access to private information. This is just like the services offered by large corporate providers with huge user databases; however you can be a member of this community, as well as a server on this network using a $35 Rasberry Pi. Your password isn't stored on a thousand different sites, or even worse, only on a few sites like Google and Facebook, beyond your direct control.

You cannot be silenced. You cannot be removed from the grid, unless you yourself choose to exit it.

Access Control

Zot's identity layer allows you to provide fine-grained permissions to any content you wish to publish - and these permissions extend across Hubzilla. This is like having one super huge website made up of an army of small individual websites - and where each channel in the grid can completely control their privacy and sharing preferences for any web resources they create.

Currently, the grid supports communications, photo albums, events, and files. This will be extended in the future to provide content management services (web pages) and cloud storage facilities, such as WebDAV and multi-media libraries. Every object and how it is shared and with whom is completely under your control.

This type of control is available on large corporate providers such as Facebook and Google, because they own the user database. Within the grid, there is no need for a huge user databaseon your machine - because the grid is your user database. It has what is essentially infinite capacity (limited by the total number of hubs online across the internet), and is spread amongst hundreds, and potentially millions of computers.

Access can be granted or denied for any resource, to any channel, or any group of channels; anywhere within the grid. Others can access your content if you permit them to do so, and they do not even need to have an account on your hub. Your private photos cannot be viewed, because permission really work; they are not an addon that was added as an afterthought. If you aren't on the list of allowed viewers for a particular photo, you aren't going to look at it.

Additional Resources and Links

For more detailed, technical information about Zot, check out the following links:

- A high level overview

- Zot development specification

- Zot reference implementation in PHP +

\ No newline at end of file diff --git a/doc/admin/administrator_guide.html b/doc/admin/administrator_guide.html new file mode 100644 index 000000000..c0a5212ec --- /dev/null +++ b/doc/admin/administrator_guide.html @@ -0,0 +1,346 @@ +

Table of Contents

+ +

+ +

Overview

+ +

Hubzilla is more than a simple web application. It is a +complex communications system which more closely resembles an email server +than a web server. For reliability and performance, messages are delivered in +the background and are queued for later delivery when sites are down. This +kind of functionality requires a bit more of the host system than the typical +blog. Not every PHP/MySQL hosting provider will be able to support +Hubzilla. Many will but please review the requirements and confirm these +with your hosting provider prior to installation.

+ +

We've tried very hard to ensure that Hubzilla will run on commodity +hosting platforms such as those used to host Wordpress blogs and Drupal +websites. It will run on most any Linux VPS system. Windows LAMP platforms +such as XAMPP and WAMP are not officially supported at this time however +we welcome patches if you manage to get it working.

+ +

Where to find more help

+ +

If you encounter problems or have issues not addressed in this documentation, +please let us know via the Github issue +tracker. Please be as clear as you +can about your operating environment and provide as much detail as possible +about any error messages you may see, so that we can prevent it from happening +in the future. Due to the large variety of operating systems and PHP platforms +in existence we may have only limited ability to debug your PHP installation or +acquire any missing modules * but we will do our best to solve any general code +issues.

+ +

Before you begin

+ +

Choose a domain name or subdomain name for your server

+ +

Hubzilla can only be installed into the root of a domain or sub-domain, and can +not be installed using alternate TCP ports.

+ +

Decide if you will use SSL and obtain an SSL certificate before software installation

+ +

You SHOULD use SSL. If you use SSL, you MUST use a "browser-valid" certificate.
You MUST NOT use self-signed certificates!

+ +

Please test your certificate prior to installation. A web tool for testing your +certificate is available at "http://www.digicert.com/help/". When visiting your +site for the first time, please use the SSL ("https://") URL if SSL is available. +This will avoid problems later. The installation routine will not allow you to +use a non browser-valid certificate.

+ +

This restriction is incorporated because public posts from you may contain +references to images on your own hub. Other members viewing their stream on +other hubs will get warnings if your certificate is not trusted by their web +browser. This will confuse many people because this is a decentralised network +and they will get the warning about your hub while viewing their own hub and may +think their own hub has an issue. These warnings are very technical and scary to +some folks, many of whom will not know how to proceed except to follow the browser +advice. This is disruptive to the community. That said, we recognise the issues +surrounding the current certificate infrastructure and agree there are many +problems, but that doesn't change the requirement.

+ +

Free "browser-valid" certificates are available from providers such as StartSSL +and LetsEncrypt.

+ +

If you do NOT use SSL, there may be a delay of up to a minute for the initial +install script * while we check the SSL port to see if anything responds there. +When communicating with new sites, Hubzilla always attempts connection on the +SSL port first, before falling back to a less secure connection. If you do not +use SSL, your webserver MUST NOT listen on port 443 at all.

+ +

If you use LetsEncrypt to provide certificates and create a file under +.well-known/acme-challenge so that LetsEncrypt can verify your domain ownership, +please remove or rename the .well-known directory as soon as the certificate is +generated. Hubzilla will provide its own handler for ".well-known" services when +it is installed, and an existing directory in this location may prevent some of +these services from working correctly. This should not be a problem with Apache, +but may be an issue with nginx or other web server platforms.

+ +

Deployment

+ +

There are several ways to deploy a new hub.

+ +

Requirements

+ +

Manual Installation

+ +

Unpack the Hubzilla files into the root of your web server document area

+ +

If you copy the directory tree to your webserver, make sure that you include the +hidden files like .htaccess.

+ +

If you are able to do so, we recommend using git to clone the source +repository rather than to use a packaged tar or zip file. This makes the +software much easier to update. The Linux command to clone the repository +into a directory "mywebsite" would be:

+ +
git clone https://github.com/redmatrix/hubzilla.git mywebsite
+
+ +

and then you can pick up the latest changes at any time with:

+ +
git pull
+
+ +

make sure folders store/[data]/smarty3 and store exist and are +writable by the webserver:

+ +
mkdir -p "store/[data]/smarty3"
+chmod -R 777 store
+
+This permission (777) is very dangerous and if you have sufficient
+privilege and knowledge you should make these directories writeable
+only by the webserver and, if different, the user that will run the
+cron job (see below). In many shared hosting environments this may be
+difficult without opening a trouble ticket with your provider. The
+above permissions will allow the software to work, but are not
+optimal.
+
+ +

The following directories also need to be writable by the webserver in order for certain +web-based administrative tools to function:

+ +

Official addons

+ +

Installation

+ +

Navigate to your webThen you should clone the addon repository (separately). We'll give this repository a nickname of 'hzaddons'. You can pull in other hubzilla addon repositories by giving them different nicknames::

+ +
cd mywebsite
+util/add_addon_repo https://github.com/redmatrix/hubzilla-addons.git hzaddons
+
+ +

Updating

+ +

For keeping the addon tree updated, you should be on your top level website directory and issue an update command for that repository::

+ +
cd mywebsite
+util/update_addon_repo hzaddons
+
+ +

Create searchable representations of the online documentation. You may do this + any time that the documentation is updated :

+ +
cd mywebsite
+util/importdoc
+
+ +

Automated installation via the .homeinstall shell script

+ +

There is a shell script in (.homeinstall/hubzilla-setup.sh) that will install Hubzilla and its dependencies on a fresh installation of Debian 8.3 stable (Jessie). It should work on similar Linux systems but your results may vary.

+ +

Requirements

+ +

The installation script was originally designed for a small hardware server behind your home router. However, it has been tested on several systems running Debian 8.3:

+ +

Overview of installation steps

+ +
  1. apt-get install git
    2. +
  2. mkdir -p /var/www/html
    3. +
  3. cd /var/www/html
    4. +
  4. git clone https://github.com/redmatrix/hubzilla.git .
    5. +
  5. nano .homeinstall/hubzilla-config.txt
    6. +
  6. cd .homeinstall/
    7. +
  7. ./hubzilla-setup.sh
    8. +
  8. sed -i "s/^upload_max_filesize =.*/upload_max_filesize = 100M/g" /etc/php5/apache2/php.ini
    9. +
  9. sed -i "s/^post_max_size =.*/post_max_size = 100M/g" /etc/php5/apache2/php.ini
    10. +
  10. service apache2 reload
    11. +
  11. Open your domain with a browser and step throught the initial configuration of Hubzilla.
    12. +

Service Classes

+ +

Service classes allow you to set limits on system resources by limiting what individual +accounts can do, including file storage and top-level post limits. Define custom service +classes according to your needs in the .htconfig.php file. For example, create +a standard and premium class using the following lines:

+ +
// Service classes
+
+App::$config['system']['default_service_class']='standard'; // this is the default service class that is attached to every new account
+
+// configuration for parent service class
+App::$config['service_class']['standard'] =
+array('photo_upload_limit'=>2097152, // total photo storage limit per channel (here 2MB)
+'total_identities' =>1, // number of channels an account can create
+'total_items' =>0, // number of top level posts a channel can create. Applies only to top level posts of the channel user, other posts and comments are unaffected
+'total_pages' =>100, // number of pages a channel can create
+'total_channels' =>100, // number of channels the user can add, other users can still add this channel, even if the limit is reached
+'attach_upload_limit' =>2097152, // total attachment storage limit per channel (here 2MB)
+'chatters_inroom' =>20);
+
+// configuration for teacher service class
+App::$config['service_class']['premium'] =
+array('photo_upload_limit'=>20000000000, // total photo storage limit per channel (here 20GB)
+'total_identities' =>20, // number of channels an account can create
+'total_items' =>20000, // number of top level posts a channel can create. Applies only to top level posts of the channel user, other posts and comments are unaffected
+'total_pages' =>400, // number of pages a channel can create
+'total_channels' =>2000, // number of channels the user can add, other users can still add this channel, even if the limit is reached
+'attach_upload_limit' =>20000000000, // total attachment storage limit per channel (here 20GB)
+'chatters_inroom' =>100);
+
+ +

To apply a service class to an existing account, use the command line utility from the +web root:

+ +

util/service_class +list service classes

+ +

util/config system default_service_class firstclass +set the default service class to 'firstclass'

+ +

util/service_class firstclass +list the services that are part of 'firstclass' service class

+ +

util/service_class firstclass photo_upload_limit 10000000 +set firstclass total photo disk usage to 10 million bytes

+ +

util/service_class --account=5 firstclass +set account id 5 to service class 'firstclass' (with confirmation)

+ +

util/service_class --channel=blogchan firstclass +set the account that owns channel 'blogchan' to service class 'firstclass' (with confirmation)

+ +

Service class limit options

+ +

Theme management

+ +

Repo management example

+ +

  1. Navigate to your hub web root

    + +

    root@hub:/root# cd /var/www

    2. +

  2. Add the theme repo and give it a name

    + +

    root@hub:/var/www# util/add_theme_repo https://github.com/DeadSuperHero/redmatrix-themes.git DeadSuperHero

    3. +

  3. Update the repo by using

    + +

    root@hub:/var/www# util/update_theme_repo DeadSuperHero

    4. +

Channel Directory

+ +

Keywords

+ +

There is a "tag cloud" of keywords that can appear on the channel directory page. +If you wish to hide these keywords, which are drawn from the directory server, you +can use the config tool:

+ +
util/config system disable_directory_keywords 1
+
+ +

If your hub is in the standalone mode because you do not wish to connect to the +global grid, you may instead ensure the the directory_server system option is +empty:

+ +
util/config system directory_server ""
+
+ +

Upgrading from RedMatrix to Hubzilla

+ +

How to migrate an individual channel from RedMatrix to Hubzilla

+ +
  1. Clone the channel by opening an account on a Hubzilla hub and performing a basic import (not content) from the original RedMatrix hub. Give your new clone time to sync connections and settings.
    2. +
  2. Export individual channel content from your RedMatrix hub to a set of JSON text files using the red.hub/uexport tool. Do this in monthly increments if necessary.
    3. +
  3. Import the JSON data files sequentially in chronological order into the Hubzilla clone using the new.hub/import_items tool.
    4. +
  4. Inform your Friendica and Diaspora contacts that your channel moves. They need to reconnect to your new address.
    5. +
  5. After successful import (check!) delete your channel on the old RedMatrix Server.
    6. +
  6. On the Hubzilla server visit new.hub/locs and upgrade to your channel to a primary one. And when the old Redmatrix server is still listed delete them here as well. Press "Sync" to inform all other server in the grid.
    7. +

Troubleshooting

+ +

Log files

+ +

Allow me to elaborate on logfiles...

+ +

There are three different log facilities.

+ +

The first is the database failure log. This is only used if you create a file called specifically 'dbfail.out' in the root folder of your website and make it write-able by the web server. If we have any database failed queries, they are all reported here. They generally indicate typos in our queries, but also occur if the database server disconnects or tables get corrupted. On rare occasions we'll see race conditions in here where two processes tried to create an xchan or cache entry with the same ID. Any other errors (especially persistent errors) should be investigated.

+ +

The second is the PHP error log. This is created by the language processor and only reports issues in the language environment. Again these can be syntax errors or programming errors, but these generally are fatal and result in a "white screen of death"; e.g. PHP terminates. You should probably look at this file if something goes wrong that doesn't result in a white screen of death, but it isn't uncommon for this file to be empty for days on end.

+ +

There are some lines at the bottom of the supplied .htconfig.php file; which if uncommented will enable a PHP error log (extremely useful for finding the source of white screen failures). This isn't done by default due to potential issues with logfile ownership and write permissions and the fact that there is no logfile rotation by default.

+ +

The third is the "application log". This is used by Hubzilla to report what is going on in the program and usually reports any difficulties or unexpected data we received. It also occasionally reports "heartbeat" status messages to indicate that we reached a certain point in a script. This is the most important log file to us, as we create it ourself for the sole purpose of reporting the status of background tasks and anything that seems weird or out of place. It may not be fatal, but maybe just unexpected. If you're performing a task and there's a problem, let us know what is in this file when the problem occurred. (Please don't send me 100M dumps you'll only piss me off). Just a few relevant lines so I can rule out a few hundred thousand lines of code and concentrate on where the problem starts showing up.

+ +

These are your site logs, not mine. We report serious issues at any log level. I highly recommend 'DEBUG' log level for most sites - which provides a bit of additional info and doesn't create huge logfiles. When there's a problem which defies all attempts to track, you might wish to use DATA log level for a short period of time to capture all the detail of what structures we were dealing with at the time. This log level will use a lot of space so is recommended only for brief periods or for developer test sites.

+ +

I recommend configuring logrotate for both the php log and the application log. I usually have a look at dbfail.out every week or two, fix any issues reported and then starting over with a fresh file. Likewise with the PHP logfile. I refer to it once in a while to see if there's something that needs fixing.

+ +

If something goes wrong, and it's not a fatal error, I look at the application logfile. Often I will +tail -f logfile.out

+ +

While repeating an operation that has problems. Often I'll insert extra logging statements in the code if there isn't any hint what's going wrong. Even something as simple as "got here" or printing out the value of a variable that might be suspect. You can do this too - in fact I encourage you to do so. Once you've found what you need to find, you can

+ +

git checkout file.php

+ +

To immediately clear out all the extra logging stuff you added. Use the information from this log and any detail you can provide from your investigation of the problem to file your bug report - unless your analysis points to the source of the problem. In that case, just fix it.

+ +

Rotating log files

+ +
  1. Enable the logrot addon in the official hubzilla-addons repo
    2. +
  2. Create a directory in your web root called log with webserver write permissions
    3. +
  3. Go to the logrot admin settings and enter this folder name as well as the max size and number of retained log files.
    4. +
\ No newline at end of file diff --git a/doc/developer/developer_guide.html b/doc/developer/developer_guide.html new file mode 100644 index 000000000..34779a7e8 --- /dev/null +++ b/doc/developer/developer_guide.html @@ -0,0 +1,473 @@ +

Table of Contents +

+ +

Who is a Hubzilla developer? Should I read this?

+ +

Anyone who contributes to making Hubzilla better is a developer. There are many different and important ways you can contribute to this amazing technology, even if you do not know how to write code. The software itself is only a part of the Hubzilla project. You can contribute by

+ +

Software developers are of course welcomed; there are so many great ideas to implement and not enough people to make them all a reality! The Hubzilla code base is an advanced and mature system, but the platform is still very flexible and responsive to new ideas.

+ +

This document will help you get started learning and contributing to Hubzilla.

+ +

Versioning system

+ +

The versioning system is similar to the popular semantic versioning but less stringent. Given x.y.z, x changes yearly. y changes for "stable" monthly builds, and z increments when there are interface changes. We maintain our date and build numbers for medium grain version control (commits within a certain date range) and of course git revs for fine grained control.

+ +

Git repository branches

+ +

There are two official branches of the Hubzilla git repo.

+ +

Developer tools and workflows

+ +

Hub Snapshots

+ +

The Hub Snapshots page provides instructions and scripts for taking complete +snapshots of a hub to support switching between consistent and completely known +states. This is useful to prevent situations where the content or database schema +might be incompatible with the code.

+ +

Translations

+ +

Our translations are managed through Transifex. If you wish to help out translating Hubzilla to another language, sign up on transifex.com, visit https://www.transifex.com/projects/p/red-matrix/ and request to join one of the existing language teams or create a new one. Notify one of the core developers when you have a translation update which requires merging, or ask about merging it yourself if you're comfortable with git and PHP. We have a string file called 'messages.po' which is gettext compliant and a handful of email templates, and from there we automatically generate the application's language files.

+ +

Translation Process

+ +

The strings used in the UI of Hubzilla is translated at [Transifex][1] and then +included in the git repository at github. If you want to help with translation +for any language, be it correcting terms or translating Hubzilla to a +currently not supported language, please register an account at transifex.com +and contact the Redmatrix translation team there.

+ +

Translating Hubzilla is simple. Just use the online tool at transifex. If you +don't want to deal with git & co. that is fine, we check the status of the +translations regularly and import them into the source tree at github so that +others can use them.

+ +

We do not include every translation from transifex in the source tree to avoid +a scattered and disturbed overall experience. As an uneducated guess we have a +lower limit of 50% translated strings before we include the language. This +limit is judging only by the amount of translated strings under the assumption +that the most prominent strings for the UI will be translated first by a +translation team. If you feel your translation useable before this limit, +please contact us and we will probably include your teams work in the source +tree.

+ +

If you want to get your work into the source tree yourself, feel free to do so +and contact us with and question that arises. The process is simple and +Hubzilla ships with all the tools necessary.

+ +

The location of the translated files in the source tree is + /view/LNG-CODE/ +where LNG-CODE is the language code used, e.g. de for German or fr for French. +For the email templates (the *.tpl files) just place them into the directory +and you are done. The translated strings come as a "hmessages.po" file from +transifex which needs to be translated into the PHP file Hubzilla uses. To do +so, place the file in the directory mentioned above and use the "po2php" +utility from the util directory of your Hubzilla installation.

+ +

Assuming you want to convert the German localization which is placed in +view/de/hmessages.po you would do the following.

+ +

  1. Navigate at the command prompt to the base directory of your +Hubzilla installation

    2. +

  2. Execute the po2php script, which will place the translation +in the hstrings.php file that is used by Hubzilla.

    + +

    $> php util/po2php.php view/de/hmessages.po

    + +

    The output of the script will be placed at view/de/hstrings.php where +froemdoca os expecting it, so you can test your translation mmediately.

    3. +

  3. Visit your Hubzilla page to check if it still works in the language you +just translated. If not try to find the error, most likely PHP will give +you a hint in the log/warnings.about the error.

    + +

    For debugging you can also try to "run" the file with PHP. This should +not give any output if the file is ok but might give a hint for +searching the bug in the file.

    + +

    $> php view/de/hstrings.php

    4. +

  4. commit the two files with a meaningful commit message to your git +repository, push it to your fork of the Hubzilla repository at github and +issue a pull request for that commit.

    5. +

Utilities

+ +

Additional to the po2php script there are some more utilities for translation +in the "util" directory of the Hubzilla source tree. If you only want to +translate Hubzilla into another language you wont need any of these tools most +likely but it gives you an idea how the translation process of Hubzilla +works.

+ +

For further information see the utils/README file.

+ +

Known Problems

+ +

To-be-organized information

+ +

Here is how you can join us.

+ +

First, get yourself a working git package on the system where you will be +doing development.

+ +

Create your own github account.

+ +

You may fork/clone the Red repository from https://github.com/redmatrix/hubzilla.git.

+ +

Follow the instructions provided here: http://help.github.com/fork-a-repo/ +to create and use your own tracking fork on github

+ +

Then go to your github page and create a "Pull request" when you are ready +to notify us to merge your work.

+ +

Important

+ +

Please pull in any changes from the project repository and merge them with your work before issuing a pull request. We reserve the right to reject any patch which results in a large number of merge conflicts. This is especially true in the case of language translations - where we may not be able to understand the subtle differences between conflicting versions.

+ +

Also - test your changes. Don't assume that a simple fix won't break something else. If possible get an experienced Red developer to review the code.

+ +

Licensing

+ +

All code contributed to the project falls under the MIT license, unless otherwise specified. We will accept third-party code which falls under MIT, BSD and LGPL, but copyleft licensing (GPL, and AGPL) is only permitted in addons. It must be possible to completely remove the GPL (copyleft) code from the main project without breaking anything.

+ +

Coding Style

+ +

In the interests of consistency we adopt the following code styling. We may accept patches using other styles, but where possible please try to provide a consistent code style. We aren't going to argue or debate the merits of this style, and it is irrelevant what project 'xyz' uses. This is not project 'xyz'. This is a baseline to try and keep the code readable now and in the future.

+ +

File system layout:

+ +

[addon] optional addons/plugins

+ +

[boot.php] Every process uses this to bootstrap the application structure

+ +

[doc] Help Files

+ +

[images] core required images

+ +

[include] The "model" in MVC - (back-end functions), also contains PHP "executables" for background processing

+ +

[index.php] The front-end controller for web access

+ +

[install] Installation and upgrade files and DB schema

+ +

[library] Third party modules (must be license compatible)

+ +

[mod] Controller modules based on URL pathname (e.g. #^[url=http://sitename/foo]http://sitename/foo[/url] loads mod/foo.php)

+ +

[mod/site/] site-specific mod overrides, excluded from git

+ +

[util] translation tools, main English string database and other miscellaneous utilities

+ +

[version.inc] contains current version (auto-updated via cron for the master repository and distributed via git)

+ +

[view] theming and language files

+ +

[view/(css,js,img,php,tpl)] default theme files

+ +

[view/(en,it,es ...)] language strings and resources

+ +

[view/theme/] individual named themes containing (css,js,img,php,tpl) over-rides

+ +

The Database:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TableDescription
abconfigcontact table, replaces Friendica 'contact'
abook
accountservice provider account
addon
addressbookchanges
addressbooks
app
atoken
attach
auth_codes
cache
cal
calendarchanges
calendarinstances
calendarobjects
calendars
calendarsubscriptions
cards
channel
chat
chatpresence
chatroom
clients
config
conv
dreport
event
group_member
groupmembers
groups
hook
hubloc
iconfig
issue
item
item_id
likes
locks
mail
menu
menu_item
notify
obj
outq
pconfigpersonal (per channel) configuration storage
photo
poll
poll_elm
principals
profdef
profext
profile
profile_check
propertystorage
register
schedulingobjects
session
shares
sign
site
source
sys_perms
term
tokens
updates
users
verify
vote
xchan
xchat
xconfig
xign
xlink
xperm
xprof
xtag
* abook - contact table, replaces Friendica 'contact'
+* account - service provider account
+* addon - registered plugins
+* app - peronal app data
+* attach - file attachments
+* auth_codes - OAuth usage
+* cache - OEmbed cache
+* channel - replaces Friendica 'user'
+* chat - chat room content
+* chatpresence - channel presence information for chat
+* chatroom - data for the actual chat room
+* clients - OAuth usage
+* config - main configuration storage
+* conv - Diaspora private messages
+* event - Events
+* fcontact - friend suggestion stuff
+* ffinder - friend suggestion stuff
+* fserver - obsolete
+* fsuggest - friend suggestion stuff
+* groups - privacy groups
+* group_member - privacy groups
+* hook - plugin hook registry
+* hubloc - Red location storage, ties a location to an xchan
+* item - posts
+* item_id - other identifiers on other services for posts
+* likes - likes of 'things'
+* mail - private messages
+* menu - channel menu data
+* menu_item - items uses by channel menus
+* notify - notifications
+* notify-threads - need to factor this out and use item thread info on notifications
+* obj - object data for things (x has y)
+* outq - output queue
+* pconfig - personal (per channel) configuration storage
+* photo - photo storage
+* poll - data for polls
+* poll_elm - data for poll elements
+* profdef - custom profile field definitions
+* profext - custom profile field data
+* profile - channel profiles
+* profile_check - DFRN remote auth use, may be obsolete
+* register - registrations requiring admin approval
+* session - web session storage
+* shares - shared item information
+* sign - Diaspora signatures.  To be phased out.
+* site - site table to find directory peers
+* source - channel sources data
+* spam - unfinished
+* sys_perms - extensible permissions for the sys channel
+* term - item taxonomy (categories, tags, etc.) table
+* tokens - OAuth usage
+* updates - directory sync updates
+* verify - general purpose verification structure
+* vote - vote data for polls
+* xchan - replaces 'gcontact', list of known channels in the universe
+* xchat - bookmarked chat rooms
+* xconfig - as pconfig but for channels with no local account
+* xlink - "friends of friends" linkages derived from poco
+* xprof - if this hub is a directory server, contains basic public profile info of everybody in the network
+* xtag - if this hub is a directory server, contains tags or interests of everybody in the network
+
+ +

How to theme Hubzilla

+ +

This is a short documentation on what I found while trying to modify Hubzilla's appearance.

+ +

First, you'll need to create a new theme. This is in /view/theme, and I chose to copy 'redbasic' since it's the only available for now. Let's assume I named it .

+ +

Oh, and don't forget to rename the _init function in /php/theme.php to be _init() instead of redbasic_init().

+ +

At that point, if you need to add javascript or css files, add them to /js or /css, and then "register" them in _init() through head_add_js('file.js') and head_add_css('file.css').

+ +

Now you'll probably want to alter a template. These can be found in in /view/tpl OR view//tpl. All you should have to do is copy whatever you want to tweak from the first place to your theme's own tpl directory.

+ +

We're pretty relaxed when it comes to developers. We don't have a lot of rules. Some of us are over-worked and if you want to help we're happy to let you help. That said, attention to a few guidelines will make the process smoother and make it easier to work together. We have developers from across the globe with different abilities and different cultural backgrounds and different levels of patience. Our primary rule is to respect others. Sometimes this is hard and sometimes we have very different opinions of how things should work, but if everybody makes an effort, we'll get along just fine.

+ +

Here is how you can join us.

+ +

First, get yourself a working git package on the system where you will be +doing development.

+ +

Create your own github account.

+ +

You may fork/clone the Red repository from [url=https://github.com/redmatrix/hubzilla.git]https://github.com/redmatrix/hubzilla.git[/url]

+ +

Follow the instructions provided here: [url=http://help.github.com/fork-a-repo/]http://help.github.com/fork-a-repo/[/url] +to create and use your own tracking fork on github

+ +

Then go to your github page and create a "Pull request" when you are ready +to notify us to merge your work.

+ +

Translations

+ +

Our translations are managed through Transifex. If you wish to help out translating the $Projectname to another language, sign up on transifex.com, visit [url=https://www.transifex.com/projects/p/red-matrix/]https://www.transifex.com/projects/p/red-matrix/[/url] and request to join one of the existing language teams or create a new one. Notify one of the core developers when you have a translation update which requires merging, or ask about merging it yourself if you're comfortable with git and PHP. We have a string file called 'messages.po' which is gettext compliant and a handful of email templates, and from there we automatically generate the application's language files.

+ +

Important

+ +

Please pull in any changes from the project repository and merge them with your work before issuing a pull request. We reserve the right to reject any patch which results in a large number of merge conflicts. This is especially true in the case of language translations - where we may not be able to understand the subtle differences between conflicting versions.

+ +

Also - test your changes. Don't assume that a simple fix won't break something else. If possible get an experienced Red developer to review the code.

+ +

Further documentation can be found at the Github wiki pages at: [url=https://github.com/friendica/red/wiki]https://github.com/friendica/red/wiki[/url]

+ +

Licensing

+ +

All code contributed to the project falls under the MIT license, unless otherwise specified. We will accept third-party code which falls under MIT, BSD and LGPL, but copyleft licensing (GPL, and AGPL) is only permitted in addons. It must be possible to completely remove the GPL (copyleft) code from the main project without breaking anything.

+ +

Concensus Building

+ +

Code changes which fix an obvious bug are pretty straight-forward. For instance if you click "Save" and the thing you're trying to save isn't saved, it's fairly obvious what the intended behaviour should be. Often when developing feature requests, it may affect large numbers of community members and it's possible that other members of the community won't agree with the need for the feature, or with your proposed implementation. They may not see something as a bug or a desirable feature.

+ +

We encourage consensus building within the community when it comes to any feature which might be considered controversial or where there isn't unanimous decision that the proposed feature is the correct way to accomplish the task. The first place to pitch your ideas is to [url=https://zothub.com/channel/one]Channel One[/url]. Others may have some input or be able to point out facets of your concept which might be problematic in our environment. But also, you may encounter opposition to your plan. This doesn't mean you should stop and/or ignore the feature. Listen to the concerns of others and try and work through any implementation issues.

+ +

There are places where opposition cannot be resolved. In these cases, please consider making your feature optional or non-default behaviour that must be specifically enabled. This technique can often be used when a feature has significant but less than unanimous support. Those who desire the feature can turn it on and those who don't want it - will leave it turned off.

+ +

If a feature uses other networks or websites and or is only seen as desirable by a small minority of the community, consider making the functionality available via an addon or plugin. Once again, those who don't desire the feature won't need to install it. Plugins are relatively easy to create and "hooks" can be easily added or modified if the current hooks do not do what is needed to allow your plugin to work.

+ +

Coding Style

+ +

In the interests of consistency we adopt the following code styling. We may accept patches using other styles, but where possible please try to provide a consistent code style. We aren't going to argue or debate the merits of this style, and it is irrelevant what project 'xyz' uses. This is not project 'xyz'. This is a baseline to try and keep the code readable now and in the future.

+ + + \ No newline at end of file diff --git a/doc/member/member_guide.html b/doc/member/member_guide.html new file mode 100644 index 000000000..6614a4b2d --- /dev/null +++ b/doc/member/member_guide.html @@ -0,0 +1,18 @@ +

Table of Contents

+ + + +
+ +

Overview

+

+While many features and capabilities of Hubzilla are familiar to people who have +used social networking sites and blogging software, there are also quite a few new +concepts and features that most people have not encountered before. Some of the +new ideas are related to the decentralized nature of the grid; others are associated +with the advanced permissions system that is necessary to protect your data privacy. +The purpose of this guide is to help you understand how to create, configure, and +use your nomadic identity. +

\ No newline at end of file diff --git a/doc/member/toc.html b/doc/member/toc.html deleted file mode 100644 index 6963c5ba9..000000000 --- a/doc/member/toc.html +++ /dev/null @@ -1,25 +0,0 @@ -

Member Guide

- diff --git a/doc/toc.html b/doc/toc.html index 90f0cbaeb..45214e210 100644 --- a/doc/toc.html +++ b/doc/toc.html @@ -1,6 +1,104 @@ - + + +
+
+
+

+ + About +

+
+ +
+
+
+

+ + Members +

+
+
+ +
+
+
+
+

+ + Administrators +

+
+
+ +
+
+
+
+

+ + Developers +

+
+
+ +
+
+
+ + \ No newline at end of file -- cgit v1.2.3 From 99a4bb63c780a939673e2153226635133fbba0eb Mon Sep 17 00:00:00 2001 From: Andrew Manning Date: Sun, 27 Nov 2016 12:52:35 -0700 Subject: Added Tutorials section with a Personal Channel tutorial --- doc/member/member_guide.html | 2 +- doc/toc.html | 16 ++++ doc/tutorials/personal_channel.html | 181 ++++++++++++++++++++++++++++++++++++ 3 files changed, 198 insertions(+), 1 deletion(-) create mode 100644 doc/tutorials/personal_channel.html diff --git a/doc/member/member_guide.html b/doc/member/member_guide.html index 6614a4b2d..d104b19c8 100644 --- a/doc/member/member_guide.html +++ b/doc/member/member_guide.html @@ -15,4 +15,4 @@ new ideas are related to the decentralized nature of the grid; with the advanced permissions system that is necessary to protect your data privacy. The purpose of this guide is to help you understand how to create, configure, and use your nomadic identity. -

\ No newline at end of file +

diff --git a/doc/toc.html b/doc/toc.html index 45214e210..4ee6eeea1 100644 --- a/doc/toc.html +++ b/doc/toc.html @@ -77,6 +77,19 @@ +
+
+

+ + Tutorials +

+
+ +
\ No newline at end of file diff --git a/view/tpl/help.tpl b/view/tpl/help.tpl index 22180bda6..484fd67c9 100644 --- a/view/tpl/help.tpl +++ b/view/tpl/help.tpl @@ -2,7 +2,7 @@

{{$title}}

-
+
{{$content}}
-- cgit v1.2.3