Atlassian Section

I have been slowly playing around with the Atlassian section, and I will focus on this so I get a starting point for other things. In Short I am building information pages for the collections and the corresponding apps. I will focus on the collections and then the big apps Jira, Confluence, Jira Service Management, and, of course, Assets. Rovo will also be there, as it has a lot of buzz at the moment, and I will probably add a section for Data Center due to the 2029 end date.

The purpose of these pages is to both act as landing pages to collect information from multiple sources of the website, but also as landing pages for SEO purposes to promote myself (and later others as well). The pages are not that difficult to create, but they require some design focus, and I have not felt that I have the inner peace to focus on such things for a while. Once I have this, I will finish the sections and start working with content for them.

Atlassian App Updates

I have opened up the Atlassian App updates again, and I will add the updates again. I stopped doing this as I did not feel it was worth my time to add the hundreds of updates, but now I will do it again. I do this both to make sure I am updated myself, but also because I see that there is a need for it in the community.

I am still testing out a few things, and I hope that I will be able to add a function so every member can add their Atlassian Home ID so they can find the release notes in their instance. I am using a custom profile field for this, which is proving to be less straightforward than I would like...

Overall, this database is working just fine, and I just might do some adjustments and improvements in 2026.

Videos

My videos section is already coming along fine. I am going to adjust some things and move over the remaining videos from YouTube, so I have a full set of all my videos here. For the Atlassian videos and the community videos, I will just finalize My Videos first, and then I will finalize those databases as well. I am also planning on making more videos in 2026, as I kind of lost traction in 2025 with all things going on.

All in all, the videos section is pretty much done, and I am just going to improve a few things in 2026.

Articles

The Articles section needs some changes because I want to separate this from blogs, which is a different category of content, as I see it. As a result, I will restructure this and move some content to blogs so the Articles section will be more professional and helpful. This will be a big task, and I need to consider how to do this so it makes sense content-wise.

Overall, the design and the code are where I want them, but I will add some functionality for views and split the content area that I have into other areas. I also want to see if I can add functionality for authorship for community-driven content to ensure that submitted articles provide value for the authors.

In 2025, I have also received several questions regarding purchasing Articles or to add links in existing articles from various SEO companies. If I add that as a possibility, I need to add some functions to mark articles as sponsored. I also need to figure out how this will work for community Articles since any income from their articles obviously should go to them. I will dig into the E-commerce aspect of this in 2026 and see what can be done.

Stories

For Stories, I might invest a bit to get help to build this as the Digg-like service I was initially planning on building. For now, I will just let it sit the way it is, with a few tweaks to add the new Views feature that I built for the Atlassian App Updates database. To build this, I might dig into the Invision Community plugin features to see what can be done, but we will see...

About Me

This section will be rebuilt in 2026, and I have several changes planned. The first change is that I will rebuild the My Work section, as it was built from a CV perspective, and I have a different approach in mind. At the moment, it is a bit cluttered, and having employment, projects, and other things in one database is not exactly optimal. So I will rebuild this section and also update the information. For this database, I will also rebuild and restructure the People database that is connected because it currently clashes with a larger people project.

For My Roles, I am considering changing things to better fit not just roles, but expertise in general. I am going to present my competence and expertise in more detail as people sometimes get surprised that I know more than they thought. I will also add some videos for this, I think.

If time permits...

Depending on how much time I have in 2026, it would be fun to build a people section and a job section. Nothing super fancy, but a nice way to present great people and a place where people can post if they are looking for work, or want to employ someone. I do get a ton of people asking me for references, connections, and so on, so why not take that to the next level?

I already have the Awesome People database, so I could just expand on that and see what I can build.

I have also toyed with the idea of doing some things with APIs. For example, I would like to see if I can build a website front for tickets to Jira Service Management so people can submit tickets. It would also be fun to see if I can get tickets from Jira Service Management as well to present on the website.

We'll see what time permits in 2026.

That is pretty much it.

