New: Initial files

Author: Joel-James

.gitignore

@@ -0,0 +1,34 @@
+.DS_Store
+node_modules
+/build
+vendor
+
+
+# local env files
+.env.local
+.env.*.local
+
+# Log files
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+# Editor directories and files
+.idea
+.vscode
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?
+
+# Build files
+*.zip
+
+# Unwanted config files
+composer.lock
+
+# Docs
+.vitepress/dist
+.vitepress/cache

.vitepress/config.mjs

@@ -0,0 +1,91 @@
+import { defineConfig } from 'vitepress'
+
+const year = new Date().getFullYear()
+
+export default defineConfig({
+	title: "Duck Dev Docs",
+	description: "Official documentation for Duck Dev",
+	lastUpdated: true,
+	cleanUrls: true,
+	head: [
+		[
+			'link',
+			{
+				rel: 'icon',
+				href: '/icon.png',
+			},
+		]
+	],
+	themeConfig: {
+		logo: '/icon.png',
+		nav: [
+			{ text: 'Home', link: '/' },
+			{ text: 'Support', link: 'https://duckdev.com/contact/' },
+		],
+
+		sidebar: [
+			{
+				text: 'General',
+				items: [
+					{ text: 'Getting Help', link: '/general/getting-help' },
+					{ text: 'Installing a plugin', link: '/general/installing-plugin' },
+					{ text: 'Updating a plugin', link: '/general/updating-plugin' }
+				]
+			},
+			{
+				text: 'Loggedin',
+				items: [
+					{ text: 'General Settings', link: '/loggedin/general-settings' },
+					{ text: 'Manage Sessions', link: '/loggedin/manage-sessions' },
+					{ text: 'Installing an Add-on', link: '/loggedin/installing-add-on' },
+					{ text: 'Managing Licenses', link: '/loggedin/managing-licenses' },
+					{ text: 'Developer Docs', link: '/loggedin/developer-docs' },
+					{
+						text: 'Addons',
+						base: '/loggedin/addons',
+						items: [
+							{ text: 'Realtime Logout', link: '/realtime-logout' },
+							{ text: 'Limit Per User', link: '/limit-per-user' },
+						]
+					}
+				]
+			},
+			{
+				text: '404 to 301',
+				items: [
+					{ text: 'Settings', link: '/404-to-301/settings' },
+					{ text: 'Translation', link: '/404-to-301/translating' },
+				]
+			},
+			{
+				text: 'Lazy Load for Comments',
+				items: [
+					{ text: 'Settings', link: '/lazy-load-for-comments/settings' },
+				]
+			},
+			{
+				text: 'About Duck Dev',
+				link: '/about',
+			},
+		],
+
+		socialLinks: [
+			{ icon: 'github', link: 'https://github.com/duckdev' },
+			{ icon: 'twitter', link: 'https://x.com/duckdev' },
+			{ icon: 'facebook', link: 'https://facebook.com/duckdev' },
+		],
+
+		editLink: {
+			pattern: 'https://github.com/duckdev/docs/edit/docs/docs/:path',
+			text: 'Edit this page on GitHub',
+		},
+
+		search: {
+			provider: 'local',
+		},
+
+		footer: {
+			copyright: `Copyright © ${year}, <a href="/about/">Duck Dev LLP</a>.`,
+		},
+	}
+})

404-to-301/settings.md

