[AI HACKATHON TEST - DO NOT MERGE] Files with some metadata - varying degrees #429
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add workflow files for ai metadata generation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Comment on lines
+1
to
+7
| --- | ||
| keywords: | ||
| - Adobe I/O | ||
| - Extensibility | ||
| - API Documentation | ||
| - Developer Tooling | ||
| --- |
There was a problem hiding this comment.
Suggested change
| --- | |
| keywords: | |
| - Adobe I/O | |
| - Extensibility | |
| - API Documentation | |
| - Developer Tooling | |
| --- | |
| --- | |
| title: Developer Community | |
| description: Join the global Developer Community to collaborate, contribute, and build innovative apps and extensions for Adobe Experience Platform and Adobe Experience Cloud. | |
| keywords: | |
| - Adobe I/O | |
| - Extensibility | |
| - API Documentation | |
| - Developer Tooling | |
| - App Builder | |
| faqs: | |
| - question: How can I join the Adobe Developer Community? | |
| answer: You can join by participating in the App Builder Developer Community on Experience League, where you can network, ask questions, and collaborate with other developers. | |
| - question: What contributions can I make to Adobe open-source projects? | |
| answer: Developers can contribute by submitting issues and pull requests to Adobe’s open-source repositories such as the CLI, SDK, App Builder, and I/O Runtime. | |
| - question: What guidelines should I follow when contributing? | |
| answer: Contributors must adhere to Adobe’s Code of Conduct and contribution guidelines to ensure a respectful and productive environment for everyone. | |
| --- |
Comment on lines
+1
to
+3
| --- | ||
| title: Creating your First App Builder Application | ||
| --- |
There was a problem hiding this comment.
Suggested change
| --- | |
| title: Creating your First App Builder Application | |
| --- | |
| --- | |
| title: Creating your First App Builder Application | |
| description: This tutorial guides you through setting up, developing, and deploying your first App Builder Application using Adobe Developer Console and CLI tools. | |
| keywords: | |
| - App Builder Application | |
| - Adobe Developer Console | |
| - Adobe I/O Runtime | |
| - CLI App Bootstrap | |
| - Extension Points | |
| faqs: | |
| - question: What is the first step to create an App Builder application? | |
| answer: The first step is to set up your local environment and ensure you have access to App Builder as described in the getting access documentation. | |
| - question: How do I create a new project in Adobe Developer Console? | |
| answer: You create a new project by signing into the Adobe Developer Console, selecting your IMS Org, and creating a project from the App Builder template. | |
| - question: What is the purpose of workspaces in an App Builder project? | |
| answer: Workspaces manage different deployment environments and provide isolated environments for each developer to connect services and credentials independently. | |
| - question: How do I sign in to Adobe Developer Console from the CLI? | |
| answer: Use the command `aio login` in your terminal to open a browser for Adobe ID sign-in; the CLI stores the resulting user token for authentication. | |
| - question: Can I customize which extension points to include when initializing an app using the CLI? | |
| answer: Yes, during app initialization with `aio app init`, the CLI prompts you to select desired extension points to implement in your project. | |
| --- |
| @@ -0,0 +1,26 @@ | |||
| # Getting Started with App Builder | |||
There was a problem hiding this comment.
Suggested change
| # Getting Started with App Builder | |
| --- | |
| title: Getting Started with App Builder | |
| description: This guide provides an introduction to getting started with App Builder and Adobe I/O Runtime, including setup, creating applications, and troubleshooting. Learn how to develop serverless applications and explore further resources for advanced features. | |
| keywords: | |
| - App Builder guide | |
| - Adobe I/O Runtime | |
| - serverless development | |
| - application publishing | |
| - development environment setup | |
| faqs: | |
| - question: How do I start using App Builder for the first time? | |
| answer: Begin with the App Builder Getting Started guide, which walks you through setting up your development environment, creating your first app, publishing it, and troubleshooting common issues. | |
| - question: What is Adobe I/O Runtime and how does it relate to App Builder? | |
| answer: Adobe I/O Runtime is a serverless platform used by App Builder to deploy and run actions. The Runtime Getting Started guide explains its fundamentals, environment setup, and deployment processes. | |
| - question: Where can I find more advanced information after completing the getting started guides? | |
| answer: After finishing the initial guides, you can explore the detailed Guides section for in-depth features and visit the Resources section for additional support and materials. | |
| --- | |
| # Getting Started with App Builder |
Comment on lines
+1
to
+5
| --- | ||
| contributors: | ||
| - 'https://github.com/duynguyen' | ||
| title: Codelab Environment Requirements | ||
| --- |
There was a problem hiding this comment.
Suggested change
| --- | |
| contributors: | |
| - 'https://github.com/duynguyen' | |
| title: Codelab Environment Requirements | |
| --- | |
| --- | |
| contributors: | |
| - 'https://github.com/duynguyen' | |
| title: Code Lab Environment Setup and Requirements | |
| description: This document outlines the environment requirements and deployment instructions for using the alarms package within the Adobe I/O Runtime environment. | |
| keywords: | |
| - Adobe I/O Runtime | |
| - alarms package | |
| - aio app deploy | |
| - OpenWhisk deployment | |
| - Code Lab environment | |
| faqs: | |
| - question: Why can't I use the alarms package with the local standalone OpenWhisk deployment? | |
| answer: The alarms package is only supported in the Adobe I/O Runtime environment, so it won’t work with local OpenWhisk deployments that use `aio app run --local`. | |
| - question: How do I deploy my app to use the alarms package properly? | |
| answer: You need to deploy or run your app using the commands `aio app run` or `aio app deploy` within the Adobe I/O Runtime environment to ensure the alarms package functions correctly. | |
| --- |
Comment on lines
+1
to
+4
| --- | ||
| title: Set Up Access, Environment, and Tools | ||
| description: App Builder is a complete framework that enables enterprise developers to build and deploy custom web applications that extend Adobe Experience Cloud solutions and run on Adobe infrastructure. | ||
| --- |
There was a problem hiding this comment.
Suggested change
| --- | |
| title: Set Up Access, Environment, and Tools | |
| description: App Builder is a complete framework that enables enterprise developers to build and deploy custom web applications that extend Adobe Experience Cloud solutions and run on Adobe infrastructure. | |
| --- | |
| --- | |
| title: Set Up Access, Environment, and Tools | |
| description: App Builder is a complete framework that enables enterprise developers to build and deploy custom web applications that extend Adobe Experience Cloud solutions and run on Adobe infrastructure. | |
| keywords: | |
| - Adobe Experience Cloud | |
| - App Builder setup | |
| - Adobe I/O CLI | |
| - NodeJS environment | |
| - Developer tools | |
| faqs: | |
| - question: What access do I need to start using App Builder? | |
| answer: You need membership in an Adobe Experience Cloud IMS organization with a Developer or System Admin role and a purchased license for App Builder. | |
| - question: Which NodeJS versions are recommended for App Builder development? | |
| answer: NodeJS versions 18 or 20 are recommended, while odd versions are not advised for compatibility reasons. | |
| - question: How do I keep the Adobe I/O CLI up to date? | |
| answer: Check your CLI version with `aio -v` and update it using `npm install -g @adobe/aio-cli` if outdated. Run `aio update` regularly to update plugins. | |
| - question: Is a GitHub account required for App Builder? | |
| answer: A GitHub account is optional but highly recommended for setting up CI/CD workflows and managing your code. | |
| - question: What development environments and terminals are supported? | |
| answer: Windows 10 and 11, and MacOS 10.14+ are supported environments. The Adobe I/O CLI terminals use the inquirer package and work on multiple platforms including Linux Xenial. | |
| --- |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.