Not as much as I usually plan, but my main focus this year will be to finish my book and a few other things outside of the website.

The biggest change so far is that I realize that I need more content around Atlassian that goes beyond what is database driven. In short that means that almost all content I have is from one of the databases and I lack proper pages with focused content. While Articles are great, I also need information pages and because of that I am adding an Atlassian section. The idea is that this section will hold a combination of Atlassian information and how I am connected to that information.

As an example I am adding a landing page for Atlassian where I want to present information about Atlassian, a list of their products, some links and useful information. I will also add myself as an expert and later also link to other experts or companies that I collaborate with. This is my top priority and from that page I will start creating different subpages for Atlassian products and some information on what I am offering in terms of services as a consultant. I aim to focus on Rovo as that is now the core of the Atlassian platform and two pages for the two new collections that I have a feeling more people will want to know more about.

The goal here is to make great pages that can generate traffic.

Tags and organization of content

When it comes to content I am also continuously working on my tags to clean out unused ones and adding new ones that are needed. In this event alone I will be adding dozens of new tags and start adding them to new content. These new tags will partially be combined with a new category setup where each database will have a field for categorization. This categorization will then be connected to custom icons I will set up in Font Awesome that I just upgraded to the new V7 Pro+ package. This allows me to have up to 500 custom icons, which should be enough for now.

With this new categorization you will also be able to filter content in each database, and for many categories you will have custom icons displayed to help identify what kind of content is in each object.

By doing this I am also removing many of the categories used to classify content before. This should provide a more fluid experience and provide a better overview of content when it is not all compartmentalized into categories.

Needless to say this is a very, very large project and with hundreds of tags to work through, it will take a while to get things sorted.

The New Atlassian

The new Atlassian also came with new graphics and new colors this year, and I am working on collecting all the Atlassian icons as SVG so I can use them in different ways, like adding them as fonts through Font Awesome. Atlassian announced two new products and added an icon for Assets this year, so I have added those as icons as well as tags. I am still chasing down the so-called Platform Apps, which are Goals and Teams for example.

Color wise we got four "new" colors this year, or rather Atlassian added them as branding now for their product apps. Yellow, green, purple and orange are now added to the blue and white as highlight colors. I will add them as primary variables so I can use them across the site. I have also added them to my Figma file where I have decided to break out my Atlassian content to a new project.

Based on these new colors I will also update my YouTube graphics.

Speaking of YouTube and Videos

When it comes to YouTube and Videos I feel that I am moving towards a good setup here on the website. I have set up the categorization standard on My Videos and I will just need to make some adjustments to the templates there, and then I think I am ready to start adding my YouTube videos and start working with them.

Once the section for My Videos is done I will add the same templates to the Community Videos.

This is going to be great!

A lot of fun things are happening behind the scenes right now, and I am working on cleaning things up and "killing my darlings" when it comes to databases. With the new way Invision Community is handling databases it is no longer possible to have a database that is not connected to a page, which makes having internal databases a bit tricky. I can get around this with some database magic, but I would prefer not to have to hack things, but it is what it is. Most of the databases though are not being used, or have very little content, so I plan to delete those databases, after I have saved the content if it is something I want to keep.

When it comes to Articles I will do some cleaning there to make it more useful for the users. I have been using it for thoughts and articles with little consideration of the difference. It is time to change that and also to consider what value the articles are actually providing. Articles should have a value and if they don't, then they should be moved to my personal blog. I will also make sure that I publish at least one article every month, so I will start planning topics for 2025.

I also realized that as I will focus a lot on the Swedish market as part of my new job. This means that since this site is in English, I need some strategy for making Swedish content. I have just purchased a few domain names for this purpose, and I'll see how I can best use this for promotional purposes. I will need to sit down and consider the best strategy for this, but I have a few ideas...

