Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-tables-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/dumblittleman/public_html/wp-includes/functions.php on line 6121

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 248

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 258

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 278

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 269

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 304

Deprecated: Return type of IfwPsn_Vendor_Zend_Config::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Vendor/Zend/Config.php on line 292

Deprecated: Return type of IfwPsn_Wp_ORM_Idiorm::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 1836

Deprecated: Return type of IfwPsn_Wp_ORM_Idiorm::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 1840

Deprecated: Return type of IfwPsn_Wp_ORM_Idiorm::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 1844

Deprecated: Return type of IfwPsn_Wp_ORM_Idiorm::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 1851

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2028

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2037

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2046

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2055

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2064

Deprecated: Return type of IfwPsn_Wp_ORM_IdiormResultSet::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 2072

Deprecated: IfwPsn_Wp_ORM_IdiormResultSet implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /home/dumblittleman/public_html/wp-content/plugins/post-status-notifier/lib/IfwPsn/Wp/ORM/Idiorm.php on line 1985

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the remove_dashboard_access domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/dumblittleman/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-table-builder domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/dumblittleman/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/dumblittleman/public_html/wp-includes/functions.php on line 6121

Deprecated: Optional parameter $rowId declared before required parameter $tableId is implicitly treated as a required parameter in /home/dumblittleman/public_html/wp-content/plugins/ninja-tables-pro/src/TableEditor.php on line 345
Writer's Guide • Dumb Little Man

Writer’s Guide

Welcome to our Writer’s Guide

We value and appreciate the contributions made by all our writers, and we are committed to recognizing their efforts and giving them the recognition they deserve. As a writing contributor, you will be recognized as an established author with credibility in your field.

We understand that our contributors are professionals and experts in their respective fields, and we believe that they should have the opportunity to showcase their skills and expertise to a wider audience. That is why we allow our contributors to include a short bio and links to their social media profiles in their author byline.

We believe that this is a great way for our contributors to build their personal brand, establish their authority in their field, and connect with like-minded individuals. So, if you're a writer looking to make a name for yourself, consider becoming a contributor to our platform.

Join our community of writers, and let us help you achieve your goals. We look forward to working with you!

Please take note of the following in order to pass the draft evaluation and have your piece published.

Guide for Content

1. Please submit a 100% unique article. 

To help you create a perfect unique article, try using Copyscape.com for a plagiarism check. You can also run it through multiple plagiarism sites if you want.

2. Minimum Word Count Requirement is 900-2000 words.

Limit each sentence to 20 words only to have a better readability rate and pass the YOAST evaluation. As a result of the word count evaluation, our Content Manager discards any material that is not directly relevant to the article such as “Author's name” and “info for author's bio”, Meta Description, and title. You need to email us at info@dumblittleman.com for your author's bio once your piece is published.

3. Use the ENGLISH language when writing.

We discourage pieces from using other languages except for “movie titles”, “names” and other words that originated in other countries and have no equivalent word in English.

4. We automatically reject AI Written pieces.

Make a manually written and unique piece. Never use AI writing tools, Google can detect which pieces are written using AI and will not be given a chance to rank on Google or worst be removed on Google and on our site.

5. Make a catchy title that tells everything about your content

Don't make your title too long. Have a unique and catchy yet concise title that will sum up your ideas. Example “Your Resume Is Probably Too Long: Here Are 3 Ways to Cut it Down”

6. Use Proper Subheadings on your Content.

Make sure to have subheadings to organize your ideas and improve your content's readability rate. Have concise and not too long subheadings that will summarize the paragraph or idea. Make your subheading relevant to your topic and title. Also, add good transitions before starting your first subheading. 

7. Proofread your piece before submitting it.

Run your written piece to Grammarly and other grammar checker tools. Eliminate misspelled words and use correct punctuations. 

Things we DO NOT ALLOW

1. Content promoting a product/business/site. 

Using the privilege to be our guess contributor to promote a product/your site/business/links and etc. is highly discouraged. Doing so will lead to your entry's disqualification.

2. Adding links to your content

The submitted piece must have NO LINKS (homepage links, links going to E-commerce sites, blog links, and links going to other blog sites. 

3. Do not add Embedded Images or Infographics

We have our own policy and system for adding photos. Our Content manager will be the one to add images with high resolution and photo credits on the site where the photo she chose was taken.

4. DO NOT write topics which fall to the following

  • sex
  • escort service
  • violence
  • gambling
  • CBD
  • vaping
  • guns and other weapons
  • topics that suggest any types of discrimination (racism, sexism, classism, ageism, homophobia, etc), prejudice, and stereotyping.

5. Do not submit an already published piece

All submissions will go through evaluations and once we found out that your submitted piece is already been published somewhere else, we will automatically reject it.

Tips for You

1. Keep the introduction short

There is no need for a lengthy introduction before getting into the core of your piece. Avoid being vague in order to increase the number of words in your sentence.

It is sufficient to have a brief introduction that consists of one to three short paragraphs.

2. Write a valuable piece you are interested with

Our goal is to provide our audience with information that is both engaging and useful. Before you send in your article, you may find it helpful to ask yourself the following questions:

  • Is the information included in this article useful?
  • Who will benefit from it?
  • How would it be beneficial to other people?

3. Keep your writing simple

Reading simple writing saves time. Complex writing makes readers uncomfortable, so they lose interest. Plain language is faster and easier to grasp.

For more questions and clarifications just email us at info@dumblittleman.com

I agree to DLM'S Writer's Guide and Policy

By clicking below you adhere to our policy and is ready to submit an entry as a guest contributor