move to acmestack (#12)

* move to acmestack

* update logo

Author: qicz

.github/ISSUE_TEMPLATE/config.yml

@@ -1,4 +1,4 @@
 contact_links:
   - name: Question 🙋
-    url: https://github.com/openingo/openingo-website/discussions/categories/q-a
-    about: Ask your question in OpeningO Discussions
+    url: https://github.com/acmestack/acmestack-website/discussions/categories/q-a
+    about: Ask your question in AcmeStack Discussions

.github/ISSUE_TEMPLATE/feature-request---.md

@@ -1,6 +1,6 @@
 ---
 name: "Feature request \U0001F680"
-about: Suggest an idea for OpeninGO
+about: Suggest an idea for AcmeStack
 
 ---
 

.github/pull_request_template.md

@@ -12,7 +12,7 @@ Why are we doing this? What use cases does it support? What is the expected outc
 
 ## Checks
 
-- [ ] Read [Create a Pull Request](https://openingo.org/docs/contributing-guide)
+- [ ] Read [Create a Pull Request](https://acmestack.org/docs/contributing-guide)
 - [ ] Supports all screen sizes (if relevant)
 - [ ] Supports both light and dark mode (if relevant)
 - [ ] Passes `npm run test`

.github/workflows/cla.yaml

@@ -19,13 +19,13 @@ jobs:
           PERSONAL_ACCESS_TOKEN : ${{ secrets.PERSONAL_ACCESS_TOKEN }}
         with:
           path-to-signatures: 'signatures/version1/cla.json'
-          path-to-document: 'https://github.com/openingo/.github/blob/main/OpeninGO-CLA.md' # e.g. a CLA or a DCO document
+          path-to-document: 'https://github.com/acmestack/.github/blob/main/AcmeStack-CLA.md' # e.g. a CLA or a DCO document
           # branch should not be protected
           branch: 'cla'
           allowlist: bot*
 
          #below are the optional inputs - If the optional inputs are not given, then default values will be taken
-          #remote-organization-name: openingo #enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository)
+          #remote-organization-name: acmestack #enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository)
           #remote-repository-name: cla # enter the  remote repository name where the signatures should be stored (Default is storing the signatures in the same repository)
           #create-file-commit-message: 'For example: Creating file for storing CLA Signatures'
           #signed-commit-message: 'For example: $contributorName has signed the CLA in #$pullRequestNo'

README.md

@@ -1 +1 @@
-# OpeninGO WebSite
+# AcmeStack WebSite

SECURITY.md

@@ -1,6 +1,6 @@
 # Reporting Security Issues
 
-The OpeninGO team and community take security issues in OpeninGO seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
+The AcmeStack team and community take security issues in AcmeStack seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
 
 To report a security issue, email [[email protected]](mailto:[email protected]) and include the word "SECURITY" in the subject line.
 

config/_default/config.toml

@@ -1,4 +1,4 @@
-baseurl = "https://openingo.org/"
+baseurl = "https://acmestack.org/"
 canonifyURLs = false
 disableAliases = true
 disableHugoGeneratorInject = true

config/_default/menus/menus.en.toml

@@ -23,7 +23,7 @@
 [[social]]
   name = "GitHub"
   pre = "<svg xmlns=\"http://www.w3.org/2000/svg\" width=\"20\" height=\"20\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\" class=\"feather feather-github\"><path d=\"M9 19c-5 1.5-5-2.5-7-3m14 6v-3.87a3.37 3.37 0 0 0-.94-2.61c3.14-.35 6.44-1.54 6.44-7A5.44 5.44 0 0 0 20 4.77 5.07 5.07 0 0 0 19.91 1S18.73.65 16 2.48a13.38 13.38 0 0 0-7 0C6.27.65 5.09 1 5.09 1A5.07 5.07 0 0 0 5 4.77a5.44 5.44 0 0 0-1.5 3.78c0 5.42 3.3 6.61 6.44 7A3.37 3.37 0 0 0 9 18.13V22\"></path></svg>"
-  url = "https://github.com/openingo"
+  url = "https://github.com/acmestack"
   post = "v0.1.0"
   weight = 10
 

config/_default/menus/menus.zh.toml

@@ -23,7 +23,7 @@
 [[social]]
   name = "GitHub"
   pre = "<svg xmlns=\"http://www.w3.org/2000/svg\" width=\"20\" height=\"20\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\" class=\"feather feather-github\"><path d=\"M9 19c-5 1.5-5-2.5-7-3m14 6v-3.87a3.37 3.37 0 0 0-.94-2.61c3.14-.35 6.44-1.54 6.44-7A5.44 5.44 0 0 0 20 4.77 5.07 5.07 0 0 0 19.91 1S18.73.65 16 2.48a13.38 13.38 0 0 0-7 0C6.27.65 5.09 1 5.09 1A5.07 5.07 0 0 0 5 4.77a5.44 5.44 0 0 0-1.5 3.78c0 5.42 3.3 6.61 6.44 7A3.37 3.37 0 0 0 9 18.13V22\"></path></svg>"
-  url = "https://github.com/openingo"
+  url = "https://github.com/acmestack"
   post = "v0.1.0"
   weight = 10
 

config/_default/params.toml

@@ -1,7 +1,7 @@
 # Meta Data for SEO
 
 ## Homepage
-title = "OpeninGO"
+title = "AcmeStack"
 titleSeparator = "-"
 titleAddition = "Opening Technology Observer"
 description = "We pay attention and research on computer open source technology, and aim to use open source to give back to open source."
@@ -10,26 +10,26 @@ description = "We pay attention and research on computer open source technology,
 docsVersion = "v0.0.1"
 
 ## Open Graph
-images = ["openingo.png"]
+images = ["acmestack.png"]
 ogLocale = "zh_CN"
-domainTLD = "openingo.org"
-titleHome = "OpeninGO Community"
+domainTLD = "acmestack.org"
+titleHome = "AcmeStack Community"
 
 ## JSON-LD
 # schemaType = "Person"
 schemaType = "Organization"
-schemaName = "OpeninGO"
+schemaName = "AcmeStack"
 schemaAuthor = "qicz"
-schemaAuthorGitHub = "https://github.com/openingo"
+schemaAuthorGitHub = "https://github.com/acmestack"
 schemaLocale = "en-US"
-schemaLogo = "openingo-logo.png"
+schemaLogo = "acmestack-logo.png"
 schemaLogoWidth = 512
 schemaLogoHeight = 512
-schemaImage = "openingo.png"
+schemaImage = "acmestack.png"
 schemaImageWidth = 1280
 schemaImageHeight = 640
 schemaLinkedIn = ""
-schemaGitHub = "https://github.com/openingo"
+schemaGitHub = "https://github.com/acmestack"
 schemaSection = "blog"
 
 ## Sitelinks Search Box
@@ -47,10 +47,10 @@ lqipWidth = "20x"
 smallLimit = "300"
 
 # Footer
-footer = "<center>Copyright © 2013-2022 <a class=\"text-muted\" href=\"https://openingo.org/\">OpeninGO</a> All rights reserved.</center>"
+footer = "<center>Copyright © 2013-2022 <a class=\"text-muted\" href=\"https://acmestack.org/\">AcmeStack</a> All rights reserved.</center>"
 
 # Feed
-copyRight = "Copyright (c) 2013-2022 OpeninGO All rights reserved."
+copyRight = "Copyright (c) 2013-2022 AcmeStack All rights reserved."
 
 # Alert
 alert = false
@@ -61,7 +61,7 @@ alertText = "We pay attention and research on computer open source technology, a
 # repoHost [Github | Gitea | GitLab | Bitbucket | BitbucketServer ] is used for building the edit link based on git hoster
 repoHost = "GitHub"
 #repoHost = "Gitea"
-docsRepo = "https://github.com/openingo/openingo-website"
+docsRepo = "https://github.com/acmestack/acmestack-website"
 docsRepoBranch = "main"
 docsRepoSubPath = ""
 editPage = true

content/en/_index.md

@@ -1,5 +1,5 @@
 ---
-title : "OpeninGO"
+title : "AcmeStack"
 description: "We pay attention and research on computer open source technology, and aim to use open source to give back to open source."
 lead: "We pay attention and research on computer open source technology, and aim to use open source to give back to open source."
 date: 2020-10-06T08:47:36+00:00

content/en/docs/_index.md

@@ -1,6 +1,6 @@
 ---
 title : "Docs"
-description: "OpeninGO Docs."
+description: "AcmeStack Docs."
 lead: ""
 date: 2020-10-06T08:48:23+00:00
 lastmod: 2020-10-06T08:48:23+00:00

content/en/docs/contributing/developer-environment-setting/index.md

@@ -20,7 +20,7 @@ toc: true
 > Copy all with format
 
 ```
-Copyright (c) $today.year, OpeningO
+Copyright (c) $today.year, AcmeStack
 All rights reserved.
 
 Licensed under the Apache License, Version 2.0 (the "License");

content/en/docs/contributing/github-workflow-guide.md

@@ -15,7 +15,7 @@ toc: true
 
 ## 1. Fork in the cloud
 
-1. Visit https://github.com/openingo
+1. Visit https://github.com/acmestack
 2. Choose one project
 2. Click `Fork` button (top right) to establish a cloud-based fork.
 
@@ -31,7 +31,7 @@ toc: true
 ## 3. Set remote repository to sync updates
 
   ```sh
-  git remote add upstream https://github.com/openingo/{project-name}.git
+  git remote add upstream https://github.com/acmestack/{project-name}.git
   ```
 
 ### Keep your branch in sync

content/en/docs/contributing/guide.md

@@ -1,7 +1,7 @@
 ---
 title: "Contributor Guide"
-description: "the OpeninGO contributor guide."
-lead: "the OpeninGO contributor guide."
+description: "the AcmeStack contributor guide."
+lead: "the AcmeStack contributor guide."
 date: 2020-10-06T08:49:31+00:00
 lastmod: 2020-10-06T08:49:31+00:00
 draft: false

content/en/docs/contributing/pull-requests.md

@@ -1,8 +1,8 @@
 ---
 title: "Pull Request Process"
-description: "This doc explains the process and best practices for submitting a pull request to the OpeninGO project and its associated sub-repositories. 
+description: "This doc explains the process and best practices for submitting a pull request to the AcmeStack project and its associated sub-repositories. 
 It should serve as a reference for all contributors, and be useful especially to new and infrequent submitters."
-lead: "This doc explains the process and best practices for submitting a pull request to the OpeninGO project and its associated sub-repositories. 
+lead: "This doc explains the process and best practices for submitting a pull request to the AcmeStack project and its associated sub-repositories. 
 It should serve as a reference for all contributors, and be useful especially to new and infrequent submitters."
 date: 2020-10-06T08:49:31+00:00
 lastmod: 2020-10-06T08:49:31+00:00
@@ -101,9 +101,9 @@ Read on to learn more about how to get faster reviews by following best practice
 
 # Best Practices for Faster Reviews
 
-Most of this section is not specific to OpeninGO, but it's good to keep these best practices in mind when you're making a pull request.
+Most of this section is not specific to AcmeStack, but it's good to keep these best practices in mind when you're making a pull request.
 
-You've just had a brilliant idea on how to make OpeninGO better.
+You've just had a brilliant idea on how to make AcmeStack better.
 Let's call that idea Feature-X.
 Feature-X is not even that complicated.
 You have a pretty good idea of how to implement it.
@@ -154,7 +154,7 @@ A pull request with 25 commits is still very cumbersome to review, so use your b
 Or, going back to our prefactoring example, you could also fork a new branch, do the prefactoring there and send a pull request for that.
 If you can extract whole ideas from your pull request and send those as pull requests of their own, you can avoid the painful problem of continually rebasing.
 
-OpeninGO is a fast-moving codebase - lock in your changes ASAP with your small pull request, and make merges be someone else's problem.
+AcmeStack is a fast-moving codebase - lock in your changes ASAP with your small pull request, and make merges be someone else's problem.
 
 Multiple small pull requests are often better than multiple commits.
 Don't worry about flooding us with pull requests. We'd rather have 100 small,obvious pull requests than 10 unreviewable monoliths.
@@ -293,7 +293,7 @@ Wrapping the width at 72 characters ensures the body text will be centered and e
 
 You can provide additional context with fewer characters by prefixing your
 commit message with the [kind] or [area] that your PR is impacting.
-These are commonly used labels that other members of the OpeninGO community will
+These are commonly used labels that other members of the AcmeStack community will
 understand.
 
 **Examples:**

content/en/docs/contributing/testing-guide.md

@@ -1,7 +1,7 @@
 ---
 title: "Testing Guide"
-description: "the OpeninGO testing guide."
-lead: "the OpeninGO testing guide."
+description: "the AcmeStack testing guide."
+lead: "the AcmeStack testing guide."
 date: 2020-10-06T08:49:31+00:00
 lastmod: 2020-10-06T08:49:31+00:00
 draft: false

content/en/news/_index.md

@@ -1,6 +1,6 @@
 ---
 title: "News"
-description: "The OpeninGO News."
+description: "The AcmeStack News."
 date: 2020-10-06T08:49:55+00:00
 lastmod: 2020-10-06T08:49:55+00:00
 draft: false

content/en/news/weclome/index.md

@@ -1,7 +1,7 @@
 ---
 title: "Welcome👋"
-description: "Introducing OpeninGO"
-lead: "Introducing OpeninGO"
+description: "Introducing AcmeStack"
+lead: "Introducing AcmeStack"
 date: 2020-11-04T09:19:42+01:00
 lastmod: 2020-11-04T09:19:42+01:00
 draft: false

content/en/released/_index.md

@@ -1,6 +1,6 @@
 ---
 title : "Released"
-description: "OpeninGO Released."
+description: "AcmeStack Released."
 lead: ""
 date: 2020-10-06T08:48:23+00:00
 lastmod: 2020-10-06T08:48:23+00:00

content/en/released/v0.0.1/_index.md

@@ -1,6 +1,6 @@
 ---
 title : "v0.0.1"
-description: "OpeninGO Docs v0.0.1."
+description: "AcmeStack Docs v0.0.1."
 lead: ""
 date: 2020-10-06T08:48:23+00:00
 lastmod: 2020-10-06T08:48:23+00:00

content/en/released/v0.0.1/contributing/developer-environment-setting/index.md

@@ -20,7 +20,7 @@ toc: true
 > Copy all with format
 
 ```
-Copyright (c) $today.year, OpeningO
+Copyright (c) $today.year, AcmeStack
 All rights reserved.
 
 Licensed under the Apache License, Version 2.0 (the "License");

content/en/released/v0.0.1/contributing/github-workflow-guide.md

@@ -15,7 +15,7 @@ toc: true
 
 ## 1. Fork in the cloud
 
-1. Visit https://github.com/openingo
+1. Visit https://github.com/acmestack
 2. Choose one project
 2. Click `Fork` button (top right) to establish a cloud-based fork.
 
@@ -31,7 +31,7 @@ toc: true
 ## 3. Set remote repository to sync updates
 
   ```sh
-  git remote add upstream https://github.com/openingo/{project-name}.git
+  git remote add upstream https://github.com/acmestack/{project-name}.git
   ```
 
 ### Keep your branch in sync

content/en/released/v0.0.1/contributing/guide.md

@@ -1,7 +1,7 @@
 ---
 title: "Contributor Guide"
-description: "the OpeninGO contributor guide."
-lead: "the OpeninGO contributor guide."
+description: "the AcmeStack contributor guide."
+lead: "the AcmeStack contributor guide."
 date: 2020-10-06T08:49:31+00:00
 lastmod: 2020-10-06T08:49:31+00:00
 draft: false

content/en/released/v0.0.1/contributing/pull-requests.md

@@ -1,8 +1,8 @@
 ---
 title: "Pull Request Process"
-description: "This doc explains the process and best practices for submitting a pull request to the OpeninGO project and its associated sub-repositories. 
+description: "This doc explains the process and best practices for submitting a pull request to the AcmeStack project and its associated sub-repositories. 
 It should serve as a reference for all contributors, and be useful especially to new and infrequent submitters."
-lead: "This doc explains the process and best practices for submitting a pull request to the OpeninGO project and its associated sub-repositories. 
+lead: "This doc explains the process and best practices for submitting a pull request to the AcmeStack project and its associated sub-repositories. 
 It should serve as a reference for all contributors, and be useful especially to new and infrequent submitters."
 date: 2020-10-06T08:49:31+00:00
 lastmod: 2020-10-06T08:49:31+00:00
@@ -101,9 +101,9 @@ Read on to learn more about how to get faster reviews by following best practice
 
 # Best Practices for Faster Reviews
 
-Most of this section is not specific to OpeninGO, but it's good to keep these best practices in mind when you're making a pull request.
+Most of this section is not specific to AcmeStack, but it's good to keep these best practices in mind when you're making a pull request.
 
-You've just had a brilliant idea on how to make OpeninGO better.
+You've just had a brilliant idea on how to make AcmeStack better.
 Let's call that idea Feature-X.
 Feature-X is not even that complicated.
 You have a pretty good idea of how to implement it.
@@ -154,7 +154,7 @@ A pull request with 25 commits is still very cumbersome to review, so use your b
 Or, going back to our prefactoring example, you could also fork a new branch, do the prefactoring there and send a pull request for that.
 If you can extract whole ideas from your pull request and send those as pull requests of their own, you can avoid the painful problem of continually rebasing.
 
-OpeninGO is a fast-moving codebase - lock in your changes ASAP with your small pull request, and make merges be someone else's problem.
+AcmeStack is a fast-moving codebase - lock in your changes ASAP with your small pull request, and make merges be someone else's problem.
 
 Multiple small pull requests are often better than multiple commits.
 Don't worry about flooding us with pull requests. We'd rather have 100 small,obvious pull requests than 10 unreviewable monoliths.
@@ -293,7 +293,7 @@ Wrapping the width at 72 characters ensures the body text will be centered and e
 
 You can provide additional context with fewer characters by prefixing your
 commit message with the [kind] or [area] that your PR is impacting.
-These are commonly used labels that other members of the OpeninGO community will
+These are commonly used labels that other members of the AcmeStack community will
 understand.
 
 **Examples:**

content/en/released/v0.0.1/contributing/testing-guide.md

@@ -1,7 +1,7 @@
 ---
 title: "Testing Guide"
-description: "the OpeninGO testing guide."
-lead: "the OpeninGO testing guide."
+description: "the AcmeStack testing guide."
+lead: "the AcmeStack testing guide."
 date: 2020-10-06T08:49:31+00:00
 lastmod: 2020-10-06T08:49:31+00:00
 draft: false

content/en/versions.md

@@ -1,7 +1,7 @@
 ---
 title: "Versions"
 description: ""
-lead: "An appendix of hosted documentation for nearly every release of OpeninGO."
+lead: "An appendix of hosted documentation for nearly every release of AcmeStack."
 date: 2021-09-24T08:50:23+02:00
 lastmod: 2021-09-24T08:50:23+02:00
 draft: false

content/zh/_index.md

@@ -1,5 +1,5 @@
 ---
-title : "OpeninGO"
+title : "AcmeStack"
 description: "We pay attention and research on computer open source technology, and aim to use open source to give back to open source."
 lead: "We pay attention and research on computer open source technology, and aim to use open source to give back to open source."
 date: 2020-10-06T08:47:36+00:00

content/zh/docs/_index.md

@@ -1,6 +1,6 @@
 ---
 title : "Docs"
-description: "OpeninGO Docs."
+description: "AcmeStack Docs."
 lead: ""
 date: 2020-10-06T08:48:23+00:00
 lastmod: 2020-10-06T08:48:23+00:00