When it comes to tags I have set up a strategic list of what tags I want to start with, and it is a fairly extensive list. I have started to create these tags and I will continue to do that for a few weeks. I will also go over all content, which is quite a lot of content, and re-tag content. I will also go over content in general to see just what kind of content I have. Some content I want to remove and some content I want to elevate with new graphics and some touch up. Some content I also want to re-publish or move to pair it with the content it should be. This means that some blog posts might become an article and some articles might become blog posts.

There are a lot of things to be done, but much of this is behind the scenes, so things might seem a bit slow for you. So just be patient and you will see things in time :)

Slow and steady wins the race.

The first thing that I need to do is to change the start page. Currently, it is just all content splashed and no real focus on direction. The new start page will have more focus on me, what I offer and how to get in touch with me. This means that much of the content that currently exist will be removed from the start page. I will also move some areas like My Personal Blog to be only for members and My Articles will be the focus for my writings. The Articles section will be renamed to just Articles and I will connect the two databases for articles differently than today.

I will also create a new page for my book The Advanced Atlassian Administration Guidebook. This way I can prepare for when it is ready to be sold. My thoughts right now are to create a section for each of the chapters with information on what I intend to write there. I will also add a newsletter sign up so I can send out updates to those that want to learn more about the progress of the book. I will add a section on the main page for this as well to make it easy to find. On the book page I will also add information on how to participate in the Club by providing feedback on the content, or inspire new content.

While this will not be a very large change for you as a member or visitor, it will be a lot of work behind the scenes to clean things out. The biggest changes for you will be a new navigation and the new pages for the start page and the book page.

It has been a long journey to get here, and I am super excited to finally, finally be able to put time and effort into this website again. I am still focusing my time of getting a new job and writing my book, but once life settles into a structured pace again, I will spend more time on this website for sure. For now, I just updated the site to the final version of Invision Community 5.0.0, and I will start planning the restructure and clean up a bit and then back into the My Work section to get that done.

This is going to be Epic!

Changes to ipsTabs

Invison Community Beta 5 introduced a change to the structure of ipsTabs and as such all my tabs stopped working. This is of course the problem with using the standards in Invision Community that if there are changes being released, then you might need to do some refactoring. This obviously happens a lot more when a new major version like V5 is in beta, so it is not a huge deal normally. In this case it was pretty quick to update and the code improved, so I have no complaints.

For ipsTabs I have an article in the works describing how they work and how you can easily build with it in Pages templates.

MyWorks is nearing completion

MyWorks is almost done now, and I just need to change the listings a bit, so I will create a new template for that, or just add some conditional additions to the base templates. I am happy with the structure and I added back the People part from the People profile database. The database itself is hidden, and you can’t access the profiles themselves, but since even guests need permissions to see profiles in order for me to show them on the MyWorks section, I will have to make some adjustments to the People Profiles templates. I will just add a condition so only I can see the content when accessed directly, and then it should work just fine.

After some annoying experimentation I figured out how to get the getReciprocalItems to output several times in different places, which allowed me to control where different fields were output. I am still struggling to get the Forms to work the way I want, but for now that is not a priority as this is not something I will work with every day and no one else will actually see the form anyway.

Reviews are getting updated

I want to add the Reviews back again and include that on MyRoles especially. It is not a big task, but it will take some time so it will have to wait until after I come home from Dublin. I am basically just going to make a new design, and it is pending some information from the Invision Community team since I have an idea that may not be possible due to how the platform stores ratings. If what I have in mind is not possible, then I have some other ideas anyway, so it is all good.

Reviews will probably be split into two as well. One will be for Recommendations and one will be for Product Reviews when I later start working on the Apps database.

There is indeed no shortage of work to be done here, but I love it and enjoy every minute of it!

Overall the My Roles section is now a great complement to my normal CV’s and I can start working on enhancing the roles with content. There are two major items I want to add there and the first is a Video presentation for each role. These will be short videos to complement the description, so the visitor get a more personal experience as well. I have not yet decided how to present these, but I have a few ideas.

The second thing I will work on is a recommendation section. This will be a separate database where people can add recommendations on different roles or work items. I have several of these already on different places, like LinkedIn, and I will add them to my website and then connect them depending on what they are related to. This will be a quick project, but it is not a priority as I want to get the My Works section up first.

