Kick off your project with this default boilerplate. This starter ships with the main Gatsby configuration files you might need to get up and running blazing fast with the blazing fast app generator for React.

Have another more specific idea? You may want to check out our vibrant collection of official and community-created starters.

1. Create a Gatsby site.

   Use the Gatsby CLI (install instructions) to create a new site, specifying the default starter.

   # create a new Gatsby site using the default starter
   gatsby new my-default-starter https://github.com/gatsbyjs/gatsby-starter-default

2. Start developing.

   Navigate into your new site’s directory and start it up.

   cd my-default-starter/
   gatsby develop

3. Open the source code and start editing!

   Your site is now running at http://localhost:8000!

   Note: You’ll also see a second link: http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby Tutorial.

   Open the my-default-starter directory in your code editor of choice and edit src/pages/index.js. Save your changes and the browser will update in real time!

Deploy this starter with one click on Gatsby Cloud:

A quick look at the top-level files and directories you’ll see in a Gatsby project.

.
├── node_modules
├── src
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md

1. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.

2. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for “source code”.

3. .gitignore: This file tells git which files it should not track / not maintain a version history for.

4. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.

5. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.

6. gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).

7. gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.

8. gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.

9. LICENSE: This Gatsby starter is licensed under the 0BSD license. This means that you can see this file as a placeholder and replace it with your own license.

10. package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).

11. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.

12. README.md: A text file containing useful reference information about your project.

Looking for more guidance? Full documentation for Gatsby lives on the website. Here are some places to start:

• For most developers, we recommend starting with our in-depth tutorial for creating a site with Gatsby. It starts with zero assumptions about your level of ability and walks through every step of the process.

• To dive straight into code samples, head to our documentation. In particular, check out the Guides, API Reference, and Advanced Tutorials sections in the sidebar.

Build, Deploy, and Host On The Only Cloud Built For Gatsby

Gatsby Cloud is an end-to-end cloud platform specifically built for the Gatsby framework that combines a modern developer experience with an optimized, global edge network.

Stubby is a project that aims to explore and experiment with UEFI firmware and its features. It is based on another one of my projects called newt_stub.

• Stubby can boot from UEFI and print some basic information on the screen.
• Stubby can interact with UEFI protocols and services, such as memory allocation, file system access, and graphics output.
• Stubby can load and execute other EFI applications, such as the shell or the bootloader.

• Linux, macOS or WSL
• A Rust compiler and cargo toolchain.
• A QEMU emulator and OVMF firmware.
• A GNU Make¹ utility.

To build and run stubby, use the following command:

make run-debug

This will compile the stubby binary, create a virtual disk image² with the EFI application, and launch QEMU with OVMF.

To clean up the generated files, use the following command:

make clean

Stubby is licensed under the MIT license. See the LICENSE file for more details.

Phalcon meta tags plugin for PhalconPHP.

This plugin allows you to easily and flexibly customize the meta tags of your view.

If this plugin helped you, be glad to see your star, thank you.

Check out new validation package for PhalconPHP
https://github.com/izica/phalcon-validation

• Install
• Plugin functions
• Usage
  • Register plugin as service
  • Add data to your layout
  • Use service in controller, view or middleware(anywhere)
  • Example of output

    composer require izica/phalcon-meta-tags

    setTitle($title)
    getTitle()
    setByProperty($property, $content)
    unsetByProperty($properties) //array or single property name

    setByName($name, $content)
    unsetByName($properties) //array or single name

    setCustom($key, $attributes) //unique key and attributes array
    unsetCustom($keys) //array or single value
    getMeta() // return metas string

    $di = new DI();
    $di->set('metatag', function() {
    	return new IzicaMetaTags();
    });

    <!DOCTYPE html>
    <html>
        <head>
            <?php echo $this->metatag->getTitle();?>
            <?php echo $this->metatag->getMeta();?>
        </head>
        <body>
             <?php echo $this->getContent(); ?>
        </body>
    </html>

    use Phalcon\Mvc\Controller;

    class IndexController extends Controller
    {
        public function indexAction()
        {
            $this->metatag->setTitle("Phalcon MetaTags Service");

            $this->metatag->setCustom("charset", ['charset' => 'UTF-8']);
            $this->metatag->setCustom("http", ['http-equiv' => 'content-type', 'content' => 'text/html; charset=UTF-8']);

            $this->metatag->setByName("description", "phalcon php metatags");

            $this->metatag->setByProperty("og:description", "When Great Minds Don’t Think Alike");
        }
    }

    <title>Phalcon MetaTags Service</title>        
    <meta name="description" content="phalcon php metatags">
    <meta property="og:description" content="When Great Minds Don’t Think Alike">
    <meta charset="UTF-8">
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">  

