http://wiki.dreamwidth.net/wiki/api.php?action=feedcontributions&user=Echan&feedformat=atomDreamwidth Notes - User contributions [en]2024-03-28T22:57:03ZUser contributionsMediaWiki 1.23.0//wiki.dreamwidth.net/wiki/index.php/Dev_TestingDev Testing2021-08-30T03:18:37Z<p>Echan: /* Configuring The Test Database */ Formatting and small changes, to make these instructions easier to follow.</p>
<hr />
<div>This is mostly for automated back-end testing. For automated testing of front-end or UI components, see [[Using Qunit for testing JS]].<br />
<br />
__TOC__<br />
<br />
<br />
= Configuring The Test Database =<br />
<br />
In early 2015 we made a separate set of config files for using with automated tests, so that they could run against a separate database and not pollute the server's primary database. These are the steps that need to be taken in order to configure a server for running the automated test suite.<br />
<br />
== Directory For Test Configs ==<br />
<br />
First, you need to make sure the local test directory exists on your server. Then, if you haven't done so already, copy the default test config files to the local test directory. (If you have a [[Dreamhack Getting Started|Dreamhack]], this may have been done for you.)<br />
<br />
cd $LJHOME<br />
mkdir -p ext/local/t<br />
cp t/config-test-private.pl ext/local/t/config-test-private.pl <br />
cp t/config-test.pl ext/local/t/config-test.pl <br />
<br />
== config-test-private.pl ==<br />
<br />
Once you have a local copy of config-test-private.pl in the right place, edit it to include the correct connection info and password for your testing database. If you are using a dreamhack, the database should be named <code>test_dreamhack_<username></code>, the username will be dh_<yourusername> and the password is likely the same password that was assigned to the <code>dreamhack_<username></code> database you normally use. Ping <dwuser>mark</dwuser> if you get an error trying to use this test database - it may not have been automatically created.<br />
<br />
If your database setup is not clustered (most dreamhacks aren't), you should delete the 'c01' and 'c02' entries from <code>%DBINFO</code> and only use 'master'. You can also safely delete the entry for 'theschwartz' if you haven't configured that. This is the simplest example of a working config-test-private.pl on a dreamhack:<br />
<br />
<syntaxhighlight lang="perl"><br />
{<br />
package DW::PRIVATE;<br />
<br />
%DBINFO = (<br />
master => {<br />
dbname => "test_dreamhack_kareila",<br />
user => "dh_kareila",<br />
pass => "xxxxxxxxxxxx",<br />
}<br />
);<br />
}<br />
</syntaxhighlight><br />
<br />
== config-test.pl ==<br />
<br />
In your local copy of config-test.pl, delete the 'c01' and 'c02' entries from <code>%DBINFO</code> in this file as well.<br />
<br />
You also need to add <code>cluster1 => 1</code> to the 'role' hashref for 'master' in config-test.pl.<br />
<br />
Finally, change <code>@CLUSTERS</code> and <code>$DEFAULT_CLUSTER</code> in t/config-test.pl to be <code>(1)</code> and <code>[1]</code>, respectively.<br />
<br />
== Initialize the DB ==<br />
<br />
Once the config files are copied and edited properly, there is one final step that must be taken, which is to initialize the test database. <strong>Note:</strong> The initial section of this script may show failure messages on newly created dreamhacks, which already have a test database prepared for the user.<br />
<br />
cd $LJHOME<br />
t/bin/initialize-db<br />
<br />
This script effectively runs update-db.pl and texttool.pl on the test database. You should do this as often as you update your regular server database, so that any schema changes are adopted in both places.<br />
<br />
If the initialize-db script gives you errors, there is likely a problem with your config files that needs to be corrected before you can proceed. Some errors can be more easily identified and troubleshooted by running the <code>dev-setup.t</code> test file and seeing which specific tests fail.<br />
cd $LJHOME<br />
prove -v t/dev-setup.t<br />
<br />
= Running The Tests =<br />
<br />
To run the entire suite of tests:<br />
<br />
cd $LJHOME<br />
prove -r t/<br />
<br />
To prove a specific test:<br />
<br />
cd $LJHOME<br />
prove t/sometest.t<br />
<br />
If everything is working as it should, you should see the text "ok" printed once per test file, to indicate that the tests in that file all passed. Sometimes you will see the text "skipped" followed by a short explanation of why that set of tests was skipped. If a test fails, you should get a large amount of information to assist in diagnosing the problem, and you can get even more information by using <code>prove -v</code>. Running the entire test suite should take less than five minutes.<br />
<br />
(See also [[Test process]] for QA testing, though this is less relevant to most devs)<br />
<br />
= Writing new tests =<br />
<br />
In an ideal world, test-driven development means writing a test to replicate the bug, fixing the bug, then checking that the test passes. Look at the lists of tests in $LJHOME/t/ to find something similar if needed.<br />
<br />
If you're adding a new test to an existing file, remember to update the count of tests planned at the top of the file - there will be a row like:<br />
<br />
use Test::More tests => 36;<br />
<br />
= Other quirks =<br />
* To have a beautiful set of passing tests, you'll need to have CAPTCHA set up on your Dreamhack, though not necessarily enabled: [[How to enable CAPTCHAs on your Dreamhack]]<br />
<br />
[[Category: Development]]<br />
[[Category: Testing]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/Dev_TestingDev Testing2021-08-29T22:27:08Z<p>Echan: /* Configuring The Test Database */ Dreamhack setup apparently includes a bit of local config setup</p>
<hr />
<div>This is mostly for automated back-end testing. For automated testing of front-end or UI components, see [[Using Qunit for testing JS]].<br />
<br />
__TOC__<br />
<br />
<br />
= Configuring The Test Database =<br />
<br />
In early 2015 we made a separate set of config files for using with automated tests, so that they could run against a separate database and not pollute the server's primary database. These are the steps that need to be taken in order to configure a server for running the automated test suite.<br />
<br />
First, you need to make sure the local test directory exists on your server. Then, if you haven't done so already, copy the default test config file to the local test directory. (If you have a [[Dreamhack Getting Started|Dreamhack]], this may have been done for you.)<br />
<br />
cd $LJHOME<br />
mkdir -p ext/local/t<br />
cp t/config-test-private.pl ext/local/t/config-test-private.pl <br />
<br />
Once you have a local copy of config-test-private.pl in the right place, edit it to include the correct connection info and password for your testing database. If you are using a dreamhack, the database should be named <code>test_dreamhack_<username></code>, the username will be dh_<yourusername> and the password is likely the same password that was assigned to the <code>dreamhack_<username></code> database you normally use. Ping <dwuser>mark</dwuser> if you get an error trying to use this test database - it may not have been automatically created.<br />
<br />
If your database setup is not clustered (most dreamhacks aren't), you should delete the 'c01' and 'c02' entries from <code>%DBINFO</code> and only use 'master'. You can also safely delete the entry for 'theschwartz' if you haven't configured that. This is the simplest example of a working config-test-private.pl on a dreamhack:<br />
<br />
<syntaxhighlight lang="perl"><br />
{<br />
package DW::PRIVATE;<br />
<br />
%DBINFO = (<br />
master => {<br />
dbname => "test_dreamhack_kareila",<br />
user => "dh_kareila",<br />
pass => "xxxxxxxxxxxx",<br />
}<br />
);<br />
}<br />
</syntaxhighlight><br />
<br />
You also need to make a local copy (i.e. in ext/local) of t/config-test.pl:<br />
cp t/config-test.pl ext/local/t/config-test.pl <br />
<br />
Then delete the 'c01' and 'c02' entries from<code> %DBINFO</code> in that file as well. You also need to add <code>cluster1 => 1</code> to the 'role' hashref for 'master' in config-test.pl. Finally, change <code>@CLUSTERS</code> and <code>$DEFAULT_CLUSTER</code> in t/config-test.pl to be <code>(1)</code> and <code>[1]</code>, respectively.<br />
<br />
<em><strong>IMPORTANT:</strong></em> Once the config files are copied and edited properly, there is one final step that must be taken, which is to initialize the test database. <strong>Note:</strong> The initial section of this script may show failure messages on newly created dreamhacks, which already have a test database prepared for the user.<br />
<br />
cd $LJHOME<br />
t/bin/initialize-db<br />
<br />
This script effectively runs update-db.pl and texttool.pl on the test database. You should do this as often as you update your regular server database, so that any schema changes are adopted in both places. If the script gives you errors, there is likely a problem with your config files that needs to be corrected before you can proceed.<br />
<br />
= Running The Tests =<br />
<br />
To run the entire suite of tests:<br />
<br />
cd $LJHOME<br />
prove -r t/<br />
<br />
To prove a specific test:<br />
<br />
cd $LJHOME<br />
prove t/sometest.t<br />
<br />
If everything is working as it should, you should see the text "ok" printed once per test file, to indicate that the tests in that file all passed. Sometimes you will see the text "skipped" followed by a short explanation of why that set of tests was skipped. If a test fails, you should get a large amount of information to assist in diagnosing the problem, and you can get even more information by using <code>prove -v</code>. Running the entire test suite should take less than five minutes.<br />
<br />
(See also [[Test process]] for QA testing, though this is less relevant to most devs)<br />
<br />
= Writing new tests =<br />
<br />
In an ideal world, test-driven development means writing a test to replicate the bug, fixing the bug, then checking that the test passes. Look at the lists of tests in $LJHOME/t/ to find something similar if needed.<br />
<br />
If you're adding a new test to an existing file, remember to update the count of tests planned at the top of the file - there will be a row like:<br />
<br />
use Test::More tests => 36;<br />
<br />
= Other quirks =<br />
* To have a beautiful set of passing tests, you'll need to have CAPTCHA set up on your Dreamhack, though not necessarily enabled: [[How to enable CAPTCHAs on your Dreamhack]]<br />
<br />
[[Category: Development]]<br />
[[Category: Testing]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/User_talk:EchanUser talk:Echan2021-08-29T22:19:23Z<p>Echan: wipe page, hit the reset button</p>
<hr />
<div></div>Echan//wiki.dreamwidth.net/wiki/index.php/User:EchanUser:Echan2021-08-29T22:12:30Z<p>Echan: </p>
<hr />
<div>== whoami ==<br />
<br />
I'm [http://echan.dreamwidth.org echan]. I love documentation. At my day job I maintain a massive 20 year old perl application, and I'm hoping some of that practice will translate to dev work on DW.</div>Echan//wiki.dreamwidth.net/wiki/index.php/User_talk:EchanUser talk:Echan2009-05-19T05:41:45Z<p>Echan: /* Leave Messages Here */ reply to Durandal</p>
<hr />
<div>=Leave Messages Here=<br />
<br />
right here!<br />
<br />
<br />
<br />
FFF said to hit you up to see if you had anything wiki-wise you needed a hand with. --[[User:Durandal|Durandal]] 08:58, 10 May 2009 (UTC)<br />
<br />
:Egads, did I not reply to this yet? Real life has been eating my brain. Wiki work that needs doing -- putting pages in categories. I'm fairly happy with the current categories, but there's a lot of pages that are insufficiently categorized. Adding them to more categories will help people find them and reduce duplicating work. --[[User:Echan|Echan]] 05:41, 19 May 2009 (UTC)<br />
<br />
=echan's scratchpad=<br />
==== dead categories ====<br />
Categories with all members recategorized, and verified to have no links to them. AKA, as deleted as can be without actually being deleted:<br />
* [[:Category:User documentation]]<br />
* [[:Category:Server management]]<br />
* [[:Category:Core2]]<br />
* [[:Category:Code documentation]]<br />
* [[:Category:BML]]<br />
* [[:Category:Suggestions]]<br />
<br />
<br />
==== account creation flow ====<br />
<pre><br />
1 - /create.bml -- takes URL parameters from email link<br />
prompts for username, email address, password, and birthday<br />
2 - /create/setup.bml -- funky dialog page for initial profile setup<br />
3 - /create/confirm.bml -- nothing but a "finished!" message and some links<br />
</pre></div>Echan//wiki.dreamwidth.net/wiki/index.php/Support_WishlistSupport Wishlist2009-05-10T18:19:13Z<p>Echan: expanded the "avoiding duplicate work" bit</p>
<hr />
<div>* See this page [[Support_Overhaul_by_gerg]]. Includes screenshots and descriptions of the idea I had. [[User:Gerg|Gerg]] 19:55, 19 July 2008 (UTC)<br />
<br />
* http://community.livejournal.com/suggestions/882211.html -- enable sorting of Support requests by ones that have no response yet. Counter-suggestions include letting a volunteer tag a request as one they don't want to look at again (e.g., if it's one they know has been answered adequately).<br />
<br />
* http://community.livejournal.com/suggestions/882065.html -- enable sorting of Support requests by ones you haven't touched. Also, enable sorting of green support requests by ones you have or haven't touched.<br />
<br />
* http://community.livejournal.com/suggestions/362810.html -- link to FAQs about certain error messages with those error messages<br />
<br />
* Bring back a link to the user's friends page to the summary area at the top of a request. (Still present for S1 users, as the link behind the style number for the friends page, but not for S2 users.) -- [[User:Pne|Pne]] 14:56, 9 February 2009 (UTC)<br />
<br />
* http://community.livejournal.com/suggestions/826109.html - reset password instructions (or link) in lost username emails (makes sense as a lost username usually means a lost password as well)<br />
<br />
* For support administrators, a log of all email sent to a particular address or username (within the last X days?)<br />
<br />
* Tag system for requests to replace bracketed in-subject tags<br />
<br />
* ESN for support page and for individual requests: new request in $category, notify of volunteer action on request, notify of regreen on a request I've answered, notify of action by $username (admins only), notify of $tag (see previous bullet point), etc<br />
<br />
* A public BBB-ish community that announces when bugs are discovered and when they are resolved. Hopefully this would give all users a place to keep informed about the status of a problem that's been affecting them. I have in mind that it wouldn't report <i>every</i> bug, just the ones that affect a lot of people, the type that would be listed in the BBB.<br />
<br />
* Avoid duplicating work, see if someone else is actively working on a support request (possibly by showing usernames that have recently viewed it & when, for people with privs? by having a check-out system?) <br />
:* A check-out system for people with the priv supportviewscreened: this would allow someone to mark a support request they are actively working on, giving them time to research and write an answer. This could also be setup to expire after a certain amount of time, to ensure it gets answered.<br />
<br />
<br />
<br />
[[Category: Wishlists]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/Talk:Volunteers_In_WaitingTalk:Volunteers In Waiting2009-05-02T03:01:30Z<p>Echan: </p>
<hr />
<div>People who might be actively volunteering already, and should be nudged to take themselves off this list and add themselves to [[Who]]<br />
<br />
* Allen<br />
* alsatia<br />
* ChemicalLace<br />
* dani-the-girl<br />
* gossymer<br />
* ivorygates<br />
* jamie<br />
* phoenix<br />
* tango<br />
* teshiron</div>Echan//wiki.dreamwidth.net/wiki/index.php/Talk:Volunteers_In_WaitingTalk:Volunteers In Waiting2009-05-02T02:57:25Z<p>Echan: </p>
<hr />
<div>People who might be actively volunteering already, and should be nudged to take themselves off this list and add themselves to [[Who]]<br />
<br />
* Allen<br />
* alsatia<br />
* ChemicalLace<br />
* dani-the-girl<br />
* gossymer<br />
* ivorygates<br />
* jamie<br />
* phoenix<br />
* piranha<br />
* tango<br />
* teshiron</div>Echan//wiki.dreamwidth.net/wiki/index.php/Talk:Volunteers_In_WaitingTalk:Volunteers In Waiting2009-05-02T02:54:48Z<p>Echan: Created page with 'People who might be actively volunteering already, and should be taken off this list and put on Who: * Allen * alsatia'</p>
<hr />
<div>People who might be actively volunteering already, and should be taken off this list and put on [[Who]]:<br />
* Allen<br />
* alsatia</div>Echan//wiki.dreamwidth.net/wiki/index.php/Main_PageMain Page2009-05-01T04:14:48Z<p>Echan: /* Current Happenings */ open beta, whoo!</p>
<hr />
<div>Hello! This is a wiki for keeping notes on Dreamwidth's continuing evolution. Those involved can use this wiki as a resource for discussion, communication, answers, and occasional giggles. <br />
<br />
Dreamwidth's leaders are using the wiki too, but that doesn't necessarily mean that everything here is up-to-date with their current opinion on things. When in doubt, information on [http://lists.dwscoalition.org/cgi-bin/mailman/listinfo the mailing lists] trumps any information here. <br />
<br />
More information about Dreamwidth can be found at [http://dreamwidth.org/ dreamwidth.org] and at [[Dreamwidth.org: FAQ]] and [[Notable Dreamwidth Reading]].<br />
<br />
Please address any questions or problems with the wiki to [[User:Foxfirefey]], who's in charge. The best way to contact her is <code>skittisheclipse@gmail.com</code>.<br />
<br />
== Current Happenings ==<br />
<br />
We have reached open beta! [http://dreamwidth.org/ Check it out]! Beta testers, read [[Beta Testing]] for useful information.<br />
<br />
We are documenting current and future volunteers at [[Who]] and [[Volunteers In Waiting]]. Projects that must be completed before launch: [[Dreamwidth.org: Pre-Launch]]. And what initiative would be complete without [[:Category: Dreamwidth Icons|icons]], [[:Category: Dreamwidth Banners|banners]], and [[:Category: Dreamwidth Macros|macros]]? If you want to make your own, there's [[:Category: Dreamwidth Stock Images|stock imagery]] you can use. If you make a post about Dreamwidth (see [[Advocacy]]), we are making a list of [[Why Dreamwidth]] posts.<br />
<br />
== Projects == <br />
<br />
These are some of the big areas of the wiki.<br />
<br />
* [[Development]] -- work on the Dreamwidth code base<br />
* [[Documentation]] -- how to write great documentation for users<br />
* [[Styles]] -- currently documenting the heck out of S2<br />
* [[From LJ Suggestions]] -- features people wish Dreamwidth included<br />
<br />
If none of these interest you, or you are looking for something specific, check out [[:Category:Index]].<br />
<br />
[[Category: Index]]<br />
__NOTOC__</div>Echan//wiki.dreamwidth.net/wiki/index.php/Support_guideSupport guide2009-04-30T05:11:00Z<p>Echan: /* Points to Consider */ shuffled category order</p>
<hr />
<div>(This is the braindump page for the Dreamwidth support answering style. It isn't finished yet, but I'm putting it up here for people to pick apart and edit as necessary.)<br />
<br />
=Dreamwidth Support Style=<br />
<br />
Dreamwidth's support answering style can be summed up in 4 points:<br />
<br />
1. Be courteous.<br />
<br />
2. Be professional.<br />
<br />
3. Be human.<br />
<br />
4. Treat everyone as though they're the most important user we have.<br />
<br />
The fine points, of course, is where all the details lie.<br />
<br />
=Points to Consider=<br />
<br />
== General Phrasing ==<br />
<br />
* Speak with a human voice. You're a person; the person on the other end of the screen is a person. Support answers should be person-to-person and human-to-human, with a tone that is both respectful and friendly. Your answers should sound like your voice: the way <em>you personally</em> would explain something to a coworker or a professional contact. Don't be afraid of contractions or the word "I".<br />
<br />
* Responses should be addressed as "Dear $name" (where the name is any name that they provide, or their username if they don't sign one), and signed with your name (whatever name you'd like to give). You can use any signoff you'd like, such as "Regards," "Best," or whatever signoff you feel most comfortable with.<br />
<br />
* A casual tone is okay, but at the same time, casual can translate as "insulting" across cultural boundaries and through language difficulties. Triple-check to make sure that your answer doesn't sound condescending or insulting. You can read the [[Manual of Style]] for specific advice.<br />
<br />
* Apologize for anything that's frustrating the user, but don't make it into the user's fault -- "I'm sorry this is frustrating" is okay, but not "I'm sorry that you feel this is frustrating" (the former validates the user's feelings; the latter places the blame on the user for feeling frustrated).<br />
<br />
* Light wittiness in answers is okay if the user is approaching us in that tone or style, but humor doesn't translate well across cultural and subcultural boundaries, so try to avoid it unless you have reason to believe that the user will be receptive.<br />
<br />
* If a user has a point -- if things are difficult to understand, confusing, or not explained as well as they could be --explicitly acknowledge the point, without getting defensive. (This applies double if the user is frustrated, upset, or angry.) <br />
<br />
== Terminology to Use ==<br />
<br />
* Work with the user's chosen vocabulary as much as possible. If they call something by a name that's not entirely accurate, work with their terminology as much as possible without being actively misleading. If you want to know what the 'official' terminology is, refer to the [[Terminology]] page.<br />
<br />
* Tailor your answer to the user's experience level. If you aren't sure what the user's experience level is, aim for as basic as possible, and acknowledge that they might already know what you're saying.<br />
<br />
* It's all right to use technical language, especially if it helps to clarify, but be sure that the first time you use any technical term, you define what the term means. (It's okay to do this in an aside or a parenthetical.)<br />
<br />
== What about Bugs ==<br />
<br />
* It's okay to tell someone that something's broken and that we're working on fixing it.<br />
<br />
* If you're going to tell someone that something's broken and that we're working on fixing it, make sure it's in Bugzilla first.<br />
<br />
* If something's broken and it's not in Bugzilla yet, take ownership of getting it in there if you're going to answer the request.<br />
<br />
* Set expectations accordingly. If something's prioritized for the next milestone, you can tell the user that. If something hasn't been prioritized yet, tell the user that it's in our bug tracking system, but we haven't set a date for when we'd like to fix it.<br />
<br />
* Remember that everyone uses the service in different ways. If the user is asking how to do something that you think is a "wrong" use, it's probably not; it's just a use that we haven't thought of yet. Make sure that someone knows what the user is trying to do, so they can consider implementing it.<br />
<br />
== Possibly Answered Elsewhere==<br />
<br />
* If the user's mentioned that they've already read the FAQ, don't send them to the FAQ without acknowledging that they've already read it.<br />
<br />
* It's okay to say something like "Before we go into advanced troubleshooting, I'd like to just rule out some of the most common causes of this problem. Can you confirm that you've already tried $commonsolution, and let me know what happened when you did?"<br />
<br />
== More Info Needed == <br />
<br />
* Never be afraid to ask the user to clarify something. If they're asking a question that could be X, but might be Y, answer X, but say "You might also mean Y. If you do, here's the quick overview, and if that doesn't answer your question, let us know." <br />
<br />
* Never be afraid to ask the user for more information. If they say "X is broken", don't be afraid to say something like, "So that we can diagnose the problem, can you tell me exactly what happens when you try to X?" (Of course, be sure to go and try X yourself first, to see if you can figure out why the user thinks it's broken and save some time.)<br />
<br />
== Unasked Questions ==<br />
<br />
* Respond to both the question the person is literally asking, and the one that they don't know that they need to ask. Answer the question they've actually asked first, and explicitly<br />
<br />
* Aim for answering all of the user's questions (even the questions they don't know they need to ask) in a single contact, but don't worry if you can't get it. If you ever think that you might not have given them a complete answer, if you think that they might have more questions, or if you're offering them a fix that might or might not fully solve their problem, include an explicit invitation for them to come back to the request and let you know if it doesn't work.<br />
<br />
== "But Whyyyy?" ==<br />
<br />
* Explain the reasoning for why things are the way they are, without coming off as sounding like those things will never change. If it <em>is</em> something you think will never change, confirm it with someone (to make sure you're right) and link the user to the official explanation of why things are that way. (If there isn't an official explanation of why things are that way, poke someone to make sure that it gets written.)<br />
<br />
* If someone doesn't like something that will never change, or that won't change for now, acknowledge the validity of their not liking it and let them know, in as courteous a method as possible, the reasons for the decision. Not everyone will like every decision we make, but they deserve to know the reasons behind the decision.<br />
<br />
== Repeat Offenders ==<br />
<br />
* We'd rather hear about something for the 50th time than not hear about it at all.<br />
<br />
* Remember that even if it's the 50th time you've answered that question today, to the person who is asking the question, it's the first time they've asked it. Respond to the 50th question as though it was the first.<br />
<br />
== General Stuff ==<br />
<br />
* Remember that there is always room for us to improve. <br />
<br />
* Remember that everyone has a different learning style. Some people need text; some people need diagrams; some people need step-by-step detailed instructions. Tailor your answers to what you can divine of the user's learning style as much as possible. If you're having trouble getting across to someone, grab a friend who has a different explaining style and have them take a stab at it.<br />
<br />
* People will take your words, your gestures, and your actions as an official communication of Dreamwidth Studios, even if all you're doing is explaining how to confirm their email address. For many people, you will be their first and only contact with us. Make the impression as positive as you can.<br />
<br />
* Go the extra mile. If there's something you can do to make things more awesome for the user, whether it's contacting the site copy team to make instructions clearer, pointing them to an official community with more information about their problem, pointing them to an unofficial community that offers resources they might be interested in, or logging a bug to get their pet peeve fixed, do it whenever possible.<br />
<br />
* If the question is being asked now, answer it now, even if the answer is "We won't have an answer for that until later." Be sure to define 'later'. Also be sure to come back and update the person when that thing happens.<br />
<br />
<br />
<br />
[[Category: Support]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/Support_guideSupport guide2009-04-30T05:04:24Z<p>Echan: /* Points to Consider */ Organized into categories</p>
<hr />
<div>(This is the braindump page for the Dreamwidth support answering style. It isn't finished yet, but I'm putting it up here for people to pick apart and edit as necessary.)<br />
<br />
=Dreamwidth Support Style=<br />
<br />
Dreamwidth's support answering style can be summed up in 4 points:<br />
<br />
1. Be courteous.<br />
<br />
2. Be professional.<br />
<br />
3. Be human.<br />
<br />
4. Treat everyone as though they're the most important user we have.<br />
<br />
The fine points, of course, is where all the details lie.<br />
<br />
=Points to Consider=<br />
<br />
== General Phrasing ==<br />
<br />
* Speak with a human voice. You're a person; the person on the other end of the screen is a person. Support answers should be person-to-person and human-to-human, with a tone that is both respectful and friendly. Your answers should sound like your voice: the way <em>you personally</em> would explain something to a coworker or a professional contact. Don't be afraid of contractions or the word "I".<br />
<br />
* Responses should be addressed as "Dear $name" (where the name is any name that they provide, or their username if they don't sign one), and signed with your name (whatever name you'd like to give). You can use any signoff you'd like, such as "Regards," "Best," or whatever signoff you feel most comfortable with.<br />
<br />
* A casual tone is okay, but at the same time, casual can translate as "insulting" across cultural boundaries and through language difficulties. Triple-check to make sure that your answer doesn't sound condescending or insulting. You can read the [[Manual of Style]] for specific advice.<br />
<br />
* Apologize for anything that's frustrating the user, but don't make it into the user's fault -- "I'm sorry this is frustrating" is okay, but not "I'm sorry that you feel this is frustrating" (the former validates the user's feelings; the latter places the blame on the user for feeling frustrated).<br />
<br />
* Light wittiness in answers is okay if the user is approaching us in that tone or style, but humor doesn't translate well across cultural and subcultural boundaries, so try to avoid it unless you have reason to believe that the user will be receptive.<br />
<br />
* If a user has a point -- if things are difficult to understand, confusing, or not explained as well as they could be --explicitly acknowledge the point, without getting defensive. (This applies double if the user is frustrated, upset, or angry.) <br />
<br />
== Terminology to Use ==<br />
<br />
* Work with the user's chosen vocabulary as much as possible. If they call something by a name that's not entirely accurate, work with their terminology as much as possible without being actively misleading. If you want to know what the 'official' terminology is, refer to the [[Terminology]] page.<br />
<br />
* Tailor your answer to the user's experience level. If you aren't sure what the user's experience level is, aim for as basic as possible, and acknowledge that they might already know what you're saying.<br />
<br />
* It's all right to use technical language, especially if it helps to clarify, but be sure that the first time you use any technical term, you define what the term means. (It's okay to do this in an aside or a parenthetical.)<br />
<br />
== What about Bugs ==<br />
<br />
* It's okay to tell someone that something's broken and that we're working on fixing it.<br />
<br />
* If you're going to tell someone that something's broken and that we're working on fixing it, make sure it's in Bugzilla first.<br />
<br />
* If something's broken and it's not in Bugzilla yet, take ownership of getting it in there if you're going to answer the request.<br />
<br />
* Set expectations accordingly. If something's prioritized for the next milestone, you can tell the user that. If something hasn't been prioritized yet, tell the user that it's in our bug tracking system, but we haven't set a date for when we'd like to fix it.<br />
<br />
* Remember that everyone uses the service in different ways. If the user is asking how to do something that you think is a "wrong" use, it's probably not; it's just a use that we haven't thought of yet. Make sure that someone knows what the user is trying to do, so they can consider implementing it.<br />
<br />
== Possibly Answered Elsewhere==<br />
<br />
* If the user's mentioned that they've already read the FAQ, don't send them to the FAQ without acknowledging that they've already read it.<br />
<br />
* It's okay to say something like "Before we go into advanced troubleshooting, I'd like to just rule out some of the most common causes of this problem. Can you confirm that you've already tried $commonsolution, and let me know what happened when you did?"<br />
<br />
== "But Whyyyy?" ==<br />
<br />
* Explain the reasoning for why things are the way they are, without coming off as sounding like those things will never change. If it <em>is</em> something you think will never change, confirm it with someone (to make sure you're right) and link the user to the official explanation of why things are that way. (If there isn't an official explanation of why things are that way, poke someone to make sure that it gets written.)<br />
<br />
* If someone doesn't like something that will never change, or that won't change for now, acknowledge the validity of their not liking it and let them know, in as courteous a method as possible, the reasons for the decision. Not everyone will like every decision we make, but they deserve to know the reasons behind the decision.<br />
<br />
== Unasked Questions ==<br />
<br />
* Respond to both the question the person is literally asking, and the one that they don't know that they need to ask. Answer the question they've actually asked first, and explicitly<br />
<br />
* Aim for answering all of the user's questions (even the questions they don't know they need to ask) in a single contact, but don't worry if you can't get it. If you ever think that you might not have given them a complete answer, if you think that they might have more questions, or if you're offering them a fix that might or might not fully solve their problem, include an explicit invitation for them to come back to the request and let you know if it doesn't work.<br />
<br />
== More Info Needed == <br />
<br />
* Never be afraid to ask the user to clarify something. If they're asking a question that could be X, but might be Y, answer X, but say "You might also mean Y. If you do, here's the quick overview, and if that doesn't answer your question, let us know." <br />
<br />
* Never be afraid to ask the user for more information. If they say "X is broken", don't be afraid to say something like, "So that we can diagnose the problem, can you tell me exactly what happens when you try to X?" (Of course, be sure to go and try X yourself first, to see if you can figure out why the user thinks it's broken and save some time.)<br />
<br />
== Repeat Offenders ==<br />
<br />
* We'd rather hear about something for the 50th time than not hear about it at all.<br />
<br />
* Remember that even if it's the 50th time you've answered that question today, to the person who is asking the question, it's the first time they've asked it. Respond to the 50th question as though it was the first.<br />
<br />
== General Stuff ==<br />
<br />
* Remember that there is always room for us to improve. <br />
<br />
* Remember that everyone has a different learning style. Some people need text; some people need diagrams; some people need step-by-step detailed instructions. Tailor your answers to what you can divine of the user's learning style as much as possible. If you're having trouble getting across to someone, grab a friend who has a different explaining style and have them take a stab at it.<br />
<br />
* People will take your words, your gestures, and your actions as an official communication of Dreamwidth Studios, even if all you're doing is explaining how to confirm their email address. For many people, you will be their first and only contact with us. Make the impression as positive as you can.<br />
<br />
* Go the extra mile. If there's something you can do to make things more awesome for the user, whether it's contacting the site copy team to make instructions clearer, pointing them to an official community with more information about their problem, pointing them to an unofficial community that offers resources they might be interested in, or logging a bug to get their pet peeve fixed, do it whenever possible.<br />
<br />
* If the question is being asked now, answer it now, even if the answer is "We won't have an answer for that until later." Be sure to define 'later'. Also be sure to come back and update the person when that thing happens.<br />
<br />
<br />
<br />
[[Category: Support]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/Support_guideSupport guide2009-04-30T04:26:30Z<p>Echan: /* Points to Consider */ linked Manual of Style and Terminology in the text</p>
<hr />
<div>(This is the braindump page for the Dreamwidth support answering style. It isn't finished yet, but I'm putting it up here for people to pick apart and edit as necessary.)<br />
<br />
=Dreamwidth Support Style=<br />
<br />
Dreamwidth's support answering style can be summed up in 4 points:<br />
<br />
1. Be courteous.<br />
<br />
2. Be professional.<br />
<br />
3. Be human.<br />
<br />
4. Treat everyone as though they're the most important user we have.<br />
<br />
The fine points, of course, is where all the details lie.<br />
<br />
=Points to Consider=<br />
<br />
* Speak with a human voice. You're a person; the person on the other end of the screen is a person. Support answers should be person-to-person and human-to-human, with a tone that is both respectful and friendly. Your answers should sound like your voice: the way <em>you personally</em> would explain something to a coworker or a professional contact. Don't be afraid of contractions or the word "I".<br />
<br />
* Responses should be addressed as "Dear $name" (where the name is any name that they provide, or their username if they don't sign one), and signed with your name (whatever name you'd like to give). You can use any signoff you'd like, such as "Regards," "Best," or whatever signoff you feel most comfortable with.<br />
<br />
* A casual tone is okay, but at the same time, casual can translate as "insulting" across cultural boundaries and through language difficulties. Triple-check to make sure that your answer doesn't sound condescending or insulting. You can read the [[Manual of Style]] for specific advice.<br />
<br />
* Work with the user's chosen vocabulary as much as possible. If they call something by a name that's not entirely accurate, work with their terminology as much as possible without being actively misleading. If you want to know what the 'official' terminology is, refer to the [[Terminology]] page.<br />
<br />
* Tailor your answer to the user's experience level. If you aren't sure what the user's experience level is, aim for as basic as possible, and acknowledge that they might already know what you're saying.<br />
<br />
* Apologize for anything that's frustrating the user, but don't make it into the user's fault -- "I'm sorry this is frustrating" is okay, but not "I'm sorry that you feel this is frustrating" (the former validates the user's feelings; the latter places the blame on the user for feeling frustrated).<br />
<br />
* It's all right to use technical language, especially if it helps to clarify, but be sure that the first time you use any technical term, you define what the term means. (It's okay to do this in an aside or a parenthetical.)<br />
<br />
* Remember that everyone uses the service in different ways. If the user is asking how to do something that you think is a "wrong" use, it's probably not; it's just a use that we haven't thought of yet. Make sure that someone knows what the user is trying to do, so they can consider implementing it.<br />
<br />
* It's okay to tell someone that something's broken and that we're working on fixing it.<br />
<br />
* If you're going to tell someone that something's broken and that we're working on fixing it, make sure it's in Bugzilla first.<br />
<br />
* If something's broken and it's not in Bugzilla yet, take ownership of getting it in there if you're going to answer the request.<br />
<br />
* Set expectations accordingly. If something's prioritized for the next milestone, you can tell the user that. If something hasn't been prioritized yet, tell the user that it's in our bug tracking system, but we haven't set a date for when we'd like to fix it.<br />
<br />
* If the user's mentioned that they've already read the FAQ, don't send them to the FAQ without acknowledging that they've already read it.<br />
<br />
* It's okay to say something like "Before we go into advanced troubleshooting, I'd like to just rule out some of the most common causes of this problem. Can you confirm that you've already tried $commonsolution, and let me know what happened when you did?"<br />
<br />
* Light wittiness in answers is okay if the user is approaching us in that tone or style, but humor doesn't translate well across cultural and subcultural boundaries, so try to avoid it unless you have reason to believe that the user will be receptive.<br />
<br />
* If a user has a point -- if things are difficult to understand, confusing, or not explained as well as they could be --explicitly acknowledge the point, without getting defensive. (This applies double if the user is frustrated, upset, or angry.) <br />
<br />
* Explain the reasoning for why things are the way they are, without coming off as sounding like those things will never change. If it <em>is</em> something you think will never change, confirm it with someone (to make sure you're right) and link the user to the official explanation of why things are that way. (If there isn't an official explanation of why things are that way, poke someone to make sure that it gets written.)<br />
<br />
* If someone doesn't like something that will never change, or that won't change for now, acknowledge the validity of their not liking it and let them know, in as courteous a method as possible, the reasons for the decision. Not everyone will like every decision we make, but they deserve to know the reasons behind the decision.<br />
<br />
* Remember that there is always room for us to improve. <br />
<br />
* Respond to both the question the person is literally asking, and the one that they don't know that they need to ask. Answer the question they've actually asked first, and explicitly.<br />
<br />
* We'd rather hear about something for the 50th time than not hear about it at all.<br />
<br />
* Remember that even if it's the 50th time you've answered that question today, to the person who is asking the question, it's the first time they've asked it. Respond to the 50th question as though it was the first.<br />
<br />
* Remember that everyone has a different learning style. Some people need text; some people need diagrams; some people need step-by-step detailed instructions. Tailor your answers to what you can divine of the user's learning style as much as possible. If you're having trouble getting across to someone, grab a friend who has a different explaining style and have them take a stab at it.<br />
<br />
* People will take your words, your gestures, and your actions as an official communication of Dreamwidth Studios, even if all you're doing is explaining how to confirm their email address. For many people, you will be their first and only contact with us. Make the impression as positive as you can.<br />
<br />
* Go the extra mile. If there's something you can do to make things more awesome for the user, whether it's contacting the site copy team to make instructions clearer, pointing them to an official community with more information about their problem, pointing them to an unofficial community that offers resources they might be interested in, or logging a bug to get their pet peeve fixed, do it whenever possible.<br />
<br />
* If the question is being asked now, answer it now, even if the answer is "We won't have an answer for that until later." Be sure to define 'later'. Also be sure to come back and update the person when that thing happens.<br />
<br />
* Never be afraid to ask the user to clarify something. If they're asking a question that could be X, but might be Y, answer X, but say "You might also mean Y. If you do, here's the quick overview, and if that doesn't answer your question, let us know." <br />
<br />
* Never be afraid to ask the user for more information. If they say "X is broken", don't be afraid to say something like, "So that we can diagnose the problem, can you tell me exactly what happens when you try to X?" (Of course, be sure to go and try X yourself first, to see if you can figure out why the user thinks it's broken and save some time.)<br />
<br />
* Aim for answering all of the user's questions (even the questions they don't know they need to ask) in a single contact, but don't worry if you can't get it. If you ever think that you might not have given them a complete answer, if you think that they might have more questions, or if you're offering them a fix that might or might not fully solve their problem, include an explicit invitation for them to come back to the request and let you know if it doesn't work.<br />
<br />
[[Category: Support]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/S2_CSSS2 CSS2009-04-27T06:39:31Z<p>Echan: </p>
<hr />
<div>[[Category: S2 CSS]]<br />
<br />
= Overview =<br />
<br />
Want to create your own journal style? You're going to have to customise the CSS. This page tells you how.<br />
<br />
* [[CSS tutorial]] for those who are new to it, or could use some pointers<br />
<br />
= Information and Template =<br />
<br />
This page will have a list of all CSS classes used by Core2.<br />
<br />
<pre><nowiki>== class label ==<br />
<br />
* '''Affects:''' What part of the page does this CSS class cover?<br />
* '''Views:''' If it's only used on specific pages (eg year page, or reply page), or on all views<br />
* '''Other information'''<br />
</nowiki></pre><br />
<br />
= Current pages of ids and classes =<br />
<br />
* [[S2 CSS: High level layout ids and classes]]<br />
* [[S2 CSS: Entry ids and classes]] -- for entries on Recent, Reading, Entry, and Day pages<br />
* [[S2 CSS: Recent and Reading page ids and classes]]<br />
* [[S2 CSS: Entry page ids and classes]]<br />
* [[S2 CSS: Sidebar ids and classes]]<br />
* [[S2 CSS: Tag page ids and classes]]<br />
* [[S2 CSS: Archive pages ids and classes]] -- for year, month, and day pages<br />
<br />
= Unclassified classes =<br />
<br />
Got a class you want documented? List it here.<br />
<br />
[[Category: Styles]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/CSS_tutorialCSS tutorial2009-04-27T06:39:01Z<p>Echan: </p>
<hr />
<div>[[Category: S2 CSS]]<br />
<br />
This is a CSS tutorial for those who are just starting out with [[S2 CSS]] and need a primer.<br />
<br />
== What is CSS? ==<br />
<br />
CSS (Cascading Style Sheets) are used to provide visual styling to web content. The idea is that a webpage is marked up in HTML that describes what the content *is*, while CSS describes what the content *looks like*. This means that you can provide a single webpage with exactly the same HTML code and, if it's marked up properly, different people can experience it in different ways by applying different stylesheets to it.<br />
<br />
An example:<br />
<br />
Your HTML code says <br />
<br />
&lt;h1&gt;Welcome to my journal&lt;/h1&gt;<br />
<br />
Your CSS says:<br />
<br />
h1: { color: #ff0000; }<br />
<br />
Result: the heading "Welcome to my journal" will be displayed in red.<br />
<br />
CSS can be used to specify any of:<br />
<br />
* foreground and background colours<br />
* fonts, sizes, etc<br />
* positioning on the screen<br />
* spacing between lines and characters<br />
* borders, underlines<br />
* spacing, margins<br />
* ... and more<br />
<br />
These can be applied to any element on the page, either by HTML tag (as in the h1 example above) or by class of element (many elements with the same role, eg. &lt;div class="entry"&gt; which is used for each entry on a DW journal page), or by the id of a single specific element.<br />
<br />
The "cascading" in Cascading Style Sheets refers to the nested relationship between HTML elements. All viewable parts of the page are nested within the &lt;body&gt; element, and so on down through layout sections, paragraphs, right through to the very smallest elements. When you apply a CSS style to any element on the page, that styling "cascades" down through any children, allowing you to write the minimum amount of CSS necessary to style the whole page.<br />
<br />
== Learning CSS ==<br />
<br />
The official source of CSS documentation is the W3C. Check out the [http://www.w3.org/TR/CSS2/ CSS 2.0 Specification].<br />
<br />
== CSS tools ==<br />
<br />
The following tools are recommended to help you explore and understand the CSS on any webpage.<br />
<br />
=== Firefox plugins ===<br />
<br />
* CSSViewer<br />
* Firebug<br />
<br />
[[Category: Styles]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/S2_CSS:_Entry_ids_and_classesS2 CSS: Entry ids and classes2009-04-27T06:37:57Z<p>Echan: added category</p>
<hr />
<div>[[Category: S2 CSS]]<br />
<br />
{{Expand|text=This page is mostly finished, but not entirely. It should be synced after open beta, as I've opened a bug with suggestions I've come up with while doing this, which may or may not get implemented. --[[User:Foxfirefey|Foxfirefey]] 20:41, 26 April 2009 (UTC)}}<br />
<br />
The following are found inside of div.entry within the #primary section of the page. These all occur on the Reading, Recent, Entry, and Day pages unless otherwise noted.<br />
<br />
= Outer shell =<br />
<br />
== <tt>.entry-wrapper</tt> ==<br />
<br />
This, along with its nested <tt>div.inner</tt>, wraps around the entire entry and all of its classes. <br />
<br />
=== Associated classes ===<br />
<br />
The below are all classes that are associated with the <tt>.entry-wrapper</tt>.<br />
<br />
==== Even/Odd ====<br />
<br />
Note: entries on Entry pages are always <tt>.entry-wrapper-odd</tt>.<br />
<br />
* <tt>.entry-wrapper-odd</tt><br />
* <tt>.entry-wrapper-even</tt><br />
<br />
{{Warn|text=These are currently <tt>.entry-wrapper-a</tt> and <tt>.entry-wrapper-b</tt>.}}<br />
<br />
==== Security ====<br />
<br />
Indicates the security level of a post.<br />
<br />
* '''<tt>.security-public</tt>'''<br />
* '''<tt>.security-custom</tt>'''<br />
* '''<tt>.security-protected</tt>'''<br />
* '''<tt>.security-private</tt>'''<br />
<br />
==== Adult content ====<br />
<br />
{{Warn|text=These are not named this currently!}}<br />
<br />
* '''<tt>.restrictions-18</tt>'''<br />
* '''<tt>.restrictions-nsfw</tt>'''<br />
* '''<tt>.restrictions-none</tt>'''<br />
<br />
==== Journal type and poster ====<br />
<br />
{{Warn|text= <tt>.journal-$JOURNAL</tt> not currently added to posts on personal journals.}}<br />
<br />
* '''<tt>.journal-type-P</tt>'''<br />
* '''<tt>.journal-type-C</tt>'''<br />
* '''<tt>.poster-$USER</tt>''' -- indicates the specific poster<br />
* '''<tt>.journal-$JOURNAL</tt>''' -- indicates the journal posted in, ie a community<br />
<br />
==== Other ====<br />
<br />
* '''<tt>.has-userpic</tt>''' -- This post has a userpic associated with it<br />
<br />
=== <tt>.separator .separator-before</tt> ===<br />
<br />
{{Warn|text=This is currently <tt>.separator-pre.</tt>}}<br />
<br />
<tt>.separator</tt> classes are found within the <tt>.entry-wrapper</tt>. They can be associated with: <br />
<br />
* <tt>.separator-before</tt> -- A separator that is before the main <tt>.entry</tt> class<br />
* <tt>.separator-after</tt> -- A separator that is after the main <tt>.entry</tt> class<br />
<br />
There is no content actually <i>in</i> these divs.<br />
<br />
=== <tt>.entry</tt> ===<br />
<br />
This class is inside <tt>.entry-wrapper</tt> and has its own <tt>div.inner</tt>.<br />
<br />
* '''Affects:''' All of a single entry: subject, text, date, mood/music, readlinks, icon, user/community name on readlist view<br />
<br />
=== <tt>.separator .separator-after</tt> ===<br />
<br />
{{Warn|text=This is currently <tt>.separator-pre.</tt>}}<br />
<br />
This <tt>.separator</tt> classes are found within the <tt>.entry-wrapper</tt>. They can be associated with: <br />
<br />
* <tt>.separator-before</tt> -- A separator that is before the main <tt>.entry</tt> class<br />
* <tt>.separator-after</tt> -- A separator that is after the main <tt>.entry</tt> class<br />
<br />
= Inside <tt>.entry</tt> =<br />
<br />
== <tt>div.header</tt> ==<br />
<br />
* '''Affects:''' Heading for each entry<br />
* '''Other information:''' Contains the entry subject matter (<tt>h3.entry-title</tt>) as well as the date/time stamp and classes for showing access filters (eg. the lock icon) and adult content filters (eg. the NSFW warning)<br />
<br />
=== <tt>h3.entry-title</tt> ===<br />
<br />
* '''Affects:''' Subject line<br />
* '''Other information:''' Subjects are shown as links, so the text of the subject line is technically found inside ''<tt>h3.entry.title a</tt>'' unless the subject itself contains a link; then only that link is printed as a link.<br />
<br />
=== <tt>span.datetime</tt> ===<br />
<br />
==== <tt>span.date</tt> ====<br />
<br />
* '''Affects:''' The date stamp on an entry<br />
* '''Other information:''' Within <tt>span.date</tt> are several a elements, for each of year/month/day.<br />
<br />
==== <tt>span.time</tt> ====<br />
<br />
* '''Affects:''' The time of day (eg. "06:53pm") that a post is made<br />
* '''Other information:''' This is found inside <tt>div.datetime</tt>.<br />
<br />
== <tt>div.contents</tt> ==<br />
<br />
* '''Affects:''' The body of an entry; what the person posted, with the userpic and poster.<br />
* '''Other information:''' This div has a nested <tt>div.inner</tt>.<br />
<br />
=== <tt>div.userpic</tt> ===<br />
<br />
* '''Affects:''' Userpics<br />
* '''Other information:''' Found within entries and also comments.<br />
<br />
=== <tt>span.poster</tt> ===<br />
<br />
This is also associated with <tt>span.entry-poster</tt>, to separate it from another <tt>span.poster</tt> in comments, which is associated with <tt>span.comment-poster</tt>. This span contains a <tt>span.ljuser</tt> as well.<br />
<br />
=== <tt>div.entry-content</tt> ===<br />
<br />
* '''Affects:''' The contents of the entry.<br />
<br />
=== <tt>div.entry-metadata</tt> ===<br />
<br />
Contains a series of spans with the following classes:<br />
<br />
* <tt>.metadata-label</tt> <br />
* <tt>.metadata-item</tt><br />
* <tt>.metadata-label-location</tt><br />
* <tt>.metadata-item-location</tt><br />
* <tt>.metadata-label-mood</tt><br />
* <tt>.metadata-item-mood</tt><br />
* <tt>.metadata-label-music</tt><br />
* <tt>.metadata-item-music</tt><br />
<br />
== <tt>div.footer</tt> ==<br />
<br />
* '''Affects:''' Tags and other metadata, management links, and interaction links.<br />
* '''Other information:''' This div has a nested <tt>div.inner</tt>.<br />
<br />
=== <tt>div.tag</tt> ===<br />
<br />
* '''Affects:''' The div containing the tags on a post, including any "Tags:" heading<br />
* '''Other information:''' The tags themselves are within a unordered list inside this div.<br />
<br />
==== <tt>span.tagtext</tt> ====<br />
<br />
This is the text that goes before the tag list, ie "Tags:".<br />
<br />
==== <tt>ul</tt> ====<br />
<br />
This list contains all of the tag links.<br />
<br />
=== <tt>ul.entry-management-links</tt> ===<br />
<br />
Note: This category is done a little bit differently on [[S2 CSS: Entry page ids and classes|entry pages]].<br />
<br />
* '''Affects:''' The links/buttons which allow you to manage an entry, eg. edit/tag/memories/email/track<br />
* '''Other information''' What falls in this category rather than in entry-interaction-links, I hear you ask. Well, these buttons/links seem to send you away from the entry's page, while the interaction links all link to the entry's page.<br />
<br />
==== Specific link classes ====<br />
<br />
* '''<tt>li.link</tt>''' -- General class for all of them<br />
* '''<tt>li.mem_add</tt>''' -- For adding to the memories<br />
* '''<tt>li.tell_friend</tt>''' -- For telling a friend<br />
* '''<tt>li.watch_commands</tt>''' -- For the tracking system NOTE: MIGHT CHANGE TO TRACK COMMENTS<br />
* '''<tt>li.edit_entry</tt>''' -- For editing the entry<br />
* '''<tt>li.edit_tags</tt>''' -- For editing the entry's tags<br />
<br />
=== <tt>ul.entry-interaction-links</tt> ===<br />
<br />
Note: This category is done a little bit differently on [[S2 CSS: Entry page ids and classes|entry pages]].<br />
<br />
* '''Affects:''' The list of links for each entry that read Link/N comments/leave a comment<br />
* '''Other information''' The text of these links can be changed by the journal owner through "Customize styles", so beware that they may be longer/shorter than you think.<br />
<br />
==== Specific link classes ====<br />
<br />
* '''<tt>li.entry-permalink</tt>''' -- The "Link" link; does not appear(?) if there are comments.<br />
* '''<tt>li.entry-readlink</tt>''' -- The "N comments" link, where N is a number; may be customised by the user to say something else. Don't make assumptions about the length of the text. Does not appear if there are no comments.<br />
* '''<tt>li.entry-postlink</tt>''' -- Link for commenting, change to <tt>li.entry-commentlink</tt> suggested; May be customised by the user to say something else. Don't make assumptions about the length of the text. Does not appear if comments are disallowed.</div>Echan//wiki.dreamwidth.net/wiki/index.php/Common_JargonCommon Jargon2009-04-26T16:44:57Z<p>Echan: /* Abbreviations */ added tl,dr</p>
<hr />
<div>The Dreamwidth project has some jargon in common use that may not be familiar to the general public. While these are not official terms that you should know, or necessarily Dreamwidth-specific, general explanations or definitions may be helpful. <br />
<br />
=Words= <br />
<br />
; Alton Brown anal nachos: Alton Brown's perhaps unnecessarily fussy [http://www.foodnetwork.com/recipes/alton-brown/ultimate-nachos-recipe2/index.html recipe for nachos]. (From IRC. You really had to be there.) <br />
<br />
; BNF: Big Name Fan. All the conflicting definitions seem to boil down to "a fan who is (very) famous within fandom". (From Western science fiction/fantasy book & media fandom.) <br />
<br />
; butterfinger: Mark branched out into [http://qdb.zhzh.org/dw/46 fanfiction]. (From IRC.) <br />
<br />
; cat macros: Images of cats with funny captions. Sometimes used as a form of protest and/or mockery. (From the internet.) <br />
<br />
; coed(s), invite coed(s): A deliberate misspelling of 'code', as in 'invite code(s)'. (From LiveJournal.) <br />
<br />
; earworm: [http://en.wikipedia.org/wiki/Earworm a song that gets stuck in your head]. See <dwcomm>earworm</dwcomm> and <dwcomm>earwormhole</dwcomm>. <br />
<br />
; fandom: A general term for a community of people who are fans of things, such as "sports fandom", or "Star Trek fandom". When used without qualification, it often (but not always) refers to Western science fiction and fantasy book and media fandom, or a certain subset of same. <br />
<br />
; nipplegate: A controversial LiveJournal event. (From LiveJournal.) <br />
<br />
; NSFW/NWS: Not Safe For Work / Not Work-Safe. Content that the average boss/mother-in-law might not appreciate. You can mark an entry as NSFW by setting the Age Restriction to Viewer Discretion Advised, and get warned about NSFW entries [http://www.dreamwidth.org/manage/settings/?cat=display by setting your Viewing Adult Content setting to Content Should Be Viewed with Discretion]. (FAQ not yet available; link to it when it is.) (From the internet.) <br />
<br />
; !pleh: 'Help!' spelled backwards. (From LiveJournal Support.) <br />
<br />
; slash: Purists will insist that this is fanfiction involving two male characters (who are not ordinarily involved) in a romantic or sexual situation. Not-so-purists can stretch this to mean any explicit fanfiction. One could write dissertations on the finer nuances. (From the fanfictiony parts of fandom.) <br />
<br />
; spoons: Finite physical/mental/emotional resources to handle daily tasks. More: [http://echan.dreamwidth.org/1086.html WTF Spoons]. (From disability advocacy.) <br />
<br />
; strikethrough: A controversial LiveJournal event. (From LiveJournal.) <br />
<br />
; twix: Mark branched out into [http://qdb.zhzh.org/dw/46 fanfiction]. (From IRC.) <br />
<br />
; zilch: An addictive dice-rolling game, with a computer that cheats. Can be found in [[IRC]], in #zilch. For all mentions of Zilch, developers take 1d6 hit to productivity.<br />
<br />
=Abbreviations=<br />
<br />
; afaik: As Far As I Know<br />
<br />
; afk: Away From Keyboard<br />
<br />
; ffs: For F-ck's Sake<br />
<br />
; iawtc: I Agree With This Comment<br />
<br />
; idk: I Don't Know<br />
<br />
; iirc: If I Recall Correctly<br />
<br />
; tl,dr: Too Long, Didn't Read. Usually said as either a joke or an insult.<br />
<br />
; wtf: Often "What the F***"; on Dreamwidth, also "Watch-Trust-Friend"; see Technical <br />
<br />
; ymmv: Your Mileage May Vary (it may be different for you; "your mileage may vary" is from auto commercials)<br />
<br />
=Technical= <br />
<br />
; Beta: Contrary to the precedent set by things like Gmail, "beta" actually means "we expect that stuff is going to be broken, that's why it's not out of beta yet". (From geek jargon.) <br />
<br />
; Bikeshed(ding): Descending into increasingly-fine hair-splitting and world-ending pro/con over an issue that's rather small in the grander scheme of the project, particularly in a "push" environment such as e-mail. See [[Bikeshed]]. (From the Open Source technical community.) <br />
<br />
; Cat: Short for Support Category. (From LiveJournal support.) <br />
<br />
; ESN: Event-Subscription-Notification, the original development name for what eventually became the inbox/[http://www.dreamwidth.org/support/faq.bml#notify notification] system. (From LiveJournal developers.) <br />
<br />
; Green: a technical support question without an answer (or without an answer that has been reviewed and approved by senior support). (From LiveJournal support.) <br />
<br />
; Kitten: a support category that has very few requests in it. Wordplay. Support Category = Category = Cat; cat that is very small = kitten. (From LiveJournal support.) <br />
<br />
; OpenID: A way for a website to know that you totally are who you claim to be from that other website over there. [http://azurelunatic.livejournal.com/6054113.html An informal explanation.] [http://www.dreamwidth.org/support/faqbrowse.bml?faqid=62 Dreamwidth OpenID FAQ] (From LiveJournal; Brad developed it!) <br />
<br />
; RTE: Rich Text Editor, something that lets you add formatting to text as well as just do plain text. Contrast with HTML editor (plain text, although you can type in HTML formatting manually). LJ's RTE gathered a lot of dislike from LJ volunteers. (From internet in general & LiveJournal.) <br />
<br />
; WTF/Project WTF: Rather than "What The F---", this is Watch-Trust-Friend(s), the project of splitting LiveJournal's original Friends into Watch/Trust (this eventually became Read/Access). (From LiveJournal development and then Dreamwidth development.)<br />
<br />
=People= <br />
<br />
;<dwuser>Mark</dwuser>: Mark Smith is one half of the founding team of Dreamwidth. He is also known as <dwuser>xb95</dwuser>.<br />
;<dwuser>Denise</dwuser>: Denise Paolucci is one half of the founding team of the site. She is known as Rahaeli or rah on IRC. She is also known as D and <dwuser>synecdochic</dwuser>.<br />
<br />
; [http://www.dreamwidth.org/site/staff.bml Staff Page]<br />
<br />
;Brad: [http://en.wikipedia.org/wiki/Brad_Fitzpatrick Brad Fitzpatrick] is the original creator of LiveJournal. While he is not affiliated with the Dreamwidth project, if someone name-drops "Brad", it's probably him. (However, <dwuser>brad</dwuser> is not him.)<br />
<br />
=Other Resources=<br />
;[http://catb.org/jargon/ Jargon File]: Many words from a gentler, more precise era of technology, although some are still in use today. <br />
;[http://www.urbandictionary.com/ Urban Dictionary]: Let the reader beware.</div>Echan//wiki.dreamwidth.net/wiki/index.php/Common_JargonCommon Jargon2009-04-26T16:43:54Z<p>Echan: changed bikeshed link, changed list type from unordered to definitions, reworded founders info</p>
<hr />
<div>The Dreamwidth project has some jargon in common use that may not be familiar to the general public. While these are not official terms that you should know, or necessarily Dreamwidth-specific, general explanations or definitions may be helpful. <br />
<br />
=Words= <br />
<br />
; Alton Brown anal nachos: Alton Brown's perhaps unnecessarily fussy [http://www.foodnetwork.com/recipes/alton-brown/ultimate-nachos-recipe2/index.html recipe for nachos]. (From IRC. You really had to be there.) <br />
<br />
; BNF: Big Name Fan. All the conflicting definitions seem to boil down to "a fan who is (very) famous within fandom". (From Western science fiction/fantasy book & media fandom.) <br />
<br />
; butterfinger: Mark branched out into [http://qdb.zhzh.org/dw/46 fanfiction]. (From IRC.) <br />
<br />
; cat macros: Images of cats with funny captions. Sometimes used as a form of protest and/or mockery. (From the internet.) <br />
<br />
; coed(s), invite coed(s): A deliberate misspelling of 'code', as in 'invite code(s)'. (From LiveJournal.) <br />
<br />
; earworm: [http://en.wikipedia.org/wiki/Earworm a song that gets stuck in your head]. See <dwcomm>earworm</dwcomm> and <dwcomm>earwormhole</dwcomm>. <br />
<br />
; fandom: A general term for a community of people who are fans of things, such as "sports fandom", or "Star Trek fandom". When used without qualification, it often (but not always) refers to Western science fiction and fantasy book and media fandom, or a certain subset of same. <br />
<br />
; nipplegate: A controversial LiveJournal event. (From LiveJournal.) <br />
<br />
; NSFW/NWS: Not Safe For Work / Not Work-Safe. Content that the average boss/mother-in-law might not appreciate. You can mark an entry as NSFW by setting the Age Restriction to Viewer Discretion Advised, and get warned about NSFW entries [http://www.dreamwidth.org/manage/settings/?cat=display by setting your Viewing Adult Content setting to Content Should Be Viewed with Discretion]. (FAQ not yet available; link to it when it is.) (From the internet.) <br />
<br />
; !pleh: 'Help!' spelled backwards. (From LiveJournal Support.) <br />
<br />
; slash: Purists will insist that this is fanfiction involving two male characters (who are not ordinarily involved) in a romantic or sexual situation. Not-so-purists can stretch this to mean any explicit fanfiction. One could write dissertations on the finer nuances. (From the fanfictiony parts of fandom.) <br />
<br />
; spoons: Finite physical/mental/emotional resources to handle daily tasks. More: [http://echan.dreamwidth.org/1086.html WTF Spoons]. (From disability advocacy.) <br />
<br />
; strikethrough: A controversial LiveJournal event. (From LiveJournal.) <br />
<br />
; twix: Mark branched out into [http://qdb.zhzh.org/dw/46 fanfiction]. (From IRC.) <br />
<br />
; zilch: An addictive dice-rolling game, with a computer that cheats. Can be found in [[IRC]], in #zilch. For all mentions of Zilch, developers take 1d6 hit to productivity.<br />
<br />
=Abbreviations=<br />
<br />
; afaik: As Far As I Know<br />
<br />
; afk: Away From Keyboard<br />
<br />
; ffs: For F-ck's Sake<br />
<br />
; iawtc: I Agree With This Comment<br />
<br />
; idk: I Don't Know<br />
<br />
; iirc: If I Recall Correctly<br />
<br />
; wtf: Often "What the F***"; on Dreamwidth, also "Watch-Trust-Friend"; see Technical <br />
<br />
; ymmv: Your Mileage May Vary (it may be different for you; "your mileage may vary" is from auto commercials)<br />
<br />
=Technical= <br />
<br />
; Beta: Contrary to the precedent set by things like Gmail, "beta" actually means "we expect that stuff is going to be broken, that's why it's not out of beta yet". (From geek jargon.) <br />
<br />
; Bikeshed(ding): Descending into increasingly-fine hair-splitting and world-ending pro/con over an issue that's rather small in the grander scheme of the project, particularly in a "push" environment such as e-mail. See [[Bikeshed]]. (From the Open Source technical community.) <br />
<br />
; Cat: Short for Support Category. (From LiveJournal support.) <br />
<br />
; ESN: Event-Subscription-Notification, the original development name for what eventually became the inbox/[http://www.dreamwidth.org/support/faq.bml#notify notification] system. (From LiveJournal developers.) <br />
<br />
; Green: a technical support question without an answer (or without an answer that has been reviewed and approved by senior support). (From LiveJournal support.) <br />
<br />
; Kitten: a support category that has very few requests in it. Wordplay. Support Category = Category = Cat; cat that is very small = kitten. (From LiveJournal support.) <br />
<br />
; OpenID: A way for a website to know that you totally are who you claim to be from that other website over there. [http://azurelunatic.livejournal.com/6054113.html An informal explanation.] [http://www.dreamwidth.org/support/faqbrowse.bml?faqid=62 Dreamwidth OpenID FAQ] (From LiveJournal; Brad developed it!) <br />
<br />
; RTE: Rich Text Editor, something that lets you add formatting to text as well as just do plain text. Contrast with HTML editor (plain text, although you can type in HTML formatting manually). LJ's RTE gathered a lot of dislike from LJ volunteers. (From internet in general & LiveJournal.) <br />
<br />
; WTF/Project WTF: Rather than "What The F---", this is Watch-Trust-Friend(s), the project of splitting LiveJournal's original Friends into Watch/Trust (this eventually became Read/Access). (From LiveJournal development and then Dreamwidth development.)<br />
<br />
=People= <br />
<br />
;<dwuser>Mark</dwuser>: Mark Smith is one half of the founding team of Dreamwidth. He is also known as <dwuser>xb95</dwuser>.<br />
;<dwuser>Denise</dwuser>: Denise Paolucci is one half of the founding team of the site. She is known as Rahaeli or rah on IRC. She is also known as D and <dwuser>synecdochic</dwuser>.<br />
<br />
; [http://www.dreamwidth.org/site/staff.bml Staff Page]<br />
<br />
;Brad: [http://en.wikipedia.org/wiki/Brad_Fitzpatrick Brad Fitzpatrick] is the original creator of LiveJournal. While he is not affiliated with the Dreamwidth project, if someone name-drops "Brad", it's probably him. (However, <dwuser>brad</dwuser> is not him.)<br />
<br />
=Other Resources=<br />
;[http://catb.org/jargon/ Jargon File]: Many words from a gentler, more precise era of technology, although some are still in use today. <br />
;[http://www.urbandictionary.com/ Urban Dictionary]: Let the reader beware.</div>Echan//wiki.dreamwidth.net/wiki/index.php/Main_PageMain Page2009-04-26T14:31:17Z<p>Echan: reworded intro paragraph</p>
<hr />
<div>Hello! This is a wiki for keeping notes on Dreamwidth's continuing evolution. Those involved can use this wiki as a resource for discussion, communication, answers, and occasional giggles. <br />
<br />
Dreamwidth's leaders are using the wiki too, but that doesn't necessarily mean that everything here is up-to-date with their current opinion on things. When in doubt, information on [http://lists.dwscoalition.org/cgi-bin/mailman/listinfo the mailing lists] trumps any information here. <br />
<br />
More information about Dreamwidth can be found at [http://dreamwidth.org/ dreamwidth.org] and at [[Dreamwidth.org: FAQ]] and [[Notable Dreamwidth Reading]].<br />
<br />
Please address any questions or problems with the wiki to [[User:Foxfirefey]], who's in charge. The best way to contact her is <code>skittisheclipse@gmail.com</code>.<br />
<br />
== Current Happenings ==<br />
<br />
We have reached closed beta! [http://dreamwidth.org/ Check it out]! Beta testers, read [[Beta Testing]] for useful information.<br />
<br />
[http://dw-news.dreamwidth.org/2173.html Open beta launches April 30th!]<br />
<br />
We are documenting current and future volunteers at [[Who]] and [[Volunteers In Waiting]]. Projects that must be completed before launch: [[Dreamwidth.org: Pre-Launch]]. And what initiative would be complete without [[:Category: Dreamwidth Icons|icons]], [[:Category: Dreamwidth Banners|banners]], and [[:Category: Dreamwidth Macros|macros]]? If you want to make your own, there's [[:Category: Dreamwidth Stock Images|stock imagery]] you can use. If you make a post about Dreamwidth (see [[Advocacy]]), we are making a list of [[Why Dreamwidth]] posts.<br />
<br />
== Projects == <br />
<br />
These are some of the big areas of the wiki.<br />
<br />
* [[Development]] -- work on the Dreamwidth code base<br />
* [[Documentation]] -- how to write great documentation for users<br />
* [[Styles]] -- currently documenting the heck out of S2<br />
* [[From LJ Suggestions]] -- features people wish Dreamwidth included<br />
<br />
If none of these interest you, or you are looking for something specific, check out [[:Category:Index]].<br />
<br />
[[Category: Index]]<br />
__NOTOC__</div>Echan//wiki.dreamwidth.net/wiki/index.php/Main_PageMain Page2009-04-26T14:23:55Z<p>Echan: /* Projects */ rewrote it based on active projects and Special:PopularPages</p>
<hr />
<div>Hello! This is a wiki for keeping notes on Dreamwidth's creation. Everyone involved in making Dreamwidth a reality can use this wiki as a resource for discussion, communication, answers, and occasional giggles. <br />
<br />
Dreamwidth's leaders are using the wiki too, but that doesn't necessarily mean that everything here is up-to-date with their current opinion on things. When in doubt, information on [http://lists.dwscoalition.org/cgi-bin/mailman/listinfo the mailing lists] trumps any information here. <br />
<br />
More information about Dreamwidth can be found at [http://dreamwidth.org/ dreamwidth.org] and at [[Dreamwidth.org: FAQ]] and [[Notable Dreamwidth Reading]].<br />
<br />
Please address any questions or problems with the wiki to [[User:Foxfirefey]], who's in charge. The best way to contact her is <code>skittisheclipse@gmail.com</code>.<br />
<br />
== Current Happenings ==<br />
<br />
We have reached closed beta! [http://dreamwidth.org/ Check it out]! Beta testers, read [[Beta Testing]] for useful information.<br />
<br />
[http://dw-news.dreamwidth.org/2173.html Open beta launches April 30th!]<br />
<br />
We are documenting current and future volunteers at [[Who]] and [[Volunteers In Waiting]]. Projects that must be completed before launch: [[Dreamwidth.org: Pre-Launch]]. And what initiative would be complete without [[:Category: Dreamwidth Icons|icons]], [[:Category: Dreamwidth Banners|banners]], and [[:Category: Dreamwidth Macros|macros]]? If you want to make your own, there's [[:Category: Dreamwidth Stock Images|stock imagery]] you can use. If you make a post about Dreamwidth (see [[Advocacy]]), we are making a list of [[Why Dreamwidth]] posts.<br />
<br />
== Projects == <br />
<br />
These are some of the big areas of the wiki.<br />
<br />
* [[Development]] -- work on the Dreamwidth code base<br />
* [[Documentation]] -- how to write great documentation for users<br />
* [[Styles]] -- currently documenting the heck out of S2<br />
* [[From LJ Suggestions]] -- features people wish Dreamwidth included<br />
<br />
If none of these interest you, or you are looking for something specific, check out [[:Category:Index]].<br />
<br />
[[Category: Index]]<br />
__NOTOC__</div>Echan//wiki.dreamwidth.net/wiki/index.php/Main_PageMain Page2009-04-26T14:16:53Z<p>Echan: /* Current Developments */ changed heading, to be less confusing with the Development category</p>
<hr />
<div>Hello! This is a wiki for keeping notes on Dreamwidth's creation. Everyone involved in making Dreamwidth a reality can use this wiki as a resource for discussion, communication, answers, and occasional giggles. <br />
<br />
Dreamwidth's leaders are using the wiki too, but that doesn't necessarily mean that everything here is up-to-date with their current opinion on things. When in doubt, information on [http://lists.dwscoalition.org/cgi-bin/mailman/listinfo the mailing lists] trumps any information here. <br />
<br />
More information about Dreamwidth can be found at [http://dreamwidth.org/ dreamwidth.org] and at [[Dreamwidth.org: FAQ]] and [[Notable Dreamwidth Reading]].<br />
<br />
Please address any questions or problems with the wiki to [[User:Foxfirefey]], who's in charge. The best way to contact her is <code>skittisheclipse@gmail.com</code>.<br />
<br />
== Current Happenings ==<br />
<br />
We have reached closed beta! [http://dreamwidth.org/ Check it out]! Beta testers, read [[Beta Testing]] for useful information.<br />
<br />
[http://dw-news.dreamwidth.org/2173.html Open beta launches April 30th!]<br />
<br />
We are documenting current and future volunteers at [[Who]] and [[Volunteers In Waiting]]. Projects that must be completed before launch: [[Dreamwidth.org: Pre-Launch]]. And what initiative would be complete without [[:Category: Dreamwidth Icons|icons]], [[:Category: Dreamwidth Banners|banners]], and [[:Category: Dreamwidth Macros|macros]]? If you want to make your own, there's [[:Category: Dreamwidth Stock Images|stock imagery]] you can use. If you make a post about Dreamwidth (see [[Advocacy]]), we are making a list of [[Why Dreamwidth]] posts.<br />
<br />
== Projects == <br />
<br />
These are some of the big areas of the wiki.<br />
<br />
* [[Development]]<br />
* [[Design]]<br />
* [[Documentation]]<br />
* [[Styles]]<br />
* [[From LJ Suggestions]]<br />
* [[Production]]<br />
<br />
[[Category: Index]]<br />
__NOTOC__</div>Echan//wiki.dreamwidth.net/wiki/index.php/Category:WishlistsCategory:Wishlists2009-04-26T14:12:35Z<p>Echan: changed category</p>
<hr />
<div>A collection of pages to put down wishes.<br />
<br />
[[Category: New Ideas]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/Category:New_IdeasCategory:New Ideas2009-04-26T14:11:52Z<p>Echan: </p>
<hr />
<div>[[Category: Index]]<br />
Got ideas on features you want? Ways to make Dreamwidth better? This is that category!</div>Echan//wiki.dreamwidth.net/wiki/index.php/Category:New_IdeasCategory:New Ideas2009-04-26T14:10:54Z<p>Echan: Created page with 'Got ideas on features you want? Ways to make Dreamwidth better? This is that category!'</p>
<hr />
<div>Got ideas on features you want? Ways to make Dreamwidth better? This is that category!</div>Echan//wiki.dreamwidth.net/wiki/index.php/Category:BrainstormingCategory:Brainstorming2009-04-26T14:10:15Z<p>Echan: changed category</p>
<hr />
<div>[[Category: New Ideas]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/Category:ClientsCategory:Clients2009-04-26T14:09:11Z<p>Echan: changed category</p>
<hr />
<div>[[Category: Dreamwidth.org]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/Category:AdministrationCategory:Administration2009-04-26T13:42:35Z<p>Echan: changed category to Production</p>
<hr />
<div>[[Category: Production]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/Production_Closed_Beta_ChecklistProduction Closed Beta Checklist2009-04-26T13:40:37Z<p>Echan: changed category to Obsolete</p>
<hr />
<div>[[Category: Obsolete]]<br />
<br />
This document describes the things that need to be done to have production setup for Closed Beta. This is the list of things Mark needs to do, mostly, as most of these can't really be farmed out yet.<br />
<br />
* Allocate four machines (small, 1GB each, $280/month?)<br />
** Two webservers, two databases<br />
* Databases...<br />
** One master, one slave<br />
** Slave takes no traffic, serves as replication target, does backups<br />
** Backups done nightly (if possible more often?)<br />
* Three memcache instances: both webservers, database slave<br />
* Gearman/TheSchwartz jobs run on database slave<br />
* Perlbal/public IP on one of the webservers<br />
* Internal IPs only on all the other machines<br />
<br />
What is missing?<br />
<br />
* DNS<br />
* Mail<br />
* ???</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-26T05:23:29Z<p>Echan: added more rows</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
(Also, please don't split up the table into multiple tables or wiki pages; I really want to be able to see everything together to identify patterns.)<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| takes invite code via URL or prompt, then prompts for account name/email/pw/age<br>account creation flow step 1 of 3<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|-<br />
| register.bml<br />
| register.bml.text<br />
| email validation dialog/success<br />
| E/C<br />
| S<br />
| /<br />
|-<br />
| reject.bml<br />
| reject.bml.text<br />
| reject someone's request to join a community<br />
| C<br />
| S<br />
| /<br />
|-<br />
| robots.txt<br />
| ''none''<br />
| commands to spiders<br />
| E<br />
| S<br />
| /<br />
|-<br />
| shop.bml<br />
| shop.bml.text<br />
| site store main storefront<br />
| E<br />
| S<br />
| /<br />
|- <br />
| stats.bml<br />
| stats.bml.text<br />
| site statistics<br />
| E<br />
| S<br />
| /<br />
|-<br />
| talkmulti.bml<br />
| talkmulti.bml.text<br />
| delete/screen/unscreen multiple comments<br />
| C<br />
| J<br />
| /<br />
|- <br />
| talkpost.bml<br />
| talkpost.bml.text<br />
| post comment dialog and immediate errors<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkpost_do.bml<br />
| talkpost_do.bml.text<br />
| actually post comment or error out<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkread.bml<br />
| talkread.bml.text<br />
| entry comment page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkread_s1short.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | hack to make S1 styles work? should be deleted?<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkscreen.bml<br />
| talkscreen.bml.text<br />
| freeze/unfreeze/screen/unscreen comments<br />
| C<br />
| J<br />
| /<br />
|-<br />
| update.bml<br />
| update.bml.text<br />
| post an entry<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| uploadpic.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
|<br />
| /<br />
|-<br />
| userinfo.bml<br />
| userinfo.bml.text<br />
| profile page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| capedit.bml<br />
| ''none''<br />
| edit user capabilities<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| clusterstatus.bml<br />
| ''none''<br />
| check clusters status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| dupkiller.bml<br />
| ''none''<br />
| delete a user's duplicate entries<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
| entryprops.bml<br />
| ''none''<br />
| check entry properties<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
| index.bml<br />
| index.bml.text<br />
| index page of admin pages<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| invitecodes.bml<br />
| ''none''<br />
| view details of invite code (by code or account)<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| logout_user.bml<br />
| ''none''<br />
| log a user out of the site<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| memcache.bml<br />
| ''none''<br />
| view current memcache conditions<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| memcache_view.bml<br />
| ''none''<br />
| view current memcache details<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| mysql_status.bml<br />
| ''none''<br />
| show current MySQL status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| navtag.bml<br />
| ''none''<br />
| tag pages for navigation<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| propedit.bml<br />
| ''none''<br />
| view and edit userprops<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| recent_comments.bml<br />
| ''none''<br />
| view a user's recent comments<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| spam_reports.bml<br />
| ''none''<br />
| view/handle spam reports<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| statushistory.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | ?<br />
| E<br />
| style="background:#ABCDEF" | S?<br />
| /admin/<br />
|-<br />
| styleinfo.bml<br />
| ''none''<br />
| show user's style info<br />
| E<br />
| style="background:#ABCDEF" | S?<br />
| /admin/<br />
|-<br />
| sysban.bml<br />
| ''none''<br />
| view/manage sysbans<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| theschwartz.bml<br />
| ''none''<br />
| view TheSchwartz queue job status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| userlog.bml<br />
| ''none''<br />
| view user's logged actions<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| index.bml<br />
| index.bml.text<br />
| admin console<br />
| E<br />
| J/S<br />
| /admin/console/<br />
|-<br />
| reference.bml<br />
| ''none''<br />
| console commands reference<br />
| E<br />
| S<br />
| /admin/console/<br />
|-<br />
| faqedit.bml<br />
| ''none''<br />
| edit a FAQ entry<br />
| style="background:#ABCDEF" | E?<br />
| S<br />
| /admin/faq/<br />
|-<br />
| index.bml<br />
| ''none''<br />
| index page for modifying the FAQs<br />
| E<br />
| S<br />
| /admin/faq/<br />
|-<br />
| readcat.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | read FAQs by category?<br />
| style="background:#ABCDEF" | E?<br />
| S<br />
| /admin/faq/<br />
|-<br />
| index.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | edit files? <br />
| E<br />
| S<br />
| /admin/fileedit/<br />
|-<br />
| distribute.bml<br />
| distribute.bml.text<br />
| generate/distribute invite codes<br />
| E<br />
| S<br />
| /admin/invites/<br />
|-<br />
| requests.bml<br />
| ''none''<br />
| view invite code requests<br />
| E<br />
| S<br />
| /admin/invites/<br />
|-<br />
| review.bml<br />
| ''none''<br />
| view user's invite code request history<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /admin/invites/<br />
|-<br />
| runoffpoll.bml<br />
| ''none''<br />
| calculate instant-runoff poll<br />
| style="background:#ABCDEF" | E?<br />
| style="background:#ABCDEF" | S?<br />
| /admin/misc/<br />
|-<br />
| import.bml<br />
| ''none''<br />
| import payment info<br />
| E<br />
| S<br />
| /admin/pay/<br />
|-<br />
| index.bml<br />
| ''none''<br />
| show user payment summary OR change user paid status<br />
| E<br />
| S<br />
| /admin/pay/<br />
|-<br />
| index.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | show user(s) privs?<br />
| E<br />
| S<br />
| /admin/priv/<br />
|-<br />
| add.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | add/preview a qotd?<br />
| E<br />
| S<br />
| /admin/qotd/<br />
|-<br />
| manage.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | stuff??<br />
| E<br />
| S<br />
| /admin/qotd/<br />
|-<br />
| index.bml<br />
| ''none''<br />
| view database table schema OR view/edit db table documentation<br />
| E<br />
| S<br />
| /admin/schema/<br />
|-<br />
| edit.bml<br />
| ''none''<br />
| edit/delete school data<br />
| E<br />
| S<br />
| /admin/schools/<br />
|-<br />
| index.bml<br />
| ''none''<br />
| school stats<br />
| E<br />
| S<br />
| /admin/schools/<br />
|-<br />
| merge.bml<br />
| ''none''<br />
| merge dup schools<br />
| style="background:#ABCDEF" | E?<br />
| S<br />
| /admin/schools/<br />
|-<br />
| pending.bml<br />
| ''none''<br />
| approve/reject pending schools<br />
| E<br />
| S<br />
| /admin/schools/<br />
|-<br />
| rename.bml<br />
| ''none''<br />
| change location of school(s)<br />
| E<br />
| S<br />
| /admin/schools/<br />
|-<br />
| add.bml<br />
| ''none''<br />
| add site message<br />
| E<br />
| S<br />
| /admin/sitemessages/<br />
|-<br />
<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-26T02:05:17Z<p>Echan: added more rows</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| takes invite code via URL or prompt, then prompts for account name/email/pw/age<br>account creation flow step 1 of 3<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|-<br />
| register.bml<br />
| register.bml.text<br />
| email validation dialog/success<br />
| E/C<br />
| S<br />
| /<br />
|-<br />
| reject.bml<br />
| reject.bml.text<br />
| reject someone's request to join a community<br />
| C<br />
| S<br />
| /<br />
|-<br />
| robots.txt<br />
| ''none''<br />
| commands to spiders<br />
| E<br />
| S<br />
| /<br />
|-<br />
| shop.bml<br />
| shop.bml.text<br />
| site store main storefront<br />
| E<br />
| S<br />
| /<br />
|- <br />
| stats.bml<br />
| stats.bml.text<br />
| site statistics<br />
| E<br />
| S<br />
| /<br />
|-<br />
| talkmulti.bml<br />
| talkmulti.bml.text<br />
| delete/screen/unscreen multiple comments<br />
| C<br />
| J<br />
| /<br />
|- <br />
| talkpost.bml<br />
| talkpost.bml.text<br />
| post comment dialog and immediate errors<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkpost_do.bml<br />
| talkpost_do.bml.text<br />
| actually post comment or error out<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkread.bml<br />
| talkread.bml.text<br />
| entry comment page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkread_s1short.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | hack to make S1 styles work? should be deleted?<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkscreen.bml<br />
| talkscreen.bml.text<br />
| freeze/unfreeze/screen/unscreen comments<br />
| C<br />
| J<br />
| /<br />
|-<br />
| update.bml<br />
| update.bml.text<br />
| post an entry<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| uploadpic.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
|<br />
| /<br />
|-<br />
| userinfo.bml<br />
| userinfo.bml.text<br />
| profile page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| capedit.bml<br />
| ''none''<br />
| edit user capabilities<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| clusterstatus.bml<br />
| ''none''<br />
| check clusters status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| dupkiller.bml<br />
| ''none''<br />
| delete a user's duplicate entries<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
| entryprops.bml<br />
| ''none''<br />
| check entry properties<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
| index.bml<br />
| index.bml.text<br />
| index page of admin pages<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| invitecodes.bml<br />
| ''none''<br />
| view details of invite code (by code or account)<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| logout_user.bml<br />
| ''none''<br />
| log a user out of the site<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| memcache.bml<br />
| ''none''<br />
| view current memcache conditions<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| memcache_view.bml<br />
| ''none''<br />
| view current memcache details<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| mysql_status.bml<br />
| ''none''<br />
| show current MySQL status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| navtag.bml<br />
| ''none''<br />
| tag pages for navigation<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| propedit.bml<br />
| ''none''<br />
| view and edit userprops<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| recent_comments.bml<br />
| ''none''<br />
| view a user's recent comments<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| spam_reports.bml<br />
| ''none''<br />
| view/handle spam reports<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| statushistory.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | ?<br />
| E<br />
| style="background:#ABCDEF" | S?<br />
| /admin/<br />
|-<br />
| styleinfo.bml<br />
| ''none''<br />
| show user's style info<br />
| E<br />
| style="background:#ABCDEF" | S?<br />
| /admin/<br />
|-<br />
| sysban.bml<br />
| ''none''<br />
| view/manage sysbans<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| theschwartz.bml<br />
| ''none''<br />
| view TheSchwartz queue job status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| userlog.bml<br />
| ''none''<br />
| view user's logged actions<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| index.bml<br />
| index.bml.text<br />
| admin console<br />
| E<br />
| J/S<br />
| /admin/console/<br />
|-<br />
| reference.bml<br />
| ''none''<br />
| console commands reference<br />
| E<br />
| S<br />
| /admin/console/<br />
|-<br />
| faqedit.bml<br />
| ''none''<br />
| edit a FAQ entry<br />
| style="background:#ABCDEF" | E?<br />
| S<br />
| /admin/faq/<br />
|-<br />
| index.bml<br />
| ''none''<br />
| index page for modifying the FAQs<br />
| E<br />
| S<br />
| /admin/faq/<br />
|-<br />
| readcat.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | read FAQs by category?<br />
| style="background:#ABCDEF" | E?<br />
| S<br />
| /admin/faq/<br />
|-<br />
| index.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | edit files? <br />
| E<br />
| S<br />
| /admin/fileedit/<br />
|-<br />
| distribute.bml<br />
| distribute.bml.text<br />
| generate/distribute invite codes<br />
| E<br />
| S<br />
| /admin/invites/<br />
|-<br />
| requests.bml<br />
| ''none''<br />
| view invite code requests<br />
| E<br />
| S<br />
| /admin/invites/<br />
|-<br />
| review.bml<br />
| ''none''<br />
| view user's invite code request history<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /admin/invites/<br />
|-<br />
| runoffpoll.bml<br />
| ''none''<br />
| calculate instant-runoff poll<br />
| style="background:#ABCDEF" | E?<br />
| style="background:#ABCDEF" | S?<br />
| /admin/misc/<br />
|-<br />
| import.bml<br />
| ''none''<br />
| import payment info<br />
| E<br />
| S<br />
| /admin/pay/<br />
|-<br />
| index.bml<br />
| ''none''<br />
| show user payment summary OR change user paid status<br />
| E<br />
| S<br />
| /admin/pay/<br />
|-<br />
| index.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | show user(s) privs?<br />
| E<br />
| S<br />
| /admin/priv/<br />
|-<br />
| add.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | add/preview a qotd?<br />
| E<br />
| S<br />
| /admin/qotd/<br />
|-<br />
| manage.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | stuff??<br />
| E<br />
| S<br />
| /admin/qotd/<br />
|-<br />
<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-25T15:15:15Z<p>Echan: added more rows</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| takes invite code via URL or prompt, then prompts for account name/email/pw/age<br>account creation flow step 1 of 3<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|-<br />
| register.bml<br />
| register.bml.text<br />
| email validation dialog/success<br />
| E/C<br />
| S<br />
| /<br />
|-<br />
| reject.bml<br />
| reject.bml.text<br />
| reject someone's request to join a community<br />
| C<br />
| S<br />
| /<br />
|-<br />
| robots.txt<br />
| ''none''<br />
| commands to spiders<br />
| E<br />
| S<br />
| /<br />
|-<br />
| shop.bml<br />
| shop.bml.text<br />
| site store main storefront<br />
| E<br />
| S<br />
| /<br />
|- <br />
| stats.bml<br />
| stats.bml.text<br />
| site statistics<br />
| E<br />
| S<br />
| /<br />
|-<br />
| talkmulti.bml<br />
| talkmulti.bml.text<br />
| delete/screen/unscreen multiple comments<br />
| C<br />
| J<br />
| /<br />
|- <br />
| talkpost.bml<br />
| talkpost.bml.text<br />
| post comment dialog and immediate errors<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkpost_do.bml<br />
| talkpost_do.bml.text<br />
| actually post comment or error out<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkread.bml<br />
| talkread.bml.text<br />
| entry comment page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkread_s1short.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | hack to make S1 styles work? should be deleted?<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkscreen.bml<br />
| talkscreen.bml.text<br />
| freeze/unfreeze/screen/unscreen comments<br />
| C<br />
| J<br />
| /<br />
|-<br />
| update.bml<br />
| update.bml.text<br />
| post an entry<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| uploadpic.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
|<br />
| /<br />
|-<br />
| userinfo.bml<br />
| userinfo.bml.text<br />
| profile page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| capedit.bml<br />
| ''none''<br />
| edit user capabilities<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| clusterstatus.bml<br />
| ''none''<br />
| check clusters status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| dupkiller.bml<br />
| ''none''<br />
| delete a user's duplicate entries<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
| entryprops.bml<br />
| ''none''<br />
| check entry properties<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
| index.bml<br />
| index.bml.text<br />
| index page of admin pages<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| invitecodes.bml<br />
| ''none''<br />
| view details of invite code (by code or account)<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| logout_user.bml<br />
| ''none''<br />
| log a user out of the site<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| memcache.bml<br />
| ''none''<br />
| view current memcache conditions<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| memcache_view.bml<br />
| ''none''<br />
| view current memcache details<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| mysql_status.bml<br />
| ''none''<br />
| show current MySQL status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| navtag.bml<br />
| ''none''<br />
| tag pages for navigation<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| propedit.bml<br />
| ''none''<br />
| view and edit userprops<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| recent_comments.bml<br />
| ''none''<br />
| view a user's recent comments<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| spam_reports.bml<br />
| ''none''<br />
| view/handle spam reports<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| statushistory.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | ?<br />
| E<br />
| style="background:#ABCDEF" | S?<br />
| /admin/<br />
|-<br />
| styleinfo.bml<br />
| ''none''<br />
| show user's style info<br />
| E<br />
| style="background:#ABCDEF" | S?<br />
| /admin/<br />
|-<br />
| sysban.bml<br />
| ''none''<br />
| view/manage sysbans<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| theschwartz.bml<br />
| ''none''<br />
| view TheSchwartz queue job status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| userlog.bml<br />
| ''none''<br />
| view user's logged actions<br />
| E<br />
| S<br />
| /admin/<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/User_talk:EchanUser talk:Echan2009-04-25T14:48:56Z<p>Echan: /* echan's scratchpad */ added account creation flow</p>
<hr />
<div>=Leave Messages Here=<br />
<br />
right here!<br />
<br />
<br />
<br />
<br />
<br />
=echan's scratchpad=<br />
==== dead categories ====<br />
Categories with all members recategorized, and verified to have no links to them. AKA, as deleted as can be without actually being deleted:<br />
* [[:Category:User documentation]]<br />
* [[:Category:Server management]]<br />
* [[:Category:Core2]]<br />
* [[:Category:Code documentation]]<br />
* [[:Category:BML]]<br />
* [[:Category:Suggestions]]<br />
<br />
<br />
==== account creation flow ====<br />
<pre><br />
1 - /create.bml -- takes URL parameters from email link<br />
prompts for username, email address, password, and birthday<br />
2 - /create/setup.bml -- funky dialog page for initial profile setup<br />
3 - /create/confirm.bml -- nothing but a "finished!" message and some links<br />
</pre></div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-25T14:29:21Z<p>Echan: added more rows</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| takes invite code via URL or prompt, then prompts for account name/email/pw/age<br>account creation flow step 1 of 3<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|-<br />
| register.bml<br />
| register.bml.text<br />
| email validation dialog/success<br />
| E/C<br />
| S<br />
| /<br />
|-<br />
| reject.bml<br />
| reject.bml.text<br />
| reject someone's request to join a community<br />
| C<br />
| S<br />
| /<br />
|-<br />
| robots.txt<br />
| ''none''<br />
| commands to spiders<br />
| E<br />
| S<br />
| /<br />
|-<br />
| shop.bml<br />
| shop.bml.text<br />
| site store main storefront<br />
| E<br />
| S<br />
| /<br />
|- <br />
| stats.bml<br />
| stats.bml.text<br />
| site statistics<br />
| E<br />
| S<br />
| /<br />
|-<br />
| talkmulti.bml<br />
| talkmulti.bml.text<br />
| delete/screen/unscreen multiple comments<br />
| C<br />
| J<br />
| /<br />
|- <br />
| talkpost.bml<br />
| talkpost.bml.text<br />
| post comment dialog and immediate errors<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkpost_do.bml<br />
| talkpost_do.bml.text<br />
| actually post comment or error out<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkread.bml<br />
| talkread.bml.text<br />
| entry comment page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkread_s1short.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | hack to make S1 styles work? should be deleted?<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkscreen.bml<br />
| talkscreen.bml.text<br />
| freeze/unfreeze/screen/unscreen comments<br />
| C<br />
| J<br />
| /<br />
|-<br />
| update.bml<br />
| update.bml.text<br />
| post an entry<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| uploadpic.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
|<br />
| /<br />
|-<br />
| userinfo.bml<br />
| userinfo.bml.text<br />
| profile page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| capedit.bml<br />
| ''none''<br />
| edit user capabilities<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| clusterstatus.bml<br />
| ''none''<br />
| check clusters status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| dupkiller.bml<br />
| ''none''<br />
| delete a user's duplicate entries<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
| entryprops.bml<br />
| ''none''<br />
| check entry properties<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
| index.bml<br />
| index.bml.text<br />
| index page of admin pages<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| invitecodes.bml<br />
| ''none''<br />
| view details of invite code (by code or account)<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| logout_user.bml<br />
| ''none''<br />
| log a user out of the site<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| memcache.bml<br />
| ''none''<br />
| view current memcache conditions<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| memcache_view.bml<br />
| ''none''<br />
| view current memcache details<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| mysql_status.bml<br />
| ''none''<br />
| show current MySQL status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-25T14:09:23Z<p>Echan: editted description of lonely .text files</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| takes invite code via URL or prompt, then prompts for account name/email/pw/age<br>account creation flow step 1 of 3<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|-<br />
| register.bml<br />
| register.bml.text<br />
| email validation dialog/success<br />
| E/C<br />
| S<br />
| /<br />
|-<br />
| reject.bml<br />
| reject.bml.text<br />
| reject someone's request to join a community<br />
| C<br />
| S<br />
| /<br />
|-<br />
| robots.txt<br />
| ''none''<br />
| commands to spiders<br />
| E<br />
| S<br />
| /<br />
|-<br />
| shop.bml<br />
| shop.bml.text<br />
| site store main storefront<br />
| E<br />
| S<br />
| /<br />
|- <br />
| stats.bml<br />
| stats.bml.text<br />
| site statistics<br />
| E<br />
| S<br />
| /<br />
|-<br />
| talkmulti.bml<br />
| talkmulti.bml.text<br />
| delete/screen/unscreen multiple comments<br />
| C<br />
| J<br />
| /<br />
|- <br />
| talkpost.bml<br />
| talkpost.bml.text<br />
| post comment dialog and immediate errors<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkpost_do.bml<br />
| talkpost_do.bml.text<br />
| actually post comment or error out<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkread.bml<br />
| talkread.bml.text<br />
| entry comment page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkread_s1short.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | hack to make S1 styles work? should be deleted?<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkscreen.bml<br />
| talkscreen.bml.text<br />
| freeze/unfreeze/screen/unscreen comments<br />
| C<br />
| J<br />
| /<br />
|-<br />
| update.bml<br />
| update.bml.text<br />
| post an entry<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| uploadpic.bml.text<br />
| style="background:#ABCDEF" | ''primary file is gone. all references to this file should be changed, then delete this file''<br />
| <br />
|<br />
| /<br />
|-<br />
| userinfo.bml<br />
| userinfo.bml.text<br />
| profile page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| capedit.bml<br />
| ''none''<br />
| edit user capabilities<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| clusterstatus.bml<br />
| ''none''<br />
| check clusters status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| dupkiller.bml<br />
| ''none''<br />
| delete a user's duplicate entries<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-25T13:57:13Z<p>Echan: editted create.bml</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| takes invite code via URL or prompt, then prompts for account name/email/pw/age<br>account creation flow step 1 of 3<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary files are MIA; these files should be deleted?''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|-<br />
| register.bml<br />
| register.bml.text<br />
| email validation dialog/success<br />
| E/C<br />
| S<br />
| /<br />
|-<br />
| reject.bml<br />
| reject.bml.text<br />
| reject someone's request to join a community<br />
| C<br />
| S<br />
| /<br />
|-<br />
| robots.txt<br />
| ''none''<br />
| commands to spiders<br />
| E<br />
| S<br />
| /<br />
|-<br />
| shop.bml<br />
| shop.bml.text<br />
| site store main storefront<br />
| E<br />
| S<br />
| /<br />
|- <br />
| stats.bml<br />
| stats.bml.text<br />
| site statistics<br />
| E<br />
| S<br />
| /<br />
|-<br />
| talkmulti.bml<br />
| talkmulti.bml.text<br />
| delete/screen/unscreen multiple comments<br />
| C<br />
| J<br />
| /<br />
|- <br />
| talkpost.bml<br />
| talkpost.bml.text<br />
| post comment dialog and immediate errors<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkpost_do.bml<br />
| talkpost_do.bml.text<br />
| actually post comment or error out<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkread.bml<br />
| talkread.bml.text<br />
| entry comment page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkread_s1short.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | hack to make S1 styles work? should be deleted?<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkscreen.bml<br />
| talkscreen.bml.text<br />
| freeze/unfreeze/screen/unscreen comments<br />
| C<br />
| J<br />
| /<br />
|-<br />
| update.bml<br />
| update.bml.text<br />
| post an entry<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| uploadpic.bml.text<br />
| style="background:#ABCDEF" | cruft for deletion?<br />
| <br />
|<br />
| /<br />
|-<br />
| userinfo.bml<br />
| userinfo.bml.text<br />
| profile page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| capedit.bml<br />
| ''none''<br />
| edit user capabilities<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| clusterstatus.bml<br />
| ''none''<br />
| check clusters status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| dupkiller.bml<br />
| ''none''<br />
| delete a user's duplicate entries<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-25T05:52:51Z<p>Echan: added more rows</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary files are MIA; these files should be deleted?''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|-<br />
| register.bml<br />
| register.bml.text<br />
| email validation dialog/success<br />
| E/C<br />
| S<br />
| /<br />
|-<br />
| reject.bml<br />
| reject.bml.text<br />
| reject someone's request to join a community<br />
| C<br />
| S<br />
| /<br />
|-<br />
| robots.txt<br />
| ''none''<br />
| commands to spiders<br />
| E<br />
| S<br />
| /<br />
|-<br />
| shop.bml<br />
| shop.bml.text<br />
| site store main storefront<br />
| E<br />
| S<br />
| /<br />
|- <br />
| stats.bml<br />
| stats.bml.text<br />
| site statistics<br />
| E<br />
| S<br />
| /<br />
|-<br />
| talkmulti.bml<br />
| talkmulti.bml.text<br />
| delete/screen/unscreen multiple comments<br />
| C<br />
| J<br />
| /<br />
|- <br />
| talkpost.bml<br />
| talkpost.bml.text<br />
| post comment dialog and immediate errors<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkpost_do.bml<br />
| talkpost_do.bml.text<br />
| actually post comment or error out<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkread.bml<br />
| talkread.bml.text<br />
| entry comment page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkread_s1short.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | hack to make S1 styles work? should be deleted?<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkscreen.bml<br />
| talkscreen.bml.text<br />
| freeze/unfreeze/screen/unscreen comments<br />
| C<br />
| J<br />
| /<br />
|-<br />
| update.bml<br />
| update.bml.text<br />
| post an entry<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| uploadpic.bml.text<br />
| style="background:#ABCDEF" | cruft for deletion?<br />
| <br />
|<br />
| /<br />
|-<br />
| userinfo.bml<br />
| userinfo.bml.text<br />
| profile page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| capedit.bml<br />
| ''none''<br />
| edit user capabilities<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| clusterstatus.bml<br />
| ''none''<br />
| check clusters status<br />
| E<br />
| S<br />
| /admin/<br />
|-<br />
| dupkiller.bml<br />
| ''none''<br />
| delete a user's duplicate entries<br />
| E<br />
| J<br />
| /admin/<br />
|-<br />
<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-25T05:32:56Z<p>Echan: added more rows</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary files are MIA; these files should be deleted?''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|-<br />
| register.bml<br />
| register.bml.text<br />
| email validation dialog/success<br />
| E/C<br />
| S<br />
| /<br />
|-<br />
| reject.bml<br />
| reject.bml.text<br />
| reject someone's request to join a community<br />
| C<br />
| S<br />
| /<br />
|-<br />
| robots.txt<br />
| ''none''<br />
| commands to spiders<br />
| E<br />
| S<br />
| /<br />
|-<br />
| shop.bml<br />
| shop.bml.text<br />
| site store main storefront<br />
| E<br />
| S<br />
| /<br />
|- <br />
| stats.bml<br />
| stats.bml.text<br />
| site statistics<br />
| E<br />
| S<br />
| /<br />
|-<br />
| talkmulti.bml<br />
| talkmulti.bml.text<br />
| delete/screen/unscreen multiple comments<br />
| C<br />
| J<br />
| /<br />
|- <br />
| talkpost.bml<br />
| talkpost.bml.text<br />
| post comment dialog and immediate errors<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkpost_do.bml<br />
| talkpost_do.bml.text<br />
| actually post comment or error out<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkread.bml<br />
| talkread.bml.text<br />
| entry comment page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkread_s1short.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | hack to make S1 styles work? should be deleted?<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkscreen.bml<br />
| talkscreen.bml.text<br />
| freeze/unfreeze/screen/unscreen comments<br />
| C<br />
| J<br />
| /<br />
|-<br />
| update.bml<br />
| update.bml.text<br />
| post an entry<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| uploadpic.bml.text<br />
| style="background:#ABCDEF" | cruft for deletion?<br />
| <br />
|<br />
| /<br />
|-<br />
| userinfo.bml<br />
| userinfo.bml.text<br />
| profile page<br />
| E<br />
| J<br />
| /<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-25T04:35:22Z<p>Echan: added more rows</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary files are MIA; these files should be deleted?''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|-<br />
| register.bml<br />
| register.bml.text<br />
| email validation dialog/success<br />
| E/C<br />
| S<br />
| /<br />
|-<br />
| reject.bml<br />
| reject.bml.text<br />
| reject someone's request to join a community<br />
| C<br />
| S<br />
| /<br />
|-<br />
| robots.txt<br />
| ''none''<br />
| commands to spiders<br />
| E<br />
| S<br />
| /<br />
|-<br />
| shop.bml<br />
| shop.bml.text<br />
| site store main storefront<br />
| E<br />
| S<br />
| /<br />
|- <br />
| stats.bml<br />
| stats.bml.text<br />
| site statistics<br />
| E<br />
| S<br />
| /<br />
|-<br />
| talkmulti.bml<br />
| talkmulti.bml.text<br />
| delete/screen/unscreen multiple comments<br />
| C<br />
| J<br />
| /<br />
|- <br />
| talkpost.bml<br />
| talkpost.bml.text<br />
| post comment dialog and immediate errors<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkpost_do.bml<br />
| talkpost_do.bml.text<br />
| actually post comment or error out<br />
| C<br />
| J<br />
| /<br />
|-<br />
| talkread.bml<br />
| talkread.bml.text<br />
| entry comment page<br />
| E<br />
| J<br />
| /<br />
|-<br />
| talkread_s1short.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | hack to make S1 styles work? should be deleted?<br />
| C<br />
| J<br />
| /<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-23T13:50:22Z<p>Echan: added a row</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary files are MIA; these files should be deleted?''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|-<br />
| register.bml<br />
| register.bml.text<br />
| email validation dialog/success<br />
| E/C<br />
| S<br />
| /<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-23T12:42:31Z<p>Echan: added more rows</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary files are MIA; these files should be deleted?''<br />
| <br />
| <br />
| /<br />
|-<br />
| moodlist.bml<br />
| moodlist.bml.text<br />
| preview mood themes<br />
| E<br />
| J<br />
| /<br />
|-<br />
| multisearch.bml<br />
| multisearch.bml.text<br />
| style="background:#ABCDEF" | search module in the site scheme header?<br />
| style="background:#ABCDEF" | C?<br />
| S<br />
| /<br />
|-<br />
| nav.bml<br />
| nav.bml.text<br />
| dispay sublevel navigation links<br />
| C<br />
| S<br />
| /<br />
|-<br />
| newuser.bml<br />
| newuser.bml.text<br />
| new account success page<br>account creation flow #last<br />
| C<br />
| S<br />
| /<br />
|-<br />
| photobucket_cb.bml<br />
| ''none''<br />
| Photobucket JWidget Callback page<br />
| C<br />
| S<br />
| /<br />
|-<br />
| post_qotd.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | supposed to redirect to the update page with the most recent QotD filled in; currently redirects to index.bml<br />
| E<br />
| J<br />
| /<br />
|-<br />
| protocol.dat<br />
| ''none''<br />
| style="background:#ABCDEF" | site API documentation?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| pubkey.bml<br />
| pubkey.bml.text<br />
| search/display PGP public keys<br />
| E<br />
| J<br />
| /<br />
|-<br />
| random.bml<br />
| ''none''<br />
| redirects to a random journal<br />
| C<br />
| S<br />
| /<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-23T04:47:47Z<p>Echan: alphabetized list</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
| <br />
|/<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary files are MIA; these files should be deleted?''<br />
| <br />
| <br />
| /<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-23T04:21:41Z<p>Echan: added more rows</p>
<hr />
<div>[[Category:Development]]<br />
<br />
This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| modify.bml.text<br>modify_do.bml.text<br />
| style="background:#ABCDEF" | ''primary files are MIA; these files should be deleted?''<br />
| <br />
| <br />
| /<br />
|-<br />
| lostinfo.bml<br />
| lostinfo.bml.text<br />
| retrieve lost account name/password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| lostinfo_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
| <br />
|/<br />
|-<br />
| logout.bml<br />
| logout.bml.text<br />
| logout dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| login.bml<br />
| login.bml.text<br />
| login dialog<br />
| E<br />
| S<br />
| /<br />
|-<br />
| interests.bml<br />
| interests.bml.text<br />
| interests search/manage<br />
| E<br />
| J<br />
| /<br />
|-<br />
| index.bml<br />
| ''none''<br />
| site homepage<br />
| E<br />
| S<br />
| /<br />
|-<br />
| imgupload.bml<br>imguploadrte.bml<br />
| imgupload.bml.text<br />
| image upload for entry posting<br />
| C<br />
| J<br />
| /<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-21T14:18:47Z<p>Echan: changed editpics to E/C</p>
<hr />
<div>This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E/C<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-21T14:16:15Z<p>Echan: added export, export_do, go</p>
<hr />
<div>This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|-<br />
| export.bml<br />
| export.bml.text<br />
| dialog to export entries & comments<br />
| E<br />
| S<br />
| /<br />
|-<br />
| export_do.bml<br />
| export_do.bml.text<br />
| style="background:#ABCDEF" | does the actual export?<br />
| C<br />
| S<br />
| /<br />
|-<br />
| go.bml<br />
| go.bml.text<br />
| travel between entries (prev/next)<br />
| C<br />
| J<br />
| /<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-21T14:10:38Z<p>Echan: made some things blue</p>
<hr />
<div>This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| style="background:#ABCDEF" | directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| style="background:#ABCDEF" | ''none''<br />
| editjournal_do.bml.text<br />
| style="background:#ABCDEF" | ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/Public-facing_Pages_WorksheetPublic-facing Pages Worksheet2009-04-21T14:09:08Z<p>Echan: Created page with 'This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http:...'</p>
<hr />
<div>This is a worksheet to document various things about Dreamwidth's [http://hg.dwscoalition.org/dw-free/file/tip/htdocs/ public-facing pages]. Eventually, this will lead to [http://bugs.dwscoalition.org/show_bug.cgi?id=112 bug 112] being solved and the site being better organized and easier to use.<br />
<br />
<br />
Table Key:<br />
E - Entry point of a task<br />
C - Continuation of a task; page receives data from elsewhere<br />
<br />
J - Journal content management (tags, comments, entries, userpic display, memories, etc)<br />
S - Site interaction management (settings, management, messages, etc)<br />
<br />
<br />
Fields with questionable or no data are highlighted blue; please remove the blue if you are able to fill in the slot with good info. If you feel something not in blue needs to be changed or corrected, feel free to do that as well!<br />
<br />
{| border="1"<br />
|-<br />
! Primary File<br />
! Associated Helper Files<br />
! width="300" | Description<br />
! EC<br />
! JS<br />
! Directory<br />
|-<br />
| _config.bml<br />
| ''none''<br />
| style="background:#ABCDEF" | setup site scheme?<br />
| style="background:#ABCDEF" | ?<br />
| S<br />
| / <br />
|-<br />
| accountstatus.bml<br />
| accountstatus.bml.text<br />
| delete / undelete journal<br />
| E<br />
| S<br />
| / <br />
|-<br />
| allpics.bml<br />
| allpics.bml.text<br />
| show all userpics of a journal or community<br />
| E<br />
| J<br />
| /<br />
|-<br />
| approve.bml<br />
| approve.bml.text<br />
| approve/accept community membership<br />
| C<br />
| J<br />
| /<br />
|-<br />
| betafeatures.bml<br />
| betafeatures.bml.text<br />
| turns on/off features in beta<br />
| E<br />
| S<br />
| /<br />
|-<br />
| birthdays.bml<br />
| birthdays.bml.text<br />
| display a circle's birthdays<br />
| E<br />
| J<br />
| /<br />
|- <br />
| changemail.bml<br />
| changemail.bml.text<br />
| set/change email address<br />
| E<br />
| S<br />
| /<br />
|-<br />
| changepassword.bml<br />
| changepassword.bml.text<br />
| change password<br />
| E<br />
| S<br />
| /<br />
|-<br />
| create.bml<br />
| create.bml.text<br />
| dialog to enter invite code<br>account creation flow #1<br />
| E<br />
| S<br />
| /<br />
|-<br />
| delcomment.bml<br />
| delcomment.bml.text<br />
| delete comment confirmation<br />
| C<br />
| J<br />
| /<br />
|-<br />
| directory.bml<br />
| directory.bml.text<br />
| directory search and view results by geography<br>''needs rename to directoryGeography ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| directorysearch.bml<br />
| directorysearch.bml.text<br />
| directory search and view results by demographics<br>''needs rename to directoryDemographics ?''<br />
| E<br />
| S<br />
| /<br />
|-<br />
| editpics.bml<br />
| editpics.bml.text<br />
| manage userpics<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editprivacy.bml<br />
| editprivacy.bml.text<br />
| bulk edit entries' privacy settings<br />
| E<br />
| J<br />
| /<br />
|-<br />
| editjournal.bml<br />
| editjournal.bml.text<br />
| find & edit entries<br />
| E<br />
| J<br />
| /<br />
|-<br />
| ''none''<br />
| editjournal_do.bml.text<br />
| ''primary file is MIA; this file should be deleted?''<br />
| <br />
|<br />
| /<br />
|-<br />
| edittags.bml<br />
| edittags.bml.text<br />
| edit tags on an entry<br />
| C<br />
| J<br />
| /<br />
|}</div>Echan//wiki.dreamwidth.net/wiki/index.php/User_talk:AzurelunaticUser talk:Azurelunatic2009-04-17T16:14:17Z<p>Echan: Created page with 'I wanted to thank you for all the work you did on the Jargon page. You really did an amazing job! --~~~~'</p>
<hr />
<div>I wanted to thank you for all the work you did on the [[Common Jargon|Jargon page]]. You really did an amazing job! --[[User:Echan|Echan]] 16:14, 17 April 2009 (UTC)</div>Echan//wiki.dreamwidth.net/wiki/index.php/Common_JargonCommon Jargon2009-04-15T06:30:39Z<p>Echan: /* Words */ added link for spoons post</p>
<hr />
<div>The Dreamwidth project has some jargon in common use that may not be familiar to the general public. While these are not official terms that you should know, definitions may be helpful. <br />
<br />
=Words= <br />
*spoons: [http://echan.dreamwidth.org/1086.html WTF Spoons]<br />
<br />
=People= <br />
<br />
*Brad<br />
[http://en.wikipedia.org/wiki/Brad_Fitzpatrick Brad Fitzpatrick] is the original creator of LiveJournal.</div>Echan//wiki.dreamwidth.net/wiki/index.php/Bug_Report_Workflow_(Support)Bug Report Workflow (Support)2009-04-15T05:34:29Z<p>Echan: added categories</p>
<hr />
<div>{{Note|text=This is currently a proposed policy that is open to comment.}}<br />
<br />
Currently a significant number of support requests are related to site functionality, many of which may be actual bugs. Most bugs are known, but since this is such a common source of inquiries we need to be able to handle them quickly to keep our stress levels down and our users happy! With this in mind, follow these steps to ensure a consistent, timely approach.<br />
<br />
If you have ideas for improving this policy, add them to the Discussion Page or contact <dwuser>invisionary</dwuser> directly. (skrshawk on IRC)<br />
<br />
= Bug Workflow =<br />
<br />
1. When a bug report comes in check to see if it's known already. The best way to do this is to search Bugzilla. Put important words into the search. Also ask around IRC - people can often point to common bugs off the top of their heads.<br />
<br />
If the bug is a known issue, reply to the user letting them know. Use appropriate soft skills, especially if the issue has resulted in frustration or data loss. Per Mark, don't give links to the Bugzilla entry. A good description of what we have on file will suffice.<br />
<br />
2. If the issue is not an obvious bug get confirmation of the steps that the user is taking to get the problem. It's possible that the issue is user error, but that doesn't mean there's no bug! You may find that a user has inadvertently stumbled on a way to make the service better, in which case you will want to file a bug to log the enhancement request. Great ideas come from everyday users.<br />
<br />
Make sure you understand what the user is trying to do - don't be afraid to ask questions! Emphasize that you are trying to get a clear understanding, while doing your best to not talk down to the user. It takes baby steps sometimes to get to the root of a problem; don't be afraid to share that with someone! Important information to get:<br />
<br />
* Operating System and Browser, versions if possible<br />
* Exactly what the user is doing, step by step.<br />
* What the user expects to happen as a result of their steps and what actually happened<br />
* Any error messages, copy/pasted<br />
<br />
If you've found the problem was based on what the user was doing give them steps to correct it - nicely, of course. If through their work you've discovered a way to improve the service, continue with the bug report process!<br />
<br />
3. If you need to file a bug, you can follow the instructions for bug reporting (anyone is welcome to file a bug!), or you can hand this off to a senior support person if you'd prefer. Do as much of the process as you're comfortable with and ask questions along the way. Try to get someone else to verify the bug and the steps to reproduce it if possible. If you can't reproduce it (or you can but someone else can't) make a note of this in your report.<br />
<br />
<b>IMPORTANT:</b> If the user is reporting a security related bug in the main support queue, don't touch it. Alert a senior support person, who will transfer the request to an appropriate private queue. We need to keep these things out of the public eye, so if you spot a miscategorized report tell us immediately! This also applies to Abuse/ToS related support requests.<br />
<br />
= Bugzilla Reporting Workflow =<br />
<br />
The entire Bugzilla workflow (which goes from bug reporting to committed patch) can be found here: http://wiki.dwscoalition.org/notes/Bugzilla_workflow . The full article is good reading so you have an understanding of the entire development process. Here is a simplified version focusing on bug reporting. If you'd rather follow the primary document, the first three steps are what you need to know. Otherwise, read on.<br />
<br />
1. To log a bug you will need a Bugzilla account. Anyone can make one, so follow the simple process. You don't need an account to search and view bugs, however. Go here to create your account: http://bugs.dwscoalition.org/createaccount.cgi<br />
<br />
2. Create the bug here: http://bugs.dwscoalition.org/enter_bug.cgi.<br />
<br />
Select a queue for your bug. Generally you're going to want the Dreamwidth Development queue. If the bug is related to something that needs to be better clarified in the FAQs or elsewhere in the site copy, use the Project Documentation queue. The next screen is the main bug entry page. Fill in the following fields:<br />
<br />
<b>Component:</b> Most of the time UI/Frontend is the nature of the bug, but use other options as appropriate.<br><b>CC:</b> Add your email here if you want to track progress of the bug.<br><b>URL:</b> The page (if appropriate) where the bug is happening.<br><b>Summary/Description:</b> Fill these in with as many details as you can - you should have plenty from your interaction with the user and other support people.<br><b>Severity:</b> Most likely the highest severity you'll need to use is minor, which is what you want if you suspect a bug affect a significant number of users. Any higher than that should be significantly affecting site usability - if so, talk to a senior about it (or check with IRC).<br><b>Priority:</b> You'll want to stick with P4 or P5. If you suspect a bug warrants a higher priority, again, talk to a senior (or mention it in IRC).<br><b>Tags:</b> Stick to the existing tag list. The tags are intuitive; use what's most appropriate.<br />
<br />
<b>Flags:</b> You may wish to use need-spec or needs-design for enhancements that aren't fully fleshed out. Spec is for enhancements that need thought as to just what should be done; Design is for enhancements that might need thought put into the visual/frontend elements. Set either to ? as appropriate.<br />
<br />
3. Hit the commit button and watch it go into the queue (and Bugsy report it in #dw!). Be prepared to field further questions from the devs if needed - don't worry, we don't bite unless asked nicely!<br />
<br />
[[Category:Support]]<br />
[[Category:Brainstorming]]<br />
[[Category:Development]]</div>Echan//wiki.dreamwidth.net/wiki/index.php/Dreamwidth.org:_FAQDreamwidth.org: FAQ2009-04-14T06:00:04Z<p>Echan: /* Will it be easy to clearly identify the difference between staff posts and personal posts? */</p>
<hr />
<div>See also: [[Dreamwidth.org: Business FAQs]]<br />
<br />
= Who is running Dreamwidth? =<br />
<br />
You can see who is behind Dreamwidth on the [http://www.dreamwidth.org/site/staff.bml staff] page.<br />
<br />
= Initial Stages of Dreamwidth =<br />
<br />
== What must be finished prior to closed beta launch? ==<br />
<br />
Tasks that must be finished prior to closed beta launch can be viewed [http://wiki.dwscoalition.org/notes/Dreamwidth.org:_Pre-Launch here], as well as their status. A list of tasks that must be completed before the move from open beta to the full site launch can be seen [http://tinyurl.com/cp4qwl here]. A detailed explanation of how the site will be hosted throughout the stages can be found [http://lists.dwscoalition.org/pipermail/dw-discuss/2008-June/000025.html here].<br />
<br />
== How will beta stages work? ==<br />
<br />
Closed beta is open! Every day more an more people are invited to join closed beta.<br />
<br />
On April 30, open beta will begin. To create an account in open beta, you can either buy a [http://wiki.dwscoalition.org/notes/Dreamwidth.org:_Business_FAQs#Why_are_accounts_going_to_cost_what_they_cost.3F paid account] or obtain an invite code. Invite codes will originally be given to those who took part in closed beta, as well as those who were active in development and discussion in pre-launch stage. Open beta will also correspond with the one-time sale of 400 seed accounts. More information about the beta process and the expected timeline can be found [http://wiki.dwscoalition.org/notes/Dreamwidth.org:_Launch_timeline here].<br />
<br />
= Importing Other Journals =<br />
<br />
== What will be imported? ==<br />
<br />
Everything that possibly can be. Friends, userpics, userpic keywords, tags, friendsgroups, bio, entries, security levels, and comments. More discussion on how the importing process will work can be found [http://lists.dwscoalition.org/pipermail/dw-discuss/2008-June/000209.html here]. The copyright issues of comments and how we will be honoring the fact that whoever commented owns their comment are addressed [http://lists.dwscoalition.org/pipermail/dw-discuss/2009-January/000658.html here].<br />
<br />
== Will security levels change on entries I import? ==<br />
<br />
No. Your private or friends-only posts will not become viewable to everyone when they’re imported from another site. We will not remove security settings that you have become used to on other sites. It is important to us that you can control who views your material and we have no intention of weakening the sense of safety you have in any way.<br />
<br />
== What if I have more icons on my LiveJournal/other account than I have available slots on my Dreamwidth account? ==<br />
<br />
If you import your journal from another site and have more icons than available slots then when the import is complete, the “hi, we’re done” email will include a link to a page where you can choose which icons you want to keep.<br />
<br />
= Invite Codes =<br />
<br />
== How will invite codes work and how will they be distributed? ==<br />
<br />
Invite codes will always be in place at Dreamwidth. They are a way to control growth of free accounts in the early days and a way to foster community as time goes on. Paid accounts will always be available if you want to avoid the hassle of finding an invite code. Price points and account levels can be found [http://wiki.dwscoalition.org/notes/Dreamwidth.org:_Business_FAQs#Why_are_accounts_going_to_cost_what_they_cost.3F here].<br />
<br />
Invite codes will be distributed throughout the community on a monthly basis, based on what the site can support. Further discussion of how invite codes will be distributed can be found [http://lists.dwscoalition.org/pipermail/dw-discuss/2009-January/000947.html here] and [http://lists.dwscoalition.org/pipermail/dw-discuss/2009-January/000962.html here]. If you want to know more about Dreamwidth before purchasing a paid account, a site tour will be available, as will as guides on how to use Dreamwidth and how to switch from LiveJournal or another LiveJournal-based site.<br />
<br />
== Will I need an invite code to create a community? ==<br />
<br />
No. We believe in encouraging community and things that allow people to interact. Any Dreamwidth user will be able to create a community.<br />
<br />
= Watch/Trust =<br />
<br />
== How will Watch/Trust work? ==<br />
<br />
The idea of a friends list from LiveJournal will be broken into 2 groups, Watch and Trust. Your watch list consists of people whose content you wish to view on your aggregation/friends page. Your trust list is people who you trust to view your protected content. <br />
<br />
You can trust someone but not watch them, watch them but not trust them, or watch and trust them. Who shows up on your aggregation/friends page will be based solely on your watch list, while the users who can see your protected entries will be based solely on your trust list. A more detailed explanation with examples can be seen [http://lists.dwscoalition.org/pipermail/dw-discuss/2009-January/000838.html here].<br />
<br />
== Will my trust list be visible to everyone? ==<br />
Yes. It will be visible so anyone commenting on an entry knows who is possibly listening. Trust filters are not made public, so anyone reading the entry will not know exactly who is listening, but they will know who might be. More discussion can be found [http://lists.dwscoalition.org/pipermail/dw-discuss/2009-January/000809.html here] and [http://lists.dwscoalition.org/pipermail/dw-discuss/2009-January/000812.html here].<br />
<br />
= Things That Will Be Added After Launch =<br />
<br />
We will continue to add features to Dreamwidth on a continuous basis. Discussion on how priority is given to additions can be found [http://lists.dwscoalition.org/pipermail/dw-discuss/2009-January/000801.html here]. <br />
<br />
We hope to add “expand threaded comments” and “expand all comments on page” as an option for paid users relatively soon after launch.<br />
<br />
We are likely to add a points system that will make it easier to make small purchases, such as v-gifts. The points would be only be redeemable for services, not cash. More discussion on this can be found [http://lists.dwscoalition.org/pipermail/dw-discuss/2009-January/000707.html here].<br />
<br />
= Things to Keep the Site Running =<br />
<br />
== Will there be advertisements or sponsored pages on Dreamwidth? ==<br />
<br />
There will never be any corporate advertising on Dreamwidth.<br />
<br />
== Will inactive accounts be deleted after a certain amount of time to free up the usernames? ==<br />
<br />
No. If you trust us to host your information, it will not be deleted, even if you are away from Dreamwidth for a year or more. However, we understand the problem of an ever-increasingly claimed namespace, so to balance that we will make sure the journals that are marked as deleted by the user actually get deleted. As well, the invite codes will help to prevent people from creating hundreds of accounts without intending to use any of them. This topic is something that we will monitor and revisit after 18-24 months to see if any changes are necessary.<br />
<br />
== Why can’t I host my icons offsite? ==<br />
<br />
Icons are hosted onsite to help control trolling. If they could be hosted offsite it would be easy to upload a 100x100px userpic and then change it to a 2000x2000px to break the display of any page that called for it. Also, although icons can only be 40kb, they're called often enough that it would burn through the amount of monthly transfer that most hosts offer pretty quickly. If the monthly transfer is exceeded or the external site goes down it would lead to broken image links, which look unprofessional and would be directly associated with Dreamwidth.<br />
<br />
== Can I view more than 1000 entries/more than 14 days on my watch page? ==<br />
<br />
No. Viewing the watch page is the [http://lists.dwscoalition.org/pipermail/dw-discuss/2009-January/000905.html single hardest thing] the servers will do. Increasing this limit would result in a huge server drain, which could cause the site to collapse.<br />
<br />
= Other Questions =<br />
<br />
== Will all styles available on LiveJournal be available on Dreamwidth? ==<br />
<br />
No. Some of the styles on LiveJournal are not available under GPL and cannot be used by other sites. However, we are creating new styles that will hopefully be more customizable and user-friendly. More detail on this can be found at the [[Styles FAQ]].<br />
<br />
== Will the profile page and settings page be fundamentally different from the current LiveJournal pages? ==<br />
<br />
Initially, no. There will be a few tweaks, but they will be recognizable as the ones used on LiveJournal. Over time they will change based on user feedback.<br />
<br />
== What browsers will Dreamwidth operate on? ==<br />
<br />
Dreamwidth will fully support Firefox 3+, Internet Explorer 7+, and the latest version of Safari. While we will make efforts to ensure backwards compatibility, we can’t guarantee that the default site will be usable in older browsers. One of our goals is to have a “Dreamwidth-light” that can be hosted on computers that are too old to use modern browsers and on mobile devices.<br />
<br />
== Can I change the colors of Dreamwidth to something I like more? ==<br />
<br />
Yes. Multiple color schemes will be available by open beta and you can choose one that you like.<br />
<br />
== Will the post limit and comment limit be increased? ==<br />
<br />
Yes.<br />
<br />
== Will the maximum length of usernames be increased? ==<br />
<br />
Yes. Usernames will have a maximum length of 25 characters.<br />
<br />
== Will there be a watchwatch page (equivalent to LiveJournal’s friendsfriends page)? ==<br />
<br />
Yes.<br />
<br />
== Is it easy to clearly identify the difference between staff posts and personal posts? ==<br />
<br />
Yes. A separate account type has been created for staff, with a separate userinfo icon, to make it clear when someone who works at Dreamwidth is speaking in an official capacity.<br />
<br />
[[Category: Dreamwidth.org]]<br />
[[Category: FAQs]]</div>Echan