Overall I am very happy with the progress on this site.

I already have a database for Roles and I will repurpose and this will be very easy to do since much of it is pretty static. I will make these entries in two languages, so each entry will have a switch between English and Swedish. For the Assignments I will simply use a plugin block that I add to a text field. This will allow me to feed in entries from the My Work database automatically. I will play around with this a bit to see how I can best use this to make it look exactly like the CV I have in the downloads section.

Speaking of the downloads section I will upload my CV’s again as I make the new ones. It should be pretty easy to do, especially if I put in the work to build the My Work properly. I will be able to get the listings of work automatically, but I will need to build multiple versions of the blocks to fetch the language specific fields depending on what language the user has selected. This should not be a problem, but it will be a bit time-consuming. As most CV’s have the same data, except for the description and in some cases the list of assignments, building this database and maintaining it should be a lot easier once I have this set up.

For the areas where I have Employments, Education and Certificates I will simply just make blocks for that since they rarely need to be updated. For Area of expertise, Industry experience, Methodologies and Tools I will have to consider that a bit. The reason for that is that I want to link those to Tags and since you can only have one section for tags, I might want to set up a new database for that. This way I can use the database link field to select the “tags” I want to add to different sections. I have to test this and see if this works, otherwise the option is to make several blocks, and I am not that keen on doing that to be honest.

To be able to work with Tags this way I need to make sure I can split the field values because they are saved as a comma-delimited list rather than individual items. This should not be that difficult, but I need to put in the time to actually solve that part.

There is no shortage of fun things to build, but it takes time and I have to make sure it does not cause stress. This is because I am still recovering from a long period of extreme stress and working on the website should be fun and cause for joy and creativity and not stress. So, I will take it slow and put this on the to-do list while I continue to work on the My Work section.

You can follow the progress in the Roadmap as always.

The biggest change I have done is to split out the New This Week status as a Yes/No toggle and adding a link to the Atlassian Product change items. The New This Week is only viable for one week and every Wednesday they need to be removed to make room for new ones from the Atlassian Cloud Changes list. I have made this toggle visible when viewing the item itself, which makes it super easy to update.

The link to the Atlassian Product Change take you directly into the Product Update object in your Jira Administration. This is for convenience for those who want to check the object itself. It also make it easier for me to follow up on things in case I want to double-check something, or refer to the actual update.

My daily routine now will include to go over the daily updates and add them to the Atlassian Product Update database. Then every week I will go through all entries in the Atlassian Cloud Changes to make sure they are updated properly in the database. This will then provide me a nice list of the latest updates that I can use when making my weekly videos.

Structure of Stories

This is by far the biggest task right now as information structure must be simple, but still make it easy to find the information you are interested in. Right now there are a lot of categories, and I am going to work with that to see what the best solution is from a UX and SEO perspective. I will probably make a few tests to see if there is a way to improve on this as I get more people trying involved.

The biggest work will also be to ensure that all products and companies have a Tag, so I can connect all Stories properly. Considering the amount of these that exists, this will be a continuous work as I can’t add the thousands of tags up front.

Pictogram CSS

I see that I will want to use pictograms for all the Atlassian products in various places, and I am going to create a new CSS for just that purpose. As I am using Font Awesome I have been playing around with the custom icons and I will update those with the official logos so it is easy to use. You can see that I have already added a few of these on the Stories listing, so I will just refactor this and create a new CSS file for this.

One issue I have is that I have a bit of a problem with setting the class name based on the Category name as it contain spaces in some cases and the names are not the same across databases. If there was a way to add a custom field to the categories, this would not be an issue, but for now I have to map the category ID to each class, which is a time-consuming activity.

I keep working on this, but I will begin with adding it to Stories first and it will be super simple.

/*** Jira ***/
.jwsea_newsHeader_logo_703:after{
  content: "\e010";
}

Simplify and create a new form

