Youtube Resource:
AEM Graphql package:
Note - If you are looking for content fragment creation in 6.5 classic, pls check: https://www.youtube.com/watch?v=sftCl5y4GN4&ab_channel=AdobeExperienceManagerUserGroups
Original article: https://www.tothenew.com/blog/aem-with-nextjs-remotespa-a-comprehensive-integration-guide/
Welcome to our comprehensive guide, where we illuminate the process of updating a Remote Single Page Application (SPA) – operating independently of AEM – to seamlessly consume and deliver content authored within Adobe Experience Manager (AEM). Throughout this blog, our focus centers on the local setup of an AEM instance and a Next.js application, as well as the binding necessary to make them work together harmoniously. We will also create a demo component and drop it on the home page, exposing you to working on Remote SPA with AEM.
Step 1: Setup Local AEM Instance
| { | |
| "collections": [ | |
| { | |
| "name": "Favorite Projects", | |
| "repos": ["repo-name-1", "repo-name-2"] | |
| } | |
| ] | |
| } |
| // In Excel make sure to have this option enabled: Home / Clipboard / Options / Collect without showing the Office clipboard | |
| // Tested in Windows 10 only | |
| let table = document.querySelector('#table').outerHTML; | |
| table = table | |
| .replaceAll('\n','<br style="mso-data-placement:same-cell;"/>') // new lines inside html cells => Alt+Enter in Excel | |
| .replaceAll('<td','<td style="vertical-align: top;"'); // align top | |
| navigator.clipboard.writeText(table).then( | |
| ()=>console.log("success"), | |
| (e)=>console.log("error", e), |
Original article: https://www.sammeechward.com/deploying-full-stack-js-to-aws-ec2
Original article: https://www.eficode.com/blog/mastering-devops-with-ai-building-next-level-ci/cd-pipelines
In an era where AI-assisted programming is rapidly evolving, the importance of robust DevOps practices can’t be overstated. In this blog post, I will demonstrate the efficient utilization of AI in building and enhancing CI/CD pipelines, highlighting that while AI brings significant advancements, human expertise remains crucial.
Establishing a solid DevOps foundation is no longer a months-long endeavor. With the right approach and tools, even small projects can and should have proper DevOps in place within days or weeks. Now, let's shift our focus to the foundational aspects of CI/CD, starting with the Git workflow.
Original article: https://blog.neetcode.io/p/doordash-robust-microservices
DoorDash is the largest food delivery marketplace in the US with over 30 million users in 2022. You can use their mobile app or website to order items from restaurants, convenience stores, supermarkets and more.
In 2020, DoorDash migrated from a Python 2 monolith to a microservices architecture. This allowed them to:
Increase developer velocity by having smaller teams that could deploy independently.
Use different tech stacks for different classes of services.
Original Articles:
SSL termination refers to the process of decrypting encrypted traffic before passing it along to a web server.
Approximately 90% of web pages are now encrypted with the SSL (Secure Sockets Layer) protocol and its modern, more secure replacement TLS (Transport Layer Security). This is a positive development in terms of security because it prevents attackers from stealing or tampering with data exchanged between a web browser and a web or application server. But, decrypting all that encrypted traffic takes a lot of computational power—and the more encrypted pages your server needs to decrypt, the larger the burden.
// index.js
const getArgs = () =>
process.argv.reduce((args, arg) => {
// long arg
if (arg.slice(0, 2) === "--") {
const longArg = arg.split("=");
const longArgFlag = longArg[0].slice(2);
const longArgValue = longArg.length > 1 ? longArg[1] : true;
args[longArgFlag] = longArgValue;