Winform Progress Trackers

My main design paradigm for this project, is to try and minimize the re-drawing of the objects as much as possible. i.e. use existing windows objects to control placement, Font usage, spacing, and only recreate images if a control re-size happens.

This project is going to take the useful indicators that are becoming common place on the web, and make them into dynamic controls for use in C# Winfom controls.

It will (eventually) have demo projects showing usage; and a simple HowTo to extend projects like MBG.SimpleWizard to create easy to re-use controls for wizard steps, which will then auto populate (And hence progress) the Tracker as a single entity.

So here is a picture of a test App:

It is showing that progress has got to what is called “Page2b”, and it’s style has a border (The other pages did not) and it has a few Winform objects on it that are responding to mouse over.

The node name is derived from the Pages name, and the initialisation (or override) is all done in the parent form that hosts the Wizard tracker.

This project has been archived. A complete rewrite and massive upgrade of this project is now available at Matrix OS.

本项目已重构，新项目在Matrix OS.

Jamstack (MPA-SSG) app for an wildlife welfare/charity organization that helps endangered species by educating the community, and running various volunteering programs. While layouts, pages & components are primarily Vue SFCs, the project also includes svelte and jsx/tsx components. Note: Iles supports component formats of multiple frameworks.

This is a sample project created using the Vue Designer Iles Tailwind CSS – Quick start template.

Demo – https://spotted-kingfisher-iles-tailwindcss.netlify.app/

A desktop visual editor for Vue apps supporting Mac, Windows, and Linux by Pinegrow. Take it for a free trial at Vue Designer!

It lets you visually design 🎨 your Vue single file components and boosts your productivity and creativity while building your component-based Vue apps.

It smartly integrates with your ⚡️ Vite based CLI and provides an amazing developer experience with its powerful visual controls and features.

Clean code 😃, No lock-in – You are in control of your projects and development workflow ❤️

Create a repo from this template on GitHub.

(or)

If you prefer to do it manually with the cleaner git history

npx giget@latest gh:pinegrow/spotted-kingfisher-with-iles-tailwindcss my-spotted-kingfisher-with-iles-tailwindcss-app #project-name
cd my-spotted-kingfisher-with-iles-tailwindcss-app
npm install #or use pnpm

Open your project in Vue Designer and follow the instructions displayed in the Config Panel (that should pop out automatically). Config Panel ⚙️ displays the key packages and the various links to their individual ecosystems and communities.

npm run dev # SPA during development

npm run build # MPA SSG (islands architecture)

Uncomment the rollup-plugin-visualizer usage in your config file and execute the build command. This command will generate stats.html. Open stats.html in your browser to analyze bundle sizes.

npm run build # open stats.html to analyze bundle sizes

npm run now # build & preview

npm run unlighthouse # Uses npx unlighthouse from https://unlighthouse.dev/ to run lighthouse on entire site (all pages)

You can deploy this repo as a site on your own to explore and experiment with, by clicking this button.

Check out the deployment documentation for more information.