Adding stories should be super easy and to make it, so I will create a new Form for Stories. This form will work like the old ones where I use tabs and collapsible areas to make the initial form view super easy to use, but with options if needed. Currently, there are so many fields that I will go over and review. I want to make things as simple as possible and then extend when it is actually needed rather than bloat things and make things feel more complicated than it is.

This will be the first form I recreate, and I will create a new CSS for Forms as well where I have the forms styles to be re-used for other Forms. I might also create a JS file or two as well if needed.

Stories will be my focus for now

Stories is the main focus at the moment, and it will be my focus for the next week or so. I am having a ton of fun building things again, but I also have a ton of clean up to do as well as saving the old code, so I can reuse some of it for future projects.

With the upgrade in place I can now start building new templates again for the databases. Yesterday I had some fun working with the Stories database, which is what I will focus on first. Once the Stories is done, I will focus on My Projects and then Awesome People I think. This is just my current plan, and it can change at any time depending on where I feel I want to put more effort in.

Prominent bugs are that all images uploaded in the content is broken and there seem to be some issues with uploading images to the gallery. This does not affect uploading new images in the content, like into this post for example, but it will require quite a lot of work to fix if there is no good way to update it programmatically in a future release. It’s not that bad though as I have a plan to go over every bit of content anyway and change the graphics and perhaps the content a bit.

The biggest work will probably be to change all the Videos as they now require an image. It used to be that I programmatically set those, but I am not sure if that is how I want to set that up again or not. There are advantages if there are static images, but then again that will cost a lot of storage as well… so I am not sure yet how to proceed.

Overall though I now have a “blank” canvas again and I can start building things again. There is a lot of work to be done, but I am loving it!

When I switch over things will be very messy for a while, but that is expected. I will basically revert all customizations and then start over with the V5 engine to redesign certain templates. Right now I am saving all the templates as code for safekeeping, and so I can check what customizations I have done in the past. Once I have that I will make a fresh export to the beta site with the production data and production files.

Next step is to change the templates for all databases to the default ones. I will then delete the old template files to make sure there are no customizations anywhere that can cause problems. After that I will do a V5 upgrade and if all goes well then I will just wait for the next Beta release to get the Tags bug fixed before I upgrade the production site.

Once everything is upgraded I will start configuring everything. I will focus on the Articles, Stories and Atlassian Product Updates since those are the ones I will work with most after the upgrade. After that I will probably take a look at the My Projects database, Videos database and then the Atlassian CVE's. This can all change depending on what I see I need to focus on next.

At the moment I am deep into planning the structure as it is a bit tricky to get all the areas set up the way I want them. This is because of the content structure is so diverse and because I want to split things up a bit, which will lead to quite a lot of configurations. I always tend to get things a bit complicated, then I simplify too much, and then...well, you get the idea 🙂

So this time I need to step back again and consider the pros and cons of the approaches, as the new tag system really will throw a wrench into this thought process. There must be a value in how I divide things, or it will just be a waste. Right now, I am considering the SEO effect as I have quite a lot of content, but I have not really put any effort into SEO in the past because this is a playground.

Part of this is also a massive update of pretty much all content. Not only to freshen up the content, but also to change all graphics to WebP and remove the branding. This to be more in line with the new branding, making the site much faster, AND to make the site easier to rebrand in the future.

So, I have a ton of work before me and I absolutely love it!

While I still expect a few months before a stable release, I feel that things are moving in the right direction and I can finally start building things here again! I will see if I can set up a test install here this weekend and do a test upgrade. This should tell me roughly what to expect for the live site.

Once I have that, I can start playing around with the templates and things of that sort. While it is now almost impossible to work with database link designs as we can no longer access those templates, I think I can work around that since the new tag system will replace many of those areas anyway.

Overall, I am excited to sink my teeth into testing Invision Community V5 in more depth using a self-hosted test site rather than a cloud hosted alpha site 🙂

