I haven’t been able to find more information on Pages other than “Add more information – Pages make it easy to brainstorm new ideas or add new content” on the tour page. I can’t for the life of me figure out why these would be useful, but I feel like I’m totally missing the boat on this. I believe there must be a great use for this feature, and I would love for others to let me know how they find them useful. Thanks for your insight!

Jason, that’s actually a rather interesting question. I’ve seen people use pages for different functions. Quite often as a style guide or instruction place for how things work in their ticket system or use. I’ve seen lots of guideline information or outlines of the quoted projects in project pages, or changelog copies and stuff.

I personally haven’t ever used the pages option in Lighthouse, but have seen them on many projects.

We are using pages for general stuff, like styleguides and information about servers.

To tell you the truth the pages functionality is a bit lacking right now. In my opinion it would work much better if some of the following functionality would be added:

• Versioning
• Comments
• watchlist
• Updates on the dashboard
• Better textile support

Now I’m thinking about it, there’s a lot of overlap between messages and pages. If you make it possible to add links to messages in the sidebar (like the links to the pages) you could probably get rid of pages altogether. I think most of the stuff I mentioned would make sense for messages and they already have comments.

In reply to “better textile support” Lighthouse doesn’t actually use textile, it’s a cut down custom setup which doesn’t offer as much. We’re actually adding in markdown in the future, and keeping the current textile system to accompany it.

Can you add support for both full-textile and markdown? Textile is a lot easier to use, IMO