If I was a little more cynical ( :D ) I'd say this is a parody site of "POW" front end with lots of empty words and weird diagonal banners trying to sell you some kind of woo
Seems like it's some kind of communication tool for teams? I dunno, kind of ironic if it is a communication tool that it's really not clear what IT is.
Manuscript - Project Management for Software Teams</title>
Go beyond done
Craft great software.
Learn how Manuscript works.
The first 14 days are on us. No credit card required.
Building software<br />
is more than a race to close issues. We know every team can craft great software, you just need the <strong>best tools</strong> and the <strong>right information</strong>.
Manuscript provides all you need to make great software, including <strong>project management</strong>, <strong>issue tracking</strong>, and <strong>support</strong>, fused with just enough process to help you deliver.
Plus, there's robust integration with other best of breed tools like Slack, GitHub and Google Docs that's free and fully customizable, using the power of
Glitch — our friendly collaborative coding community.
Manuscript shows you the issue and project info you need, alongside updates from your integrated tools.
<p>As well as providing expert advice and insights from two decades of studying how great software really gets built.
Clear, upfront pricing.<br />
We don’t nickel and dime.
$10 per user, per month
It starts with software that ships on a predictable schedule, but goes far beyond that, with software that’s trusted by your community, thoughtful about user experience, and responsible in the ways it treats people and data.
<strong>…is crafted by teams</strong> because no-one works alone, and we only get better when we learn from each other.
Why Choose Manuscript?
Based on the engine of FogBugz, the platform that pioneered bug tracking, Manuscript is a purpose built project management tool for software teams.
Crafted by Fog Creek Software, the creators of Glitch. We invented Trello, and co-founded Stack Overflow.<br />
Learn how Manuscript works:
The first 14 days are on us. No credit card required.
This could have be a description of Jira. Or another tool.
We are trying to help you here.
Let me add: do add screenshots.
I really really don’t like videos. Screenshots are faster and cheaper to add and tells me way more than a video I won't watch.
(Feel free to add a video in addition to the screenshots though.)
No it fucking doesn't. Here's your how it works page, with all statements that tell me nothing commented out: https://gist.github.com/honnibal/a57e00faf74c7d43182c3568aa7...
I was pretty generous with the definition of "tells me nothing".
The features page looks like it has most of the information I was looking for from the How It Works page. However your features page is laid out in a way that makes it very hard to use: I have to click a category, scroll down a whole screen, and then look at four paragraphs of text that together have about one paragraph of information. Then I have to scroll back up, click on another category, and scroll back down.
My company's FogBugz sub-domain also seems to be already registered. Maybe they're going to migrate everyone from FogBugz automatically.
Anyone have an info about this? I haven't noticed anything in any emails from Fog Creek. Nor do I remember seeing anything else about this anywhere.
But, very sadly, Manuscript seems to be FogBugz, not just 'based on the engine'. Still no Markdown for one.
Here's a little background on why we built Manuscript:
We launched FogBugz back in 2000 as one of the first bug-tracking systems around. Since it launched, the platform has been used to fix over 50 million bugs, by tens of thousands of teams around the world. But recently, we’ve been thinking about “Big Bugs” , trying to imagine how we can address both the necessary parts of shipping software and the larger risks that too often get overlooked.
So today, we’re using that same engine to create something new: Manuscript. See our launch post for further info: https://medium.com/make-better-software/introducing-manuscri...
And you've made some cosmetic changes to the client-side code that uses the 'FogBugz engine' (back-end code).
And now you're spouting really insipid bullshit about "Big Bugs". Please excuse my intense skepticism about that being anything other than nothing.
There's a few things I still like about FogBugz versus its 'competitors' – creating a 'case' (issue/ticket) from an email, being able to create hierarchical trees of cases, and being able to search cases. But everything else has been stale for a long time.
You don't even have real integrated version control! Kiln is about as basic of a web wrapper around Git as possible. Or maybe the code reviews are okay? I don't know. I've never used them nor ever heard or read of anyone else doing so either. Why's Kiln off on its own? Hosting a Git repo isn't exactly trivial if you're offering it for free, but you killed the free plan a while ago and I don't think anywhere near as many people as are using GitHub have ever even known of Kiln.
The propose UX improvements are also very very un-inspiring. To whom is FogBugz – I mean Manuscript – going to be marketed? Because it certainly doesn't seem to be programmers.
You mentioned using other tools – "like GitHub for integrated version control". I can't understand why anyone would use GitHub and FogBugz/Manuscript. GitHub already does pretty much everything FogBugz does, plus it's like 'embedded version control' instead of just 'integrated'.
Maybe Anil will push thru some fucking Markdown support tho before I'm finished migrating to GitLab. You guys (the extended Fog Creek family anyways) are probably half the reason why Markdown has been so widespread [i.e. Stack Overflow]. FogBugz has been marketed forever as being just for making software! How can you have relegated all of your users to using 'rich text' for so many years? Why?!
(Also, would you please add a 'description' to the cases so everyone can see, at the top of the case, a checklist [written in Markdown!] with everything that needs to be completed before the case can be closed? And how 'bout some case description templates too why'll you're at it?)
One big reason why people use us with a GitHub integration is that GitHub is almost entirely used by developers only, and yet creating software requires input from people across roles and departments. Manuscript with GitHub integration means you can collaborate across your whole organization, and involve Design, Support, Marketing and other teams, while developers still get to use the version control system they want.
I can tell you've got real passion and enthusiasm for what we're doing, otherwise the critiques wouldn't be as detailed and pointed. We want to get this right, so if you're game, drop me a line at email@example.com and we'll find some time to talk through what you expect and what'll keep you excited about where we're headed with Manuscript.
Not to nitpick, but having "introduction" pricing doesn't seem to be very upfront.
Seems like a good option for an org that want more than Trello but less than JIRA.
How is Fog Creek allowed to do this after the sale of Trello to Atlassian? I would have expected some provision related to not releasing product/project management software for some period of time?
Or is that not the case, contractually?
Their previous project is named [Glitch](https://glitch.com/) for example.
And Manuscript is just FogBugz anyways, tho I've at least grown used to the original name.
HyperDev -> Gomix -> Glitch
(HyperDev I guess is a play on HyperCard, Gomix is "go mix!" since they allow you to remix other people's apps, Glitch is ???)
That said, Glitch is pretty neat for small apps or demos, I just wish it would support more languages.