The first advantage is that Stories is focused on a fairly limited number of topics, where the Atlassian ecosystem is the main focus. While the Interesting and Ways of Working categories are fairly broad areas, they are still limited to a reasonably niched community. I also do not expect to go viral anytime soon, so the volume should be manageable. If things escalated, then we can always split the database into several areas....which I might do anyway now that I think about it...

Functionality wise, I will try to keep things as easy as possible and expand only if I see that it actually lead to more value. The main focus will of course be to make sure the users quickly can get to the website to read the full article. The secondary function is to rate the Stories to help them become more visible, and the third is to provide a discussion area for the story for those that want to comment or discuss the story.

I think that once I have some traffic it might make sense to split up to have more than one sorting on the start page, but in the beginning I will just have the latest Stories. I will also have the latest Stories block for the sidebar, and then I can add blocks for top ranked over time and make that a tabbed block.

For now my main focus is to update the categories for the Atlassian categories, since they are the main focus, and then I will consider if I want to split the Stories for the other main focus areas, or keep them in one database.

Stories will be a fun thing to build, I think, and I will look at how I can combine this with the Release notes as well...

This weekend I have updated the forums a bit so they have descriptions and are toned back a bit when it comes to colors and things like that. I am also adding a new level since the new design require that, and I have moved a few things around to accommodate the new databases I have added. Those databases are the Atlassian Release Notes, Atlassian Product Versions and the Atlassian CVE databases.

In the clubs, I have created two new clubs: The Swedish Jira Users and the Content Creator clubs. Swedish Jira Users will be for local Swedish users that prefer to discuss things in Swedish, and the Content Creator club are for those of us that create content on various social media and on our websites or blogs. This should be enough for now and show that there are more than just one club.

For the blogs, I have added a second group blog named "If you don't - Mind" where I will post more about psychology and how that affects us. It is a pretty big area and I hope we will see that people will enjoy it, have opinions and of course contribute with their own perspectives.

I am also getting back to add Stories that I will rebuild a bit to remove the colors to unify the color scheme. For now, I am adding news update as I find them in the Atlassian Community and some other resources.

I am going to duplicate the databases for Articles and Videos because I want to divide them into My Articles (since it is my website) and community content. So rather than messing with the categories, I will keep the database separately. This way I can also develop those separately, which will be good since I might have different need than the community in general. Both Articles and Videos will be rebuilt to reset the design and go back to a more standardized template. I also want to make sure the videos especially get more room in the display template.

I will also make some changes to the My Projects database, since I have not updated that in a while. As I am looking for new employment, I will also update my CV's in the Files section and I want to make sure I have my projects updated with proper information in case potential employers drop by and read it.

For all content, I will do a massive overhaul of the graphics. This is one of the reason why I am also investing in graphics and set up new workflows. The idea is that all content will have new graphics that is optimized and in the WebP format. While doing this, I am also going to promote some content or repurpose it into new content. This will reduce the content size and improve load times by a lot, but it is also a massive undertaking that will take a while to get through.

So there are things happening, even if you might not see much design wise 🤖

I am currently alpha testing the new V5 version of Invision Community, and it will be some time before it will be ready. It has a lot of potential and I very much look forward to it being released, but it has a lot of bugs at the moment, so I don't expect it to be released anytime soon. This means I have more time to play around with things, but it also means that I will probably not have any new site done this year, or very late this year.

This is neither good nor bad, but the way things are.

There are a lot of other things I can still do on this site to prepare it for the new design. One of those things is to go over all the content and adjust it a bit to make sure it fit the new structure and focus. I already wrote about the new focus in my personal blog here:

What I am looking into deeper now is how the new tags system work and how I can best use that. The new tags system will allow for more of a node thinking, which is something I have wanted for a very long time! This new system will allow for easy organization of content, so you have tag sites that will give you the latest and greatest content for a specific tag from all products within Invision Community. This will be a very interesting way to summarize and group content that I very much look forward to.

