Added a github link to gulp.js
← Older revision
Revision as of 17:28, December 26, 2016
Line 62:
Line 62:
|-
|-
|[http://gulpjs.com/ Gulp]
|[http://gulpjs.com/ Gulp]
−
|
+
|
Check out the [https://github.com/gulpjs/gulp/blob/master/docs/getting-started.md github] page to get started.
|-
|-
|[https://git-scm.com/ Git] and [https://github.com/ Github]
|[https://git-scm.com/ Git] and [https://github.com/ Github]
Line 388:
Line 388:
perl -ni -e 'print unless /keyword/' -pi $(find . -name "*.js")
perl -ni -e 'print unless /keyword/' -pi $(find . -name "*.js")
−
These commands
are particularly useful with translation-related work.
+
These commands
−
−
===Testing the Swagger API Interface Locally===
−
Habitica has an [https://habitica.com/static/api API interface], which uses the production database and code. When you have made your own local install of Habitica, you can test the local version of that interface at http://localhost:3000/static/api
−
−
If your version of config.json was created a long time ago and you don't have the most up to date data from config.json.example, you might need to edit config.json to change the BASE_URL line to <code>"BASE_URL":"[http://localhost:3000/ http://localhost:3000]"</code> and then cancel and rerun the '''npm start''' command.
−
===Preference Settings===
−
Habitica has preference settings for the users to customize the website's behavior. New settings may be added if necessary. Please do not add settings only a small proportion of users are likely to use, or settings for trivial customizations. Instead choose a behavior the majority of users are likely to enjoy.
−
−
Too many preferences makes the settings screen look cluttered and increases the appearance of complexity. If you're uncertain about whether a preference setting is desirable, you can discuss it in the [https://habitica.com/#/options/groups/guilds/68d4a01e-db97-4786-8ee3-05d612c5af6f Aspiring Blacksmiths (Habitica Coders)] guild or in a relevant Github issue or pull request.
−
−
=== Tip for storing preferences ===
−
When a new user preference setting is necessary, it can be added to <code>website/src/models/user.js</code>. Generally, the database will then pick them up the new setting automatically and add it to user accounts as necessary. If it is ever necessary for the database to be modified manually, admins can do that.
−
−
=="Information for Developers" Sections on General Wiki Pages==
−
At the bottom of some wiki pages, are sections called '''Information for Developers'''. These contain useful tips for Blacksmiths related to the content on that page.
−
−
The information is hidden behind a spoiler-style show/hide toggle button so it doesn't clutter the page for non-technical users.
−
−
The sections use the {{t|InfoForDevs Start}} and {{t|InfoForDevs End}} templates to ensure correct formatting and wording for the buttons and other text. To see how that is done, open any page with an Information for Developers section in the source editor.
−
−
To see a list of all pages with this section, use the [http://habitica.wikia.com/wiki/Special:WhatLinksHere/Template:InfoForDevs_Start?hidelinks=1&hideredirs=1 "What links here" tool for the 'Start' template].
−
−
To see all Information for Developers sections unhidden by default:
−
* Create a Wikia account if you don't already have one.
−
* Edit your personal Wikia css file, located at: <nowiki>http://habitica.wikia.com/wiki/User:YOUR_USERNAME_HERE/wikia.css</nowiki>
−
* Insert these lines into CSS file:
−
/* Force all "Information for Developers" sections to always be visible */
−
.habitrpg-InfoForDevs {
−
display:block !important;
−
}
−
.habitrpg-InfoForDevs-hideIfDev {
−
display:none;
−
}
−
You can see an example at [[User:LadyAlys/wikia.css]]
−
−
== Contributor Tier Process ==
−
You're in luck! Blacksmiths do not need to do anything special, like complete a Contributor Tier request, in order to earn Contributor Tiers. Contributor Tiers will be granted by the admins as they review and accept Blacksmith submissions. Admins will track Blacksmith contributions for credit toward future Contributor Tiers.
−
−
The first one or two Contributor Tiers are fairly easy to get and you might find that a single pull request is enough for each of them. The higher tiers require progressively more work and several pull requests might be needed. Admins will record each pull request as it is made and will award a tier when enough have been made.
−
−
−
[[fr:Guide de la forge]]
−
[[ru:Руководство_для_кузнецов]]
−
[[Category:Contributing]]