php avatar php committed c4fd656

Restructure

Comments (0)

Files changed (6)

Main.txt

-Main page
-=========
-
-Mercurial is... 
----------------
-
-Mercurial is a free, distributed source control management tool. It offers you the power to efficiently handle projects of any size yet provides an easy, intuitive interface. 
-
-Every Mercurial clone is a full-fledged repository with complete history and revision tracking capabilities. It is independent of network access or a central server. Committing, branching and merging are fast and cheap. 
-
-Mercurial is used for version control of files, much like tools such as [Git](http://git-scm.org), [Bazaar](http://bazaar-vcs.org), [Subversion](http://subversion.tigris.org/) and [CVS](http://www.nongnu.org/cvs/). It is written in Python and available on many different platforms, including Microsoft Windows, Mac OS X, Linux, FreeBSD and OpenSolaris. 
-
-
-Projects using Mercurial
-------------------------
-
-* [Mercurial](http://selenic.com/repo/hg)
-* [Mozilla](http://hg.mozilla.org/)
-* [Cython](http://hg.cython.org/)
-* [MoinMoin](http://hg.moinmo.in/)
-* [OpenJDK](http://hg.openjdk.java.net/)
-* [NetBeans](http://hg.netbeans.org/)
-* [OpenSolaris](http://hg.genunix.org/)
-
-[and many more](http://www.selenic.com/mercurial/wiki/index.cgi/ProjectsUsingMercurial)
-
-
-How you can benefit from using Mercurial
-----------------------------------------
-
-### Power and speed
-Mercurial offers you the power and speed to efficiently handle projects of any size and kind. You can use a multitude of [workflows]() and enhance its functionality with [extensions](). 
-
-### Ease of use
-Mercurials consistent and intuitive interface makes it easy to learn and understand. You can simply start with the [bare basics]() and learn incrementally or print a copy of the [hgbook]() to understand the big picture in one go. 
-
-### Just works
-Mercurial strives to deliver on each of its promises. If it looks like you could use it for a specific task, chances are that it will just work on the first try. (if it doesn't, that's most likely no feature but a [bug](http://selenic.com/mercurial/bugs/))
-
-[bare basics]: Quick_Start - Learn to use Mercurial in 30 seconds (or similar). 
-
-(just works instead of webserver: webserver can far more easily be delivered by other projects, too. Just works better fits the "hg is powerful yet easy" theme -> Integrated webserver into quick start?)
-
-
-Get Mercurial
--------------
-
-If you're using Windows, download TortoiseHG for full Explorer integration. ![TortoiseHG Logo]()
-
-GNU/Linux: Just [get it from your package manager](link to a simple guide for the different distros). 
-
-MacOSX: Download (app). 
-
--> A "news" link should be alongside the version. This makes the site itneresting to returning visitors.
-
-
-Mercurial Quick Start
----------------------
-
-Clone a project and create a patch
-
-$ hg clone http://bitbucket.org/ArneBab/hello_world
-$ cd hello_world
-$ (edit files)
-$ hg add (new files)
-$ hg commit -m 'My changes'
-$ hg export > patch.diff
-
-Create a project and commit
-
-$ hg init (project-directory)
-$ (add some files)
-$ hg add
-$ hg commit -m 'Initial commit'
-
--> [Workflows]()
-
-(maybe instead of "Take a look"; it would be great to be able to detect the OS of the visitor and show Windows users TortoiseHG while showing MacOSX and GNU/Linux users the Quick Start)
-
-(### Integrated webserver
-With the "serve" command, Mercurial offers you an integrated webserver as the fastest way to show and share your work.)
-
-Footer
-------
-

about.txt

-Mercurial Distributed SCM
-
-Mercurial is a free, distributed source control management tool. It offers you the power to efficiently handle projects of any size while using an easy, intuitive interface. It is easy to use and hard to break, making it ideal for anyone working with versioned files. 
-
-Distributed architecture
-Traditional version control systems such as SVN are typical client-server architectures with a central point to store the revisions of a project. In contrast, Mercurial is truly distributed, giving each developer a local copy of the entire development history. This way it works independent of network access or a central server. Committing, branching and merging are fast and cheap. 
-
-Fast
-Mercurials implementation and data structures are designed to be fast. You can generate diffs between revisions, or jump back in time within seconds. Therefore Mercurial is perfectly suiteable for large projects such as OpenJDK or NetBeans.
-
-Platform independent
-Mercurial was written with platform independence in mind. Therefore most of Mercurial is written in Python, with a small part written in C for performance reasons. As a result, binary releases are available on all major platforms.
-
-Extensible
-The functionality of Mercurial can be increased with extensions, either by activating the official ones which are shipped with Mercurial or downloading some [from the wiki](http://www.selenic.com/mercurial/wiki/index.cgi/UsingExtensions) or by [writing your own](http://www.selenic.com/mercurial/wiki/index.cgi/WritingExtensions). Extensions are written in Python and can change the workings of the basic commands, add new commands and access all the core functions of Mercurial. 
-
-Open Source
-Mercurial is free software licensed under the terms of the GNU General Public License Version 2.
-
-Similar projects
-Mercurial is used for version control of files. Similar projects include [Git](http://git-scm.org), [Bazaar](http://bazaar-vcs.org), [Subversion](http://subversion.tigris.org/) and [CVS](http://www.nongnu.org/cvs/). 

structure.txt

-= Structure =
-
-Discussion about a structure for the Mercurial Website. 
-
-
-== First site ==
-
-Theme: Just works. 
-
-
-== First step: The needs of visitors ==
-
-=== First time visitors ===
-
-''Imagine I'm a first time visitor of the website. How did I hear of Mercurial?''
-
- * ''"I read an article or a blog post about it"'' 
- * ''"I read a 'which VCS' discussion"'' 
- * ''"I just read the word in a chat"'' 
- * ''"A friend told me about Mercurial"'' 
-
-The last two users will want a basic overview 'what Mercurial is', before they 
-download. All will want a basic description how to use Mercurial - maybe after they 
-downloaded it. 
-
-Windows and MacOSX Users will want a Download-Link, as well as GNU/Linux users whose 
-distribution doesn't offer the most recent Mercurial version. 
-
-Windows Users should directly see a link to TortoiseHG. 
-
-<ArneBab> I just had a look on the git-scm.com site
-
-<ArneBab> They seem to get that quite well, but they miss information for extending 
-git (maybe they don't want it). 
-
-Their idea of having a guide for designers and one for coders is great! (two target 
-groups with entirely different needs). 
-
-Also the question ''What can I gain by using Mercurial?'' needs to be answered 
-somehwere. 
-
-
-=== People who want to learn more about Mercurial ===
-
- 1. Returning visitors. ''"What changed since my last visit?"'' 
- 2. Developers who want to try out workflows. ''"What else can I do with it?"''
- 3. People who want to understand Mercurial. ''"How does it work internally?"''
- 4. People who want to adapt Mercurial to their workflow. ''"How can I make Mercurial 
-work for me?"''
- 5. People who want to contribute. ''"How can I help improve Mercurial with the 
-skills I have?"'' or ''"How can I help Mercurial most efficiently - what should I go 
-for?"''
- 6. People who have a specific need. ''"How can I find exactly this?"''
-
-Group 5 needs a quick link to the most relevant extensions. 
-
-A specific need of group 6 could be ''"I heard about extension XY, where is it?"'' A 
-FAQ should be a good starting point, as well as the search function and maybe a short 
-list of very frequently asked questions. 
-
-
-=== People who are currently coding on Mercurial ===
-
-''They give additional momentum for the actual development''
-
- * ''"How to do X?"''
- * ''"Where and how can I tell others of my changes?"''
- * ''"How can I send patches - how should I do them and how are their chances for 
-being accepted?"''
-
-
-
-== Some more ideas ==
-
-''You always need a section like this :) ''
-
- * dsop: It's probably out of scope for this discussion, but I keep thinking it'd be 
-nice if there was some sort of "I'm using this" voting for extensions.
-
- * ArneBab: Another point for the Website: "Testimonials" (what people like about 
-Mercurial). It would be great to find the reasons why the different projects chose 
-Mercurial, and get them on the site. 
-
- * Which target group consists of multiplicators who will pass Mercurial along? - 
-that's something Git got somehow right: Integrators switch, then they push their devs 
-to switch and those push users to switch. Which chain can Mercurial use? 
-
-
+Main page
+=========
+
+Mercurial is... 
+---------------
+
+Mercurial is a free, distributed source control management tool. It offers you the power to efficiently handle projects of any size yet provides an easy, intuitive interface. 
+
+Every Mercurial clone is a full-fledged repository with complete history and revision tracking capabilities. It is independent of network access or a central server. Committing, branching and merging are fast and cheap. 
+
+Mercurial is used for version control of files, much like tools such as [Git](http://git-scm.org), [Bazaar](http://bazaar-vcs.org), [Subversion](http://subversion.tigris.org/) and [CVS](http://www.nongnu.org/cvs/). It is written in Python and available on many different platforms, including Microsoft Windows, Mac OS X, Linux, FreeBSD and OpenSolaris. 
+
+
+Projects using Mercurial
+------------------------
+
+* [Mercurial](http://selenic.com/repo/hg)
+* [Mozilla](http://hg.mozilla.org/)
+* [Cython](http://hg.cython.org/)
+* [MoinMoin](http://hg.moinmo.in/)
+* [OpenJDK](http://hg.openjdk.java.net/)
+* [NetBeans](http://hg.netbeans.org/)
+* [OpenSolaris](http://hg.genunix.org/)
+
+[and many more](http://www.selenic.com/mercurial/wiki/index.cgi/ProjectsUsingMercurial)
+
+
+How you can benefit from using Mercurial
+----------------------------------------
+
+### Power and speed
+Mercurial offers you the power and speed to efficiently handle projects of any size and kind. You can use a multitude of [workflows]() and enhance its functionality with [extensions](). 
+
+### Ease of use
+Mercurials consistent and intuitive interface makes it easy to learn and understand. You can simply start with the [bare basics]() and learn incrementally or print a copy of the [hgbook]() to understand the big picture in one go. 
+
+### Just works
+Mercurial strives to deliver on each of its promises. If it looks like you could use it for a specific task, chances are that it will just work on the first try. (if it doesn't, that's most likely no feature but a [bug](http://selenic.com/mercurial/bugs/))
+
+[bare basics]: Quick_Start - Learn to use Mercurial in 30 seconds (or similar). 
+
+(just works instead of webserver: webserver can far more easily be delivered by other projects, too. Just works better fits the "hg is powerful yet easy" theme -> Integrated webserver into quick start?)
+
+
+Get Mercurial
+-------------
+
+If you're using Windows, download TortoiseHG for full Explorer integration. ![TortoiseHG Logo]()
+
+GNU/Linux: Just [get it from your package manager](link to a simple guide for the different distros). 
+
+MacOSX: Download (app). 
+
+-> A "news" link should be alongside the version. This makes the site itneresting to returning visitors.
+
+
+Mercurial Quick Start
+---------------------
+
+Clone a project and create a patch
+
+$ hg clone http://bitbucket.org/ArneBab/hello_world
+$ cd hello_world
+$ (edit files)
+$ hg add (new files)
+$ hg commit -m 'My changes'
+$ hg export > patch.diff
+
+Create a project and commit
+
+$ hg init (project-directory)
+$ (add some files)
+$ hg add
+$ hg commit -m 'Initial commit'
+
+-> [Workflows]()
+
+(maybe instead of "Take a look"; it would be great to be able to detect the OS of the visitor and show Windows users TortoiseHG while showing MacOSX and GNU/Linux users the Quick Start)
+
+(### Integrated webserver
+With the "serve" command, Mercurial offers you an integrated webserver as the fastest way to show and share your work.)
+
+Footer
+------
+
+Mercurial Distributed SCM
+
+Mercurial is a free, distributed source control management tool. It offers you the power to efficiently handle projects of any size while using an easy, intuitive interface. It is easy to use and hard to break, making it ideal for anyone working with versioned files. 
+
+Distributed architecture
+Traditional version control systems such as SVN are typical client-server architectures with a central point to store the revisions of a project. In contrast, Mercurial is truly distributed, giving each developer a local copy of the entire development history. This way it works independent of network access or a central server. Committing, branching and merging are fast and cheap. 
+
+Fast
+Mercurials implementation and data structures are designed to be fast. You can generate diffs between revisions, or jump back in time within seconds. Therefore Mercurial is perfectly suiteable for large projects such as OpenJDK or NetBeans.
+
+Platform independent
+Mercurial was written with platform independence in mind. Therefore most of Mercurial is written in Python, with a small part written in C for performance reasons. As a result, binary releases are available on all major platforms.
+
+Extensible
+The functionality of Mercurial can be increased with extensions, either by activating the official ones which are shipped with Mercurial or downloading some [from the wiki](http://www.selenic.com/mercurial/wiki/index.cgi/UsingExtensions) or by [writing your own](http://www.selenic.com/mercurial/wiki/index.cgi/WritingExtensions). Extensions are written in Python and can change the workings of the basic commands, add new commands and access all the core functions of Mercurial. 
+
+Open Source
+Mercurial is free software licensed under the terms of the GNU General Public License Version 2.
+
+Similar projects
+Mercurial is used for version control of files. Similar projects include [Git](http://git-scm.org), [Bazaar](http://bazaar-vcs.org), [Subversion](http://subversion.tigris.org/) and [CVS](http://www.nongnu.org/cvs/). 

text/structure.txt

+= Structure =
+
+Discussion about a structure for the Mercurial Website. 
+
+
+== First site ==
+
+Theme: Just works. 
+
+
+== First step: The needs of visitors ==
+
+=== First time visitors ===
+
+''Imagine I'm a first time visitor of the website. How did I hear of Mercurial?''
+
+ * ''"I read an article or a blog post about it"'' 
+ * ''"I read a 'which VCS' discussion"'' 
+ * ''"I just read the word in a chat"'' 
+ * ''"A friend told me about Mercurial"'' 
+
+The last two users will want a basic overview 'what Mercurial is', before they 
+download. All will want a basic description how to use Mercurial - maybe after they 
+downloaded it. 
+
+Windows and MacOSX Users will want a Download-Link, as well as GNU/Linux users whose 
+distribution doesn't offer the most recent Mercurial version. 
+
+Windows Users should directly see a link to TortoiseHG. 
+
+<ArneBab> I just had a look on the git-scm.com site
+
+<ArneBab> They seem to get that quite well, but they miss information for extending 
+git (maybe they don't want it). 
+
+Their idea of having a guide for designers and one for coders is great! (two target 
+groups with entirely different needs). 
+
+Also the question ''What can I gain by using Mercurial?'' needs to be answered 
+somehwere. 
+
+
+=== People who want to learn more about Mercurial ===
+
+ 1. Returning visitors. ''"What changed since my last visit?"'' 
+ 2. Developers who want to try out workflows. ''"What else can I do with it?"''
+ 3. People who want to understand Mercurial. ''"How does it work internally?"''
+ 4. People who want to adapt Mercurial to their workflow. ''"How can I make Mercurial 
+work for me?"''
+ 5. People who want to contribute. ''"How can I help improve Mercurial with the 
+skills I have?"'' or ''"How can I help Mercurial most efficiently - what should I go 
+for?"''
+ 6. People who have a specific need. ''"How can I find exactly this?"''
+
+Group 5 needs a quick link to the most relevant extensions. 
+
+A specific need of group 6 could be ''"I heard about extension XY, where is it?"'' A 
+FAQ should be a good starting point, as well as the search function and maybe a short 
+list of very frequently asked questions. 
+
+
+=== People who are currently coding on Mercurial ===
+
+''They give additional momentum for the actual development''
+
+ * ''"How to do X?"''
+ * ''"Where and how can I tell others of my changes?"''
+ * ''"How can I send patches - how should I do them and how are their chances for 
+being accepted?"''
+
+
+
+== Some more ideas ==
+
+''You always need a section like this :) ''
+
+ * dsop: It's probably out of scope for this discussion, but I keep thinking it'd be 
+nice if there was some sort of "I'm using this" voting for extensions.
+
+ * ArneBab: Another point for the Website: "Testimonials" (what people like about 
+Mercurial). It would be great to find the reasons why the different projects chose 
+Mercurial, and get them on the site. 
+
+ * Which target group consists of multiplicators who will pass Mercurial along? - 
+that's something Git got somehow right: Integrators switch, then they push their devs 
+to switch and those push users to switch. Which chain can Mercurial use? 
+
+
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.