I am currently considering how I can best utilize this functionality, since all tags are curated and require manual setup. I want to combine this with the databases, but I am not 100% sure how I want to do that yet. I know that everything related to Atlassian as a company will be one tag and then one tag for every Atlassian product. I also want one tag for each of the Ways of Working and Interesting categories. This means that I can provide a pretty nice structure of information and allow people to subscribe to the content they are interested in.

I have not yet decided how to do with other companies and other products, but I figure I will add some of the largest companies and products that I will write about most...

This will require quite a lot of work to create the tags and then go over all content and tag them with the new tagging system. It does allow me to touch up and republish some articles, though, which is always a good thing.

So, I guess the summary here is that I am kind of waiting for the release of V5, so I can start working on this site again and rebrand myself again. For now there is not much point in doing anything since the code is still moving in V5, and I am not sure what CSS classes I will be using once it gets released.

I will keep posting thoughts here until we are getting closer to release.

I think the problem is not so much to set this up as it is to present it. So while I can just create the products as categories and then have the Features as subcategories, it will mean that I separate content from the main product. This is because I can't have a data object connected to more than one category.

So what I can do instead is to work with Prefixes.  This allows us to mark articles and stories that are for example related to Data Center or Cloud, but also if it is related to a Feature like Assets or Plans. While I can't lock down the Prefixes per category, and it will be a little messy if people start to abuse it, I think it will be worth exploring it to see how it will pan out.

I will also ponder a bit on how to make this visible in the product pages as well once I get to those.

In short, I have been trying to adjust the SuperVote page template by OpenType, one of the best Pages developer there is. While partially successful, I never got it working 100% and that is probably because I broke everything while trying to adjust it to my liking. Instead of trying to hack the ratings update from the page listing, I will see if I can work with what already works.

There are a few things that already work very well. For example, the actions taken are very nicely displayed based on the actual rating given. A little indicator show which news items you have rated, and the news itself is dimmed out if it has been given a low rating.

These things are very nice, and I can work with this to show things nicely when I redesign this. If I can figure out how to update the ratings in the listing view, then that would be awesome, but I will not put too much effort into this to get started. Getting the news added in a news section will be the main focus.

Automate News

Automation of news will be important. Getting it done without ripping full articles is a bit trickier. While Invision Community comes with RSS import, it is crude and basically just show the RSS content. This will not work because that way I will basically be stealing articles from the Atlassian Community for example and that is not what I want. I can kind of mitigate this by truncating the content, but that is crude and not really a proper solution either.

I can go with Zapier, of course, and I probably will do that in a limited way as it is quite expensive. The advantage with Zapier is that I have a lot more control, and I can for example truncate the content before it even comes to the site. Setting this up can be done using multiple Zapier accounts, where I set up one Zapier account for each RSS feed. Considering the number of RSS feeds, this is quite a lot of accounts to set up.

Designing a new News setup

I will spend some time to design a new News setup and try to figure out where to take this today and what the vision would be for the future. I am looking into the old Digg setup from the early 2000 as inspiration for what I would like to build eventually.

For now, I am just brainstorming to try to figure out what functionality would make sense. I see some of these functions also being useful for other databases, so I will gather some functions together as a base for future database ideas as well.

I will update with some designs once I have something to show.

As for what I am currently doing I am playing around with design while I am waiting for Invision Community V5 to be released. I am creating the new icons and playing around with the colors a bit. I have decided to steal the Atlassian colors because they fit pretty well with what I have in mind and it provides a pretty good starting point.

I am also playing around with the Atlassian product logos where I am exploring a line art version, but I am also creating new icons that are based on the Atlassian logos. These logos are different because unlike the Atlassian logos that have curves, my icons are built up with "pills" instead.

I am having fun, but there is a lot of work to be done to set this up the way I want it. The colors alone are around 130+ colors and then I will need to decide on product colors and make the new icons. I will also need to create the CSS classes for all the colors, but for ths icons I am adding them to FontAwesome, so that is super handy!

I will write more about the changes here as I get deeper into the process.

So, more to come!