• îles – A Joyful Site Generator.
  • 🏝 [Partial Hydration] – zero JS by default, hydrates the interactive bits
  • 🔌 [Batteries Included] – layouts, components, site-wide data
  • 🧱 [Multi-Framework] – vue, preact, svelte, solid
  • 📖 [Markdown] – use components in markdown and viceversa
  • 🛣 [Routing] – automatically configured from files
  • 🛠 [Devtools][devtools] – debug panel and [hydration timeline]
  • ⚡️ [Fast][vite] – instant reloading powered by [Vite]

• Tailwind CSS – The amazing utility-first CSS framework.

• @islands/mdx – file-based CMS powered by Markdown & Vue components. This module is shipped inside îles. Note: This page is a markdown file 🗒.
• @islands/prism – an îles module that injects a remark plugin to provide syntax highlighting for MDX documents.

• UnoCSS Preset Icons – use over 100,000 open-source Iconify icons. Uses the unocss format for icon names, for example, i-mdi-home.

• Pinegrow îles Module – enables you to live-design your Vue single-file components visually in Vue Designer.
• Pinegrow Tailwind CSS Plugin – via Design Panel, enables visual controls customization (automatic) and theme customization (optional).
• @islands/pages – enables file-based routing, hooks to extend frontmatter and route data, supports a block in Vue single-file components for meta-data. This module is shipped inside îles.
• 📲 unplugin-vue-components – On-demand components auto importing for Vue.
• 📲 unplugin-auto-import – Auto import APIs on-demand for Vite, Webpack and Rollup.
• VueUse – collection of essential Vue composition utilities.
• 🍍 Pinia stores for global state management. Its light-weight, type-safe, extensible, modular with vue-devtools support.
• VeeValidate takes care of value tracking, validation, errors, submissions and more.

• îles Devtools – Page information is available in the in-app debug panel (similar to Vitepress). Also access the “Islands” inspector in Vue devtools.
• Vite Devtools – A Vite plugin for Vue that enhances your DX (developer experience) with an amazing set of in-app features. This is an in-app alternative to browser-based/standalone Vue Devtools.
• Vue Devtools – Official devtools that can be used as a standalone app alongside Vue Designer. It’s conditionally configured in app.ts (only during development).
  • ACTION REQUIRED: Currently deactivated. In app.ts, uncomment the top devtools related snippet to activate.

• [VS Code Extensions](./.vscode/extensions.json & ./.vscode/settings.json)
  • Volar – Vue 3 <script setup> IDE support
  • ESLint
  • Prettier

• Use Composition API with <script setup> SFC syntax
• ESLint with @nuxt/eslint-config – opinionated not-so-strict set of linting rules. Nuxt & îles share a similar directory structure, so are their linting rules.
• Prettier with eslint-config-prettier – format without conflicting with eslint rules.

This project allows JS, and strict mode is turned off. Update tsconfig.ts as required.

{
  "compilerOptions": {
    // ...
    "strict": false,
    "allowJs": true
  }
}

• Vue Designer Community

This project uses the Retail Sales dataset to analyze sales performance, identify trends, and understand product demand across different regions and time periods. The goal is to uncover key insights related to sales volume, revenue, and product performance.

