Skip to content

Commit

Permalink
[#4] Show alternatives in alphabetical order and add prettier
Browse files Browse the repository at this point in the history
  • Loading branch information
Shouvojit Sarker committed Jan 12, 2021
1 parent f081ee2 commit c7db15a
Show file tree
Hide file tree
Showing 27 changed files with 1,142 additions and 991 deletions.
18 changes: 18 additions & 0 deletions .github/workflows/on-push-validations.yml
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
name: on-push-validations

on: [push]

jobs:
test:
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v2
- name: Set up Node.js
uses: actions/setup-node@v1
with:
node-version: 15
- name: Install dependencies
run: yarn install
- name: Validate alphabetical ordering of alternative products
run: yarn validate
1 change: 1 addition & 0 deletions .prettierignore
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
**/public/assets/hint.min.css
2 changes: 2 additions & 0 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,3 +7,5 @@ Community Repository for the Bye-Bye-Server Website
If you want to contribute a product - edit the products.json in the public directory

Make sure your product supports on premises deployments, as we want to provide alternatives for Atlassian Server customers.

There is a husky pre-commit hook that will automatically sort the product list in a alphabetical order. Committing with `--no-verify` and subsequently pushing will result in the github action validation failing if the products are not in alphabetical order. The pre-commit hook also runs prettier, maintaining a styling consistency.
14 changes: 6 additions & 8 deletions _posts/blog/betting-on-datacenter.mdx
View file
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
---
title: 'Betting on Atlassian DataCenter?'
excerpt: 'With Atlassian Server products being retired, customers are tempted choose Atlassians Data Center offering instead. Let us explain why that might not be the greatest idea.'
coverImage: '/assets/blog/blog6.jpg'
title: "Betting on Atlassian DataCenter?"
excerpt: "With Atlassian Server products being retired, customers are tempted choose Atlassians Data Center offering instead. Let us explain why that might not be the greatest idea."
coverImage: "/assets/blog/blog6.jpg"
copyright: Photo by Taylor Vick on Unsplash
date: '2020-11-02T06:35:07.322Z'
date: "2020-11-02T06:35:07.322Z"
author:
name: Stefan Ernst
ogImage:
url: '/assets/blog/blog6.jpg'
url: "/assets/blog/blog6.jpg"
---

With Atlassian Server products being retired, customers are tempted choose Atlassians Data Center offering instead. After all, you can
Expand Down Expand Up @@ -35,7 +35,7 @@ When making investment decisions on this scale, it also helps to read Atlassian
has an interesting choice of words when it comes to Atlassian Data Center:

_Now that said, I have talked to a whole number of CIOs over the last three months from everything from regulated industries, banks, European customers. And every single one of those CIOs have a plan to move to our cloud. They are -- and whether they're in a regulated industry or a European customer, and it's just a matter of when. And so, our data center product is going to be critical in making sure those customers are supported over the time frame for migration.
But we expect that all our customers **will migrate to cloud over the medium term**._ (Scott Farquhar -- Co-Founder & Co-Chief Executive Officer)
But we expect that all our customers **will migrate to cloud over the medium term**._ (Scott Farquhar -- Co-Founder & Co-Chief Executive Officer)

So don't bet all your horses on Data Center products. After all, everyone else is anyway moving to Cloud, so what are you doing?

Expand Down Expand Up @@ -66,5 +66,3 @@ of a normal server license. The security of investments looks very weak to us.
As we mentioned in our [next steps blog](/posts/next-steps), we advise you to wait, don't panic and look at competing products for the next year.

If you have more questions, or you want to discuss with us on an individual basis, reach out to us at [[email protected]](mailto:[email protected])


30 changes: 7 additions & 23 deletions _posts/blog/con-reasons.mdx
View file
Original file line number Diff line number Diff line change
@@ -1,56 +1,40 @@
---
title: 'Five reasons to look for alternatives'
excerpt: 'The community reaction to Atlassians announcement to stop selling server products was ... to put it mildly ... mixed. There was a lot of frustration on social media - and even though Atlassian Solution Partners are trying to clean up the mess, here are five reasons why it might be time to turn our backs on Atlassian products and move on'
coverImage: '/assets/blog/blog5.webp'
title: "Five reasons to look for alternatives"
excerpt: "The community reaction to Atlassians announcement to stop selling server products was ... to put it mildly ... mixed. There was a lot of frustration on social media - and even though Atlassian Solution Partners are trying to clean up the mess, here are five reasons why it might be time to turn our backs on Atlassian products and move on"
coverImage: "/assets/blog/blog5.webp"
copyright: Photo by Jonas Weckschmied on Unsplash
date: '2020-10-19T06:35:07.322Z'
date: "2020-10-19T06:35:07.322Z"
author:
name: Stefan Ernst
ogImage:
url: '/assets/blog/blog5.webp'
url: "/assets/blog/blog5.webp"
---

In this article we list the counterarguments to "[Five Reasons to stick to Atlassian products](/posts/pro-reasons)".


The community reaction to Atlassian's announcement to stop selling server products was ... to put it mildly ... mixed. There was a lot of frustration on social media - and even though Atlassian Solution Partners are trying to clean up the mess, here are five reasons why it might be time to turn our backs on Atlassian products and move on



### Reason 1: Atlassian is not interested in you


Many customers now feel completely let down by Atlassian. And that impression is not unjustified. In fact, for customers with small to medium-sized user tiers, the only way forward is to go to the cloud. And not everyone wants to go down this path - no matter how much Atlassian tries to convince people to do so. Atlassian seems to have come to terms with the fact that its own product offering is no longer suitable for all customers. And is also prepared to lose these customers.



### Reason 2: You are in an endless price increase spiral


The announced price increases for data center and server editions are just the newest additions to a long list of price hikes.
The formerly low priced server offer has long since become a major cost factor in the 5-digit range for many customers. And with Data Center everything is getting worse. A Jira installation that was purchased for less than $10000 a few years ago suddenly costs >$100000 ... every year. Also caused by the price increases of app vendors in the Atlassian Marketplace.

The formerly low priced server offer has long since become a major cost factor in the 5-digit range for many customers. And with Data Center everything is getting worse. A Jira installation that was purchased for less than $10000 a few years ago suddenly costs >$100000 ... every year. Also caused by the price increases of app vendors in the Atlassian Marketplace.

### Reason 3: Ignored for years


Have you ever been to jira.atlassian.com and voted for a feature or bug? You may have noticed that many of them were opened over 15 years ago. Unfortunately, Atlassian has let customers down for years and failed to address many of their concerns.
Some of the gaps have been filled by app vendors but many still exist - like the famous [CLOUD-6999](https://jira.atlassian.com/browse/CLOUD-6999) - Custom Domains for Cloud Apps or [JRASERVER-7266](https://jira.atlassian.com/browse/JRASERVER-1391) - Editor for email templates.



### Reason 4: Technical frustrations


If you read about Jira on social media, you will find many frustrated users who are not satisfied with the Jira installation in their company. Partly this is due to badly set up local instances that do not perform properly or fail more often due to technical problems or lack of resources. Surprisingly often though, these people talk about Atlassian's own cloud - and indeed: Atlassian products have become slow and frustrating to use. With Confluence Cloud today, you can watch every single button load, slowing you down a lot.
Insert macros - and what takes fractions of a second on Server can cause some decent waiting times in Cloud - especially when it comes to third party apps.


Insert macros - and what takes fractions of a second on Server can cause some decent waiting times in Cloud - especially when it comes to third party apps.

### Reason 5: You want more

A change of products also offers opportunities - maybe competing products offer features that the Atlassian platform does not - or only through third party vendors? The search for alternatives also always offers the chance to clean out your application portfolio and make room for new ones, to optimize processes, to work better together - or simply to eliminate what is no longer needed and save costs.



We are looking forward to taking a closer look at the wide world beyond Atlassian products and will write a lot more about it in our blog. Any suggestions or questions? Please write to us at [[email protected]](mailto:[email protected])
23 changes: 5 additions & 18 deletions _posts/blog/next-steps.mdx
View file
Original file line number Diff line number Diff line change
@@ -1,38 +1,25 @@
---
title: 'What to do next?'
excerpt: 'Atlassian has announced the discontinuation of sales and support for its own server products. The announcement came as a shock to many existing server customers. Now there are many questions - but the most important one at this time is probably the following: What are the next steps? We try to find answers. '
coverImage: '/assets/blog/blog3.webp'
title: "What to do next?"
excerpt: "Atlassian has announced the discontinuation of sales and support for its own server products. The announcement came as a shock to many existing server customers. Now there are many questions - but the most important one at this time is probably the following: What are the next steps? We try to find answers. "
coverImage: "/assets/blog/blog3.webp"
copyright: Photo by Javier Allegue Barros on Unsplash
date: '2020-10-18T05:35:07.322Z'
date: "2020-10-18T05:35:07.322Z"
author:
name: Stefan Ernst
ogImage:
url: '/assets/blog/blog3.jpg'
url: "/assets/blog/blog3.jpg"
---

Atlassian has announced the discontinuation of sales and support for its own server products. The announcement came as a shock to many existing server customers. Now there are many questions - but the most important one at this time is probably the following: What are the next steps? We try to find answers.



Atlassian Server products have been around for many years - the first version of Jira was released in 2002 - and there are many customers who have been loyal to Atlassian for decades. The more you invest in the platform over the years and the more users you have in Confluence, Bitbucket or Jira, the harder it becomes to decide what to do next. Thousands of Jira projects, Confluence areas, apps, user data, custom apps. How do you migrate all that? And the answer is not always clear, because Atlassian customers are so diverse. It always depends on what your needs are - what's important to you - and what you can possibly do without.



Many Atlassian administrators probably feel overwhelmed at the moment because of the collossal task that lies ahead. But like every journey, everything begins with a step - after all, you don't climb a mountain by jumping up.



The first advice I want to give you is very simple - just wait. The server version of your products is supported until 2024. And time is playing for you!



Atlassian's announcement has caused a big stir in the market. Now the phone is ringing off the hook at many alternative product providers, Atlassian partners and Atlassian itself. Chances are that in a few months, the transition will be much easier for you than it is today - either Atlassian Cloud products will become more attractive and support the features you lack today - or the competition will fill the gap. In the meantime - if you have an active server maintenance license - reach out to your Atlassian partner so they can generate a quote with the existing pricing. You have until February to do so.



We will try to follow this development on this page, analyze the market, try out third party products and give you tips on how to make the migration - wherever - easier.



This work will be continued, so please add this page to your favorites and visit us again soon.

127 changes: 69 additions & 58 deletions components/BlogList.js
View file
Original file line number Diff line number Diff line change
@@ -1,64 +1,75 @@
import Link from "next/link";
import React from "react";

export default function BlogList({posts}) {
return (
<>
<style jsx>
{`
h1, h2, h3 {
padding: 0;
margin: 0;
margin-bottom: 10px;
font-weight: 300;
export default function BlogList({ posts }) {
return (
<>
<style jsx>
{`
h1,
h2,
h3 {
padding: 0;
margin: 0;
margin-bottom: 10px;
font-weight: 300;
}
h2 {
font-size: 1.6rem;
font-weight: 300;
}
.half {
flex-grow: 1;
flex-shrink: 1;
flex-basis: 0%;
padding: 1rem;
}
.text {
flex-grow: 3;
}
.half p {
font-size: 1.2rem;
font-weight: 300;
}
.half .inner {
max-width: 1200px;
}
@media only screen and (max-width: 1000px) {
.Flex {
flex-direction: column;
}
h2 {
font-size: 1.6rem;
font-weight: 300;
}
.half {
flex-grow: 1;
flex-shrink: 1;
flex-basis: 0%;
padding: 1rem;
}
.text {
flex-grow: 3;
}
.half p {
font-size: 1.2rem;
font-weight: 300;
}
.half .inner {
max-width: 1200px;
}
@media only screen and (max-width: 1000px){
.Flex {
flex-direction: column;
}
}
`}
</style>
<div style={{flexDirection:'column',justifyContent:'center'}}>
{!posts && <div>No posts!</div>}
{posts &&
posts.sort((a,b) => new Date(b.date) - new Date(a.date)).map((post, index) => {
return (
<div className={'Flex'} key={index}>
<div className={'half image'}> <img src={post.coverImage} style={{width:'100%',maxWidth:500}} /></div>
<div className={'half text'}>
<div className={'inner'}>
<h2><Link href={`/posts/${post.slug}`}><a>{post.title}</a></Link></h2>
<p>{post.excerpt}</p></div>
</div>
}
`}
</style>
<div style={{ flexDirection: "column", justifyContent: "center" }}>
{!posts && <div>No posts!</div>}
{posts &&
posts
.sort((a, b) => new Date(b.date) - new Date(a.date))
.map((post, index) => {
return (
<div className={"Flex"} key={index}>
<div className={"half image"}>
{" "}
<img
src={post.coverImage}
style={{ width: "100%", maxWidth: 500 }}
/>
</div>
<div className={"half text"}>
<div className={"inner"}>
<h2>
<Link href={`/posts/${post.slug}`}>
<a>{post.title}</a>
</Link>
</h2>
<p>{post.excerpt}</p>
</div>

)
</div>
</div>
);
})}
</div>
</>
)
}
</div>
</>
);
}
13 changes: 7 additions & 6 deletions components/ExternalLink.js
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
export default function ExternalLink({url,children}) {

return (
<a href={url} target="_blank" rel="noopener">{children}</a>
)
}
export default function ExternalLink({ url, children }) {
return (
<a href={url} target="_blank" rel="noopener">
{children}
</a>
);
}
Loading

0 comments on commit c7db15a

Please sign in to comment.