@@ -0,0 +1,9 @@
+---
+title: Settings
+---
+
+# Settings
+
+::: info Note
+Not yet published. If you can help, [please let us know](https://duckdev.com/contact/).
+:::

404-to-301/translating.md

@@ -0,0 +1,28 @@
+---
+title: Translating 404 to 301
+---
+
+# 🌐 Help Translate 404 to 301
+
+Want to help translate the 404 to 301 plugin into your language? You can do so directly from the [GlotPress project page](https://translate.wordpress.org/projects/wp-plugins/404-to-301)!
+
+## How to Start Translating
+
+Follow these steps and you can start contributing to the 404 to 301 translation at any time:
+
+* Log in to the GlotPress translation platform using your WordPress.org account.
+* Go to the official 404 to 301 translation [project page here](https://translate.wordpress.org/projects/wp-plugins/404-to-301).
+* You will see a list of available languages. Select your language from the list.
+* All translatable strings for your language will be displayed. Add or modify string translations by selecting "Details."
+* Save your translation suggestions and wait for the translation editors in your locale to approve them. You can see your [local translation team here](https://make.wordpress.org/polyglots/teams/).
+
+## Need a New Language?
+
+If you don't see your language listed, you can request support for it by following [this guide](https://make.wordpress.org/polyglots/handbook/translating/requesting-a-new-locale/).
+
+## Useful Links
+
+* [WordPress translation handbook](https://make.wordpress.org/polyglots/handbook/).
+* [Translation teams for each language](https://make.wordpress.org/polyglots/teams/).
+
+Thank you for helping the WordPress community use 404 to 301 in their own language—it makes a huge difference!

about.md

@@ -0,0 +1,13 @@
+---
+publish: false
+---
+
+# About Duck Dev
+
+<img src="/duckdev.jpg" align="right" width="230" height="230" alt="Duck Dev" style="margin: 0 0 1em 1em; border-radius: 10px;">
+
+Loggedin is developed and maintained by [Duck Dev, LLP](https://duckdev.com/), a small, two-person team driven by a love for open source.
+
+[Joel James](https://github.com/Joel-James), the lead developer, specializes in WordPress and is a strong advocate for open source, actively maintaining [several free WordPress plugins](https://profiles.wordpress.org/joelcj91/#content-plugins).
+
+When not coding, he dedicates his spare time to stock market trading.

api-examples.md

@@ -0,0 +1,49 @@
+---
+outline: deep
+---
+
+# Runtime API Examples
+
+This page demonstrates usage of some of the runtime APIs provided by VitePress.
+
+The main `useData()` API can be used to access site, theme, and page data for the current page. It works in both `.md` and `.vue` files:
+
+```md
+<script setup>
+import { useData } from 'vitepress'
+
+const { theme, page, frontmatter } = useData()
+</script>
+
+## Results
+
+### Theme Data
+<pre>{{ theme }}</pre>
+
+### Page Data
+<pre>{{ page }}</pre>
+
+### Page Frontmatter
+<pre>{{ frontmatter }}</pre>
+```
+
+<script setup>
+import { useData } from 'vitepress'
+
+const { site, theme, page, frontmatter } = useData()
+</script>
+
+## Results
+
+### Theme Data
+<pre>{{ theme }}</pre>
+
+### Page Data
+<pre>{{ page }}</pre>
+
+### Page Frontmatter
+<pre>{{ frontmatter }}</pre>
+
+## More
+
+Check out the documentation for the [full list of runtime APIs](https://vitepress.dev/reference/runtime-api#usedata).

general/getting-help.md

@@ -0,0 +1,25 @@
+---
+outline: deep
+title: Get Help with Our Plugins
+---
+
+# 🛠️ Get Help with Our Plugins
+
+Despite our best efforts to make our plugins as easy to use as possible, you might still run into trouble. Don't hesitate to ask us for support. We don't just want to help you fix things; we also want to learn from how you use our plugin.
+
+::: tip Note
+If you need help with one of our free WordPress plugins, please open a support request on the WordPress.org plugin forum.
+:::
+
+## How to Ask for Help
+
+We kindly request that you keep these things in mind when asking us for help. It will allow us to assist you much faster and more accurately!
+
+* **Provide a link to your website**. If possible, share the link to the specific page where the issue is occurring.
+* **Describe the errors you are seeing**. These details tell us a lot about what we need to do to fix things. A screenshot of the error is also very helpful!
+* **Tell us which version of WordPress you are using (if a WordPress product)**. You can find this info in the "At a glance" section of your website’s admin Dashboard.
+* **Tell us which version of the product you are using**. Please consider updating to the latest version, as it usually contains fixes for problems we have found in the past.
+
+## A Note on Support Priority
+
+We will try our best to answer everyone in a timely manner, whether you are a paid user or not. Paid users do, however, have a right to priority support. If you are in need of this type of immediate assistance, please consider buying a paid version of the product.

general/index.md

@@ -0,0 +1,5 @@
+---
+publish: false
+---
+
+# General

general/installing-plugin.md

@@ -0,0 +1,33 @@
+---
+outline: deep
+---
+
+# Installing a plugin
+
+There are several ways to install a WordPress plugin.
+
+## Installing from the WordPress dashboard
+
+Follow these steps to install any WordPress plugin from your dashboard. Make sure you are logged in and have the correct permissions to manage plugins.
+
+* Go to Plugins and then click on **Add New**.
+* Search for the plugin name (**Loggedin** for example), then click **Install Now** and then **Activate**.
+
+Alternatively, you can [download the plugin from WordPress.org](https://wordpress.org/plugins/) and follow these steps:
+
+* Go to Plugins and click on **Add New**.
+* Click **Upload Plugin** and select the downloaded zip file.
+* Click **Install Now** and then **Activate**.
+
+## Installing a plugin via FTP
+
+Follow these steps to install a plugin via FTP.
+
+To install it via FTP, you will need direct access to your web host's file server. Make sure you have a file transfer program (for example, [Filezilla](https://filezilla-project.org/)) and the necessary permissions from your hosting provider.
+
+* On your local machine unzip the plugin zip file which you have downloaded already. 
+* Login to your site using FTP or SFTP.
+* Upload the extracted folder to the `/wp-content/plugins/` directory on your site.
+* Go to the WordPress Plugins dashboard and Activate the plugin.
+
+If the installation did not work or you see an error after pressing Install Now you may need to try again or [contact the support](https://duckdev.com/contact/)

general/updating-plugin.md

@@ -0,0 +1,41 @@
+---
+outline: deep
+---
+
+# Updating a plugin
+
+You will receive a notification on your WordPress admin when an update is available for any of your plugins, be it free or Premium. You can then update to the latest version directly from your WordPress admin panel.
+
+::: tip Important
+A valid license is required for premium plugins/add-ons to receive updates.
+:::
+
+If for some reason you cannot perform automatic updates through your WordPress Admin panel, you can manually update the plugin to the latest stable version.
+
+Before you start, download the latest version of the free plugin from WordPress.org or the premium plugin/add-on from [your user dashboard](https://customers.freemius.com/store/21/).
+
+## Updating from the WordPress dashboard
+
+Updating via the WordPress Admin panel is a straightforward process.
+
+* Navigate to **WP Admin > Plugins > Add New > Upload**.
+* Browse to the location of the plugin ZIP file on your computer and press “Upload”.
+* Select “Replace current with uploaded” on the confirmation page.
+
+[![Manual Update](/general/manual-update.png)](/general/manual-update.png)
+
+## Updating a plugin via FTP
+
+Follow these steps to install a plugin via FTP.
+
+To install it via FTP, you will need direct access to your web host's file server. Make sure you have a file transfer program (for example, [Filezilla](https://filezilla-project.org/)) and the necessary permissions from your hosting provider.
+
+* Unzip the downloaded ZIP file somewhere on your computer.
+* Connect to your web server over FTP and navigate to `/wp-content/plugins/your-plugin-name/`.
+* Replace all the files in this directory with the files from the downloaded ZIP file.
+
+Following either of these two update methods ensures you will not lose your plugin's configuration settings. These methods are applicable to all plugins.
+
+::: info Note
+`your-plugin-name` is a sample name. Don't forget to use your plugin's actual name instead.
+:::