Experience working as Full stack developer as project of company or freelance, Simple and quick way to build a company profile website project sometime has challenges using Craft CMS with element based. Then 4 Years using Craft CMS getting consistency to work with composer which is also in Laravel. Be different level that use Laravel to build a CRM with complexed architecture. PHPStorm really help to assist both quality on coding
I think you're putting the cart before the horse. This won't make sense to you now, but it will one day. Coding doesn't matter; programming is the least of your problems in getting a job. Any language learned well is all that matters. They are all more or less the same. You don't get a job because of your skills in a specific language, you get a job because the person giving you the job thinks you'll stick around and not give up. That's why they all want 2+ years experience. They want to know you're in it for the long haul. The best thing you could do is pick a language -- any language -- and work on some opensource project or projects until you graduate. Find a problem people have, and solve it. I don't mean create an app, or do something huge. I mean a small issue. A library that does one thing well. Write it, publish it, and maintain it. Document it. Help people use it.
I feel the first thing to do is find out what you want to do. Frontend, Backend, Fullstack, Dev ops, Cybersecurity, Game dev and the likes. After that you can find out their respective languages to learn.
Hello, I wanna build an e-commerce website for myself and planning to build for others in the future. I really like Node.js, React, ExpressJS. But I don't know if MySQL or MongoDB is what suits me the best because at the moment I have a webhotel at a hosting provider and I like that setup, setting up emails, and having more control I guess over my situation.
But is there any way I can use MongoDB on cPanel or direct admin except using MongoDB Atlas which costs a lot of money?
Because I have a setup using React, Node, Express, and MySQL and it works kind of well when working in the direct admin panel. But I just wanna make sure I make the right decision now when I start building an e-commerce website both to be cost effective and also not have to learn too many things.
I am also open to tips for example choosing Next.js instead etc if that is actually necessary and would help me in the long run.
I think you should use MySQL but with php or Python because e-commerce websites needs to be fast and reliable with more admin tools and you’ll find what you need and more in e-commerce when using php or python frameworks with MySQL database.
Example: Using django (python framework) with MySQL gives you administration dashboard that you can use to edit in a lot of things and django also supports a lot of things like generating ready forms linked to the models you generated
We chose slack for our remote team because of the flexibility, fast product features and Easy integration with my fav startup tools. While pricing is a consideration as a non-bundle item our teams loves Slack. We appreciate the video Sharing tools and all the added integrations. We would chose Slack over teams regardless of budget...........
Its an amazing tool for your startup, integrate firebase with your app and get super useful analytics, you can add your custom events as well, Get authentication done with Firebase with so much ease.
Finally we also used to store some critical configurations, also the firestore for real-time database events.
These keyboard shortcuts that can make your life easier during a call. Press "Ctrl + D" to mute or unmute your microphone and "Ctrl + E" to turn your camera on or off.
I find the Breakout rooms feature very useful too for splitting large groups into smaller ones to help split certain tasks or activities amongst participants. To use this feature, click on the "Activities" button and select "Breakout rooms."
Our main use case for ES/OS is as a storage backend for Graylog. However they stated that they won't offer compatibility beyond Elasticsearch 7.10 and instead will focus on OpenSearch instead, so that's what we did as well. Migration was pretty easy as there is a lot of well written documentation from both Graylog and OpenSearch.
I love dart, even not many people use dart as server side, but it easy and fun to learn than PHP.
so i choose dart with one languange can compile to android, ios, web, and desktop app for windows.
I love dart as well, it is like js but with types. I have more than 15y of PHP, and still like dart.
With hundreds of companies offering virtual meeting services, getting the best app for your video conferencing needs requires you to follow strict criteria. The best web conferencing software varies across organizations depending on the size, niche, pricing, and features required. Therefore, it is essential to understand the different aspects that come with the virtual meeting app you choose. https://zavi.live/
While much of this stack involves complicated platforms that have numerous forms of list making options -which I utilise- sometime you just want to quickly jot down an idea or reminder for yourself and if you're not inside your platform of choice you can ... ok, i can (relatable?) end up following the dopamine to 19 other things and by the time i get to my to do list i've forgotten the idea or reminder that sent me there. SO, enter the bare bones task list!
Todoist is by far the most powerful of the two, and it offers many easy to implement 3rd party integration (notably with Obsidian!) Has a paid option, which of course I need to have if I'm going to use it, so I try not to!
Google Tasks is also a fine choice (it's hard to screw up a todo list, really) especially when paired with TaskBoard (Kanban!). Won't go wrong with it.
I chose Microsoft To Do over them both because it has the simplicity of Google Tasks, with the integrations of Todoist, and when you take a bit of time to configure it, it looks damn pretty.
now, because i rabbit holed this concept hard for months, you can start to really stretch your wings with n8n or Make or, if you like wasting money, Zapier, you can have your quick ideas and reminders from Microsoft To Do Transferred to your higher level planning and productivity apps like Obsidian or ClickUp. I will nerd out about that somewhere on this site, soon. Comment with questions, qualms, quibbles.
Staying on brand, I have 180'd on this decision within a day.
All my points above remain true, but the integration between Obsidian and Todoist is just too smooth not to use. I might set up a sync between To Do and Todoist (pre-made on Make, or easily built in n8n) but for now it's back on the Todoist train for Plains.Digital Inc.
Ember.js is a complete framework for developing frontend applications. Design concerns are addressed neatly and comprehensively, following a lot of time-tested software design principles; everything has its place - models and data access, views and UI stuff, rendering performance, controllers/view-models, routing, development tooling, test support, CI/CD integration. Every common web app architecture problem has a solution with this framework, and the less common problems are solved by packages - which tend to be high quality, and the community tends to agree on which packages to use. Upgrading has been relatively straightforward. Inheriting a code-base developed on this framework is also straightforward because your predecessor didn't invent a novel way of organizing code or pull in dozens of packages that you've never seen before. There's also not a new way of solving problems every year, for things that were settled 5 years ago. Lastly, the framework has had a consistent trajectory for many years with a core group of industry-leading engineers that "own" it because they love it.
A long while ago, GitLab was one of the best git servers with a lot of advanced capabilities, and they grew the feature set ever since. Back in the day, GitLab provided unlimited users compared to 3 users limit in GitHub. For us, this was a life saver, as we are working as part-time organization, which contains both developers and non-developers, at our best, we reached 15 users, spanning over product, web, mobile and other services. So, instead of having the 15 users in GitHub with full price of users for half of us coding, and working like 3 hours a day tops, and 5 days a week, this was an overkill. So, GitLab was the best one to choose at that time.
When Microsoft acquired GitHub, I was skeptical, I though they will ruin the platform (to some degree), and for a while there was no noticeable difference. Well, until they made the service free by lifting the 3-user limit. It did not effect us for a while, as we were using GitLab extensively. Our usages was mainly version control and nothing else, one time for one project, we tried to set up a CI\CD, our first one ever. Even thought we discarded that thought, it was a good experience. We heavily relay on version-control-based features, like forking and branching, tags and milestones, and pull/merge requests but nothing fancy.
When the bad time stormed us for the first time, when GitLab first announced the price change and the 5-user limit per namespace, we planned our migration to GitHub, it was in a critical time, and the situation was dire. So, we decided to breakdown the teams, we were like 8~10 members at that time, and so, we broke the team into 3 smaller teams. One for frontend web, one for backend, and one for mobile. We had 2 people in common in all 3 for redundancy and availability, as we are using other services that require some people to handle the integrations and usages of the other platforms, namely Netlify, CloudFlare, and Laravel Forge. So it worked out well, despite the quick changes.
When another round of price increase came, it killed GitLab in my eyes. The one who stood for open source and challenged GitHub at sometime, is now only seeking revenue at all costs. It does not effect us in any other way apart from splitting the team into 5-or-less members in a namespace, so it does not bring any new damage to us. But morally, we started to favor GitHub over self-hosted GitLab, as we don't know how bad will GitLab turn. In the first round, the price was way too high, with the second, it was just an overkill. So, I thinking GitLab is seeking its death by its own hands, and we will probably jump ships to GitHub or any suitable service when the times comes.
I am out of my league here due to my limited technical knowledge compared to most people on stackshare. I am learning so I will contribute my thoughts in return plus stackshare asks me to add something that I have learned. I owned a good sized Internet candy distributor five years ago and about 8 years ago moved from Bigcommerce because they raised their price from $80.00 to something like $750 with only 2 months advanced notice to pay or leave. The price is fair but I should have been given maybe 6 months notice. I spent a month analyzing and testing other ecommerce solutions then another month finding a developer to help me move.
First, only choose a platform that's complicated like Magento if you can afford a developer to fix bugs and update security. I experienced some horrible developers but in the end found a great honest small shop to help me. Secondly, don't install a new version (in my case Magento 2.0) and stick with the time tester older version (Magento 1.X) until most big bugs are fixed. I know this information is old but not the lesson I learned which is timeless. My guess is Magento still needs to be updated constantly so stick with something like Shopify until your company grows larger.
Even thou Wordpress is an amazing tool, it can get pretty heavy, specially after a lot of Plugins. I came across Astro and found it to be an amazing quick and fast tool for our company's website. It's a static component based framework that makes creation of websites pretty simple and fast. You can also make http requests but, where it shines is that it supports markdown. So creating blog posts, for example, it's super simple to do, you don't need anybody technical to do that and it can be easily deployed through pipelines.
I am currently working on preparing a multi-tenant app with one database per tenant. The app will have data analytics dashboards, CRM, and task management modules. Originally my thoughts were to build with Angular, Laravel, and MySQL, as the development team mainly consists of PHP developers.
However, the team is recommending to develop the app entirely using WordPress by utilizing a multisite model, saying that it will not have any impact on performance even as the user base increases.
My own take is that this will have a negative impact on performance. Can you please advise me if this is true?
WordPress can build the multisite model quickly, it can achieve faster results on a limited budget and time But during business maintenance and refinement after running the first version, WordPress may become a hindrance, also it could get heavier when load more plugin
Laravel needs more code work at the early stage of the project, page build, business logic, and so on, use Laravel will cost more time on the first version But after the first release, the maintenance and refinement will be much better than WordPress
I will advise going with the team in which your team is comfortable with, as you mentioned you have less time. WordPress is a good tool for customize development. Just care about the securities and don't use more than 2-3 plugins. Assign proper resources in terms of Ram and others using custom configurations of PHP and wpconfig. About Restful API it provides you built-in facility which you can us later on for the App developments for mobiles. Wish you good luck with your project.
Visual Studio Code App Crashing on my Gaming Laptop
I am facing an issue with the Visual Studio Code app on my gaming laptop. The app crashes frequently and it is becoming increasingly difficult for me to get any work done. I am hoping to get some advice on how to resolve this issue.
Firstly, let me provide some details about my laptop. It's an Intel Core i7 processor, 16GB RAM, and an NVIDIA GTX 1070 graphics card. I have installed the latest version of Windows 10, and all my drivers are up-to-date.
Now, let's talk about the issue at hand. The Visual Studio Code app crashes randomly while I am working on a project. It doesn't matter if I am working on a small or large project, the app crashes regardless. I have tried to reinstall the app, but that didn't solve the problem.
I have also tried to run the app with administrator privileges, but that didn't help either. I have also checked the task manager to see if any other processes were interfering with the app, but that didn't show any results either.
I am not sure what else to try. Does anyone have any suggestions on how to resolve this issue? I would greatly appreciate any advice.
Thank you in advance for your help.
Best regards, Judy
Try the Insider version (https://code.visualstudio.com/insiders/) with any chances you'll get something that solve the issue you're facing. With the insider you'll get problems faster but you'll also get bug fixes faster. I never faced that issue though so it's hard to tell what's the source of the problem.
I'd recommend going into your Home/My Documents folder, and deleting the ".vscode" folder, and then running VSCode again. Might help!
Search on youtube about it
Visual Studio sucks. Whenever I launch it on my state of the art iMac it starts making noise like Visual Studio has started a Jet Engine. I gave up on Visual Studio. I use Xcode which is far better that VS.
Overall, using Redis, Aurora Postgres, Lambdas written in Golang, and AWS EventBridge allowed us to build a stable and robust system that could easily scale to meet our needs. I highly recommend these technologies to any startup if you have a highly proficient team of developers. And if you are looking to build a reliable, scalable system from the first MVP release, faster and with scale in mind.
Redis was a great choice for our caching layer due to its speed and scalability. It allowed us to cache frequently-accessed data, reducing the load on our database and improving performance.
We chose Aurora Postgres for our database because of its high availability, durability, and scalability. This allowed us to easily scale our database as our data grew, while ensuring that it remained reliable.
Lambdas written in Golang allowed us to easily build serverless, event-driven microservices that could scale up or down based on demand. Golang is a great language for building scalable and lightweight microservices, and Lambda is a perfect fit for running these services in a serverless environment.
Finally, we used AWS EventBridge to manage the events between our microservices, decoupling our system into smaller, more manageable pieces. EventBridge allowed us to easily trigger actions based on events, making our system more responsive and improving performance.
For my next project I'll definitely use functions / serverless lambdas but will give an opportunity to Temporal.io as an alternative to AWS Step-Functions looking for a more robust and faster to grow code base. Temporal.io is a Single stateful service in your entire deck stack that lets everything else be stateless... Which as been one of the main pain points using AWS lambdas a part from the cold starts and few other issues we had to face on this two years learning journey.
As a digital strategist, I've helped many Saas owners, tech founders, and startup owners to get signups on their products. 🚀
In this post, I'm sharing my personal experience and a detailed guide on how to get 450+ upvotes on the Product Hunt launch. 💪
Launch Your Saas Product with a Bang 🔥
Launching a Saas product is a crucial stage, and it can make or break your product's success. Therefore, it's essential to plan your launch strategy carefully.
The first step is to identify your target audience 🎯. Who are the people that would benefit the most from your Saas product?
Once you have identified your target audience, it's time to reach out to them.
Leveraging Twitter for Your Saas 🐦
Twitter is an effective way to reach out to your potential audience. With a massive user base of tech enthusiasts, it's an excellent platform to find your target audience.
I usually start by searching for keywords related to the Saas product, helping me find people who are already interested in my product.
Video Prospecting Made Easy 🎥
Creating a video for video prospecting is a must. I found that personalized videos are the best way to reach out to potential customers. One of the best tools for creating personalized videos is Hify.io. With Hify, I can create 100's of Ai-personalized videos in minutes. 🤖
In the video, I explain the benefits of my Saas product and how it can solve my target audience's problems.
Twitter Outreach 📩
After creating my video, it's time to reach out to my potential audience on Twitter DMs. I send personalized messages to each person and share my video.
This helps me build a relationship with my potential customers and increase my chances of getting signups.
Asking for upvotes on Product Hunt and offering amazing discounts incentivizes potential customers to sign up. People love discounts, and it's an excellent way to get more signups.
Product Hunt is a community of tech enthusiasts, and getting upvotes on Product Hunt can significantly increase your product's visibility.
In conclusion, getting 450+ upvotes on the Product Hunt launch requires a strategic approach. It starts with identifying your target audience, creating a video for video prospecting, reaching out to your potential customers on Twitter DMs, asking for upvotes on Product Hunt, and offering amazing discounts.
By following these steps, you can increase your chances of getting more signups and make your Saas product a success. 🚀
So, if you're planning to launch your Saas product soon, follow these steps, and don't forget to try out https://bit.ly/Hify-io for Ai-personalized video outreach. 💻
Hello everyone, I want to have a project developed similar to the PCPartPicker Website. Various technologies were proposed to me, like WordPress, Laravel, ASP.NET, etc.
Since I don't have the knowledge to evaluate this choice correctly, and since it is fundamental to the success of the project, I wanted to know the community's opinion on the matter.
Obviously, the developers promote the one they know best or which suits them best, so I would need an 'independent' opinion about which one you think would be the best option possibly also considering development costs.
Thank you for your help.
Being a Laravel dev (I've used ASP.net too), I would hands-down recommend Laravel. It's convenient to build on, easy to deploy, and there are plenty of skilled Laravel engineers in almost every country. So if you ever want to bring development 'in-house' or work intermittently with freelancers after you've finished with the agency you're working with, you'll find that quite easy wherever you are.
As has been mentioned, Laravel is very ergonomic for developers and it has an incredible community (mostly filled with really positive people) and ecosystem (lots of ready-to-use open source packages to augment your application with new features).
Development costs for the two I'd expect to be about the same, but possibly the agencies using .net will charge a little more as it has historically commanded a slightly higher price point, but I'm not sure how true that still is.
Both will get the job done perfectly well. Laravel would be my choice.
OK I see, thank you for your advices, from the outside is very difficult to understand which direction to go. But at least now I know that I am not wrong in either case.
I love .NET, and have a bit of experience in Laravel (nothing in production though). I would recommend sticking to Laravel for a project like the one you want to do. It is loved by developers for its elegancy and features. Laravel has incredible ecosystem with many packages available to implement features fast and easy. The development cost will be much less than .NET (PHP developers are cheap).
What about maintenance? It is a different story. PHP doesn't scale as well as other technologies, but it will have no problem handling traffic for a website like that.
>PHP doesn't scale as well as other technologies
PHP is used by Facebook and Wikipedia, which represent a significant proportion of internet traffic. I think it scales just fine. Laravel on top of PHP will be slower, but you should only worry about scale when scale is your problem. There will likely be a lot more interesting problems to solve before scale becomes an issue.
Thank you for your suggestion, I will take it into account. Are there possibly other technologies to consider besides the two mentioned?
Oh yes.. There are almost infinite number of possible tech stack you can choose from. Remember that there will be downsides to all technologies though.
I would recommend looking into React or Svelte for front-end development.
React is more mature and established in the development community. It won't be a problem to find experienced developers.
Svelte is a relatively new one, but is growing fast.
There are a few options for the server side too.
Golang is a new "cool" guy on the block. It is fast and secure, but it's harder too find developers and they cost more.
Python is a great choice for a quick prototype with Flask or Django, but is harder to scale than Golang or Node.
It is hard to recommend something without understanding the set of features that you're aiming for. What UI & UX design will look like? Is it gonna be reactive and highly interactive? What type of user system do you have in mind? How much data do you want to collect? What do you want to do with that data afterwards? Do you have plans for real-time interactions between clients and servers (chat system for example)? Those are only high level question that come to mind right now, but they greatly affect the architecture of the whole project. I can assure you there will be many decisions that you will have to make that will affect the development process.
OK thank you very much, I will try to understand better the technologies you mentioned.
Frontend development is a crucial part of web development, and it has become increasingly important in recent years. The role of frontend developers has evolved to meet the ever-changing demands of the digital landscape. With new frameworks, libraries, and technologies emerging every year, it can be challenging to keep up with the latest trends and best practices.
So, what is the most important thing for frontend developers? While there are many essential skills and qualities that frontend developers should possess, the most crucial aspect of frontend development is user experience.
User experience, commonly abbreviated as UX, refers to the overall experience that a user has when interacting with a website or application. UX is a combination of design, accessibility, and usability, and it plays a critical role in ensuring that users are satisfied with the product.
As a frontend developer, it is essential to keep the user experience in mind when designing and developing web applications. Here are some of the most important aspects of user experience that frontend developers should focus on:
Design The design of a website or application is crucial for user experience. The design should be visually appealing, intuitive, and easy to navigate. The frontend developer should work closely with the designer to ensure that the design is implemented correctly and that it meets the needs of the users.
Accessibility Accessibility refers to the ability of users with disabilities to access and use a website or application. Frontend developers should ensure that their code is accessible to all users, regardless of their abilities. This includes using semantic HTML, providing alternative text for images, and ensuring that the site is navigable using a keyboard.
Performance The performance of a website or application is also critical for user experience. Users expect websites and applications to load quickly and respond to their actions in a timely manner. Frontend developers should optimize their code to ensure that the site loads quickly and that it runs smoothly.
Usability Usability refers to the ease with which users can complete tasks on a website or application. Frontend developers should ensure that their code is easy to use and that users can complete tasks quickly and efficiently. This includes designing intuitive user interfaces and providing clear instructions and feedback.
In conclusion, while there are many important skills and qualities that frontend developers should possess, the most crucial aspect of frontend development is user experience. By focusing on design, accessibility, performance, and usability, frontend developers can ensure that their websites and applications meet the needs of users and provide an excellent user experience. By prioritizing user experience, frontend developers can create websites and applications that are not only visually appealing but also easy to use and navigate, leading to increased user satisfaction and engagement.
If you find someone who is owning above skills, please call me anytime. https://jnarihira.vercel.app Thank you for seeing my first article.
I was exploring OpenAI's API various endpoints and decided I wanted to show and discuss the possibilities with my teammates (I work as a Digital Transformation Consultant). While I tested making the request and receiving the response in Python, I realized if I wanted to make a working, somewhat presentable prototype fast, Python was not a good choice, even if I was proficient in GUI-Development on Python or some other traditional code tool, I would've have to make several decisions and considerations that went far beyond the scope of what I was trying to do (show case the language models available through OpenAI's API). That's why I decided to use a low-code approach.
On the span of an afternoon I was able to quickly put together a friendly GUI that allowed the user to make requests on various endpoints, play around with parameters, and save the responses on a SharePoint list. Am glad to write my team was really impressed and we all had an amazing integration time prompting the models with all sorts of ideas, from making fun stories about consultants to develop highly optimized SQL code to later use with our clients.
Before any technology choice always have a clear scope in mind and keep a laser focus to it.
I'm working on a project that lets users track vehicles from their phones, each of theses vehicles have a device (running android) that sends the gps location and all the required info to a realtime database and then the user that requests to see a vehicle's location gets those info from the mentioned database, what database is best to work with, I'm looking for something that's open source, free and easy to use since I'm fairly new to this 🙂.
I would recommend Firebase for this as it has an amazing SDK with pretty much everything you need out of the box. Depending of how 'realtime' your project needs to be, you can go with Firestore, latency is a bit higher than Realtime DB, but price is much lower. The combination with Node, using CloudFunction, will streamline your process having it all under the same roof.
Hi. I am a backend developer in a company tasked with recoding a legacy application, choosing the right technology stack, and then later hiring for that stack.
This is a freight/logistics/courier application made 15 years ago in PHP with no modern framework used. In this application, customers from different countries login into their accounts and add a huge number of shipments, like let's say 500, and then, later on, generate PDFs for them after calling third-party APIs. This application has API integrations with lots of other companies and also offers API access to its own software as well. This application is also used in-house by warehouse people to scan different shipments using barcode scanners and to process shipments by performing different actions on them. The database being used currently is MySQL.
Now we have the choice to write this application in a modern technology stack. Performance, speed, reliability, and security are the primary concerns here.
Should I go with Java/Spring Boot with Angular2+ as the front end or PHP/Laravel with Vue.js as the front end?
Switching at this point from PHP to Java will not be hard if Java is considered better here because we can hire as per our final decision.
As a Laravel developer, I'd have to say go with Laravel. Although you can move away from PHP, it means any of that legacy code will still need to be completely ported to Java or whatever other language you use. Whereas, staying with PHP, you may find it easier to re-use/adapt that existing code.
Of course, if you're going for a full rewrite, then that might not be a useful consideration. However, even a full rewrite will introduce a lot of changes. When having to do this kind of thing, I recommend changing as few things as possible at once. So staying in the same language while upgrading may keep some pain points down.
Vue.js with PHP/Laravel (vue.js is much better than Angular for building the frontend. I feel much cleaner and faster). you already using MySQL database PHP is prefered.
Are your only choices Java+Angular or PHP+Vue? My recommendation as an engineer with 10 years in a few fortune 50 companies:
(Option 1) React: This will probably be your best bet as it has a huge market share and will be the easiest to hire for. Less opinionated which leads to a billion different libraries to choose from but also potential for bloat when hiring developers that want to use the tools and libraries they know.
(Option 2) Angular: This is also a good option still a decent market share share slightly more difficult to hire for but more suitable for large scale applications as it is more opinionated and more structured, in general, than React is.
(Option 3) Vue: Ive never recommended this before but it is a fine option, will be harder to hire for but not that much, not as mature as the other options but has as solid following.
I typically would never recommend PHP, it used to be a trouble child but in recent years has picked up in quality. Still would recommend lots of other options first but if you want to minimize the amount of refactoring this could still be fine.
Java/Kotlin great options, Java is a mature language that will interface with MySQL with no problems. Should be easy as any to hire for these roles.
Golang is a younger popular Language for building microservices architectures, could be a good option if you want to change the architecture to be more resilient.
Tons of other options here as well C# and .NET, NodeJS with something like NestJS, etc...
Thank you for the detailed answer.
we already have an application running on Angular and have a resource for it also so would be okay to just keep on going with Angular?
Our existing application on PHP has matured over the years and is mostly in maintenance mode. Would you still recommend to rewrite this in Java? Thanks
Angular is a perfectly acceptable option for a front-end framework as Google has committed to consistent LTS (long term support) with 6 month cadence on major releases. For reference I work with VMware on their UI and it is nearly 100% Angular and has worked very well for them.
Regarding backend, if you are in maintenance mode with PHP I dont see any reason you should need to rewrite unless you are unable to fix issues for reasons related to the language. Just remember to keep security updates current and should be fine.
Best of luck
I wanted to use an open-source CMS for this project so that ruled out a lot of options (Contentful, Sanity, Prismic etc...). The only other open-source option I found worth considering was Payload CMS. Since this was my first headless CMS project, I chose Strapi over Payload CMS. Payload CMS is very powerful and flexible but may be TOO flexible and abstracted for my first crack at this. Strapi also seems to have a lot of momentum which is important for open-source projects.
I've been happy with Strapi so far and it's been able to do what I needed. I may try Payload CMS on a future project now that I have some experience.
If possible, can you share what are you using as DB in this case, and how are you planning to use the CMS' features?
I'm using postgres for the db on digital ocean.
One thing I've found as I've gotten farther into this is that there are a few limitations with Strapi on user permissions. For example, I need to be able to set users as owners of specific pages on the site. This is possible but does require writing some code and the solution isn't documented that well. They also need to make some improvements to the wysiwyg editor.
Other than that I'm still happy with Strapi.
Great choice. Using strapi with nextjs in my current project and I must say, I'm really impressed by the two.