Hi,
I'm running a Wiki on Wikia (I have asked a question on the community
forums [http://community.wikia.com/wiki/Thread:789971], some six days
ago, with no reply, if you're wondering if that would be a better place
to ask it) and I've love to be able to add a drop-down menu to
monobook's sidebar, which I know is possible (see this screenshot of
another Wikia wiki which has this drop-down menu
http://community.wikia.com/wiki/File:Layton_Wiki,_drop-down_menu.png).
Does anyone in this mailing list know how to do this? Please keep in
mind I am a noob when it comes to programming so please, just give me
simple, step-by-step, instructions on how to do this. I do have
administrative privileges on the Wiki in question, so I can edit pages
in the MediaWiki namespace, if need be.
Thanks for your time,
Brenton
Thank you for your thoughts! Our projects are definitely different but its
still nice to know that someone is trying to make something positive.
I will have to get help about what to do next.
Jay
On Mon, Feb 2, 2015 at 7:10 AM, JFC Morfin <jefsey(a)jefsey.com> wrote:
> At 00:26 02/02/2015, Jay R wrote:
>
>> I've been creating a job description for making a non-profit ad-free
>> website which will allow people to setup their own communities where they
>> can work on solving problems relating to specific areas. Different tools
>> will be provided to them including a custom-built task management system,
>> a
>> forum and a wiki.
>>
>
> I am working on a similar Libre concept I call a cyberagora. Unfortunately
> in French (http://cybagora.org).
> The idea is the smartest conviality afficient support of "agoras" (cities,
> wg, communities, personal windows to the world, mathematical concept, etc.)
>
> The whole website will be "wiki" based i.e., people will collaboratively
>> work together and edit task items which are not Wiki pages. For example it
>> may be a row in a database of another table.
>>
>
> My idea is of a flexible federation of SQLite based mediawikis (as a
> start), and eventually a cloud of "intellipages" (i.e. smart independent
> json based wikipages) virtually gathered together through a DDDS (
> http://en.wikipedia.org/wiki/Dynamic_Delegation_Discovery_System).. This
> way I have no hosting to consider and maximum flexibility.
>
> Anyone can fill out a form and a new community is created along with a
>> wiki
>> of their own. So each community will have access to its own set of wiki
>> pages. They may have 5 or 20 or 100 pages. In the long term there may be
>> 100's or 1000's of communities if the website is a success. The URL of a
>> wiki could be something like: en.Solveissues123.org/Community6543/Wiki
>> <http://en.Solveissues.org/Community6543/Wiki>
>> The issues are:
>> (1) User database. I'd like to keep a common user database so people can
>> login once and edit other community wikis.
>>
>
> I suggest a different approach: by capacities. Can access an intellipage
> only those with the necessary capacity. They acquire the capacities through
> a DDDS service (like the DNS) for a limited duration.
>
> (2) Interlinking between various wiki communities
>> (3) Sidebar content for each community so they have their own navigation.
>> (4) Communities may be set up in their own language so a wiki may have
>> its own language.
>> (5) There may be customization for aesthetics.
>>
>
> OK for all of this. This is part, from my POV, of the VGN (Virtual Glocal
> Network) contextual parametring (the participating sites to a relational
> space).
>
> My idea is as follows:
> - the intellipages follows a common formating JSON standard.
> - they are registered by their owner in one or several relational spaces
> - these relational spaces are supported by people's VGN with their local
> global or global local constraints (like a format, verification tools,
> Quality control; langages, etc.).
>
> It will be like Wikia but I have to reserve the sub-domains for languages.
>> I want to use Mediawiki and it will have to be customized to a large
>> extent.
>> I have different options:
>>
>> 1. Use one Mediawiki for the whole website (so one database). Let people
>> separate their community wikis by using different page titles for example
>> [[Community6543/Title of Page]]. They would have to use a similar notation
>> to keep their categories separate. There will be one user database so
>> that's good since anyone can edit a page from any community.
>> The issue are the sidebar and other navigational links and language
>> options. I could get the installation fully customized and change it so
>> they need to edit [[Community6543/Sidebar]] to show their own navigation.
>>
>> 2. Use one mediawiki for each community. They can all use the same user
>> database ($wgSharedDB). Not sure how to manage interlinking here. Any
>> other
>> issues I need to think about? This may be a good solution since a
>> community
>> may have its own language.
>>
>> 3. Use a 3rd light weight wiki software that provides basic wiki functions
>> (editing, page history, diffs). Is there anything like that available or
>> would it need to be created from scratch?
>>
>
> This is a good question :-)
> The best would be syntaxic/use compatibility with wikipedia. So the best
> products of the personal/group wikis could be copied to wikipedia.
>
> A sidenote: Any general advice on how to manage the individual forum
>> creation as well? I would not like to use the talk pages as forums but
>> rather an independent traditional forum for each community.
>>
>
> IMHO you need everything you can findimagine (blogs, mailing list, fora,
> heuristic maps, etc.) and be totally language independent (except js as the
> bowsers' language).
>
> Any advice would be appreciated. Or if you know where I can get
>> professional help in creating the job description for this website let me
>> know. I can then post the job at a freelancing website to have the website
>> made.
>>
>
> Not so easy. I would advise for each tool to look first at all the
> parameters being supported (mediawiki, wordpress, etc.) to make sure you do
> not forget any of them. Then to compare them from one tool to another and
> establish your own common parameter tables. Then review each functionality
> in a multiple tools context, to see what can be aggregated or extended.
>
> From there you will need to design a system architecture taking care of
> replications/security/backup/restorations and of the mix of the different
> databases (DDDS, Semantics) included. At the same time you need to imagine
> how you can make it commercial (business and non-profit alike) and support
> extensions by third parties (API).
>
> Then, not so much to write a job desciption, but a protocol, like an RFC.
> Then to start with a prototype, and test it. Then to add foreseen and new
> features you will have discovered from experimentation.
>
> Just half a cent, for a big project.
> jfc
>
>
> Jay
>> _______________________________________________
>> MediaWiki-l mailing list
>> To unsubscribe, go to:
>> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>>
>
>
> _______________________________________________
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
Exceptional cross-post. Your help spreading this message is welcome.
---------- Forwarded message ----------
From: Quim Gil <qgil(a)wikimedia.org>
Date: Tue, Feb 3, 2015 at 10:17 AM
Subject: Promote GSoC, Outreachy, and Wikimedia Hackathon in France
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
This is a call to all Wikimedia tech contributors with contacts in France.
We need your help reaching out to new developers!
We have the Wikimedia Hackathon in Lyon (23-25 May), which is a good excuse
to focus our developer outreach efforts in France already now. Google
Summer of Code and Outreachy (was FOSS Outreach Program for Women) are
around the corner. Can we coordinate an action between you, your contacts,
Wikimedia France, WMF Engineering Community team... ?
Please subscribe and participate in these tasks:
Promote GSoC, FOSS OPW, and Wikimedia Hackathon in France
https://phabricator.wikimedia.org/T88274
Engage with established technical communities at the Wikimedia Hackathon
2015
https://phabricator.wikimedia.org/T76325
PS: for similar calls focusing on Russia, China, Japan, and your preferred
country, see https://phabricator.wikimedia.org/T925
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi,
I'm building a custom mediawiki skin for 'dual contents view' trying to show another wiki content on the right panel 'Secondary Content'.
Please refer the link. https://www.dropbox.com/s/e3cfk5d73k1xwyt/DualPanelView%20Skin%20for%20Medi…
A concept is the following.
Step(1) If a user click a specific 'word', Step(2) a linked wiki page will be displayed on the second content panel.
First part (1) seems easier, putting a custom tag which make special a href tag would be a solution.
However part (2), I could not find a solution. ( Considering div(with Ajax if it is possible) alternatively iframe. )
I've selected a base skin with 'monobook' since it is easier to customize by fixing MonoBookTemplete.php and main.css.
(I can adjust CSS, but not familiar with PHP)
If I use the following code in the <div>, the second panel synchronizes with the main panel while viewing or editing the content. Of course to display another wiki text, this is not a solution...
<?php $this->html( 'bodytext' ) ?>
Could you give me some hints - which method/functions can be used to display 'other wikitext' not current text?
-Michael K.
p.s Advice for Step(1) also would be very appreciated.
(Apologies in advance for the cross-post)
I’d like to let you know that tickets are now available for SMWCon Spring 2015. Get them here: http://smwcons2015.eventbrite.com
SMWCon (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015), the twice-yearly conference about Semantic MediaWiki, is coming to St. Louis this Spring.
The event, organized by local volunteers, will be hosted at T-Rex May 6-8. Attendance is open to anyone wanting to learn about the intersection of the semantic web and collaborative wikis.
==What is Semantic MediaWiki?==
Semantic MediaWiki (https://semantic-mediawiki.org/wiki/Semantic_MediaWiki) (SMW) is a free, open-source extension to MediaWiki – the wiki software that powers Wikipedia – that lets you store and query data within the wiki's pages.
Semantic MediaWiki is also a full-fledged framework, in conjunction with many spinoff extensions, that can turn a wiki into a powerful and flexible knowledge management system. All data created within SMW can easily be published via the Semantic Web, allowing other systems to use this data seamlessly.
Semantic MediaWiki is used on sites like Gamepedia’s League of Legends wiki (http://lol.gamepedia.com/League_of_Legends_Wiki), the W3C’s WebPlatform.org (https://docs.webplatform.org/wiki/Main_Page) and Practical Plants (http://practicalplants.org). It’s also used by numerous organizations internally to document and share information. At past SMWCon’s we’ve had folks from NATO, NASA, MITRE, and Cirque du Soleil talking about how they use a wiki within their organizations.
==What is SMWCon?==
SMWCon is a twice annual gathering of SMW administrators, developers, and users who come together to discuss the latest in SMW developments, share what they’re working on, and learn how others are using SMW in various industries.
SMWCon Spring 2015 is a 3-day event. The first day focuses on tutorials and introductions to Semantic MediaWiki. The second day is a traditional single-track series of presentations from various folks within the community. The third day is a continuation of talks, and breakout sessions for groups to discuss project work - planning for new development, documentation, or other SMW-related efforts.
The conference is May 6-8, 2015 and will be at T-Rex, a local tech incubator and co-working space. We’ll have breakfast for all three days, lunch for two, and a social night out at a local venue.
If you’re thinking about attending, visit the conference page (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015) and add your name to the list. That’s right, just edit the page. It’s a wiki after all.
Formal registration and tickets can be found at http://smwcons2015.eventbrite.com We have Early-bird and Academic pricing available.
==Speakers Wanted==
We’re looking for folks to share their experience using wikis - from the technology and administration to the community building and philosophy behind open collaborative sharing platforms like Semantic MediaWiki. If you’d like to present, you guessed it, just edit the conference page (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015) with your proposed talk.
I hope you’ll attend this year and please help spread the word to anyone you think might be interested.
For more information or questions, contact the local chair, Chris Koerner, at Chris.Koerner(a)Mercy.Net.
This electronic mail and any attached documents are intended solely for the named addressee(s) and contain confidential information. If you are not an addressee, or responsible for delivering this email to an addressee, you have received this email in error and are notified that reading, copying, or disclosing this email is prohibited. If you received this email in error, immediately reply to the sender and delete the message completely from your computer system.
Hi,
I've installed MediaWiki on my PC and I was wondering how I could turn
this installation into a website for free. Is this possible? I have
created a Wiki with Wikia but they have far less customization than that
allowed by MediaWiki software (e.g., the extensions they have are all
constant across the Wikia family of sites and while you could request
new ones from Wikia staff I have never seen a case where they actually
installed a new extension based on these requests, even for one single
Wiki) so hence why I'd like to know if I could set up my own
fully-customizable Wiki based on my current MediaWiki installation.
Thanks for your time,
Brenton
At 00:26 02/02/2015, Jay R wrote:
>I've been creating a job description for making a non-profit ad-free
>website which will allow people to setup their own communities where they
>can work on solving problems relating to specific areas. Different tools
>will be provided to them including a custom-built task management system, a
>forum and a wiki.
I am working on a similar Libre concept I call a cyberagora.
Unfortunately in French (http://cybagora.org).
The idea is the smartest conviality afficient support of "agoras"
(cities, wg, communities, personal windows to the world, mathematical
concept, etc.)
>The whole website will be "wiki" based i.e., people will collaboratively
>work together and edit task items which are not Wiki pages. For example it
>may be a row in a database of another table.
My idea is of a flexible federation of SQLite based mediawikis (as a
start), and eventually a cloud of "intellipages" (i.e. smart
independent json based wikipages) virtually gathered together through
a DDDS
(http://en.wikipedia.org/wiki/Dynamic_Delegation_Discovery_System)..
This way I have no hosting to consider and maximum flexibility.
>Anyone can fill out a form and a new community is created along with a wiki
>of their own. So each community will have access to its own set of wiki
>pages. They may have 5 or 20 or 100 pages. In the long term there may be
>100's or 1000's of communities if the website is a success. The URL of a
>wiki could be something like: en.Solveissues123.org/Community6543/Wiki
><http://en.Solveissues.org/Community6543/Wiki>
>The issues are:
>(1) User database. I'd like to keep a common user database so people can
>login once and edit other community wikis.
I suggest a different approach: by capacities. Can access an
intellipage only those with the necessary capacity. They acquire the
capacities through a DDDS service (like the DNS) for a limited duration.
>(2) Interlinking between various wiki communities
>(3) Sidebar content for each community so they have their own navigation.
>(4) Communities may be set up in their own language so a wiki may
>have its own language.
>(5) There may be customization for aesthetics.
OK for all of this. This is part, from my POV, of the VGN (Virtual
Glocal Network) contextual parametring (the participating sites to a
relational space).
My idea is as follows:
- the intellipages follows a common formating JSON standard.
- they are registered by their owner in one or several relational spaces
- these relational spaces are supported by people's VGN with their
local global or global local constraints (like a format, verification
tools, Quality control; langages, etc.).
>It will be like Wikia but I have to reserve the sub-domains for languages.
>I want to use Mediawiki and it will have to be customized to a large
>extent.
>I have different options:
>
>1. Use one Mediawiki for the whole website (so one database). Let people
>separate their community wikis by using different page titles for example
>[[Community6543/Title of Page]]. They would have to use a similar notation
>to keep their categories separate. There will be one user database so
>that's good since anyone can edit a page from any community.
>The issue are the sidebar and other navigational links and language
>options. I could get the installation fully customized and change it so
>they need to edit [[Community6543/Sidebar]] to show their own navigation.
>
>2. Use one mediawiki for each community. They can all use the same user
>database ($wgSharedDB). Not sure how to manage interlinking here. Any other
>issues I need to think about? This may be a good solution since a community
>may have its own language.
>
>3. Use a 3rd light weight wiki software that provides basic wiki functions
>(editing, page history, diffs). Is there anything like that available or
>would it need to be created from scratch?
This is a good question :-)
The best would be syntaxic/use compatibility with wikipedia. So the
best products of the personal/group wikis could be copied to wikipedia.
>A sidenote: Any general advice on how to manage the individual forum
>creation as well? I would not like to use the talk pages as forums but
>rather an independent traditional forum for each community.
IMHO you need everything you can findimagine (blogs, mailing list,
fora, heuristic maps, etc.) and be totally language independent
(except js as the bowsers' language).
>Any advice would be appreciated. Or if you know where I can get
>professional help in creating the job description for this website let me
>know. I can then post the job at a freelancing website to have the website
>made.
Not so easy. I would advise for each tool to look first at all the
parameters being supported (mediawiki, wordpress, etc.) to make sure
you do not forget any of them. Then to compare them from one tool to
another and establish your own common parameter tables. Then review
each functionality in a multiple tools context, to see what can be
aggregated or extended.
From there you will need to design a system architecture taking care
of replications/security/backup/restorations and of the mix of the
different databases (DDDS, Semantics) included. At the same time you
need to imagine how you can make it commercial (business and
non-profit alike) and support extensions by third parties (API).
Then, not so much to write a job desciption, but a protocol, like an
RFC. Then to start with a prototype, and test it. Then to add
foreseen and new features you will have discovered from experimentation.
Just half a cent, for a big project.
jfc
>Jay
>_______________________________________________
>MediaWiki-l mailing list
>To unsubscribe, go to:
>https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
I've been creating a job description for making a non-profit ad-free
website which will allow people to setup their own communities where they
can work on solving problems relating to specific areas. Different tools
will be provided to them including a custom-built task management system, a
forum and a wiki.
The whole website will be "wiki" based i.e., people will collaboratively
work together and edit task items which are not Wiki pages. For example it
may be a row in a database of another table.
Anyone can fill out a form and a new community is created along with a wiki
of their own. So each community will have access to its own set of wiki
pages. They may have 5 or 20 or 100 pages. In the long term there may be
100's or 1000's of communities if the website is a success. The URL of a
wiki could be something like: en.Solveissues123.org/Community6543/Wiki
<http://en.Solveissues.org/Community6543/Wiki>
The issues are:
(1) User database. I'd like to keep a common user database so people can
login once and edit other community wikis.
(2) Interlinking between various wiki communities
(3) Sidebar content for each community so they have their own navigation.
(4) Communities may be set up in their own language so a wiki may have its
own language.
(5) There may be customization for aesthetics.
It will be like Wikia but I have to reserve the sub-domains for languages.
I want to use Mediawiki and it will have to be customized to a large
extent.
I have different options:
1. Use one Mediawiki for the whole website (so one database). Let people
separate their community wikis by using different page titles for example
[[Community6543/Title of Page]]. They would have to use a similar notation
to keep their categories separate. There will be one user database so
that's good since anyone can edit a page from any community.
The issue are the sidebar and other navigational links and language
options. I could get the installation fully customized and change it so
they need to edit [[Community6543/Sidebar]] to show their own navigation.
2. Use one mediawiki for each community. They can all use the same user
database ($wgSharedDB). Not sure how to manage interlinking here. Any other
issues I need to think about? This may be a good solution since a community
may have its own language.
3. Use a 3rd light weight wiki software that provides basic wiki functions
(editing, page history, diffs). Is there anything like that available or
would it need to be created from scratch?
A sidenote: Any general advice on how to manage the individual forum
creation as well? I would not like to use the talk pages as forums but
rather an independent traditional forum for each community.
Any advice would be appreciated. Or if you know where I can get
professional help in creating the job description for this website let me
know. I can then post the job at a freelancing website to have the website
made.
Jay
Hi,
I've added Cite and refToolbar to my Wiki but they aren't being loaded.
Cite was automatically in my extension directory immediately after
installation, so what I did was I added
require_once "$IP/extensions/Cite/SpecialCite.php";
To near the end of LocalSettings.php and while cite appears @
Special:Version it does not appear to be working. For example, citation
templates I've added to my Wiki are not organized into footnotes when
contained between <ref> </ref> tags and these tags are, in fact, left
unparsed in articles.
As for refToolbar I added this extension (via copy-pasting the files
listed here
[https://en.wikipedia.org/wiki/Wikipedia:RefToolbar#Related_scripts]
into their respective MediaWiki namespace pages (including adding
* refToolbar[ResourceLoader|default|dependencies=user.options,mediawiki.legacy.wikibits]|refToolbar.js
* refToolbarBase[ResourceLoader|hidden|rights=hidden]|refToolbarBase.js
to MediaWiki:Gadgets-definition). <gadget-refToolbar> appears @
Special:Preferences under Gadgets and is ticked.
Thanks for your time,
Brenton