• Source: Retail Sales dataset (can be obtained from sources like Kaggle or company data). (https://www.kaggle.com/datasets/pavitpreetsingh/relience-sales-data)

1. Power BI: Install Power BI Desktop from Power BI Downloads.
2. Dataset: Download the Retail Sales dataset from a reliable source (e.g., Kaggle).
3. Import Dataset: Import the dataset into Power BI.
4. Data Analysis: Use Power BI to create reports and dashboards, analyzing sales by product, region, and customer behavior.

• Cost Comparison Across Categories:
  The total cost for fruits is lower compared to categories like office supplies and household, which have significantly higher costs.

• Profit Distribution Across Regions:
  Both Sub-Saharan Africa and Europe contribute to more than 50% of the total profit, while North America has the lowest profit contribution among all regions.

• Total Profit and Total Revenue:
  In this case, Total Profit and Total Revenue are the same, indicating that there are no expenses or costs subtracted from the total revenue, which is uncommon in a typical business scenario.

• Total Profit by Item Category:
  The highest total profit comes from Cosmetic and Household items, while Meat has the lowest total profit among all item categories.

• Cost Optimization:
  Focus on reducing costs in the office supplies and household categories to improve overall profit margins. Consider negotiating supplier prices or exploring cheaper alternatives without compromising quality.

• Profit Maximization in Europe and Sub-Saharan Africa:
  Since Sub-Saharan Africa and Europe contribute heavily to the total profit, consider expanding efforts in these regions to further capitalize on their profitable performance. Increase marketing and sales campaigns to boost revenues.

• Review and Adjust Expenses:
  Investigate why Total Profit and Total Revenue are the same, as it might indicate an error or an unusual business structure where no operating costs are considered. Ensure accurate tracking of expenses to maintain profitability.

• Focus on High-Profit Items:
  Given that Cosmetic and Household items generate the highest profit, focus on expanding the product offerings in these categories. Consider bundling these items together or running promotions to increase their sales.

⚠️ The VMware KB API changed which introduced a breaking change for this project. This is tracked in issue #9
⚠️ At the moment, release data is not updated

This Python code parses VMware product release data from the kb
article Correlating build numbers and versions of VMware products (1014508)
and transforms them into a machine-readable format.
A combination of parsing with beautiful soup and data handling
with Pandas is the used to achieve the goal. A process is scheduled with GitHub actions to
run daily, the results will be pushed to the
repo Machine-readable VMware release data
.

Since v0.1.0 the raw data from the published KB is transformed to establish a standard in terms of column headers,
formatting, etc. KB 2143832 (ESXi) is used as the model for providing a standardized information set.

Columns describing the same data set have different labels, e.g. “Build number”, “Build Number”, “BuildNumber”.
In case of the example, the columns will be renamed to “Build Number” per KB 2143832.

Columns may have more than one value, e.g. “Build Number – Version” in KB2143850 (vRealize Automation).
In this case, two additional columns (Version, Build Number) will be added to the table each containing just a single
Value.

Roadmap: There may be more than one table that hold the version information, e.g. in KB2143838 (vCenter Server). A merge
operation will attempt to provide a unified table.

Since v0.2.0: For vCenter build information (KB2143838), this release based on PR #5 offers merged tables:
The KB article contains three tables:

• Release information for VCSA 7
• Release information for VCSA/Windows VC 6.7
• Release information for VCSA/Windows before that

The merged output available is now:

• one table for all VCSA releases
• one table for all Windows releases
• one table for all releases Unicode issues are addressed as well

Since v0.4.0 the script can handle KB52075 (vxrail). This table has none of the default column names and also multi-line
column headers.

The way the output is currently structured is:

• Directory: based on Pandas options to
  handle json data orientation
  • Files: KB(a)_(b)_table(c)release_as(d)”
    • a: knowledge base article id – the unique ID for the KB article
    • b: product name – The first product from the meta data, all in lower case and spaces replaced by underscores
    • c: An id to identify multiple html tables on the section (starting at 0)
    • d: json data orientation – see above

This is not an official VMware repository and in no way linked in official capacity to my employment at VMware.

An Innovative way of minting Cardano Native Assets

This project introduces a new way of selling a CNFT.

Currently, the most widely used model of minting NFTs is where the Buyer sends a payment to the Seller who then proceeds to mint the said NFT and then returns it.
This means that there are at least two transactions that occur in such an exchange. This method is very inefficient.

Cardano’s EUTXO model means that multple exchanges, mints and script executions can occur inside one transaction. This project just leverages those capabilities and proves a way of minting a token without revealing the script’s private keys to the end user. This means that the buyer makes the payment and the seller mints and returns the NFT in the same transaction.

The benifits of this new model are:
✔ Maximum Efficiency
✔ Minimum Costs
✔ Less Congestion
✔ Absolute Transparency

git clone https://github.com/rumourscape/Minting-API
cd Minting-API
npm install

Create the env.json file according to the example-env.json template.

npm run start

To run Newspeak, launch with python newspeak.py with argument –run program.txt. This will launch the file program.txt in interactive mode.

python newspeak.py --run program.txt

Newspeak was created with python 3.11.8, the further from this version the less likely it will run.

Newspeak operates on lists of commands, with some commands accepting an argument. Here is an example of a command list:

{FIND|deceased|REPLACE|born}

Most programs in Newspeak consist of several lists of commands:

{FIND|Jhonson|INSERT|comrade }
{FIND|Stevenson|INSERT|traitor }

Lists of commands can contain other lists:

{FIND|@|REPLACE|{FIND|#|REPLACE|@}}

On execution, the above command will replace the mark “@” with the following command:

{FIND|#|REPLACE|@}

When executing a file, Newspeak will search for the first valid command list it encounters. After finding one, it executes every command one after another. If any of them fail, the command list is deleted from the file. If every command in a list executes successfully, Newspeak resets itself to start executing from the beginning.

This ensures that if a command is able to be executed, it is executed on every part of the file. However, it is a job of an editor at MINITRUE to keep programs from going into infinite loops.

Because lists and text they edit coexist in the same space, Newspeak can be said to be self-modifying.

Full list of commands for the interactive Newspeak interpreter:

• simply pressing Enter without entering any command will advance 1 turn of processing the current program and output the report on processing. The vast majority of progams need several steps to complete!
• help will output this message.
• stop, exit, quit, e, q are all aliases of each other. They stop the current interpeter session.
• snap will output the current state of the field being processed.
• output [file name with extension] will output the current state of the board to a file at the passed argument.
• process will enter the intepreter into a processing mode. In this mode, processing turns will advance without the input from the editor. To stop it, enter s (as in stop) and press Enter.

Full list of Newspeak language keywords:

• FIND|arg: finds the argument in text, starting from the end of current selection. If finds, sets selection cursors to the edges of the argument. If doesn’t find, fails the current command list.
• REMOVE|arg: finds the argument between the current selection cursors. If finds, deletes this text from the field. If doesn’t find, fails the current command list.
• DELETE: Has no argument. Simply deletes everything between current selection cursors. Always succeeds.
• REPLACE|arg: replaces everything between current selection cursors with the argument. Always succeeds. Can accept SELF.
• INSERT|arg: inserts the argument at the start of current selection. Always succeeds. Can accept SELF.
• APPEND|arg: inserts the argument at the end of current selection. Always succeeds. Can accept SELF.
• ONCE: does nothing. Accepts no arguments. Always fails. Useful for making commands one-time-use-only.
• SEEK|arg: moves the starting and ending cursors to coincide according to arg. Arg can take one of the following forms:
• • SOL: start of line, relative to the start of current selection.
  • EOL: end of line, relative to the end of current selection.
  • SOF: start of file.
  • EOF: end of file.
  • n: can be any integer.
  • • If positive, moves the end of selection by n characters right and the start of selection to coincide with it.
    • If negative, moves the start of selection by n characters left and the end of selection to coincide with it.
    • If 0, does nothing.
• Finally, arguments to REPLACE, INSERT and APPEND can be SELF. In this case, the text that is inserted with these commands is the current command’s very text.

Additional features of the language include:

• Comments can be included in the program with <angle brackets>. They need to be paired and can’t be nested for now. Comments are removed from the file before running it.
• Commands can include newlines and tabs for better readability. These characters are removed from commands before running the file. Pro tip: switch your code editor to use tabs for indentation. Turn on line wrap, while you’re at it.
• Command arguments can contain escaped characters \{, \}, and \|.
• • When FIND, REMOVE, INSERT, APPEND, and REPLACE have an escaped special character, they turn it into the unescaped version for searching in text or inserting into text. If you want to find an escaped character or to insert an escaped character, escape it in the argument twice: \\|.